azerothcore-wotlk icon indicating copy to clipboard operation
azerothcore-wotlk copied to clipboard

(Creature): Certain creatures spontaneously have wrong display ID.

Open heyitsbench opened this issue 2 years ago • 9 comments

Current Behaviour

Sometimes certain creatures seem to have the wrong display ID from what they should according to the database. This has been observed with Zephyr and Gelanthis. Zephyr sometimes shows up with a display ID of 19278, Gelanthis sometimes appears with ID 15505. This seems to be a very inconsistent issue.

Expected Blizzlike Behaviour

Zephyr's native model ID is 19282, Gelanthis' expected ID is 15504. They should never deviate.

Source

Assumption, values from the database

Steps to reproduce the problem

  1. .go c id 25967/16624
  2. .npc info
  3. Observe their display ID.
  4. Restart AC until it deviates from what's in the DB.

Extra Notes

I noticed the issue with Zephyr in this AC issue. Vyperhand observed the issue with Gelanthis in this CC issue.

This is an inconsistent issue, but it most definitely does happen. Don't know if the model can swap while the server is running (I doubt it), but it can swap between restarts.

AC rev. hash/commit

a696227e8de1b26088d3a2abbb29d861aeb48672

Operating system

Windows 10 x64

Custom changes or Modules

None.

heyitsbench avatar Jun 01 '23 19:06 heyitsbench

Model_other_gender in the model table, pretty common issue (e.g captain greenskin)

Nyeriah avatar Jun 01 '23 19:06 Nyeriah

Model_other_gender in the model table, pretty common issue (e.g captain greenskin)

Well that's dumb.

heyitsbench avatar Jun 01 '23 19:06 heyitsbench

Those values should be sniffed as well, no? I can't see why someone would decide to add a random model there for fun.

Gultask avatar Jun 01 '23 19:06 Gultask

I remember another similar issue with model_other_gender I had to fix by forcing the model on script

Gultask avatar Jun 01 '23 20:06 Gultask

So why don't we simply remove that dumb code?

wzw1990 avatar Jun 10 '23 02:06 wzw1990

So why don't we simply remove that dumb code?

It's not dumb code, it's just a possibly bad database entry.

heyitsbench avatar Jun 10 '23 02:06 heyitsbench

Was this solved by #19068 ?

avarishd avatar Jun 18 '24 09:06 avarishd

Don't believe so, I think the issue with this is incorrect 'model_other_gender' value.

heyitsbench avatar Jun 18 '24 12:06 heyitsbench

https://github.com/chromiecraft/chromiecraft/issues/1617

avarishd avatar Jun 18 '24 13:06 avarishd