settings.lua

[martian]

everytime i update my sever after modifying this file it shows up as potenial conflict... Don't know what rev. this changed at, but it didnt use to do this. And until I change it back to original version it will not allow me to update. Is there a way to make this a uncommitted so it's not listed as a potenial conflict some new users may not know how to fix it. I now keep 2 settings.lua files one as a copy for updating purposes...

[kjLotus]

tortoise svn: right click -> tortoise svn -> unversion and add to ignore list -> settings.lua

[PrBlahBlahtson]

But that may cause issues if you're missing any variables that have been added to settings.lua Nothing like player:giveGil(150*0) or *nil because GIL_RATE isn't declared anywhere

[lautan]

I think all configuration files should be named "settings.lua.default", "search.conf.default" in the repo. Then when you download it, you can just rename it and configure without worrying about conflicts.

[bluekirby0]

And add in one more thing that can go wrong in setting up the server.

[PrBlahBlahtson]

I use an RSS feed reader named TT-RSS that handles things that way, lautan. Users would screw it up.

They also have trouble figuring out the error message: "cache is not writable. (chmod -R 777 /cache/images)"

[xipies]

Here's a way to handle local settings w/ source control. Works ootb w/o user action, but allows for local changes that source control ignores. It would be nice for .conf files, too.

Source control:
settings.master.lua -- contains what settings.lua is currently
settings.localsample.lua (or settings.mysample.lua, etc.) -- optional, just gives an example usage

Ignored from source control:
settings.local.lua (or settings.my.lua, etc.) -- actual local settings
settings.lua -- merged runtime settings

On game-server start:
Merge settings.master.lua with settings.local.lua (if exists) -> settings.lua
Not sure if this could be in game-master.exe, or require a preloader that does it, then loads game-master.exe