PEQ Weekly
 

Hopefully this is a reasonable place to post this.

For a long time i've been using the peq weekly dump to keep my database updated/current. I generally bring the server down once a month for an hour or two for maintenance, at which time updating the DB is one of those tasks.

Last month I noticed that the weekly dump hadn't been updated, but was still newer than my previous, so updated it. That was the 2017-02-22-02:02 dump.

I'm running a little behind on my maintenance window for this month, and went to check on the new PEQ dump and noticed it was still Feb. 22.

Does anybody know if the weekly dumps are still being done or have been moved to a new location (old location was edit.peqtgc.com/weekly/)?

Thanks a bunch!

Updates seem to go to this file now:
http://edit.peqtgc.com/weekly/peq_beta.zip
But it appears this is also the link used in the eqemu_server.pl script for updating database.

If it's not updating, it's a bug.

The PEQ server was moved sometime last month.

The Weekly build no longer generates as it is redundant with:

http://edit.peqtgc.com/weekly/peq_beta.zip

That zip is a nightly dump of the database and will always be up to date

A lot of this documentation will be refreshed within the next few months

I always use the update script which works good, but I think the OP was referring to the old file link peqbeta_2017-02-22-02:01.tar.gz which feb 22 was the last
one showing for that link.
EDIT: Sorry Akka, was typing as you were posting :P

I've edited the weekly build page to also use the nightly build so there is no confusion for anyone.

http://edit.peqtgc.com/weekly/

Excellent! I appreciate everyones response. I knew the emu update script was updated, but for some reason thought it was only updating entries required by code changes.

Thanks for the updated link, as well as information. This saves me a step in my updates/backup process.

Just noticed in that particular peqbeta.zip updated db, it has what I think is a typo in the rule_values table.Map:FixPathingZWhenMoving has a ruleset_id of 20 ?
Some users might want to edit their command_settings table for default status entries in some of them as well.

It is not a typo

Better rulevalues:
https://www.dropbox.com/sh/8c9bmh8zh...000's?dl=0

Why did you just dump your entire database and tell everyone it's "better" rule values?

I apologize, I didn't think to look for an added ruleset (of 20), since there was only one entry with that.

We are temporarily using it for zones that have a big struggle with pathing through terrain, we have some changes that are en route to be a more elegant fix for this solution.

20 is a temporary ruleset for these zones. Mainly, it uses that one rule and inherits everything from ruleset 1 that isn't in 20.

Rule Inheritence:

• Use the assigned rulset rule value
• If not in assigned ruleset, use the default ruleset (in this case its 1)
• If not in default ruleset of 1, use the default values in the source code

Oh ok, for what I'm working on, I'm sticking to one ruleset for all zones and making sure everything I need is in the rule_values

DBVersion in variables is NEQ1000 series ? It's not a vacuum cleaner.