"Unable to find rule" errors
 

Hello all, I have just had a problem come up that i cant seem to get fixed. I had the server up for most of the day yesterday made a couple changes to some spells (or tried to anyways, changes would never take effect). Anyways i restarted the server a few times with no issues all of sudden on my last restart of the server. I started getting a bunch of "Unable to find rule" and "Unable to interpret rule record for" errors.

I am using the latest version of MySQL on Windows XP and using EQemu 0.7.0-942. Using this older version becuase it seems to be the best as far as when in basic attack mode I hit the mobs ALOT more then I do in the newer versions

That is because you are using such an old release of the Emu code. You miss out on new features by not updating. All of those rules were added since the 942 code you are using. You can update up to 1071 and still have the old combat system if you want. You won't get all of the most recent rules, but you will still get more than you currently have in your 942 build.

Ok well what got me was those never appeared for almost a full day then all of a sudden they started to appear yet the rules were in the DB. Or at least i never noticed them until then, but those lines were int he SQL database.

The reason I was using the older version was because it was around that version that the code got changed and now on the newer versions my character swings and misses alot. I have no problem with anything else on the newer version just hat that out of a average of 30 swings i will hit maybe 12 times.

Well, the change that happened that made characters start missing a lot more and hitting for less damage happened after the 1071 code. So, any code up till then should be fine for you.

Also, rules don't load unless you enable them in your database. You have to set the ruleset_id field to 1 (by default) for the rules to load. By default all rules are set to ruleset_id 0 which means they are disabled and do not load.

Maybe you changed that setting and that is when the errors started. Otherwise, they were always there and you just didn't notice them. The main thing to know is that these errors don't really matter. They won't cause any problems. It is just reporting to you that it couldn't load the rule.

I don't think that's true. From what I understand, the ruleset_id can be whatever you want. The value in rule_sets can be changed so that in rule_values you can have multiple configurations and switch between them by changing 1 value.

I could be wrong, but mine are all 0 and they load and work fine.