If you go and create a new world all Blueprints will be set to "others" and "enemy usable" + they will lose their owner.
Created permission test in world0
The DEFAULT_BLUEPRINT_ENEMY_USE = false from the server.cfg has no effect on this.
Putting this on high since it can break worlds if all titan blueprints are auto spawnable
<replace this line with the file content>
<replace this line with the file content>
The game doesn't know who owns a blueprint. It would make no sense to put it into the blueprint itself, as then i couldnt be spawned when downloaded and would be easily changable anyway. To use the same catalog in another world, copy over the catalog.cat file. Setting them to enemy usable might be a bug though. What is the server setting for that?
The default is:
DEFAULT_BLUEPRINT_ENEMY_USE = true //Default option to use uploaded ships in waves
However, setting this to false does still set all blueprints to "enemy usable" on first load of the world.
It appears that only the first blueprint (aka the cheapest, since they are sorted by price) is set to enemy usable when "DEFAULT_BLUEPRINT_ENEMY_USE" is false. @schema might be aware of why this was implemented but I'm not sure.
got to retest that then,
in all former server-resets we had them all checked on first loading of the world.
This MAY be related to the fact you have to start the server once, to generate a config, it actually starts on default settings then.
Possibly this confused the result.
Ok! Tested again
How to reproduce
1 -empty the blueprint folder then put in a couple of none default blueprints
2 -start the game and use reset all world to make a new universe
3 -open the catalog in game and check the settings on the inserted blueprints
will look like
4 -Default blueprints wont be listed anylonger after reset
5 -after explanation that the settings for this is stored with the universe files (makes sense) i would have assumed that:
sorry .. slight correction here
the enemy usable is gone when the server setting is put to false ...
but still "other" and the lack of any default blueprints is a bug
Well, as they all loose their owner, it would leave you without access to blueprints when they have "other" revoked.
This is "good" for single-player and new players not knowing about admin status and how to use it,
but for "servers" this is bad, as you have to manually remove the "other" flag from several hundred blueprints before any player should be able to connect to avoid blueprint stealing.
Can we possibly get a:
Default permission set for all blueprints that "pop in" for the server? (new world, or manually moving blueprints in the folder) in the config?
It could also be "binary" like,
1 = Faction
2 = Homebase
4 = Other
8 = Enemy usable
Example:
3 would then state: Faction + Homebase checked
This would allow a later reuse when other options come up or options get renamed.
create world now has the option to copy over teh catalog of another world. Also, the server config has now settings to define a default handling for entries that arent in the catalog
DEFAULT_BLUEPRINT_ENEMY_USE = false Default option for blueprints not in catalog yet
DEFAULT_BLUEPRINT_FACTION_BUY = false Default option for blueprints not in catalog yet
DEFAULT_BLUEPRINT_OTHERS_BUY = false Default option for blueprints not in catalog yet
DEFAULT_BLUEPRINT_HOME_BASE_BUY = true Default option for blueprints not in catalog yet
These appear to work, not entirely sure about this copy over to another world feature, or how it would influence the settings above. Will have to check that out later, or someone else can do that instead.
the settings in server.cfg are taken in any case
(which is good so you at least can prevent them from all beeing assigned to pirates and everyone)
Thank you for this information. We had an issue on LVD where we had to do a new install, but the server had been run without the blueprints present once. Then when ran with the blueprints copied over, none of the blueprints had owners anymore. Copying the catalog.cat file from the backup world fixed the problem.