Leaderboard

Fix was commited here. Please pull the latest source code, rebuild and test for every known case. Awaiting feedback.

INSERT INTO `creature_ai_scripts` (`id`, `creature_id`, `event_type`, `event_inverse_phase_mask`, `event_chance`, `event_flags`, `event_param1`, `event_param2`, `event_param3`, `event_param4`, `action1_type`, `action1_param1`, `action1_param2`, `action1_param3`, `action2_type`, `action2_param1`, `action2_param2`, `action2_param3`, `action3_type`, `action3_param1`, `action3_param2`, `action3_param3`, `comment`) VALUES ('2123300','21233','11','0','100','1','0','0','0','0','21','0','0','0','0','0','0','0','0','0','0','0','Prevent Movement'), ('2123301','21233','9','0','100','1','0','50','50','200','11','36238','1','0','0','0','0','0','0','0','0','0','Cast Fel Cannon Blast'), ('2246100','22461','11','0','100','1','0','0','0','0','21','0','0','0','0','0','0','0','0','0','0','0','Prevent Movement'), ('2246101','22461','9','0','100','1','0','50','50','200','11','36238','1','0','0','0','0','0','0','0','0','0','Cast Fel Cannon Blast'); Seems to work very well. What do you think? @H0zen

All issues fixed in https://github.com/mangoszero/server/commit/9af47a5582b46b1678387c2e58f3b8e4de5ac2fa Awaiting feedback

@D Q I have pushed a PR out on the original repository where the fix was initial committed too.

4 years later. 😅 Rel22_03_032

Fix can be found here. Rel21_15_008

Tested on deDE: Works like a charm! Thank you.

Should now be fixed by this commit: https://github.com/mangoszero/server/commit/df20a5b97f1b9a9507824565c40688ca30e98381 Release: https://github.com/mangoszero/server/releases/tag/v22.01.25

I believe that Russian is not supported directly on vanilla client

Zero: REL21_22_008 One: REL21_15_018 Two: Rel21_12_012 Three: REL21_13_007

Changed Status to Awaiting Dev Review Changed Assigned to Necrovoice Seems to be an easy fix.. When I am back in town on monday i will have a look.

Hi @My Channel Some updates have been done for newer Mysql server versions.

This update should fix the Druid flight path issue as well as the Startup errors. REL21_16_039

Rel21_16_32 Update with the fix above and both quests should be working correctly. Will leave this open for a short time in the event this does not resolve the current reported issues. If you find any more, please create a new report. Thanks

@Natrist, I was just about to close this as complete. lol Thanks for the submit

Changed Status to Confirmed Changed Assigned to H0zen, antz Changed Implemented Version to Unset Changed Milestone to 22 (Next) Changed Priority to Low Changed Sub-Category to Code Enhancement

This is fixed latest revision.

I'll be the first to admit, it was a hack. I just tested your code and it works. Much better than my hack. I'm not at all familiar with the code and to be honest, it has been over 15 years since I wrote any C++...back in my Baldur's gate modding days. However, at least we got the ball moving on this bug.

it is a server I was invited to play on they told me to report bug here so not sure

Changed Status to Unconfirmed Changed Assigned to Necrovoice Changed Implemented Version to Unset Changed Milestone to Unset Changed Priority to Normal

Hi samljer, as you can see in http://wowwiki.wikia.com/wiki/Formulas:Mob_XP , in the zero difference section, is ok for you to receive xp from a 48 lvl creature. As described in this link, only creature with -16 lvl will not give you xp at this lvl

Updating with more info + reproduction steps: This issue seems to be far more wide ranging than the original report, and is present regardless of the Loot mode (eg, Need before Greed, Free for All), and is in fact reproducible when not in a group. Steps to reproduce: 1. Kill a mob 2. Open the loot window, if there are 3+ items of loot take the top one 3. Close the loot window, then reopen it 4. Attempt to loot the item at the top: "Item is already looted" 5. Attempt to loot the second item in the list: Success The issue appears to be that for each mob each position in the loot window can only be looted once. Therefore once item at position 1 has been looted reopening the loot window reorders the items and it can't be looted again. While solo this isn't really an issue - just loot from the bottom up In a group this is a major issue with FFA loot, and more importantly with Quest Items which are largely un-lootable

Hi there Stefan! I can explain Dodge Cap and what it means and does. Dodge Cap is the maximum amount of the Dodge % a class can have. I see you are using Mangos One, so allow me to explain a bit more. During TBC, Rogues could actually be Dodge Tanks. This is because the Dodge Cap is actually extremely high. It is impossible to hit the actual limit for Dodge as a Rogue, and probably a Druid also. A Rogue needed 102.4% total Avoidance (the combination of Dodge+Parry+enemy miss chance). What you are seeing is not a bug, but a very annoying Rogue. Here is more information: http://wowwiki.wikia.com/wiki/Rogues_as_tanks

News I try old releases and i think last commits are ok ,but Commits on Aug 15, 2017 are wrong because release Aug 12, 2017 , there spell type charge, polymorph work normally

We need: an exact description of the Mangos core you're using (which means the core and DB version and, for a repack, the repack origin) a stack trace for the crash Without the info, we just cannot do anything.

I consider a "fixing" as "to make things blizzlike". It's more complex to make the mentioned spells exclusive (as they are now) than to make them stackable. But, in this case "blizzlike" means "exclusive since 1.7.0 version", so until we support either 1.12 or a TBC version here, it's all right. The "bugged server" can support vanilla 1.6 version and be correct in the buff stackability. But if they claim supporting any TBC (2.x), the stackable Sayge's buffs are non-blizzlike (more exactly, antiblizzlike due to our knowledge of desired behaviour) and, in my terminology, bugged.

Cannot reproduce any of these database errors. Maybe you messed up the DB importing? Are you using the actual repo's db or are you using a third party DB?

This is not the only Burning Crusade thing which was in code or database. I wasn't around then but it could be that Mangos zero was backported from one of the later expansions.

not enough info. Not reproducible. Please clarify.

Not sure what happened there on covenant, but all is well in my DB. Ran a GM command to see if that corrected it. I suggest reset of the server and try again at this point.. If its still an issue after I will track it down why it works for me and not on covenant and submit a fix.

Changed Status to Completed Changed Type to Core

Fixed by https://github.com/mangostwo/server/commit/e8502e3e759be7eb18767f5cceb1a62a6994218d

Changed Assigned to H0zen Changed Version to 21.11 (Current Master Branch) Changed Implemented Version to Unset Changed Milestone to 22 Changed Priority to Normal Changed Type to Core Changed Category to Transports / Flight Paths Changed Related to to Investigate and implement handling for NPCs on transports

Changed Status to In Progress Changed Assigned to H0zen Changed Version to 22.1 Changed Implemented Version to Unset Changed Milestone to 21

since mariaDB is not currently supported, this is actually a low priority. It will get reviewed in time and when the build system fully supports mariaDB all the existing updates beyond the base db will need to be adjusted at well,

- Removed extra Jaina Proudmoore from Alliance version of Forge of souls. She will not spawn inside herself....(eww) - Removed Jaina Proudmoore from Horde version of Forge of souls. Lady Sylvanas is pleased. Fix found here: Rel21_06_008

I can either confirm that is fixed with the latest update Thank you for your amazing work!

soon

Any chance of this getting looked into? Flametongue procs, etc. are still triggering spell-casting animations. While it's not game-breaking, combat-related animations are pretty significant.

@Necrovoice - could you pr this for me ? Add "Thanks Caliginuex" to the commit title

UNIT_FLAG_DISABLE_MOVE is a confusing flag; despite its name, it only applies to players and simply means "the player is no longer in the control of its movement". For the chasing cannons issue, the only viable method I see is to use EventAI with ACTION_T_COMBAT_MOVEMENT on EVENT_T_SPAWNED For the casting spell issue, one is tempted to think that creature_template_spells table from the database is enough to make a creature cast spells. The truth is that table has nothing to do with creatures' spells, it simply describes what spells are available in your action bar if you CONTROL that creature (mind control, for example). Please remember, in MaNGOS and all it's descendants, no creature will cast spells unless instructed to do so via scripting! All creatures, by default, can only do melee attacks (and have combat movement enabled). So, for the cannons to cast spell 36238, it is mandatory to script them (EventAI is the most simple approach).

You can find the fix to this issue here #78

Yes, but it should be one bug per-entry on the tracker. If anyone works on this they will need to open an entry for each bug as they work on them.

Amazing job H0zen, tested all your fixes and they were working perfectly.

Hey Nolin, just add them per Hand in your Database in Script Bindings.

Should be working now, thanks for reporting it here in the tracker Find it here

Changed Status to Confirmed Changed Assigned to Necrovoice Changed Milestone to 21 I know exactly what has to be done.. in fact the fix is already done on my pc... it should of been released in Rel21_02_28 but never made it in (ie. I forgot)

Its all good. when theres a bunch like that, but if therea a hand full then dont bother... use your judgement

@Black Shadow, would be be so kind as to place all them errors in a spoiler box? Saves us gnomes from scrolling when we can be inventing bigger and better tinker thingy mabobs...

Yay, nice one, necrovoice