Xenithar

Odd, I had replied one evening with my troubleshooting steps. I must have closed the browser prior to it going all the way through. I tried all kinds of settings for this variable, including 30, which means level one quests SHOULD show up all the way up to level 30 or 31. Nothing worked. I also did some debugging in GDB, but I do not have the data now. I believe the variable kept setting to some other value, but I did not figure out why. Also, I am closing this since a new thread on the same subject has been opened which is getting some attention. The new one is ticket 706.

Well I will close mine as duplicate since this one is getting attention. We will have it as a reference for what I did.

I have a tickets on this from a few weeks (months?) ago also. You may wish to merge them. I went into detail on the testing I did about this.

Build from yesterday, happened a few minutes ago. [code] DealDamageStart deal dmg:41 to health:41 DealDamage Player Ryuk (Guid: 6) Killed Pet (Petnumber: 635 Guid: 90) PLAYER: RewardHonor DealDamageAttackStop creature 90 stopped attacking player 6 creature 87 stopped attacking creature 90 SET JUST_DIED Aura 53 now is remove mode 4 Aura 99 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 41 damage Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb20f1b70 (LWP 10434)] 0x0d000213 in ?? () (gdb) #0 0x0d000213 in ?? () #1 0x0882df54 in SpellAuraHolder::Update (this=0xd75c008, diff=100) at /home/---/zero/src/server/src/game/WorldHandlers/SpellAuras.cpp:5445 #2 0x086a0f95 in SpellAuraHolder::UpdateHolder (this=0xd75c008, diff=100) at /home/---/zero/src/server/src/game/WorldHandlers/SpellAuras.h:154 #3 0x0868ba49 in Unit::_UpdateSpells (this=0xd661f40, time=100) at /home/---/zero/src/server/src/game/Object/Unit.cpp:2979 #4 0x086828fa in Unit::Update (this=0xd661f40, update_diff=100, p_time=100) at /home/---/zero/src/server/src/game/Object/Unit.cpp:329 #5 0x0871ba96 in Creature::Update (this=0xd661f40, update_diff=100, diff=100) at /home/---/zero/src/server/src/game/Object/Creature.cpp:582 #6 0x086b6e0e in Pet::Update (this=0xd661f40, 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=0xbb7a21c, visitor=...) at /home/---/zero/src/server/src/framework/GameSystem/Grid.h:111 #15 0x087e1722 in NGrid > > >, TypeList > > > >::Visit > > > > (this=0xbb72850, x=@0xb20f00dc: 8, y=@0xb20f00d8: 11, visitor=...) at /home/---/zero/src/server/src/framework/GameSystem/NGrid.h:360 #16 0x087dd6ae in Map::Visit > > > > > (this=0xbb02c38, cell=..., visitor=...) at /home/---/zero/src/server/src/game/WorldHandlers/Map.h:449 #17 0x087d49e0 in Map::Update (this=0xbb02c38, t_diff=@0xb20f123c: 100) at /home/---/zero/src/server/src/game/WorldHandlers/Map.cpp:521 #18 0x088e3cd6 in MapManager::Update (this=0xb40e8d8, diff=46) at /home/---/zero/src/server/src/game/WorldHandlers/MapManager.cpp:184 #19 0x087f15fb in World::Update (this=0x8e51290, diff=46) at /home/---/zero/src/server/src/game/WorldHandlers/World.cpp:1498 #20 0x085b7fcf in WorldRunnable::run (this=0xbb5ebc0) at /home/---/zero/src/server/src/mangosd/WorldRunnable.cpp:66 #21 0x0898db5d in ACE_Based::Thread::ThreadTask (param=0xbb5ebc0) 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]

Alright, I can do that. I was hoping there would be a way we could switch in-game for testing purposes, but I can live with testing one all week and then the other the next week. Thanks! Now, can you get me more than say 30min a day to actually test the fixes? :p

Are you sure Fade does not work? It appears to work here, but it could be chance. I will test the others.

Is there a way we can force one to override the other? In fact, maybe we should take this conversation to PM since it is not related to the quest Chucksta is working on. I would like to have Eluna override SD2 for a week, do my weekly build, then allow SD2 to be the library in use. This way I can get some time in using both. Perhaps a GM command which would switch libraries?

Well thanks! Now here comes something I did not think of. I do intend on using just SD2 in the long-run (when Zero is 100% perfect and we're on One or Two), but I use both so I can report any issues with either. Due to this, how will this quest be handled since it is handled in SD2 AND Eluna? Will SD2 or Eluna take lead? Will they both fire? What about the situation where say SD2 kicks off the quest but for some reason I turn it in and Eluna handles the turn-in?

I will try to reproduce this.

Wait, I thought you implemented this in Eluna? That looks like C++/SD2.

No worries. Warlocks need love in general and this can wait. I know R20 needs to be released and once I get caught up with Le Froid and look into SD2 and the DB stuff, I will be happy to lend a hand here.

Yeah the corpses sliding on the floor following you is hilarious. This appears to be an SD2 issue however. I have added it to my to-do list but it is down the line. The thing is, it works correctly the second time around so TECHNICALLY you could have a rogue aggro Mograine, vanish, and then the party could attack and have it work.

I can when I login again. I'll get my weapon skill levels and everything. I normally keep my skill levels maxed or close to it. I have the attitude, if it moves, it dies. My melee skills stay high due to that. Either way, I will get you specifics this weekend if not tonight.

Well the thing is, the second time around it is flawless. I may try to look at it, but right now the spell system is my focus.

No problem. Closing bug report.

Is the current AI in SD2 or core? If it is in SD2 it should be moved to the core since it is a core functionality. I will volunteer to do that once my Linux system is back up.

Then this isn't glancing. I am testing this on mobs my level. I will do more testing when I can actually play again.

This is odd. Here is what is going on right now. [list] [*]Warlock pets lose all mana, but they can keep casting spells. However, using "Dark Pact" returns no mana, since the pet is really out [*]Hunter pets eventually lose all focus, but keep right on using skills, so this isn't as bad for them [*]NPC voidwalker minions have rage instead of mana, and it is maxed out [/list]

I can confirm this. It REALLY makes the rogue hard to play at times.