Forums WoW Modding Support Archives TrinityCore Discord Archives [DiscordArchive] Does anyone know if the naked bug (periodically other players show with no armor when you teleport)

[DiscordArchive] Does anyone know if the naked bug (periodically other players show with no armor when you teleport)

[DiscordArchive] Does anyone know if the naked bug (periodically other players show with no armor when you teleport)

rektbyfaith
Administrator
0
01-14-2022, 12:43 PM
#1
Archived author: SynSQ • Posted: 2022-01-14T12:43:04.127000+00:00
Original source

Does anyone know if the naked bug (periodically other players show with no armor when you teleport) is an issue with the blizz 335 client itself in general or emulator issue?
rektbyfaith
01-14-2022, 12:43 PM #1

Archived author: SynSQ • Posted: 2022-01-14T12:43:04.127000+00:00
Original source

Does anyone know if the naked bug (periodically other players show with no armor when you teleport) is an issue with the blizz 335 client itself in general or emulator issue?

rektbyfaith
Administrator
0
01-14-2022, 01:15 PM
#2
Archived author: <o> • Posted: 2022-01-14T13:15:21.072000+00:00
Original source

likely both, it also happened on blizzard servers but it's very clear some private servers handles it far better than others. It's certainly related to wdb cache somehow (almost always happens when cache is empty), and can probably be mitigated by sending some packets more than once (item cache? updates?)
rektbyfaith
01-14-2022, 01:15 PM #2

Archived author: <o> • Posted: 2022-01-14T13:15:21.072000+00:00
Original source

likely both, it also happened on blizzard servers but it's very clear some private servers handles it far better than others. It's certainly related to wdb cache somehow (almost always happens when cache is empty), and can probably be mitigated by sending some packets more than once (item cache? updates?)

rektbyfaith
Administrator
0
01-14-2022, 01:15 PM
#3
Archived author: <o> • Posted: 2022-01-14T13:15:53.179000+00:00
Original source

i haven't looked too closely at it
rektbyfaith
01-14-2022, 01:15 PM #3

Archived author: <o> • Posted: 2022-01-14T13:15:53.179000+00:00
Original source

i haven't looked too closely at it

rektbyfaith
Administrator
0
01-14-2022, 01:30 PM
#4
Archived author: jackpoz • Posted: 2022-01-14T13:30:51.941000+00:00
Original source

we change cache number quite often now with monthly tdb updates
rektbyfaith
01-14-2022, 01:30 PM #4

Archived author: jackpoz • Posted: 2022-01-14T13:30:51.941000+00:00
Original source

we change cache number quite often now with monthly tdb updates

rektbyfaith
Administrator
0
01-14-2022, 01:32 PM
#5
Archived author: SynSQ • Posted: 2022-01-14T13:32:16.373000+00:00
Original source

<@787614711738138634> ah I see, I had rebuild the server from a fresh pull from 335 the other day since I thought I did something wrong and that's why it was happening but I'm still seeing it now
rektbyfaith
01-14-2022, 01:32 PM #5

Archived author: SynSQ • Posted: 2022-01-14T13:32:16.373000+00:00
Original source

<@787614711738138634> ah I see, I had rebuild the server from a fresh pull from 335 the other day since I thought I did something wrong and that's why it was happening but I'm still seeing it now

rektbyfaith
Administrator
0
01-14-2022, 01:34 PM
#6
Archived author: SynSQ • Posted: 2022-01-14T13:34:22.370000+00:00
Original source

About 90% of the time relogging seems to fix it but it's pretty inconsistent
rektbyfaith
01-14-2022, 01:34 PM #6

Archived author: SynSQ • Posted: 2022-01-14T13:34:22.370000+00:00
Original source

About 90% of the time relogging seems to fix it but it's pretty inconsistent

Recently Browsing
 1 Guest(s)
Recently Browsing
 1 Guest(s)