config.properties in /resources is ignored

[nightm4re94]

^{This post has been migrated automatically from the old LITIENGINE forum (2018 - 2022).
Posted: 2019-03-11 14:50:56
User: pma8444 [] (age: 1335 days 🔥; posts: 16)}
Greetings
My src folder is structured as follows:
/src /main /java /resources
I'd like to have the config.properties, the info-xml and the game.litidata as well as some other stuff in the resources folder instead of the project-root.
For the info-xml and the .litidata it works, however not for the config.properties.
I believe the problem lies in Configuration.java .loadFromFile()-method:
final File settingsFile = new File(this.getFileName()); try (InputStream settingsStream = FileUtilities.getGameResource(this.getFileName())) { if (!settingsFile.exists() && settingsStream == null || !settingsFile.isFile()) {
With my setup, settingsFile will never exist and a config.properties with default values is created, even though FileUtilites finds my "custom" .properties file within the resources folder.
Would it be possible for you to change this? A simple approach could be to just look for the file and to not create it if not found, simply setting up a default-Properties object.

[nightm4re94]

^{This post has been migrated automatically from the old LITIENGINE forum (2018 - 2022).
Posted: 2019-03-11 17:53:16
User: CalvinMT [] (age: 1451 days 🔥; posts: 114)}
pma8444
Did you try creating a new object with Configuration?
Configuration c = new Configuration(fileName, configurationGroups);
I don't know what "configurationGroups" are yet, but you might be able to give it a try.

[nightm4re94]

^{This post has been migrated automatically from the old LITIENGINE forum (2018 - 2022).
Posted: 2019-03-11 19:23:49
User: steffen [Admin 👑, Mod 🔧] (age: 1568 days 🔥; posts: 100)}
pma8444 I'd say this behavior is by design. The ~~~~config.properties are ought to be located in the filesystem and not treated like resources because the configuration there should still be possible, even if the game is distributed as .exe or .jar.
If you just want to bundle a set of static configurations with your game, you might as well just set it directly in code.
So, I think the question here boils down to whether we want the default ~~~~config.properties always to be created or not. I guess if you don't want the user/player to change stuff there it might make sense to disable this serialization process.

[nightm4re94]

^{This post has been migrated automatically from the old LITIENGINE forum (2018 - 2022).
Posted: 2019-03-11 19:57:11
User: pma8444 [] (age: 1335 days 🔥; posts: 16)}
CalvinMT As I understand, ConfigurationGroups are just containers for properties belonging to the same aspect, grouped by a prefix (e.g. gfx_ prefixed Properties are stored in the GraphicConfiguration).
As the Game-class statically initializes the private static final GameConfiguration, you cannot simply replace it. You'd have to replace every configurationGroup within separately and Game.init() would still create a config.properties file on the file system.
steffen Ok, I see. I'd argue that not all properties are meant to be edited by a player and even if, you could still edit the file if it was within a .jar (unless some fancy signing and whatnot was involved) - but anyway, I can respect your design-decision. I just need to keep my project-folder clean :D
Both of you, thanks for the prompt answers.