Xenithar

Alright. I have no problem since it is right off of five CDs, but I would like to see if the upgrade fixes his problem first, which is why I left this open.

LOL! I have not looked at it. I always got that when low on focus/mana. It does have a good effect though. For things like prowl, you just click the heck out of it and learn it in seconds.

I am back at work but will help when I can.

Stack overflow is a Windows error. It sounds like a client crash. Now on Zero I have only ONE way to crash a client. Try the Hero for a day quest for the Christmas celebration. The client crashes as soon as you click on the quest. It reads NULL memory.

Let me get it uploaded tomorrow. I am in eastern time. Also, note that Max just updated Covenant to R20. 90% of the bugs you reported that we could not reproduce are due to them being fixed in R20. If you could have posted a screenshot of ".server info" I could have seen that. How about giving it a go tomorrow on Covenant and seeing if those bugs still exist first? Also, I am American so I would have the American client. I am not sure if it is the same as the EU client.

I have a bug report on pet focus/mana already. Voidwalkers have rage, lock pets never regen mana but keep using spells without it, and hunter pets never regen focus, but seem to use skills anyway. The "pet is in combat" is due to having no focus. It is the wrong message.

It is funny you figured that out. My fiance was taming him for the higher rank of bite. However, I tamed some Winterspring animals to get bite R7 and R8, no issues. In fact I have almost all pet spells now learned, minus the ones for birds.

Good point, if the mob is already there, all it has to do is trigger everything when the mast is used. I saw one of these "mob-triggers" today in LBRS. I was in the area wit the trolls testing some AI and I noticed a small infernal with the warlord. It had the name of a trigger, and turning off GM mode made it invisible.

Which would be more effective at testing your theory? Also, I have tamed several rare/elite pets since with no problems. Taming Barnabus crashes it though. For instance, I tamed Rak'shiri without a hitch.

Well I tamed Broken Tooth and so did she. I also have Lupos. I normally only tame rare/elite/unique pets. I actually tamed Barnabus a month or so back and later released him. This must be tied to an update somewhere.

She did it again. Went to Barnabus, started taming. Taming finishes and the small version (her pet) spawns but the big one does not despawn and the server crashes. Only appears to happen to Barnabus though. I tamed an elder shardtooth in Winterspring seconds before with no issues and did a ".save". I now have the bear. Barnabus has something going on causing the crash. I also tamed quite a few pets yesterday to learn higher-rank skills without issue.

This is rearing its head again. [code] Holder of spell 19591 now is in use Spell 20782 Effect0 : 6 Targets: Pet (Petnumber: 574 Guid: 16), -, - Spell: Aura is: 157 Aura: construct Spellid : 20782, Aura : 157 Target : 1 Damage : -46 Holder of spell 20782 now is in use Spell 20784 Effect0 : 6 Targets: Pet (Petnumber: 574 Guid: 16), -, - Spell: Aura is: 42 Aura: construct Spellid : 20784, Aura : 42 Target : 1 Damage : 0 Holder of spell 20784 now is in use Spell 24529 Effect0 : 119 Targets: Pet (Petnumber: 574 Guid: 16), -, - Aura: construct Spellid : 24529, Aura : 20 Target : 1 Damage : 2 Holder of spell 24529 now is in use creature 134445 stopped attacking player 14 Aura 23 now is remove mode 4 Pet (Petnumber: 574 Guid: 16) enters grid[18,26] Pet Spells Groups Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb20f1b70 (LWP 5251)] 0x08843241 in Aura::UpdateAura (this=0xd841018, diff=100) at /home/---/zero/src/server/src/game/WorldHandlers/SpellAuras.h:455 455 void UpdateAura(uint32 diff) { SetInUse(true); Update(diff); SetInUse(false); } (gdb) backtrace #0 0x08843241 in Aura::UpdateAura (this=0xd841018, diff=100) at /home/---/zero/src/server/src/game/WorldHandlers/SpellAuras.h:455 #1 0x088425e4 in SpellAuraHolder::Update (this=0xe8e1e20, diff=100) at /home/---/zero/src/server/src/game/WorldHandlers/SpellAuras.cpp:5448 #2 0x086b4199 in SpellAuraHolder::UpdateHolder (this=0xe8e1e20, diff=100) at /home/---/zero/src/server/src/game/WorldHandlers/SpellAuras.h:154 #3 0x0869ed17 in Unit::_UpdateSpells (this=0xd0ed5a0, time=100) at /home/---/zero/src/server/src/game/Object/Unit.cpp:2928 #4 0x08695e62 in Unit::Update (this=0xd0ed5a0, update_diff=100, p_time=100) at /home/---/zero/src/server/src/game/Object/Unit.cpp:325 #5 0x0872eb94 in Creature::Update (this=0xd0ed5a0, update_diff=100, diff=100) at /home/---/zero/src/server/src/game/Object/Creature.cpp:583 #6 0x087ee0e0 in WorldObject::UpdateHelper::Update (this=0xb20effc4, time_diff=100) at /home/---/zero/src/server/src/game/Object/Object.h:473 #7 0x087ee83a in MaNGOS::ObjectUpdater::Visit (this=0xb20f11a0, m=...) at /home/---/zero/src/server/src/game/WorldHandlers/GridNotifiersImpl.h:54 #8 0x087fb950 in VisitorHelper (v=..., c=...) at /home/---/zero/src/server/src/framework/GameSystem/TypeContainerVisitor.h:72 #9 0x087fb57f in VisitorHelper > > (v=..., c=...) at /home/---/zero/src/server/src/framework/GameSystem/TypeContainerVisitor.h:85 #10 0x087faf57 in VisitorHelper > > > (v=..., c=...) at /home/---/zero/src/server/src/framework/GameSystem/TypeContainerVisitor.h:86 #11 0x087fa215 in VisitorHelper > > > > ( v=..., c=...) at /home/---/zero/src/server/src/framework/GameSystem/TypeContainerVisitor.h:98 #12 0x087f8fee in TypeContainerVisitor > > > > >::Visit (this=0xb20f119c, c=...) at /home/---/zero/src/server/src/framework/GameSystem/TypeContainerVisitor.h:127 #13 0x087f722c in Grid > > >, TypeList > > > >::Visit (this=0xe6cfb7c, visitor=...) at /home/---/zero/src/server/src/framework/GameSystem/Grid.h:99 #14 0x087f4a16 in NGrid > > >, TypeList > > > >::Visit > > > > (this=0xe6c40f0, x=@0xb20f00dc: 13, y=@0xb20f00d8: 5, visitor=...) at /home/---/zero/src/server/src/framework/GameSystem/NGrid.h:360 #15 0x087f0896 in Map::Visit > > > > > (this=0xbb66020, cell=..., visitor=...) at /home/---/zero/src/server/src/game/WorldHandlers/Map.h:449 #16 0x087e7cde in Map::Update (this=0xbb66020, t_diff=@0xb20f123c: 100) at /home/---/zero/src/server/src/game/WorldHandlers/Map.cpp:522 #17 0x088f7f1e in MapManager::Update (this=0xb44cd48, diff=47) at /home/---/zero/src/server/src/game/WorldHandlers/MapManager.cpp:184 #18 0x08804b31 in World::Update (this=0x8e87290, diff=47) at /home/---/zero/src/server/src/game/WorldHandlers/World.cpp:1523 #19 0x085cb3c7 in WorldRunnable::run (this=0xbbe9b88) at /home/---/zero/src/server/src/mangosd/WorldRunnable.cpp:66 #20 0x089a2059 in ACE_Based::Thread::ThreadTask (param=0xbbe9b88) at /home/---/zero/src/server/src/shared/Threading.cpp:197 #21 0xb7f43171 in ACE_OS_Thread_Adapter::invoke() () from /usr/lib/libACE-6.0.3.so #22 0xb7f051cf in ace_thread_adapter () from /usr/lib/libACE-6.0.3.so #23 0xb77ccc39 in start_thread () from /lib/i386-linux-gnu/i686/cmov/libpthread.so.0 #24 0xb77399fe in clone () from /lib/i386-linux-gnu/i686/cmov/libc.so.6 [/code] My fiance was taming Barnabus in Badlands. When it finished taming, the core crashed.

It would be cool if you made it work exactly like Blizzard. Invisible mob which summoned the baddies. I'd LOVE to go out there in GM mode to see the invisible mob.

Cannot reproduce this. It appears as though your client is missing their bow/crossbow animation. Poachers can do ranged attacks. I have had four players through here since June and none reported issues, and that does not include my main character (Tauren Shammy). Oh, and my neighbor's kid now plays with us and he had a warrior go through there, no issues. My fiance is right next to me now on her system and poachers are working. She got close, it started attacking with a sword. She rooted it and backed off, and it used a crossbow. Is there anything special you were doing to cause this? If not, I will have to close it as "cannot reproduce". I'll allow some time for a reply.

I take it back, it is not applying the +60 to all resistances to me. I added up my gear resistances and I am good. The problem is that the spell is being applied to my pet, but my pet only gets the +40 stamina. In other words, it won't apply the +60 to each resistance.

What I meant was, if you use a function introduced in 6.3, and a user has 6.0, they can no longer use external ACE, which is the better way to go in the Linux world. That was what I was getting at. I am not concerned as much since Gentoo is fairly bleeding edge itself. Heck, I am installing it on a laptop now. When I did my first Gentoo install a month ago I got kernel 3.16-5. This one pulled 3.17-7! Talk about speedy! I am just trying to make sure the project is available to as many users as possible. Maybe once the project is stable we can switch to using pure C++ for some of that stuff via the new boost types. It could REALLY reduce code, especially the cross-platform, cross-architecture variable types.

And what happens if it breaks on half the Linux distros? We need to stay off the bleeding edge of every library, or we need to stop using them and use C/C++ standards to get the job done. Remember, once anything from 6.3 is used that is not in 6.0, you break Debian and everything under, which is quite a bit. I am moving away from Debian due to systemd, but many users use Debian or Ubuntu.

I had a level 43 undead lock before BC came out. I had a 60 lock in the beta. I never was disallowed use of my pets. If you can find something that says it was disallowed in 1.12.1, I am sure the team will change the quest.

Wheezy has 6.0.3 backported. It is not a good idea to use the latest and greatest. The problem is that normal distros (not Gentoo) will sometimes be a year or two out due to stability. For example, when Wheezy was released, 5.x was stable, so they froze it there and offer security updates only for it. When Jessie (Debian 8, not out just yet) was frozen, it was at 6.0.3, so that was backported. If you get too far ahead with internal and do not use what major Linux distros use, you will eventually get far enough ahead that you will not be able to build MaNGOS under Linux. We REALLY need to choose a stable set of tools and use that version for a year, then upgrade, and repeat. Anyway, 6.0.3 is the current STABLE version. If you like unstable Linux, you can get 6.2.8, but expect a broken OS from time to time. Most people run stable Debian/Ubuntu/Mint/whatever.

I'll rebuild shortly. What existing crash is happening?

External. I always use external.

I am using the old box for testing. It is running Debian Wheezy 32bit.

I just did as Reaper said and the old crash is gone. Now I have a new crash, related to the Eluna hooks, apparently. [code] server exit CLI command under processing... Table `command` overwrite for command 'honor show' default security (2) by 1 Table `command` overwrite for command 'modify honor' default security (1) by 2 Exiting daemon... Command: server exit [Account: 0 from Console] mangos>[Thread 0xb18f0b70 (LWP 4170) exited] Network Thread Exitting Network Thread Exitting [Thread 0xb08eeb70 (LWP 4172) exited] [Thread 0xb10efb70 (LWP 4171) exited] [Thread 0xb20f1b70 (LWP 4169) exited] Program received signal SIGSEGV, Segmentation fault. 0x08ab5799 in Eluna::OnShutdown (this=0x0) at /home/---/zero/src/server/src/modules/Eluna/HookMgr.cpp:378 378 EVENT_BEGIN(ServerEventBindings, WORLD_EVENT_ON_SHUTDOWN, return); (gdb) backtrace #0 0x08ab5799 in Eluna::OnShutdown (this=0x0) at /home/---/zero/src/server/src/modules/Eluna/HookMgr.cpp:378 #1 0x085c52a6 in Master::Run (this=0x8e46840) at /home/---/zero/src/server/src/mangosd/Master.cpp:352 #2 0x085c4994 in main (argc=1, argv=0xbffff314) at /home/---/zero/src/server/src/mangosd/Main.cpp:214 [/code] Again, this happens on shutdown, not during gameplay, so it is not a major stopper. My only concern is if all of the data is being saved before a crash on shutdown.

I did not know that. I will do that now. Yes, I used pull.