FOSS gamedev and creative worlds

Hello
I think it would be a good Idea to split the World.mt File.
It should be splitted into two Files,
- a world.mt which holds Information for the Database Backend and the gameid.
- a mod.mt which holds the list of installed and active mods.
That would make the testing, migrating and synching of settings from the local Installation to the Server much easier.
Thanks,
JPR

Text is text. So what's the "very special" part about splitting a text file into 2 parts?

Krock wrote:Text is text. So what's the "very special" part about splitting a text file into 2 parts?

convincing the program to bother to read it ?

Hello
It is exactly as twoelk says.
Thanks,
JPR

Krock wrote:Text is text. So what's the "very special" part about splitting a text file into 2 parts?

That's right. We should also store all inventory data for all players in a big text file. Why not store authentication data in the same file too? And world metadata, and...

This will really help server administration!

This post is 100% not not sarcastic.

Hello
Are you Pro or Contra?
I made this request because I am not everytime using the same Database backend on my Test System (local Server) and my Server on another System. As it is I must always edit the world.mt after moving it to the Server, thats not very comfortable. If it were splitted I could move the mod configuration without thinking of the Database Backend.
Thats all.
Thanks,
JPR

I'm in favor of this change, since it separates editable from uneditable information.

World information is not meant to be edited once created (except under special circumstances). It is perfectly valid, on the other hand, to modify which mods are enabled.