goodbadguy

Not sure if it's just me but recently Savage Combat doesn't even get applied to players anymore.

Bug still exists in clean core.

What is this? There is no spell 70799 and the T10 Priest 4P Healer bonus affect Power Word: Shield and Circle of Healing, not any cooldowns. Reference: http://www.wowhead.com/spell=70798

This is not a core issue. You just need to set the unit_flags to 8 to make an NPC healable/buffable. example: update creature set unit_flags=unit_flags|8 where entry = ####

Confirmed, but to clarify this: It ONLY happens if you had more than a 5 stack to start and then you try to mill/prospect the from the SAME stack. To dupicate: - Add 10 Peaceblooms and/or 10 Titanium Ores to yourself. - Mill/Prospect the stack of 10, leaving 5. You will get loot. - Mill/Prospect the 5 remaining and you will get a blank loot window. If you separate the stacks of 5 first this does NOT happen.

Please post an update for the sql since the table has changed and if you don't mind post the SpellFamilyMasks as integers instead of hex. Thanks.

Looks to be an invalid pet or guardian the player is trying to summon according to "CreateFromProto@Creature"

It was up less than an hour before that.... why not just give it a day? Hell there were no new posts on SD2 the past 2 days anyhow.

I didn't see that posted anywhere. Thanks!

Looks like it's back down again. Been 2 days+ and I can't connect to http://udbforums.kicks-ass.net at all. It just says "Server not found".

Does this fix that Paladin Judgments are currently able to be blocked,dodged and parried?

Having the same issue. I summoned one of the creatures to test myself and it appeared green and attacked me. Afterwards I summoned another and it was red. Every concurrent summon was red. Seems to be some strange caching issue....

I have had the same problem since 3.3 update. The issue seems to be when the OTHER player is NOT PvP flagged. If they do not attack back they do not get flagged and you must hit attack again until they attack back or become flagged....

Also, UDB's been down for 2 days.. at least when I use http://udbforums.kicks-ass.net

This girl made quite a lot of money selling just about every possible drop for a price via their website, which is why it was being sued by Blizzard probably for selling their virtual property.

Didn't solve my problem. There are many many other creatures that use that spell and none of them seem to crash the realm versus the Azuremyst problem.

I tried removing the spells from the Blood Elf Bandit and although I did seem to travel further on the island I eventually got a popup when nearing Bristlelimb Village that strangely said: World of Warcraft: Disk error Please insert the disk The it had Cancel, Skip or Continue. I clicked continue twice then the client crashed just as before. Very strange indeed.

Confirmed. Happens to myself and most of my players almost anywhere on Azuremyst. I use Mangos 10309.

This also happens when a rogue or druid wear any item that increase hp regen...

Could you SHARE with us how you disabled the spell?

j4r0d, your patch indicates placing case 48018 in the HUNTER family? Placing that code properly in the WARLOCK family works, however with the newest core if you go to re-cast the Demonic Circle: Summon before it's 6 minutes the old object is removed but no new object is created and the spell becomes useless.

Sometime this afternoon suddenly clicking the "New Posts" button is failing to work for me giving me this error: Not Found The requested URL /gs-bin/search.php was not found on this server. Apache/2.0.54 Server at getmangos.eu Port 80

VS2010 runtime support worked. Thanks!

Since Revision 10165 with the new Vmaps system when trying to use the makevmaps batch file I get the error that I am missing the MSVCP100.DLL file. Finding this file on the internet doesn't help as then it says I'm missing the MSVCR100.DLL file. Finding that file allows the batch to almost start but then it says there's a mismatch in the MSVCR100.DLL file.... Why are extra DLL's now needed to extract VMAPS?

This bug has existed for me ever since the inception of MaNGOS 3.3.3. For some reason the core code that should prevent this client crash seems to actually be causing it.