Quote:
Multiplier == 0 in Client::CalcBaseHP
Unknown type/pettype of: 174,236
Multiplier == 0 in Client::CalcBaseHP
Unknown type/pettype of: 174,17
Multiplier == 0 in Client::CalcBaseHP
Unknown type/pettype of: 174,8
|
This is a code issue, from what I understand. Yesterday I saw LE helping someone with this problem, and the fix seemed to come from (trying to remember) somewhere in the code where you see Getplayer () and you need to change it to Getplayer ()-1 to stop the above error from crashing your client, if in fact it does so. (don't ask LE to clarify.. wait for the next release).
I've noticed this myself, typically when an npc is assigned to an incomplete grid... it begins to run its course, but doesn't find the next closest waypoint and just runs off into the 'great abyss' yet the target circle remains. This is really just a db issue, and with enough patience (let me reitterate the word - PATIENCE) you'll get it fixed.
This, from what have been able to figure out is a problem with the npc's/mob's Z coordinate. If it's told to spawn above ground, it drops to the ground upon spawning and sometimes causes an undesirable animation. Fix this by locating that spawn in the db, recording its supposid Z coordinate then finding the spawn ingame and doing a #loc when get exactly where that spawn should be. Then go back to the db and set that new value. Teadious? I know.
Quote:
Bug:Ghost NPCs (blackburrow)
|
Hehehe. Stay out of blackburrow until the npcmovdb team can fix this (I'm currently working on this one). Dungeon-style zones are extremely difficult to get working correctly. Don't you remember how bad the trains were in BB on eqlive? On eqemu, BB is just evil
Quote:
Explanation: Just a small bug: The #flymode command seems to toggle between OFF, OFF and OFF
|
Whenever a #command in eqemu doesn't seem to toggle, it usually means there are command options. In this case, the proper use of the #flymode command is #flymode 1/0 (1 for ON, 0 for OFF)
Not exactly sure about this one, but if I had to make a money-based-guess, I'd say this was fixable in your DB.
Hope I helped you a bit, and thank you for posting your bugs... many people don't understand this is the only way requested features will be fixed imho.