Description:
In a local enviroment, Everything that has an "hour of the day when xxx occurs" in worldserver.conf occurs 3 hours earlier.
At least in my case, (GMT-3).
Example:
Worlserver.conf: Instance.ResetTimeHour = 4
(default)
Server: Global instance resets at 1 AM
Is this intended? Or it should use the timezone of the machine where the core is running?
Branch(es): 3.3.5
TC rev. hash/commit: 7e579a98483313cb68b58dcc1dd0d25903812f93
Operating system: Win 8.1
on my case instance reset set to 6 enables reset on 7am.
You should configure your timezone of the machine for this case
Configured for my case:
Timezone
(UTC-3:00) Buenos Aires
Adding the difference when configuring worldserver.conf would work but I was wondering if this was intentional.
I use the default setting ( Instance.ResetTimeHour = 4
) and my resets occur at 03:00 (am). My TZ is GMT+1.
@TheWinchesters : have you checked your auth realmlist.timezone
setting?
Same issue as https://github.com/TrinityCore/TrinityCore/issues/8390
Not the same issue as this is about events running serverside while the other issue is about timezone ignored in the packet sent by the client
I opened a draft PR https://github.com/TrinityCore/TrinityCore/pull/23540
which configs does it affect other than Instance.ResetTimeHour ?
and not sure about CleanOldMailTime
Do all these reset at wrong time ?
I tried Guild.ResetHour and it called World::ResetGuildCap() at the right hour of the day
Oh, sorry. My mistake.
could you check the others too and see which ones are broken ?
This is everything I have experienced so far, (UTC -3):
A easy test for anyone would be entering an instance and see what the welcome message says or wait to see when the Kalu'ak event starts tomorrow.
could you check if https://github.com/TrinityCore/TrinityCore/pull/23540 fixes the instance reset ?
Updated https://github.com/TrinityCore/TrinityCore/pull/23540 to support Respawn.RestartQuietTime and weekend xp rate too
https://github.com/TrinityCore/TrinityCore/pull/23540 fixed some issue
which cases are still left to be handled ?
Stranglethorn Fishing Extravaganza is still problematic, isn't it? Or maybe I have forgotten to check if the events occur at a different time than 14:00 local time on Sunday, and whether I could have set a different time deviation somewhere in the config.
Most helpful comment
I tried Guild.ResetHour and it called World::ResetGuildCap() at the right hour of the day