Difference between revisions of "New setting structure"
From Armagetron
m (add blueprint link) |
(→Goals: + anticheat) |
||
| Line 8: | Line 8: | ||
* Ghost settings (allowing a setting to be set BEFORE it gets declared) | * Ghost settings (allowing a setting to be set BEFORE it gets declared) | ||
* nSettingItem backward compatibility | * nSettingItem backward compatibility | ||
| + | * Attempt making cheating harder (but break compatibility :<) | ||
==General concept overview== | ==General concept overview== | ||
TODO | TODO | ||
Revision as of 08:02, 23 September 2008
This wiki page has an associated Blueprint on launchpad.
Currently, settings are put together in a "flat" manner, ie. related settings are sometimes not grouped together, which causes confusion and eats children. If that was not enough, admin commands are mixed in, too, and it's soon going to be a real mess when scripting/modules/other becomes usable. This is why I think commands should be put away from settings (and that's why I wont be talking about admin commands here) and that settings should be organized in a better way.
Goals
- Structured settings tree (Give the rim(flat!) a break! Hug a tree instead!)
- Put a line between admin command and setting
- Ghost settings (allowing a setting to be set BEFORE it gets declared)
- nSettingItem backward compatibility
- Attempt making cheating harder (but break compatibility :<)
General concept overview
TODO
