I noticed this is actually displaying GMT, not UTC. Dagger ( talk) 21:07, 20 September 2016 (UTC) UTC vs GMT There are also a few pages ( Map bonus reward/profit, World versus World, Guild mission, Guild Merit) that would benefit from something like 'at TIME on DAY' or 'on DAY at TIME' format, but I'm not sure if it's worth the effort to support that.

I'm not quite sure what to do with Template:Dry Top rare creature table, and Sous-Chef Seimur Oxbone is obviously just wrong but I'm not sure what the right time is. JS seems to have roughly nothing to help you do dates/times. :/ I've been through everything. This talk section- Relyk ~ talk < 01:18, 20 September 2016 (UTC)

Light source -> You -> Globe - 1 || wgNamespaceNumber = - 1) to make sure they're using it right.

Put the support for the globe pointing away from you, and the light shining past your head at the globe (we'll pretend it's the Winter Solstice to make life easier). Dagger ( talk) 13:11, 20 September 2015 (UTC) I suggest grabbing a globe, a flashlight, and heading into a dark room. We know what it's trying to say (since we all know when missions reset, right?), I'd just prefer that the page actually said it, rather than be wrong and rely on the reader to figure it out. Is this information wrong? G R E E N E R 12:56, 20 September 2015 (UTC) It actually tells you that it's 5 PM on Sunday, then tells you that Sunday is Saturday. It tells me that my time zone is seven hours behind UTC, which is correct (I'm in PDT at the moment). This tells me that when it's 5:00 PM on Saturday where I live, in Vancouver, Canada, the servers are reset for guild missions. (This is Saturday in the Americas and Sunday in the EU, Asia, & Oceanic zones.)'. Dagger ( talk) 11:51, 20 September 2015 (UTC) To quote what I see from my computer, 'Guild mission rewards: Sunday 00:00 UTC (17:00 UTC-7). But it relies on JS, so I can't actually edit it myself. (This is Saturday in the Americas.)' - how can Sunday 17:00 UTC-7 be Saturday? That's not how it works! Either this template needs to accept and spit out a day, or we need a second template that does. Now, for American users, it says 'Guild mission rewards: Sunday 17:00 UTC-7. I replaced it w a giant table that gave the day/time in different timezones, because I couldn't think of any other way to handle it, but somebody changed it back to use this template. Server reset used to say 'Guild missions are reset once each week on Saturday at server reset (01:00 UTC+1)' for me, which is an entire 24 hours out from when they actually reset (Sunday at 1 AM). zeeZ ( talk) 13:05, 4 September 2015 (UTC) 'Is it not the same as any other clock?' There's a difference between clocks and specific datetimes though.

I just hate it when conversion like that wraps around but doesn't tell. Chieftain Alex 12:37, 4 September 2015 (UTC) I just see the potential for random confusion, for example usage on Beta for example: The second public Beta Weekend Event will take place from September 4 at 19:00 UTC (05:00 UTC+10) to September 7 at 6:59 UTC (16:59 UTC+10).

Is it not the same as any other clock? '00:00 UTC (01:00 UTC+1) or 23:59 UTC (00:59 UTC+1)' looks fine to me, and I don't see a problem. Another option would be introducing a ], but how crazy do you want to get with those edge (depending on how far off the norm you are) cases? - zeeZ ( talk) 11:17, 4 September 2015 (UTC) Would it make sense to add something like 'the next/previous day' suffix to the script? E.g. Currently crossing over to the next/previous day during conversion is not handled (see 00:00 or 23:59 if your current time zone is not UTC).

Utc clock gadget for win 7