Watermaps

[cavedude]

No, it's outdated a bit. Give it a few days, and the whole db will be updated on CVS, including all of the rules.

[cubber]

Thank you!

[Angelox]

Here's all my rules, you should be able to take and use what you want;

INSERT INTO rule_sets VALUES (0,"default");

INSERT INTO rule_values VALUES (0,"Character:AutosaveIntervalS","300");
INSERT INTO rule_values VALUES (0,"Character:CorpseDecayTimeMS","10800000");
INSERT INTO rule_values VALUES (0,"Character:DeathExpLossLevel","6");
INSERT INTO rule_values VALUES (0,"Character:EnduranceRegenMultiplier","100");
INSERT INTO rule_values VALUES (0,"Character:ExpMultiplier","1.0");
INSERT INTO rule_values VALUES (0,"Character:HPRegenMultiplier","100");
INSERT INTO rule_values VALUES (0,"Character:LeaveCorpses","true");
INSERT INTO rule_values VALUES (0,"Character:LeaveNakedCorpses","false");
INSERT INTO rule_values VALUES (0,"Character:ManaRegenMultiplier","100");
INSERT INTO rule_values VALUES (0,"Character:MaxLevel","65");
INSERT INTO rule_values VALUES (0,"Combat:BaseCritChance","0.0");
INSERT INTO rule_values VALUES (0,"Combat:BerserkBaseCritChance","0.06");
INSERT INTO rule_values VALUES (0,"Combat:NPCBashKickLevel","6");
INSERT INTO rule_values VALUES (0,"Combat:WarBerBaseCritChance","0.03");
INSERT INTO rule_values VALUES (0,"GM:MinStatusToZoneAnywhere","200");
INSERT INTO rule_values VALUES (0,"Guild:MaxMembers","2048");
INSERT INTO rule_values VALUES (0,"Pets:AttackCommandRange","150");
INSERT INTO rule_values VALUES (0,"Skills:MaxTrainTradeskills","21");
INSERT INTO rule_values VALUES (0,"Spells:BardSpellAggroMod","3");
INSERT INTO rule_values VALUES (0,"Spells:PetSpellAggroMod","10");
INSERT INTO rule_values VALUES (0,"Spells:SpellAggroModifier","100");
INSERT INTO rule_values VALUES (0,"World:ClientKeepaliveTimeoutMS","65000");
INSERT INTO rule_values VALUES (0,"World:ZoneAutobootTimeoutMS","60000");
INSERT INTO rule_values VALUES (0,"Zone:GraveyardTimeMS","1200000");
INSERT INTO rule_values VALUES (0,"Zone:EnableShadowrest","0");
INSERT INTO rule_values VALUES (0,"Map:FixPathingZWhenLoading","true");
INSERT INTO rule_values VALUES (0,"Map:FixPathingZAtWaypoints","true");
INSERT INTO rule_values VALUES (0,"Map:FixPathingZWhenMoving","true");
INSERT INTO rule_values VALUES (0,"Map:FixPathingZOnSendTo","true");
INSERT INTO rule_values VALUES (0,"Watermap:FishingLineLength","40");
INSERT INTO rule_values VALUES (0,"Watermap:CheckForWaterWhenFishing","30");
INSERT INTO rule_values VALUES (0,"Watermap:CheckForWaterOnSendTo","false");
INSERT INTO rule_values VALUES (0,"Watermap:CheckForWaterWhenMoving","false");
INSERT INTO rule_values VALUES (0,"Watermap:CheckForWaterAtWaypoints","false");
INSERT INTO rule_values VALUES (0,"Watermap:CheckWaypointsInWaterWhenLoading","true");

[Derision]

Originally Posted by Angelox

INSERT INTO rule_values VALUES (0,"Watermap:CheckForWaterWhenFishing","30");

That rule should be true or false, e.g.

INSERT INTO rule_values VALUES (0,"Watermap:CheckForWaterWhenFishing","true");

[cubber]

Thanks for that post Angelox! That should be helpful to a lot of people.

[cubber]

Cavedude,

I just updated to the latest PEQ CVS and noticed that my rules_values table is still identical to what it was before. When I update I just do drop_system.sql then load_system.sql, I noticed that when doing drop system I still have to comment out aa_swarmpets and merchantsets in order for it to complete without error. Then when I do a load_system.sql I have to comment out merchantsets because it still tries to load it even though it is not in cvs anymore.

Are these scripts going to get updated? Also how is rules_valuse supposed to get updated out of CVS if it is only included in the load_player script? If I have a db that I am updating I do not want to drop_player , load_player to get the new rules_values table cause I would loose all of my player data.

Can I just do a mysql -u root -p -v -D eqemu < rules_values.sql to get my whole DB up to date after I do a load_system.sql?

[cavedude]

No, those scripts will not be updated because those tables are no longer needed and people still have them. Data in this community has the way of sticking around, and confusing people years later, so this is my way of purging the system Just source with verbose mode off (drop the -v) and it'll skip right past them. *Releases will not have this issue, only tables contained in the release will be sourced/droped*

rule_values is a player script because it is a table commonly changed by the end user. Having it as a system table would piss people off with tweaked rulesets. Having a third category is not an option because I am too lazy to update PEQ's script, and quite frankly having two scripts confuses many people as is, adding a third would make matters worse.

Yes, any and all tables can be sourced in separately. rule_values, commands, variables, etc. I don't recommend doing this for system tables because obviously many tables are linked together, so sourcing in one without the other will create errors and/or features to not function.