EZ Server

Source code was updated today.

Seems there might be some changes to the way pets work. Let me know if anything is out of order, such as the pet names or being able to control them. There were new fields created in the pet table.

Other changes can be seen on the changelog.txt from eqemu.

Woot,,


Thanks again Hunter, can't wait to see what's on you grand plan as mentioned in your other post for just really starting!!

Golems are still evil pavement rollers that hit and roll ya!! Which is great and fun as hell.

There are some issues with pets after update. Quite a few epic pets are not working; they have no name (Soandso's pet) and don't attack. I can confirm Beast 3.0/4.0 and Mage 3.5 are not working, however, necro 3.0 is fine.

Mage pet 5.0 and Necro pet 5.0 not working as well.

Keep up the good work Hunter,

and thx alot! ;D

Ha 1/2 the server is down OHH NOOO No more nerco's!!!

Cannot log in at all, dont know if it is a code change server thing or on my end, I have tried everything for at least a hour says somthing about "the amount of server lag between you and the server might be extraordinariliy high"? Any ideas would be greatly apprecieated.

having serious trouble staying connected since update. May be something on my isp but it was fine until the update. The % that appears just left of my ping time will start rolling down to 0 and all toons dissappear until it hits zero then i get the disconnected message, boots me to charecter select on all toons.

also occurs when i only log in a single toon so it's not a box lag problem.

as if this post.. Mage 4.0 and Necro 4.0 working correctly on UF client. 

BST 4.0 will not attack or defend.  Will not respond to any command (including hail) and doesn't zone with the player.

I don't know if this is a problem brought on by the update but there seems to be bad lag in QVIC. Just a hunch but it feels like it's related to looting corpses.

I found the pets I missed to edit the the pets table. There was a 2nd page of records to look at :)

Should be fixed after next reboot.

That sounds like it might be a zone crash.  Have you had it happen in a zone with others to see if it's everyone or just you?

i was alone (6box) in gi's each time

What time will the next reboot be? Not complaining, I love this server, but my beast is pretty useless since none of his epic pets work right now. :(

Server reboots every day at 3 am PST and is down until about 3:30 AM PST. Usually up no later than 4 AM PST.

(http://i179.photobucket.com/albums/w281/Xiggie/forever-alone-meme.png)

it's my day off!!!!!!!!! i wanna play i was farming stuff for Thebone he said he would get me a 6.0 on all my toons if i famred 25 Dargon minors and 15 majors =[ now im sad. why di the server go down anyway i was afk

How long is it going to be locked for?

No.

Good Evening Hunter,

I just wanted to report that BST Epic 3.0 pet is still acting up despite the server reboot earlier this evening. Not sure if you've already figured it out and didn't need this input or not, but I figured it's best to say something then nothing at all in this case.

Keep up the great work! :)

Yep.. 4.0 BST still unresponsive as well.

Mage 5.0 pet seems to be working like normal on UF client.

Sorry I missed the Beastlord pets. They should be working now.

Thanks,

Hunter

Shadow Knight pets don't seem to work either

Mage 2.5 is still non functioning as of this morning. Thanks for working on this so much Hunter!

Ok, I found those 2 pets. Should be working after next reboot.

Thanks,

Hunter

Hi Hunter

I'm not sure when this started (or even if it's related to the source code update) - but it seems you can now kill waypoints again.  It's a little odd - it's mainly the permenant waypoints.  You can't kill the ones you make yourself.

Cheers
Strix

I meant to make the ones you summon to be killable, guess the static ones were a different NPC in the table. I'll take a look, thanks.

Also, just made recast delay of Summon Waypoint down to 5 minutes from 15 minutes.

Enjoy!

I just searched and the Pet waypoints and the static NPC waypoints are the same. The reason you can't kill your own pet is cause there is no pvp, but I'm sure a mob could kill your waypoint pet now.

I'm just having a great day here.... hehe.  I just had an officer remove Strix from the guild and we're now without a leader.  Seems the failsafes to stop that aren't working.

Any idea how I can get the Leader tag back?

If you cannot make the static waypoints invulnerable, would you consider making their respawn time nearly instant? Somewhere between 0 and 1 minute would be great. I haven't checked their current spawn time but it is long enough that I got tired of waiting around and just summoned a regular one.

what was the point of making it being able to be killed anyway?

Which Guild?

People were exploiting the Waypoint pet as an invincible tank.

Anyways, just don't kill them now. I'm sure people will learn.

The House of Strix   :D

I had seen that, was rather odd to see Strix as (main) and not (Leader)

All done.

Thanks again Hunter!

ok, my problem since the updates not zone crashing; just happened in pub HoH and my group was the only casualties. All toons disappeared and my connect % started rolling to zero and then whole group got disconnect message. it's not my internet connection, it's something that just started with the update.

trying a solution Thebone suggested ingame, hope it will work; if so i may finally trust my connection to try t5.

I'm not sure that it's the zone dying out, but since the updates all of my toons are experiencing intermittent LD using the UF client from Steam.  They seldom all go at once, but one or more go LD very frequently.  Call it... one or more every 3 - 4 fights.

This doesn't have the same look as the memory leak issue we used to have in T3/4 where all toons would suddenly go quiet and stop moving, but it is the same effect on a more limited basis.  This one seems to affect single clients rather than the entire zone.  Camping to char select fixes it... until the next time.

Yeah, its rather recent for me too -- as I refuse to use the "HoT client" the UF client from Steam has been the only reliable one and now im having terrible issues with it on EZ. It could be from this -- but not entirely sure, just through my 2cs around

The ranged attack in T6 seems to crash the zone a lot if 3 assbeater golems hit a ranged class all at once.. not sure why though. Guessing those crashes aren't healthy for the server stability. But when the golems are in melee range and blow up my mage it doesn't seem to crash.

Could be that mobs in the zone summon? I'll have to check it out later.

My first question would be why is your mage getting agro? Warrior's proc enough hate to keep this from happening? Now I don't play a Mage and I could be missing something but if warrior's can keep off monks wizzys and even pallys chain casting there Jolt there shouldn't be a issue..

Unless your pet pulling the zone??

If you wipe and have a mage at ranged.. they all go for that mage and he dies.. fast from ranged attacks which causes the crash... if I stand the mage in mellee range and dies to melee damage .. zone doesnt crash. Same thing happens to my cleric as well when I stand her back.

Edit.. Even the Ukuns on phase 1 MM will do the same if they get agro on my cleric at ranged.. since I do not use my mage for that fight. So mostly I just chill in melee range now which is silly.

I'm honestly still in shock how much you guys are crashing the zone. I can count on two fingers the amount of times we have crashed the zone with 30 in the zone..

Both crashes have been around the Decons near the commander and administrator.

No crash has ever been with OMM Phase 1 2 or 3

Not saying it isn't happening just like wow, how..

We haven't crashed in awhile but I know how to replicate the crash sequence.. thus I have avoided doing those things I mentioned. Last week I don't think we crashed a single time.

I guess the whole part about where I said HOW we were crashing went over your head... you think we would keep doing the same method if it gave the same results? I was merely pointing out a flaw in system.

Well gnomes are short...