Yeah, the ruleset_id column in both rule_sets and rule_values have to match. Meaning, if you have a default ruleset_id 0, then all of the rules need to have a ruleset_id of 0 you want associated with it. It isn't a bool value, it's an id. If you have a rule with ruleset_id 2, then any rules you want associated with that has to have a ruleset_id of 2. It isn't often used, but in this way you can define several rulesets which can be changed in-game. So you could have one rulset where your max level is 65, and another where it is 70. You can then swap them in-game without needing to reboot.
The big issue causing a lot of confusion is the ids in rule_set is set to auto-increment. I never realized this until I finished the installer, however it makes sense. So, that means when the data is loaded with the table schema, if will automatically gives the rules id 1, because MySQL won't give an entry an ID of 0. Now, if you source in the data without the table schema (so the table is already created) you can then give the rules an ID of 0. I corrected this in the installer, and will be updating PEQ's CVS to also account for this.
Last edited by cavedude; 03-12-2008 at 12:16 PM..
|
Threaded Mode
