I've updated overthere zone to not allow UW.

Checks when you zone in, and also checks during the time your in the zone based on certain events.

By looking over the code, I realized a possible bug for pvp (commons and overthere) that would add your IP to the list again each time you got booted, so you could be on the IP list multiple times. I've commented this out to fix it. Was more of a problem for level 60 pvp if player got booted for custom BD armor. This IP list seems to get refreshed each hour too so in case your bugged, just wait 1 hour and the IP list refreshes.

The bug was also a big problem if you tried to log in 2 characters into the zone, you'd get added to the IP list twice, but not removed, meaning you were permanently banned for 1 hour from entering the zone. Anyways, this is fixed.

I could write a script to not allow them to equip their UW, else they would get booted.

Possible after next reboot, pvp zones will have zone wide resist debuff on everyone by -10,000 value.

This will give casters ability to pvp, and ability for melee tanks to kill each other too.

Might update leaderboards for level 60 players only if they are in the level 60 pvp zone, since I know outside the zone they can wear and use BD armor which inflates their HP on leaderboards.

So with all spells landing in pvp, what will the new tactics be? Snare, root, fear, etc?

Going to turn off levitate in OT.

The gem guy in OT has 500k pp loot so hopefully its still reasonable bait to get people into the zone. Easy money!

I doubled that and immediate results of less lag has been reported. Although I also edited timers and other quest stuff, so I'm not sure which fixed it.

Spell file 01-17-14 now available.

A bunch of spell updates from Hateborne.

Edited max connects on mysql.

Edited Timers in global_player.pl

Rebooted Machine.

Keep me posted on any lag if the same, better, or worse.

For the MySQL experts out there...

I checked out the my.ini file for mysql.

How high should this be set to:
max_connections=

Probably would require reboot whole machine if I edit this.

If Hateborne wants to add Epic Aug slot to Whip that is fine by me, depends on what he is doing with Epic Augs currently as I gave the project to him to manage.

I've actually had almost ALL scripts turned off in T5-T9 lately except for the AA per hour and the T8 npc cast spells timer. I didn't want to tell anyone that I turned off the scripts in case people decide it would be a good time to afk bot the zones. I reserve the right to flip the switch to turn on certain scripts again if I get a feeling people are botting again. I don't check every zone, ie I don't think Nexus needs to be monitored for AA per hour.

I realize the lag started around the same time I started the scripts, but those scripts are off right now. So moving forward...

The ONLY script running really is the AA per hour, which checks your AA every 15 min, 60 min, and when you zone. It does this by comparing 2 values in memory. It doesn't log to the database unless you meet X amount of AA per hour when it does a check.

T8 has special script for npc to cast spells on a timer as some are aware. These npcs (as of a week ago) will no longer even start to cast AoE until you engage them. Only npc that are in combat will have timer running to cast spells.

Not sure why T5/T6 are lagging.

Hateborne and myself tested this. Logged in a full group, and killed a small train. Mean while I observed (and recorded) the debug logs, and viewed the RAM being used for the zone(s). Everything was normal, and both of us never got any additional lag or ping added. Nothing was lagging, no debug errors, nothing.

I'm starting to think that the few of you that have problems, is a problem client side. Maybe custom spell, spell particles, combat filter, MQ2 plugin, client type, global model file, etc.

We did this testing just before midnight eastern, so the server has been booted up for a while, and we still got no lag.

Will continue to search for the cause of the lag that a few people are getting. So far we're running out of ideas.

Will see if there is any other EVENT_TIMER stuff going on, and if we need to stoptimer settimer each time to prevent the same timer from being redundantly created. So that is what next reboot will test, if timers fixed anything.

Very good idea.

I was also thinking about required number of votes to be a percentage of the players online, maybe 5 votes per 100 players online?

Voting no to counter the yes vote also great idea.

Players love to vote!

T6 was fine for  me with 6 toons the other day on  prime time. I logged in 12 for this mornings run with 100 ppl on and it was awful.

Is the anti-train code checking each character for an aggro count? That might be causing some issues.

Anti train code checks 1 variable value every 60 seconds. This does NOT cause lag.

If Nate or Hate abuse this without reason, then they will be revoked from using it.

Everything is logged.

Because I don't feel like giving anybody the power to permanently suspend or ban accounts.

Besides, this is an entertaining way to get rid of trolls.

Why you so worried? You going to troll?

So far Nate and Hate will have the power, but if I add more people then I probably won't announce their name unless they want to be publicly known.

I really do my best not to reboot server other than regular 6am EST scheduled reboot, but today I had several versions of the Vote Kick code in different zones and needed them to all be synced up. Server will be back up within a few minutes.

I've updated the Vote Kick code to disconnect and suspend ALL accounts linked to a Character's name by IP address. This way a multiboxer can't continue to troll ooc or whatever.

The suspensions will last for currently 3600 seconds (1 hour).

A trusted person can now start a vote to kick a player.

The person starting the vote will not have their name appear in the announcement, but their reason will be displayed when the vote starts.

After a mod or guide has started a vote, then other players can vote to kick the person by typing:

/say vote kick <name>

Currently requires 5 votes and to reach that goal within 15 minutes to work.

This system allows only one vote from the same toon or IP, per 15 minutes, per person getting voted for.

Once a player is vote kicked, they will be immediately disconnected, a suspended for a total of 30 minutes.

This will allow the mods to get rid of troublesome players when I'm not around, and of course can be entertaining to vote for someone as well.

This system should be about 99% finished right now. I might later add feature to disconnect and suspend ALL characters linked to the one being voted so we wouldn't have to have redundant votes on all the alt boxes of a player.

Right now this only works if you do this from a new instance since the global_player.pl was uploaded after servers reboot today. After next reboot this feature will work from all zones.

Waypoint List

/say Waypoint List
/say Instance List

Shows a list of instances that belong too, or been invited too, with saylink to click to enter them.

Added the list as a menu option on:
/Say Waypoint

The Time Left format is:
00:00:00:00
Days : Hours : Minutes : Seconds

Each item in the list will say if your the owner, guild member, or invited (pending / joined).

(Can be used now in new instances, or wait for reboot time)