Next Game Time Shows GMT But Is Attually in BST

So the next game time in my campaigns is basically an hour off what it should be, for example a game I'm in is starting in 10 minutes at 20:00 BST, says the following currently: " Next Game Sunday June 14 7:00PM GMT Standard Time (50 minutes ago)" 7:00 PM GMT, is 8:00 PM BST which is in 10 minutes, not 50 minutes ago. BST = British Summer Time (Daylight Savings Time) and is GMT+1

I've heard this is supposed to be based upon your Computer's time settings. Please doublecheck and see if the game time / time zone matches what is set on your computer OS.

My timezone is GMT in daylight saves time, which makes it GMT+1 or British Summer Time, GMT is a time standard and should never change, it's basically the same as UTC, so the fact it says "GMT Standard Time" and is showing one hour ahead of GMT makes it wrong. At the very least it should say GMT Daylight Saving Time, but even then that's technically not correct as it's not a valid timezone.

Would you say the time is wrong, or is it the wording of how the time zone is named? The time, should be based on your computer settings, and will appear differently from player to player (computer to computer). Times like "50 minutes ago" should be relevant to the user's computer's time settings. If that is not working for you, please re-state it and I will try to help you troubleshoot the issue. If the wording is not accurate, but the numerical time is working in order, I'll be happy to follow up with the Roll20 Dev Team and ask if the time zone wording can be changed.

The timezone name is wrong, the time is correct to the time on my computer, but that time is BST, or GMT+1. And it just reads GMT. Basically it's reads " Next Game Sunday June 14 7:00PM GMT Standard Time (50 minutes ago)" when the time is 7:50 BST (GMT would be 6:50 at that time). So it should read " Next Game Sunday June 14 7:00PM BST (50 minutes ago)" Or " Next Game Sunday June 14 7:00PM GMT+1 Standard Time (50 minutes ago)" That make sense, I know timezones get confusing.

We are working on this issue currently and will post back here when it is resolved.