I'm working on my input system. I'm including some graphics for the configuration program, which are only going to be useful for my system, and not useful for any builds. Right now, I will have to suggest the user to delete anything that is not part of the run-time system when they make builds so that the assets don't get included. Note that part is this comes from me using a room for configuration of my input system(waiting on that extendable plugin IDE stuff). It also is the reason behind my suggestion for a constant for the project directory(at the least for IDE test builds). This leads me to a couple ideas.
1. Couldn't an asset package include a configuration as well as texture/audio groups(plus associated options)? The fonts and other graphics could then be assigned to the proper groups before I create the package, and then the user of the package could simply import it and switch configurations to use the configuration stuff, while at other times those graphics are already not going to be included in the builds.
2. Expanding on the above suggestion, couldn't almost all assets work similar to texture groups, where they don't get included based on the configuration? It may not be worth it for scripts so much, but for something like rooms it might be, especially for smaller games.
3. Could we maybe have the starting room be part of the configuration as well? This would allow me to set the starting room for my input system's "configuration" configuration be the right room so the user doesn't have to change it each time they want to access the configuration build.
Please sign in to leave a comment.