Many mechanisms and config files are rather vague, such as, setting available ships for factions (AI or otherwise), each line in the server config file, how AI is supposed to work, all the original key settings, including the hidden ones (ie TAB+F keys?), oh and simply, many many more.
Some settings seem ingame, some in the server config file, some in other files.
A good explanation for everything would be great.
As a manager and former programmer it is good to set out "Description of Operations/wiki" as you finish each feature and provide a description for the intended use of everything (so we know if there is a bug).
Doing this at the end is a disaster, especially as this game seems it will stay as an Alpha for all eternity.
Many admin commands and server config lines are vague, along with poor explanation of how simple things work.
I realise part of the attraction is to find out for yourself, but you need good sources of information to find out. Many YouTube videos are awful or outdated with the odd gem shining through. Asking on the StarMade chat is nice but depends on who is online and whether they are playing some obscure role play with themselves.
Get people working on the wiki that can write and explain operations, configurations and ideally people that know what they are talking about. Many of the wikis are either non existant (red links) or far too simple.
Use good video from people that explain without needing you to watch them build, block by block, their latest 8 floor battle cruiser in pink armour.
Plus, start adding more explanations to everthing (help on mouse hover for instance).
Examples;
REMOVE_MODIFIED_BLUEPRINTS (which blueprints? in what folder? What do you class as modified?)
BATTLE_MODE (Love the name, what is it, where is it properly explained?)
ENABLE_SIMULATION (Does the game become real life if I make this false?)
CONCURRENT_SIMULATION (A multi-verse? What is a simulation group?)
Try to understand, you program it, we want to understand how to play it...
Some settings seem ingame, some in the server config file, some in other files.
A good explanation for everything would be great.
As a manager and former programmer it is good to set out "Description of Operations/wiki" as you finish each feature and provide a description for the intended use of everything (so we know if there is a bug).
Doing this at the end is a disaster, especially as this game seems it will stay as an Alpha for all eternity.
Many admin commands and server config lines are vague, along with poor explanation of how simple things work.
I realise part of the attraction is to find out for yourself, but you need good sources of information to find out. Many YouTube videos are awful or outdated with the odd gem shining through. Asking on the StarMade chat is nice but depends on who is online and whether they are playing some obscure role play with themselves.
Get people working on the wiki that can write and explain operations, configurations and ideally people that know what they are talking about. Many of the wikis are either non existant (red links) or far too simple.
Use good video from people that explain without needing you to watch them build, block by block, their latest 8 floor battle cruiser in pink armour.
Plus, start adding more explanations to everthing (help on mouse hover for instance).
Examples;
REMOVE_MODIFIED_BLUEPRINTS (which blueprints? in what folder? What do you class as modified?)
BATTLE_MODE (Love the name, what is it, where is it properly explained?)
ENABLE_SIMULATION (Does the game become real life if I make this false?)
CONCURRENT_SIMULATION (A multi-verse? What is a simulation group?)
Try to understand, you program it, we want to understand how to play it...