Foereaper

[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.

Alright :) Whenever someone confirms that this is fixed, I'll close the issue.

I don't have the access to merge issues :P The issue in question is here:

[url]https://www.getmangos.eu/issue.php?issueid=581[/url]

Possibly fixed here, please test and confirm:

[url]https://github.com/mangoszero/server/commit/565fd0d26265625ca7d3a64256dadcc3ed81c7a2[/url]

After testing this seems to be something overwriting eConfigInt32Values (World.h) at index 1. This is the index for CONFIG_INT32_QUEST_LOW_LEVEL_HIDE_DIFF. If you manually change the index of CONFIG_INT32_QUEST_LOW_LEVEL_HIDE_DIFF to 2, everything works as it should. Still looking into what, and why, index 1 is overwritten.

Renamed issue to be more descriptive, as the issue is broader than first expected.

This would not be possible with the current script loading system. The entire scriptloader and manager would have to be rewritten. You can however just disable Eluna in the config files and SD2 will take precedence.

With the current implementation, Eluna overrides SD2's events. If two scripts exist for the same function, SD2's is discarded and Eluna is ran.

He did both :) one for eluna, and one for those not wanting to use it

If a quest is considered too low level for your character (if it will have a gray color in your log), it will be much less visible. By default, an exclamation point will not appear above the quest giver's head, nor will one appear on the minimap without an extra step (see below). Since Patch 2.3, the quest title in the quest giver's talk window will also be tagged "(Low Level)".

Before Patch 3.0.2, a low-level quest could be discovered only by mousing over (or interacting with) its quest giver. Since 3.0.2, selecting "Low Level Quests" on the minimap radar will display exclamation points for every available quest, including those considered "low level". This also causes a dull exclamation point to appear over NPCs offering low-level quests.

This means, if the quest is still > gray in your quest log, it should show as yellow above the NPC's head. Not necessarily a core issue, it could also be an issue with the "quest level" not being consistent with the actual quest level requirement.

That's how group loot should work isn't it? To me that sounds correct :P

No, the code is not removed. It is flagged as used, but kept for issues such as rollbacks or whatever so you can verify that the player has actually used the code.