Thoughts on LiCe 5.2.0 - Feedback Please!

Submitted by tjh on Sun, 07/18/2010 - 01:46

Submitted by Anonymous (not verified) on Mon, 07/19/2010 - 12:16


Hm... Good question indeed.

While I'm usually a fan plain-text config files, in this particular case I think the advantage of not having to /SAVE configs is a better deal.

Submitted by mrmeval (not verified) on Tue, 07/20/2010 - 11:12


I'm not a fan of binary config files only because it's difficult to tell if such files are corrupt. When the size of the file exceeds easy human parsing then it does not matter. An example is Firefox's prefs.js file which can be corrupt yet Firefox blithely reads it in then will glitch or crash etc.

If your effort adds some sort of corruption detection, maybe a checksum per entry then it should be ok. If it's easier to maintain for the coder and is more robust it's probably better.


I am deep in some coding changes to LiCe that use permanent variable storage. What this means to the end user is no longer will you need to /SAVE. Currently I have it so that any changes to /SENS, /TOG /MTOG /DTOG /WTOG and /CTOG are saved to the new system, which is automatic.

The flipside to this is that no longer can you just edit your save file, because we're now using the dbmctl system provided by epic5.

So I'm curious. Do people think this is a good idea or a bad idea? Do people like the ability to /SAVE and edit their config files, or would you prefer to have it all done in the background with needing to remember to save?

The version I am working on at the moment doesn't currently save your friend/shit list to the new format, nor does it save SET's. I wouldn't release until everything was covered by the new system though.

It's such a big change that it's impossible to release a version that "does both". If people think it's a good idea I'll go ahead with it, if everyone hates it well I'll put it in the "interesting project" pile but go back to the current LiCe 5.1.1 way of doing things.

Please post your thoughts and comments below!