Page 1 of 1

Playing Hours Time zone

Posted: 21 May 2021, 23:01
by jknitnerd
Hello,
I have been assuming that for the tournaments I created when I put my timezone in for the start time that the player hours were also based off of that same time zone… but I am wondering if this is not the case… Are the playing hours set for some sort of default time zone so therefore you need to convert it to your time zone in order to not have playing hours in the middle of the night?

Re: Playing Hours Time zone

Posted: 22 May 2021, 10:44
by Cheery Dog
On the individual tournament page I believe they are in the French timezone.

They will use your own timezone in the tournament list page. Possibly in the in-game settings as well if you search them.

Re: Playing Hours Time zone

Posted: 22 May 2021, 17:20
by jknitnerd
That should be listed, otherwise how would anyone know?

Re: Playing Hours Time zone

Posted: 25 May 2021, 16:03
by The_T
Yeah, I've definitely noticed the "playing time" not matching my time zone, with no indication that it wouldn't. Sounds like a bug that needs to be fixed.

Re: Playing Hours Time zone

Posted: 29 May 2021, 18:12
by jknitnerd
For the most recent tournament I created if I assume the place to input playing hours is in the French time zone and do the conversion myself for my time zone and hit save the tournament is then in the playing hours I intended and lists accurately for participants. I would not have known I needed to assume the playing time setup was not in my timezone without this forum thread, so thank you. I agree that this should be treated like a bug and fixed so that the time zone you are selecting during the tournament configuration should be the same for start time and playing hours.

Re: Playing Hours Time zone

Posted: 29 June 2021, 16:57
by Wyldeknite77
Interestingly enough, during the most recent set of tournaments I created, the Playing Hours selected were the actual hours for my time zone. It also reflected correctly in one of my friend's time zones in a different country so I guess they fixed this concern. :)