-
Posts
1402 -
Joined
-
Last visited
-
Days Won
3 -
Donations
90.00 GBP
Content Type
Bug Tracker
Wiki
Release Notes
Forums
Downloads
Blogs
Events
Everything posted by Xenithar
-
Sorry to break the news, but I killed a voidwalker minion and the server instantly died. I had five ranks of deadly poison 2 on him, and that MAT have ticked before I hit him. [code] WORLD: Sending SMSG_ATTACKERSTATEUPDATE AttackerStateUpdate: (Player) 3 attacked 66 (TypeId: 3) for 0 dmg, absorbed 0, blocked 0, resisted 0. WORLD: Received opcode CMSG_SETSHEATHED for Player Marrek (Guid: 3) - value: 1 PeriodicTick: Player Marrek (Guid: 3) attacked Pet (Petnumber: 537 Guid: 66) for 26 dmg inflicted by 2819 DealDamageStart deal dmg:26 to health:26 DealDamage Player Marrek (Guid: 3) Killed Pet (Petnumber: 537 Guid: 66) PLAYER: RewardHonor DealDamageAttackStop creature 66 stopped attacking player 3 player 3 stopped attacking creature 66 SET JUST_DIED Aura 3 now is remove mode 4 Aura 79 now is remove mode 5 Aura 133 now is remove mode 5 Aura 132 now is remove mode 5 DealDamageEnd returned 26 damage Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb20f1b70 (LWP 3220)] 0x0eac300a in ?? () (gdb) backtrace #0 0x0eac300a in ?? () #1 0x0882df54 in SpellAuraHolder::Update (this=0xd955130, diff=100) at /home/---/zero/src/server/src/game/WorldHandlers/SpellAuras.cpp:5445 #2 0x086a0f95 in SpellAuraHolder::UpdateHolder (this=0xd955130, diff=100) at /home/---/zero/src/server/src/game/WorldHandlers/SpellAuras.h:154 #3 0x0868ba49 in Unit::_UpdateSpells (this=0xd8c8eb0, time=100) at /home/---/zero/src/server/src/game/Object/Unit.cpp:2979 #4 0x086828fa in Unit::Update (this=0xd8c8eb0, update_diff=100, p_time=100) at /home/---/zero/src/server/src/game/Object/Unit.cpp:329 #5 0x0871ba96 in Creature::Update (this=0xd8c8eb0, update_diff=100, diff=100) at /home/---/zero/src/server/src/game/Object/Creature.cpp:582 #6 0x086b6e0e in Pet::Update (this=0xd8c8eb0, update_diff=100, diff=100) at /home/---/zero/src/server/src/game/Object/Pet.cpp:600 #7 0x087dadee in WorldObject::UpdateHelper::Update (this=0xb20effc4, time_diff=100) at /home/---/zero/src/server/src/game/Object/Object.h:473 #8 0x087db558 in MaNGOS::ObjectUpdater::Visit (this=0xb20f11a0, m=...) at /home/---/zero/src/server/src/game/WorldHandlers/GridNotifiersImpl.h:54 #9 0x087e85f6 in VisitorHelper (v=..., c=...) at /home/---/zero/src/server/src/framework/GameSystem/TypeContainerVisitor.h:72 #10 0x087e826e in VisitorHelper > > (v=..., c=...) at /home/---/zero/src/server/src/framework/GameSystem/TypeContainerVisitor.h:85 #11 0x087e7c2c in VisitorHelper > > > (v=..., c=...) at /home/---/zero/src/server/src/framework/GameSystem/TypeContainerVisitor.h:86 #12 0x087e6edd in VisitorHelper > > > > (v=..., c=...) at /home/---/zero/src/server/src/framework/GameSystem/TypeContainerVisitor.h:98 #13 0x087e5cb0 in TypeContainerVisitor > > > > >::Visit (this=0xb20f1198, c=...) at /home/---/zero/src/server/src/framework/GameSystem/TypeContainerVisitor.h:127 #14 0x087e3f17 in Grid > > >, TypeList > > > >::Visit (this=0xda4e394, visitor=...) at /home/---/zero/src/server/src/framework/GameSystem/Grid.h:111 #15 0x087e1722 in NGrid > > >, TypeList > > > >::Visit > > > > (this=0xda4db88, x=@0xb20f00dc: 0, y=@0xb20f00d8: 9, visitor=...) at /home/---/zero/src/server/src/framework/GameSystem/NGrid.h:360 #16 0x087dd6ae in Map::Visit > > > > > (this=0xbb1e288, cell=..., visitor=...) at /home/---/zero/src/server/src/game/WorldHandlers/Map.h:449 #17 0x087d49e0 in Map::Update (this=0xbb1e288, t_diff=@0xb20f123c: 100) at /home/---/zero/src/server/src/game/WorldHandlers/Map.cpp:521 #18 0x088e3cd6 in MapManager::Update (this=0xb408e10, diff=48) at /home/---/zero/src/server/src/game/WorldHandlers/MapManager.cpp:184 #19 0x087f15fb in World::Update (this=0x8e51290, diff=48) at /home/---/zero/src/server/src/game/WorldHandlers/World.cpp:1498 #20 0x085b7fcf in WorldRunnable::run (this=0xbb5dcc8) at /home/---/zero/src/server/src/mangosd/WorldRunnable.cpp:66 #21 0x0898db5d in ACE_Based::Thread::ThreadTask (param=0xbb5dcc8) at /home/---/zero/src/server/src/shared/Threading.cpp:197 #22 0xb7f43171 in ACE_OS_Thread_Adapter::invoke() () from /usr/lib/libACE-6.0.3.so #23 0xb7f051cf in ace_thread_adapter () from /usr/lib/libACE-6.0.3.so #24 0xb77ccc39 in start_thread () from /lib/i386-linux-gnu/i686/cmov/libpthread.so.0 #25 0xb77399fe in clone () from /lib/i386-linux-gnu/i686/cmov/libc.so.6 [/code] This is a build from last Friday, if I am not mistaken. R20, of course.
-
I did not see any messages in my log about glancing, but even then it should not glance repeatedly. For that matter, were glancing blows in Vanilla? I honestly do not remember this type of behavior in Vanilla. I do not remember damage this low at high levels in ANY version, for that matter.
-
This sounds like pooling. On official, there were "pools" of each type of item in each area. Only so many could spawn at one time. When one was picked/mined, another instantly spawned elsewhere. This works well on populated servers. Not so much on solo servers.
-
Quest 702 sequence bugged...
Xenithar commented on Xenithar's bug in Archived Reports (Zero)(Resolved issues)
Emote 15 is sequence 15. There are loads of animations. This makes him do animation 15. There is a GM command to test these on yourself. I forget it though! -
2 times seal of rightousness rank 1
Xenithar commented on Goullio's bug in Archived Reports (Zero)(Resolved issues)
This is a bug when learning a new spell. When my rogue learns new ranks in sinister strike for example, he learns it twice. It shows two copies in his spellbook. However, once you log out of the game and then in again, one copy will be gone. -
every field boss instant, raid hp is very low
Xenithar commented on ascentu's bug in Archived Reports (Zero)(Resolved issues)
We should be posting stuff like that on the forum, or in a ticket. I can't use Skype since MS took it over and canned the 64bit Linux port. yes, we've had 64bit systems since 2003 but MS only writes 32bit code in 2014. Makes perfect sense. Anyhow, if you can get the SQL, I'll test it also. -
Quest 702 sequence bugged... This may be a script issue, not sure. When turning in 702, the Orc speaks instead of emoting. It says something like "%s feels the power rush through him..." instead of emoting it.
-
Group loot doesnt work correctly
Xenithar commented on trimken's bug in Archived Reports (Zero)(Resolved issues)
That is how group loot works. One member is chosen to loot the corpse. Any items of green or better (unless you changed it) are rolled on by everybody. The next time a mob dies, somebody else gets to. Think of it like this. You have three players. Player A, B, and C. You kill a mob, player A is allowed to loot. You kill a mob, player B is allowed to loot. You kill a mob, player C is allowed to loot. You kill a mob, player A is allowed to loot. This repeats over and over again. If there is a green, blue, purple, or orange item on the corpse the entire party rolls on it and the winner gets it. -
Horde quest 6622 broken...
Xenithar commented on Xenithar's bug in Archived Reports (Zero)(Resolved issues)
You should try it on a fully optimized Gentoo system. I replaced Debian Wheezy with Gentoo on my work laptop. I set the USE flags and such for my hardware. My GOD it is faster! I am going to be getting to my new Xeon server this month and I intend to put Gentoo on it also. -
Way too low... I noticed something after testing the quest 6622 fix this morning. My shaman is level 47 and according to the stats screen hits for 144-something. Against mobs my level (Noxious Lair, Tanaris) I normally hit around 120~170, and crit for over 230. However, randomly during combat I hit for some REALLY low numbers. I am talking 19, 21, 7, and so on. That makes no sense. I tested this on my 37 Orc warrior also. Same thing. Randomly he gets a REALLY weak hit. This seems to happen against all mobs, not one specific type or race. This should not happen. My mace hits for a bare minimum of 77, so ignore the 144 that my stat screen shows, even if I hit for 77 and accounted for armor there is no way a normal, non-elite mob should take that much out of a hit. Can anybody else reproduce this? I built the server last night from a fresh clone of the repo. I also did a fresh clone of the database repo, completely dropped my world database, re-added it, and updated it, so it is fresh also.
-
Horde quest 6622 broken...
Xenithar commented on Xenithar's bug in Archived Reports (Zero)(Resolved issues)
I forgot I was on Linux for a moment. Linux runs WoW perfectly. Had to grab the client and add my home IP address (hostname), but it worked. I still cannot see my servers in the realm list, but I manually edited the config and added it. Anyway, it appears to work. I will have my fiance and mother test also. That WILL be tonight or maybe even tomorrow. -
I am trying to remember if the murloc pet was account or character bound. I seem to recall having it on more than one character, but my memory may be incorrect. The only problem I see here could be the adding of all those codes to the DB. If I add a code and a player uses it, is the code removed from the DB?
-
Horde quest 6622 broken...
Xenithar commented on Xenithar's bug in Archived Reports (Zero)(Resolved issues)
I can try it tonight. I am not at the gaming rig right now. I will test though and get back to you. -
Group loot doesnt work correctly
Xenithar commented on trimken's bug in Archived Reports (Zero)(Resolved issues)
That is how it worked on official. If a friend and I are grouped and I killed a mob that had an item he wants, I could right-click the corpse and look, then close the loot window and he could then loot the corpse. It seems to be working in R20 on my end. -
That is actually kind of cool, Reaper. Would these be account-bound like on Blizzard or character-bound? The CE pets and things are account-bound and every character gets an email thanking them for the CE with the items as attachments when they first login.
-
Horde quest 6622 broken...
Xenithar commented on Xenithar's bug in Archived Reports (Zero)(Resolved issues)
The way it worked on official was that each worse case had less health, but I believe the rate of loss was the same. The critical soldiers just had little to begin with so you had less time in that essence, but it was not hard to do. I have redone this repeatedly now for testing and it IS possible to save them, but the problem then is that even after being saved, they take a few steps and die. After being saved the decay should stop. Oh, and to save them you have to start bandaging them as they fade in. If you do not start until they are solid, you cannot save them at this point. -
Well since we're on unofficial, maybe we should add flags t the account DB or something that define things like special edition. I bought the collector's edition of everything up to and including Cata, so when I log into the game with each character, I have to give myself those pets (Diablo, Onyxia Whelp, etc) each time. We could add a flag for CE to the account table. If it is 0, no CE. 1 would be CE, and upon first login the character gets the email with the pets and such. We could take it a step farther and do a flag-based entry of integer type. [list] [*]0 - Normal Game [*]1 - Collector's Edition [*]2 - Allowed to get Murky [*]4 - Allowed to get costume [*]8 - Allowed to get mount [/list] You could combine any of those and when the character walks up to the NPCs and chats he will either get the item when selecting it or get a message that he or she wasn't really at Blizzcon, or whatever. You could even extend this list for the extras that may come in future expansions. No code needed!
-
Horde quest 6622 broken...
Xenithar commented on Xenithar's bug in Archived Reports (Zero)(Resolved issues)
I just did this with my shaman. Epic fail. It kept wanting to give me those critical patients. I lost fast. I even had some stand up, thank me, run two or three steps, then die. After being healed the drain should stop, they should run outside and despawn. -
It isn't game-breaking however, so this should not be a top priority. It should get some love though, maybe in R21.
-
They should not do this... I have reported in the past about how certain buffs, such as Frostbrand or Flametongue cause the player to enter spell-casting animations. However, I may have just realized something that may not be known. While playing my undead rogue with T1 gear which will randomly restore energy as well as my troll hunter with T1 which randomly restores 200 mana, I noticed something. It isn't buffs alone. Any time ANY effect is applied on a player character, the character does the spell-casting animation. So I have an undead rogue in the heat of combat, his armor restores some energy, and he goes into a casting pose as though he is a mage. The same for my hunter. Same for my shaman when Windfury, Frostbrand, or Flametongue proc. When an armor or weapon buff proc the characters should NOT go into a casting pose.
-
NPC should not be here... In Orgrimmar on the pier in the lake next to the fishing trainer you have two Orcs which are there to redeem prizes for Blizzcon attendees. For one, they do not appear to work (yes, I have codes) and for another, the second guy I do not believe was added until Lich King. He offers the "Big Blizzard Bear" which is a lv20 mount. There were no lv20 mounts in Vanilla that I recall. I believe the Orc closest to the end of the pier was there in 1.12, and he was removed in BC or LK and replaced by the other, who offered the Murloc pet as well as both the BC award and the LK award. This guy should not be here in Zero.
-
Well, almost! The quest appears to work, except that the critically injured patients die WAY too quickly. In all the years I played WoW I never lost a single patient on official or on MaNGOS. I kept failing tonight due to two possibly related bugs. The first is that the critically injured patients die WAY too fast. Even if you start healing them before they have spawned completely in, they die at the exact moment you heal them. If you manage to get there a hair quicker they will stand up, turn, and die while thanking you. It is like even after they're healed, they keep losing life.
-
Another Scripting bug ?...
Xenithar commented on Xenithar's bug in Archived Reports (Zero)(Resolved issues)
Still happens. Command: server shutdown 10 [code] Aura 17 now is remove mode 5 [Thread 0xb20f1b70 (LWP 5809) exited] [Thread 0xb6e4db70 (LWP 5805) exited] [Thread 0xb765eb70 (LWP 5804) exited] Halting process... [Thread 0xb664cb70 (LWP 5806) exited] Program received signal SIGPIPE, Broken pipe. 0xb7fe1424 in __kernel_vsyscall () (gdb) backtrace #0 0xb7fe1424 in __kernel_vsyscall () #1 0xb77d42eb in write () from /lib/i386-linux-gnu/i686/cmov/libpthread.so.0 #2 0xb7b7cead in vio_write () from /usr/lib/i386-linux-gnu/libmysqlclient.so.18 #3 0xb7b6b00e in net_real_write () from /usr/lib/i386-linux-gnu/libmysqlclient.so.18 #4 0xb7b6b268 in net_flush () from /usr/lib/i386-linux-gnu/libmysqlclient.so.18 #5 0xb7b6b580 in net_write_command () from /usr/lib/i386-linux-gnu/libmysqlclient.so.18 #6 0xb7b68598 in cli_advanced_command () from /usr/lib/i386-linux-gnu/libmysqlclient.so.18 #7 0xb7b65381 in mysql_close () from /usr/lib/i386-linux-gnu/libmysqlclient.so.18 #8 0x08978d3b in MySQLConnection::~MySQLConnection (this=0xafded70, __in_chrg=) at /home/---/zero/src/server/src/shared/Database/DatabaseMysql.cpp:80 #9 0x08978d8d in MySQLConnection::~MySQLConnection (this=0xafded70, __in_chrg=) at /home/---/zero/src/server/src/shared/Database/DatabaseMysql.cpp:81 #10 0x0897379a in Database::StopServer (this=0x8df92e0) at /home/---/zero/src/server/src/shared/Database/Database.cpp:158 #11 0x08978c4f in DatabaseMysql::~DatabaseMysql (this=0x8df92e0, __in_chrg=) at /home/---/zero/src/server/src/shared/Database/DatabaseMysql.cpp:65 #12 0xb769122f in ?? () from /lib/i386-linux-gnu/i686/cmov/libc.so.6 #13 0xb769129f in exit () from /lib/i386-linux-gnu/i686/cmov/libc.so.6 #14 0xb7678e4e in __libc_start_main () from /lib/i386-linux-gnu/i686/cmov/libc.so.6 #15 0x085ac9d1 in _start () [/code] Command: server exit [code] mangos>server exit CLI command under processing... Exiting daemon... Command: server exit [Account: 0 from Console] mangos>[Thread 0xb18f0b70 (LWP 24678) exited] Network Thread Exitting Network Thread Exitting [Thread 0xb10efb70 (LWP 24679) exited] [Thread 0xb08eeb70 (LWP 24680) exited] [Thread 0xb20f1b70 (LWP 24677) exited] [Thread 0xb6e4db70 (LWP 24674) exited] [Thread 0xb765eb70 (LWP 24673) exited] Halting process... [Thread 0xb664cb70 (LWP 24675) exited] [Inferior 1 (process 24671) exited normally] [/code] This seems to be normal now. Using exit works, using shutdown fails. I would think that "server shutdown " would wait X seconds and then simply call whatever method exit calls. Apparently this is not the case. -
Pet skills not working 100% I have noticed something odd this past week in the few times I have managed to play a hunter. The pets do not appear to be using their skills when they are set to use them. This includes things like growl, claw, bit, and shell shield. The pet will be engaged in combat with a mob and the skills will not be used. If you click on the skill to force use of something like growl, you get the message "Your pet is in combat". Well, duh! That is why I want to use the skill. I do not remember this behavior from roughly two or three weeks back, but I may not have noticed.
-
Extractors are not able to compile
Xenithar commented on drarkanex's bug in Archived Reports (Zero)(Resolved issues)
I can do a build shortly. I will report back when complete.
Contact Us
You can also email us at [email protected]
Privacy Policy | Terms & Conditions
This website is in no way associated with or endorsed by Blizzard Entertainment®