Fyre

Update: 2022-02-19 Confirmed that the fix posted above does appear to fix the Combo Points problem. Spell Entry: 79327 Spell Name: Sinister Strike Enabler At level 1, you do not earn Combo Points. Combo Points are only earned when Eviscerate is learned from the trainer. I haven't seen any bad side effects or issues out of this fix.

Update: 2022-02-19 Looks like this one can be marked as completed/archived.

Update: 2022-02-19 Confirmed, transport does not occur when approaching/clicking the helicopter. Mangosd Snippet: From clicking on the helicopter. Mangos Video: Video from 2015:

Another bug topic has been opened for this one in 2015: As of 2022-02-18, this has not been fixed.

Update: 2022-02-19 Problem: The spell, Arrest, shows that the ambassador is an Invalid Target. Quest Entry: 26118 Quest Name: Seize the Ambassador NPC Entry: 42146 NPC GUID: 180861 NPC Name: Ambassador Slaghammer Item Entry: 56837 Item Name: Sturdy Manacles Spell Entry: 78628 Spell Name: Arrest Mangosd Error: Video from 2015: Mangos Proof Video:

Update: 2022-02-18. Confirmed - this behaviour still exists and has not been patched. Mangos Proof: Video showing that the Rockjaw Invaders should be running towards the center and Joren Ironstock should be shooting them as they approach:

Update: 2022-02-18 Confirmed. This quest is broken for all classes. Currently working on a script to get this to work as expected.

Update: 2022-02-18 Confirmed - this is still a problem.

Update: 2022-02-18 Confirmed that Arcane Missiles continues to not work. Arcane Missiles! aura is applied to the player, but they cannot use the Arcane Missiles spell. Proof:

Update: 2022-02-18 Tested start to finish with activating the Chicken to become a guest giver, buying seed, re-activating the chicken to complete the quest, clicking the game object egg, looting the egg, using the egg, and summoning the companion. No issues with this any more. Proof:

Update: 2022-02-18 Character does sit forwards when sitting in a chair. However, noticed that my character sits, stands, then sits back down. Proof:

Update: 2022-02-18 Rel 21 is stable and is compiling/building without issue. Rel 22 is unstable and still in testing.

Update: 2022-02-18 This bug is not fixed. I was able to confirm that after flying, I automatically had GM Fly Mode on. Proof:

Update: 2022-02-18 Flying mount does NOT crash the core. Proof:

Double Spawns:

Update: 2022-02-18. Quest is working. Did not observe NPCs moving while asleep. However, they may move a little bit funny after being woken up (watch video attached). Still some doubled spawns. M3 Rel 21 Video: Video from 2015:

Don't believe this is a problem any longer. I'm able to clone, build with EasyBuild, and get the binaries and conf files without issue. At this time, Rel 21 is the supported version. Rel22 is still in development.

Confirmed. Still an issue as of 2022-02-18. Blinking in Eastern Kingdom takes you to: Blinking in Kalimdor takes you to: Blinking in Outlands takes you to: Common theme is that the blink spell teleports you to 0,0,0 on the continent.

Confirmed - still not working. Notes Creatures/triggers are already spawned. Tested killing one with .die, does provide quest credit. Using the provided item at the creature/trigger does not provide quest credit. Some additional data Quest Entry: 26391 Quest Name: Extinguishing Hope Creature Entry: 42940 Creature Name: Northshire Vineyards Fire Trigger Item Entry: 58362 Item Name: Milly's Fire Extinguisher Spell 1 Entry: 80199 Spell 1 Name: Spray Water Spell 2 Entry: 80209 Spell 2 Name: Fire Extinguisher ExtinguishingHopeProof.mp4

To be added: https://github.com/mangosthree/server/blob/master/src/game/Server/SharedDefines.h Line 68 shows that RACE_WORGEN = 22, which would mean that in RequiredRaces Worgens would have a value of 2097152.

Hey Jimdobbswow, One of the first things I noticed is that you were grabbing the database files from the releases section. Is that also where you go the server files from? Personally (I use Ubuntu - so just keep that in mind), I do everything from scratch, i.e. no installer script. That being said, I will still try to help out where I can. I grab the server files from: https://github.com/mangostwo/server and the database files from: https://github.com/mangostwo/database. ... But before you go ahead and try that... I noticed something... You have already created your three databases, and that's fine. I would then run the command you did to load the realm tables into the database... but try to use mariadb instead of mysql (mysql 8 especially can give really weird errors): mariadb -u root -p two_realm < realmdLoadDB.sql (are you using root as your user for this? if you were following the guide that you linked, you should be using 'mangos' as the user.) Let me know if that command still causes you any issues? - Fyre. (If you have Discord, jump in and tag me for faster responses :D)

Sauranok Will Point The Way - Quest Text When going in to complete this quest, Sauranok had very strange text. It only read: "mage." It wasn't capitalized, it didn't have any structure to it, etc. First I needed to find the quest id. I used the SQL 'LIKE' statement to search with wildcards - I could have just done it with an = and no %'s... but I wanted to show you some other methods. I could have gone LIKE "%Sauranok%", and it may have given me more options in the output that I would need to pick from. SELECT `Entry`, `Title` FROM `quest_template` WHERE `Title` LIKE "%Sauranok Will Point The Way%"; The output was: +-------+-----------------------------+ | Entry | Title | +-------+-----------------------------+ | 28909 | Sauranok Will Point the Way | +-------+-----------------------------+ Okay - so Quest ID/Entry = 28909. Because I couldn't remember the correct column name for the part of the window that was showing me "mage.", I needed to do the following: SELECT * FROM `quest_template` WHERE `Entry` = 28049; I'm not going to post the output this time, because it would be very long and messy. But I noticed that OfferRewardText was equal to: "$c." $c is a variable for "class", so... because I was playing a Mage, it displayed "mage." I needed to find the correct text for this, so I went to Youtube and found a 10 year old video (around the time of actual Cataclysm). It showed me the following text: <Sauranok nods toward you> Paladin. So, oddly enough the text quest was essentially correct - it's just the class name. However, there does seem to be an extra line above it, and the class name should be capitalised. The formatting for this uses "$B" to go to a new line. For more information on these variables, see here. The final SQL fix for this one was: UPDATE `quest_template` SET `OfferRewardText` = "<Sauranok nods toward you.>$B$B$C." WHERE `Entry` = 28909;

Echo Island Tiki Targets Are Chasing Me! When attacking these Tiki Targets on Echo Isles, they were moving around towards the player. That's incorrect behaviour - they should remain stationary. I began by using the ingame chat command: ".npc info" to get the creature Entry #38038. Now I could go into my database and begin looking to see what the UnitFlags were (this is where I suspected I would need to apply my fix). SELECT `Entry`, `Name`, `UnitFlags` FROM `creature_template` WHERE `Entry` = 38038; The output was: +-------+-------------+-----------+ | Entry | Name | UnitFlags | +-------+-------------+-----------+ | 38038 | Tiki Target | 393216 | +-------+-------------+-----------+ Time to go to the creature template documentation for UnitFlags. Starting with the UnitFlags value, let's subtract the largest possible flag. 393216 - 262144 (UNIT_FLAG_STUNNED) = 131072 131072 - 131072 (UNIT_FLAG_PACIFIED) = 0 Stunned and Pacified made sense to me. I did do some comparisons with other Target Dummies (who also stay stationary when attacked), they - most of the time - had the same flags. So I guess the flags weren't the problem this time. I did do a lot of trial and error with numerous different strategies, values, etc. and finally the thing that worked was... AIName (see documentation here). SELECT `Entry`, `Name`, `AIName` FROM `creature_template` WHERE `Entry` = 38038; The output was: +-------+-------------+--------+ | Entry | Name | AIName | +-------+-------------+--------+ | 38038 | Tiki Target | | +-------+-------------+--------+ I didn't really like the description for any of the AIName values in the documentation. The one that sounded most correct was NullAI --> Do nothing. Same as empty string. > Do nothing... that sounds perfect! > Same as empty string... but I already have an empty string? I decided to try putting NullAI into there - couldn't hurt, right? IT WORKED! It actually worked! My final SQL fix for this was: UPDATE `creature_template` SET `AIName` = "NullAI" WHERE `Entry` = 38038;

Auctioneer Drezmit's Gossip Window Fix When clicking on the auctioneers to open the auction house, Auctioneer Drezmit would open up a gossip dialog window. Based on a comparison of him and his three neighbours (using the ingame chat command: .npc info), I determined that the NpcFlag was probably the culprit. I did a nice quick comparison in my mangos_world3 database. SELECT `Entry`, `Name`, NpcFlags` FROM `creature_template` WHERE `Entry` IN (44865, 44866, 44867, 44868); The output was as such: +----------+---------------------+-----------+ | Entry | Name | NpcFlags | +----------+---------------------+-----------+ | 44865 | Auctioneer Fazdran | 2097152 | | 44866 | Auctioneer Drezmit | 2097155 | | 44867 | Auctioneer Ralinza | 2097152 | | 44868 | Auctioneer Xifa | 2097152 | +----------+---------------------+-----------+ I used the creature template documentation (NpcFlags) to determine what the NpcFlags meant. The best way is to start with the largest value that fits into the flag. With a flag of 2097152, there is a perfect fitting "2097152" flag which is for: UNIT_NPC_FLAG_AUCTIONEER. Well - that makes sense for Fazdran, Ralinza, and Xifa. Drezmit however has some flags left over. 2097155 - 2097152 = 3 The next largest flag that fits into there is "2" which is for: UNIT_NPC_FLAG_QUESTGIVER, which, as I'm sure you have already guessed... is for quest givers. That leaves us with: 3 - 2 = 1. And now we can fit one last flag into there with a value of "1": UNIT_NPC_FLAG_GOSSIP. Well, I've never heard of auctioneers handling out quests or providing gossip. So I was pretty sure that I could change Drezmit's NpcFlags to 2097152. "Fun" story about this one. I had originally submitted a fix to the GitHub repo which removed the extra NPCFlags for quest giver and gossip, only to have a recurring thought in the back of my head... "check the quests." So I needed to find a quest that was started by Drezmit in order to confirm this. I used the quest_relations table to find this. SELECT * FROM `quest_relations` WHERE `entry` = 44866; The output was: +-------+-------+-------+------+ | actor | entry | quest | role | +-------+-------+-------+------+ | 0 | 44866 | 29416 | 1 | | 0 | 44866 | 29425 | 0 | +-------+-------+-------+------+ Role of 0 = starts a quest, Role of 1 = ends a quest. So we know that he starts quest #29425 and ends quest #29416. For the purpose of this tutorial, it doesn't really matter what those quests are - we just needed to know if he was Quest Giver or not. So I had to provide a 2nd pull request on Github to fix this mistake. My final SQL fix was: UPDATE `creature_template` SET `NpcFlags` = 2097154 WHERE `Entry` = 44866; NpcFlags value of 2097154 = Quest Giver + Auctioneer. So in the end, we just removed the Gossip flag. I did go back and test a few things to make sure his behaviour was still correct when the quest was available and after it was completed. Things seemed appropriate, so I felt comfortable with that final fix.