[creature_addon] visibilityDistanceType of 5 does not work

[Gultask]

Current Behaviour

Setting this to 5 will not change the visibility of the creature

Expected Blizzlike Behaviour

According to the wiki:

Infinite = 5, SIZE_OF_GRIDS // max distance for visible objects)

Source

No response

Steps to reproduce the problem

Run this query:

DELETE FROM `creature_addon` WHERE (`guid` IN (67001, 203341));
INSERT INTO `creature_addon` (`guid`, `path_id`, `mount`, `bytes1`, `bytes2`, `emote`, `visibilityDistanceType`, `auras`) VALUES
(67001, 670010, 0, 0, 1, 0, 5, '34623 19818'),
(203341, 2033410, 0, 0, 1, 0, 5, '34623 19818');
UPDATE `creature_template_addon` SET `auras` = '34623 19818' WHERE (`entry` = 18733);

.go c 67001 move away from Fel Reaver, see that it disappears at lower distances.

Extra Notes

No response

AC rev. hash/commit

https://github.com/azerothcore/azerothcore-wotlk/commit/721711d70f31ad46b615b630c379d61837d263f6

Operating system

Windows 10

Custom changes or Modules

No response

[UltraNix]

Works okay for me. Just client limitations - increase visibility distance in settings.

[Gultask]

Config settings are set to 250y Still can't see Fel Reaver past that

[Gultask]

Also some people that reported it can't see it in Chromiecraft.

[UltraNix]

Maybe because you must activate its grid?

[Gultask]

In my setup setting visibilityDistanceType to 2 made the creature despawn about 10y or so from my character

[acidmanifesto]

In my setup setting visibilityDistanceType to 2 made the creature despawn about 10y or so from my character

I was the one who did the visibility distance refactor for azerothcore about a year ago. At first most creatures you were view grid wide in distsnce, and there was a few other pr's made by other people that further corrected it. I honestly do not recall which pr that came out to adjust it further or who made it. But the issue may be among one of those follow prs not done by me.

[virgo77]

Hi! I just saw this topic as I got the same issue and I can say that just modifying the SQL DB with the good value works great:

Maybe updating the DB with an SQL file when doing a git pull origin?

Great Work btw! :)

NOTE: if we stay static, the creature stays on screen. But, if we move to it, it's flashing until we reached a lower distance to it. But in fact, it works ^^ NOTE2: the second Fel Reaver, ID 203341, walks slower than 67001. Is it a core adjustment? Or can I fix it through the db?

Regards, V.