Question to developers on latest builds?

[So_1337]

I'm almost certain that's what that rule means, as I now remember Cavedude saying that NPCs on PEQ will now stop and stand still for 10 seconds when hailed, etc. So it must be from that rule. It took you suggesting it for it to make sense, though.

As for the rest, I find it's far easier to put the rules in from in game. For that rule, for instance, it'd be "#rules setdb NPC:SayPauseTimeInSec 10" and you have to remember that case counts on the actual rule name. Then do the same for other rules. The only thing that I find difficult about setting the rules in game is that you don't get to see the defaults when you list the rules. Though it's hard to find them anywhere else, either. Of course, I haven't done much looking to be honest

Now of course, you can do the same in MySQL, you just have to set it all manually. Or you could run a query, I guess. To add the rule we've been talking about with its default value, it'd be:

INSERT INTO rule_values VALUES(0,'NPC:SayPauseTimeInSec','5')

That's two ways to do it. I'm sure someone else has a better way.

[cavedude]

Those rules are all currently on the PEQ CVS. Take a look at rule_values.sql. The only ones that are missing are the ones dealing with watermaps which I haven't gotten to updating yet.

[cavedude]

Edit timeout expired. I hate that thing. Anyway:

Yes, NPC:SayPauseTimeInSec controls how long a NPC with sub EVENT_SAY will pause when triggered. The original hardcoded value was 5, which I found to be too short. 10 seconds is a lot more like it, and is what is currently on TGC. Also note due to this patch, NPCs will only stop if they have a sub EVENT_SAY. No other event will cause a NPC to pause, including an item hand-in.

[So_1337]

Hrm. I guess it's only recently that we changed any rules away from PEQ's, because I hadn't noticed. I didn't realize it was included in the drop/load system series. That's twice today I've spread misinformation, damn.

[KLS]

Rules don't need to be set if you're not changing it from the default. The default will be taken from the code if it doesn't find the SQL entry. Which is why new rules don't post a required SQL... because it's just not required.

#rules setdb Category:Rule is generally how I set my rules.

[So_1337]

That's it, then, okay. I think the main reason I was confused on them never being in the rules_values table until I set them was for the reason you just said; I hadn't had to change them from the defaults before. Thanks for clearing that up