Auntie Mangos

@lillecarl: I replied to you time ago in this topic when you asked for linux warden, but it took you several days to reply again and probably you didn't see my answer. http://getmangos.eu/community/post/136559/#p136559

MaNGOS Revision: 10 8xx Bug report: http://getmangos.eu/community/topic/15708/bug-fix-applyauraname-138-and-192-haste/ Fix: http://pastebin.com/BmcsSv2P Sadly, I didn't get any comments in Bug Reports section ;( Maybe no more people noticed it All in all, I'm posting this fix in Under Review section. To sum up, wrong handling of 2 haste auras and because of it ranged haste is applied where it shouldn't.

why not better use something like this http://getmangos.eu/community/viewtopic.php?id=14757

i think this program can be very useful for GMs or novice admins and can be used another users on some targets http://getmangos.eu/community/viewtopic.php?id=14985

What bug does the patch fix? What features does the patch add? This patch would fix Siphon Life after client switch. For which repository revision was the patch created? 8016 Is there a thread in the bug report section or at lighthouse? If yes, please add a link to the thread. http://getmangos.eu/community/viewtopic.php?id=8383 Who has been writing this patch? Please include either forum user names or email addresses. Corfen and ChanF07. Core patch: diff --git a/src/game/Unit.cpp b/src/game/Unit.cpp index 4d53011..84d9378 100644 --- a/src/game/Unit.cpp +++ b/src/game/Unit.cpp @@ -5140,6 +5140,13 @@ bool Unit::HandleDummyAuraProc(Unit *pVictim, uint32 damage, Aura* triggeredByAu triggered_spell_id = 37378; break; } + //Siphon Life + case 63108: + { + basepoints0 = int32(damage * triggerAmount/100); + triggered_spell_id = 63106; + break; + } } break; } and sql fix: INSERT INTO spell_proc_event VALUES ('63108', 0x00, 5, 0x00000002, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0.000000, 0.000000, 0); INSERT INTO spell_bonus_data VALUES ('63106', '0', '0', '0', 'Warlock - Siphon Life'); patch file

You mean autocast? http://getmangos.eu/community/viewtopic.php?id=7789

Little bug, use http://getmangos.eu/community instead http://www.getmangos.eu/community.. I cant login with http://www.getmangos.eu/community, but all ok without www =). P.D: I like new style but my mobile browser (blackberry browser) not think the same

Please report bugs in our bug report section.

What bug does the patch fix? What features does the patch add? The patch adds correct dummy effect for dagger http://www.wowhead.com/item=49982 and it's heroic version http://www.wowhead.com/item=50641 For which repository revision was the patch created? 10312 Is there a thread in the bug report section or at lighthouse? If yes, please add a link to the thread. http://getmangos.eu/community/viewtopic.php?id=14584&highlight=Heartpierce Who has been writing this patch? Please include either forum user names or email addresses. Me http://paste2.org/p/937541 Description: Original dbc data is wrong, there's other item's triggered spell in it. Spellfamily is paladin, that's a bit confusing too. Proc chance is 100% and according to wowhead this item has no internal cooldown. Maybe I've forgotten something to mention, you can read original bugreport thread. Tested ingame, works fine.

http://getmangos.eu/community/showthread.php?14110-patch-Small-aura-related-change&p=118939&viewfull=1#post118939 Already report. I think too it's a visual bug but a can't find the problem

What features does the patch add? Modify the stacks management of auras. For which repository revision was the patch created? The backport is made for the revision : b5c6b556bc2093a302967dd5a14972afaa5d772a of the branch mangos-0.12 Who has been writing this patch? Please include either forum user names or email addresses. No idea about original author of this patch, my work is based on the patch of KAPATEJIb : http://github.com/kpw/kpw/blob/master/12_aura_stack.patch Final work : MiLk <[email protected]> Code : https://gist.github.com/b93e6691650036171088

I rollbacked 8eb70eff6e9727a404e095a9978add4fd09677fc and crash stoped . Now i endeavor backporting related fix patch from master to last rev of mangos-0.12 . not tested stability yet [some-backporting-from-master]"]This Patch

http://getmangos.eu/community/viewtopic.php?id=9776

In my opinion, spells with same Family but different spellIcons should be allowed to stack generically, except when they have the same family flags, as is the case with raid buff versions of single target buffs (Greater Blessings, Gift of the Wild, etc.)

ReputationMgr::GetRank was changed in the core and was reverted back later. It should be OK in the latest version. I ran into an issue about melee combat caused by bot->SetFacingToObject() which sometimes not able to turn the bot facing the enemy. So latest commits have this code reverted back to bot->SetInFront() (MovementActions.cpp:314) which makes client think that bot is not facing the enemy (enemy is behind and the bot is meleeing him in an opposite direction and actually hits ). Same issue persists in original Playerbot as well. Please see this post for the details.

I agree here Multithreading worked perfectly on a Quadcore with this branch and the current branches are not usable on MultiCPU Systems or simply useless.

What bug does the patch fix? What features does the patch add? Implement proc rate for spells 45401 and 45403 For which SubVersion revision was the patch created? 6730+ Link to the Thread in the bug report section? http://getmangos.eu/community/viewtopic.php?id=29354 Who has been writing this patch Malah DELETE FROM spell_proc_event WHERE entry IN(45401); INSERT INTO `spell_proc_event` VALUES (45401,0,0,0,0,0x0000000000000000,0x00000000,1.24,45); DELETE FROM spell_proc_event WHERE entry IN(45403); INSERT INTO `spell_proc_event` VALUES (45403,0,0,0,0,0x0000000000000000,0x00000000,1.24,45); according to wowhead data: proc rate - 1.24 ppm internal cooldown - 45 seconds

http://getmangos.eu/community/showthread.php?12131-mangosd-exe-problem-%283-3-core%29

Hi there, Well I am testing mangchat for a week now. Everything works fine. Nice addition! A few days ago I wanted to compile it again and got 2 errors with compiling. These two are back: 2 errors I know that it has something to do with Revision 8318 from Mangos I cannot find exactly what the problem is. Anybody who can help me? Thanks in advance!

Hi mates, had not much time doing anything else than working. But maybe I can explain some upcoming issuses. @yad02: I added the UpdateAttackerInfo() and IsInCombat() functions to try to check for all ongoing combat and to manage all threatening hostil creatures. GetAttackers will only return creatures dealing damage to a Unit. Cause of this I changed the search to check for all creatures threatened by us. This includes also creatures not already attacking someone. And both functions check whole group for ongoing combat and attackers. Before I miss it - a criticial todo: 1) Lately I changed combat behaviour of HunterAI and also the MovementGenerator stuff in GetCombatOrders. I tried to make i.e. Hunter (also applies to warlock, mage, etc.) to just follow a target in range of its spells. With just follow I meant to walk directly in direction of the target to a distance where spells can be casted. Using current MoveChase, or MoveFollow MovementGenerators won't do the work. Follow will follow in an angle relative to the world orientation of target. Chase will make bot follow a target in the defined angle (i.e. dist=10.0, angle=0.0 bot is 10yards north of victim). Tried to calculate the correct angle between victim und bot but sometimes it happens the bot tries to run to the opposite side of the target - and eventually threatens more creatures. Have to study my mathbooks angain, cauze using PI for angle calcs is notvery familiar to me... long time not used any real math 2) Combat Orders, Movement Orders: currently working on this issue. COs will be tank, protect, assist, heal, etc. MOs will be follow, near, stay. Whereby stay means stay. Even if combat goes on. Near shall make bots stay next to master (in range of i.e 10 yards). I think follow I have not to explain. Will kepp you up to date with this. 3) Finishing moves: Bot should check if target has aura which says it is under 20% of health (do not remember the aura name). Which should mean that fighters should cast finishing moves (rogue, warrior), other should care about movement rate at humanoids (prevent fleeing, calling for assistance). Who can do this? 4) Clean up spell casting code the way I did for hunter and rogue. And if possible improve it Cheers!

i would be happy for that too

When some API part dependent from another project that changes in ways not contoroled by mangos team this is impossible have backwards compatibility working well. As noted by Ntsc attempt have client backwards compatibility will push code in wrong side and will only create performence/support problems. As noted by TheLuda internal structures and related APIs in project beta state expected to change while depvelopment and selecting better implementions. Also its partly dependent from client features and its required rewriting for new features support in proper way. Freeze like structures for just backwards compatibility will only make some features implementation possible only in slow/hack ways.

I assume you are using windows: http://getmangos.eu/community/viewtopic.php?id=13121 http://getmangos.eu/community/viewtopic.php?id=7318 3.3.5 works just fine. If something doesn't work you probably didn't extract all the needed files!

there was this patch -Fishing-in-Dalaran&p=92775&viewfull=1#post92775"][8044] Fishing in Dalaran

1 ) make sure that the spell focus GO is spawned 2 ) make sure you're close enough to it (one of the datax fields determines this) 3 ) be sure to restart server and clean out client cache after changing gameobject_template Failing at this, please contact your DB provider for support. MaNGOS forum is ok for general questions about how the server works, but not for content-specific help. As listed here: http://getmangos.eu/community/viewtopic.php?id=84 TBCDB is probably your best bet for help, since it's focused on the MaNGOS 0.12 branch that you're using.