EQEmulator Forums - Watermaps

EQEmulator Forums (https://www.eqemulator.org/forums/index.php)

- Support::Linux Servers (https://www.eqemulator.org/forums/forumdisplay.php?f=588)

- - Watermaps (https://www.eqemulator.org/forums/showthread.php?t=24142)

How do we enable these? I downloaded the .wtf files and extracted them into my maps folder. I noticed that all the rules are set to false, where do I change this so they are enabled on my server? Can it be done in the web interface? Or do I need to recompile my server with the values all set to true in ruletypes.h?

Just change the rule values to true in your db.

I am using the latest peq CVS and do not see those values in the rules_values table. Was there a mysql update I was supposed to run also?

Ok i think i see my issue. When I load the newest CVS peq I always just do a drop_system and a load_system, never drop_player load_player.

It looks like the rules_values and other variable tables are only dropped and loaded with the character tables. So I must be still be using some old tables that only get dropped and added with the player scripts.

So my question is how do I update all of these tables without loosing any of my character data?

You can find rules in the download logs at EqEmu. just read and apply whatever rules you see fit

Thanks for your reply,

I saw the rules in the logs, but do not see them anywhere in my DB. So I have no place to change the values. As I have stated I am running the latest peq CVS as of I believe 7 days ago. I figured these rule values should already be in that DB somewhere. Hopefully Cavedude will be able to shed some light on my db questions in my previous post.

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.

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

Code:

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");

Quote:

Originally Posted by Angelox (Post 141949)

Code:

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

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

Code:

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

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

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?

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.

Thanks for the reply, it is understandable that you want to cause as little confusion as possible.

So if I understand you correctly... If I just source in the new rules_values.sql to my updated database, I will be good to go with a fully updated database without any issues? If I made any changes to my old rules_values table I obviously will have to go back and make those changes again because they will get reset to default.

But sourcing in anything that is in the load_system.sql file by itself will cause problems...

I just want to be clear before I do this to my year old database.

One other question, I noticed that tables like variables and commands have been updated as well. Is it worth updating these to the newest revisions also or are the updates mostly comments and such? If so a list of tables that are considered "player scripts" that should be watched for changes and updated manually would be helpful.

Thanks again for your help!