Foereaper

Corrupted ashbringer did indeed have sound in vanilla, however I'm pretty sure this was handled by a script and not through the dbc files. I'll take a look whenever I find the free time, however it would be really nice to know what setup the op is testing on.

An if check isn't really needed with the separated code bases, just don't add the dismount code to 3+ :P

This is what I seemed to remember as well, however I will try and dig for some more information. Edit: I cannot find an official changelog as to when the dismount was officially changed, however several discussions are to be found on their forums about this feature, and most state this was changed roughly around 3.0. If I had some older patches I could go manually digging for it, however I don't :(

Does this happen on boats as well? Pretty sure I know what's causing it, though I think it has been deliberately done for some reason.

Is this when trying to mount anywhere afterwards, or just on the zeppeline itself?

Has already been fixed, just hasn't pushed the newest Eluna revision to the main repo due to some experimental changes that comes with it as well.. Will be updated soon(ish)

On the Blink issue, I'm thinking it is possibly map related. Will test whenever I have time to see if I can reproduce.

This would be a core side issue.

Yeah, I was looking for a changelog of the above myself, I know I have seen one around before but I can't for the life of me find it again :P

Please leave it open till the OP has a chance to reply in case he/she has any more questions on the matter :) Will close it myself whenever it's all sorted

[URL]http://prntscr.com/5lcvpq[/URL] [url]http://prntscr.com/5lcw4a[/url] None of the Kodos have any sound information. Edit: I also noticed Blizz originally called them Koto, pretty funny

Do you happen to have the display ID's, then I can look it up sure

Alright, quick run down :) - Every single model that uses a sound has a sound entry in CreatureDisplayInfo.dbc (3rd column) - This integer points to an entry in CreatureSoundData.dbc - If an entry is not present, then a creature did not have sound data tied to the model at the time. Sound data includes jump sound, /space etc. 1.12.1 using enGB: Display ID: [COLOR=#545454][FONT=arial]10426 - Winterspring Frostsaber Mount [/FONT][/COLOR]http://i.imgur.com/Z1OvMVb.png This model does NOT contain any sound data (3rd column). Thus it's safe to assume the sounds for the Winterspring mount was added at a later date. [URL]https://getmangos.eu/wiki/Reference%20Information/DBC%20Files/MaNGOSZero/CreatureDisplayInfo.md[/URL] [URL]https://getmangos.eu/wiki/Reference%20Information/DBC%20Files/MaNGOSZero/CreatureSoundData.md[/URL]

If you wouldn't mind getting me their display ID then I can check the client side sound tied to the models :)

Anything stored within the client itself (Tooltips, sound information, spell animations) etc. is handled by the client itself. Thus if a tooltip is wrong, it is either an issue within the respective client side DBC file or your cache. That doesn't mean it's just you, but it's an issue with all clients on that version. If a tooltip at 1.12.1 is wrong for you, then it would also have been wrong back in the days on the same client version :) Though, some things like tooltips may vary between the different regions and platforms.

Spell tooltips like the above is handled by the client itself :)

Yep, at level 60, 1.12.1, using the warhorse :P I remember it very well because of the introduction of the Crusader Aura in TBC made it so much easier than before

Hmm, as a paladin I did this several times by myself using a water walking potion, whilst mounting after drinking it.. Could this depend on the spell itself? I'll have a look in the dbc later

The current spell handler is in the works to be rewritten /replaced, depending on how long this will take, spell related issues will probably not be prioritized until the new system is in place to prevent having to redo things over and over again :P though, if someone wants to look into it, then they're more than welcome to :D

Despawning through both SD2 and Eluna is currently having some issues. See the internal discussion thread about this.

This has been tested and is related to way points and general creature movement. Easiest way to test is to talk to a gossip npc while it's moving. Guards in Stormwind or Org work nicely for testing.

The above commit has nothing to do with saving raid states. Functions to save raids/variables have been discussed for a while, it's still in the design stage.

A pooling system was implemented on zero, but due to instability and crashes, it had to be disabled. The code is still there however, so if someone's up to fixing it up then have a look at that

The mods in this thread are correct indeed

Issue tested and confirmed resolved by Chuck :) closing ticket.