Miscellaneous: GAMEBREAKING BUGS THAT HAVE EXISTED SINCE BETA

[Lovely]

6. Ice Comet should not be in game. Harvest should not be in game.

Not TRUE IT HAS ALWAYS BEEN IN THE GAME. Stop posting bullshit - Staff of Wheel quest hasn't however always been in game, but the spell has.

Ima Go solo that noob Vox dragon if I have to, np boys. Eye of zoom in da hizzah

[Leftoverture]

Don't take away my bullshit spell! [You must be logged in to view images. Log in or Register.]

[Kringe]

SEPTEMBER 28, 1999

--------------------------------------------------------------------------------
The following changes have been implemented with the latest patch, most importantly, changes to corpse resurrection. It should be noted that all corpses generated previous to this patch may not be resurrected, however, all corpses generated from this point forward may be resurrected with the changes listed below applying.
Corpses that are older than 2 hours cannot be resurrected.
Corpses that are produced from a duel cannot be resurrected after 10 minutes.
General Enhancements:A Yes/
No request window is now brought up when ever turning in the PK note to the Priest of Discord.
It is now possible to manually reorganize icons within the spell book. This may be performed by right-clicking on the currently placed icon (the icon will then be highlighted), then right-clicking on the desired slot you wish to move it.
Pet damage inflicted during PvP combat has been slightly reduced.
It is now possible to place items marked as "No Drop" in the bank.
NPC corpses will only remain for 8 minutes, even while looting.
If a party member goes link-dead, the remaining members will be notified.
Pets with less than 20 hit points cannot receive hit point buffs.
When viewing an invisible PC with See Invisible, the name will be shown in parentheses over the character.
All beneficial speed spells may be canceled left-clicking on the spell icon.
We have also made revisions to the /text command section of the EverQuest manual.


Thats a huge start nilbog.... It doesnt give you specific numbers, but the TOP end focus'd mage pet hitting for 26s while Sword of runes is procing for 41s at 50 is laughable... Wouldnt even eat through diamond skin...

We have Spell damage at 80% and pet damage hits set to 50% but yet melee damage is 100%....


Ill dig more for classic screenshots but this should be a start.

[Lubian]

Originally Posted by nilbog [You must be logged in to view images. Log in or Register.]

For the devs who don't play, it's quite hard to narrow down what causes this. If someone can find a way to replicate the bug, we'll have a chance of fixing it.

This can be caused by a few things:

• The client tries to accurately predict mana regen for each tick. When you're mixing sitting up and standing the client will inaccurately think you got a sitting mediate tick, while server side the mana tick may have occurred while the player was standing. When you actually try to cast a spell the mana will be updated client side, and you'll see your mana seemingly decrease more than it should, or not have enough mana to cast the spell.
• The server and client mana regen formula or a mana regen value isn't properly synced between the client and server. I don't see a mana regen value in eq_packet_structs.h, is it possible that it's one of the unknowns? I don't know the eqemu source code that well though.

[Arillious]

Originally Posted by Arillious [You must be logged in to view images. Log in or Register.]

The first mana bug you described is the one that has plauged me since beta. About 20% of the time i med, my mana will actually stop increasing. I need to drink water to fix.

The second issue I have ran into only a few times, usually when im trying to get in a few meds while kiting. I can see this being much mroe of an issue for a shaman and canni.

For exp loss in pvp death, I'd say the goal would be to lose about 20-30 minutes of exp time(hard to quantify I know). It's enough to make it hurt, and prevent bind rushing but not enough to make a single pvp death make someone ragequit.

I have more information regarding the first mana bug, where while medding, you do not get mana back sometimes until you drink water.

While this was happening I actually got the "You are Thirsty" message even though I had an entire stack of water in my inventory. This means that the client really thinks that the person is out of water when this happens(which makes sense since drinking water fixes it.)

If you cannot identify the problem, I would suggest simply removing the need to have water to begin with until the problem can be identified. This bug outweighs any need to mandate that someone carry water on them. I dont think anyones going to miss it while you guys figure this one out.

[Mardur]

Something interesting about the mana bug:

My stamina bar stopped regenerating today until I ate some food. So not only does the game sometimes think you're out of water when you're not, sometimes it thinks you're out of food when you're not. These issues occur separately (my mana was regenerating but not my stamina).

If I had to guess when this was broken, it would be here: http://www.project1999.org/forums/sh...ad.php?t=48145

Kanras: Food/Drink duration now varies per item.

This was found to be non-classic and was repealed shortly after. I assume either when making food/drink duration vary per item, or when removing that functionality, something got dun goofd that sometimes makes the server think you're lacking food/drink when you're not.

[Truth]

Secrets commented in IRC about the mana bug. He said something about cancelling the client side update in like call__DoTimeUpdate() and just updating the value when server sends the verification packet. I could see that helping when you appear to have the mana and cast spell but it like "nope u oom", but perhaps not the other symptom when you are just sitting there medding at 0% for 45 seconds until it finally starts ticking up or whatever.

[Lubian]

Originally Posted by Truth [You must be logged in to view images. Log in or Register.]

Secrets commented in IRC about the mana bug. He said something about cancelling the client side update in like call__DoTimeUpdate() and just updating the value when server sends the verification packet. I could see that helping when you appear to have the mana and cast spell but it like "nope u oom", but perhaps not the other symptom when you are just sitting there medding at 0% for 45 seconds until it finally starts ticking up or whatever.

That's not fixing the underlying bug, but rather just sending the mana over and over again, because he doesn't understand what is causing the desync issue. Don't misunderstand me though; it could still be used as a (hopefully temporary) solution.