EQEMU 0.4.4 OFFICIAL Bug Report !

[Bigpull]

Originally Posted by lucan

Combat:

Combat was working closer to EQ live in 4.4dr1, now it seems mobs are hitting 3 to 4 time harder than they should. I tested this at level 11 with a ranger in ivy armour. It would be imposible to play a new char with the combat damage like it is in 4.4. I have been able to level up a char on a 4.4dr1 exe with no problems , it was about right on difficulty.

Just saying stuff hits to hard isn't much help, do you have damage set on the mob in the database, if not what level and class is the mob, how much does it hit for

Accounts:

All accounts seem to flag as GM, even when logging in with a non GM log on. If I turn it off and zone it turns back on again.

Show an effected account, odds are it has a gm status set, or your pc is possessed and you should flee the building.

Zones:

Some zones don't seem to be available, Rivervale for eg.

Database issue, doors zone points and stationary objects are the major culprits. bad doors or objects will generaly close the zone server with an error.

Agro:

What agro? There is no agro in 4.4, could be the GM status.....even if GM off you get no agro though.

This has been covered a billion times, the gm flag is irrelevent to agro, it checks your status not the gm flag, and no it's not gonna be changed, make a status 0 account for "client" testing, unlike live a gm should never be agroed by a mob not even the awakened sleeper. we've all seen shots of that poor gm running for his life i imagine....
[qoute]
Spells:

HP buffs don't drop properly sometimes.
EG; You zone on full life with a Heroism, First mob hits you and your HP drop to you base HP but buff is still there.
After you HP drop you can not heal above your base HP.
[/quote]

Buff syncinzation sucks, Feel free to dig into the code and propose fixes. One issue i know of for sure is if a buff timer expires while your zoneing, the server can't send the "buff removal" nor will the client send the "buff removal".
The second half of that problem is caused by the first, the client thinks it has a buff while the server doesn't..