Dani RK
Newcomer
If all your alliance members live in the same time zone (e.g.: all in Germany) the following might not make much sense to you.
If you play with players in countries from different countries, or a country with multiple time zones (e.g.: USA, Australia, Russia) you probably know the pain.
When the players in an alliance live in different time zones, it gets very complicated to communicate the time of an upcoming event in the alliance forum.
Example:
Player A lives in Los Angeles, USA (GMT-7) and correctly set the game time zone settings to Los Angeles.
It is 23:32 (11:32pm) in the evening according to his local time. He sees that he will be attacked at 06:22:30 next morning (the game correctly displays this in his local time).
He asks in the alliance forum for help and posts: "Help needed, incoming attack at 6:22:30 next morning"
Player B lives in New York (GMT -4)
He reads the post but has no clue what 6:22 actually means. Is it HIS local time? Is it Player A's local time, which? Is it GMT?
To avoid this Player A has some options:
What I suggest for posting in the alliance forum:
If you play with players in countries from different countries, or a country with multiple time zones (e.g.: USA, Australia, Russia) you probably know the pain.
When the players in an alliance live in different time zones, it gets very complicated to communicate the time of an upcoming event in the alliance forum.
Example:
Player A lives in Los Angeles, USA (GMT-7) and correctly set the game time zone settings to Los Angeles.
It is 23:32 (11:32pm) in the evening according to his local time. He sees that he will be attacked at 06:22:30 next morning (the game correctly displays this in his local time).
He asks in the alliance forum for help and posts: "Help needed, incoming attack at 6:22:30 next morning"
Player B lives in New York (GMT -4)
He reads the post but has no clue what 6:22 actually means. Is it HIS local time? Is it Player A's local time, which? Is it GMT?
To avoid this Player A has some options:
- calculate time difference from now (wait, hmm, 6hr 48 min 30 secs) : "Help needed, incoming attack in 6 hours, 48 minutes since sending this post".
Now player B would read the post. The forum correctly displays the time of the post in his local time: 02:32 (am) and does some calculations to get the attack time in his local time.
- Just send the GMT (after he figured out what his local time is in GMT taking into account any dalylight saving in his local time): "Help needed, incoming attack at 10:22:30 GMT", letting layer B doing the calculation from GMT back to HIS local time.
- (only theoretically) Force all members of the alliance to set the in-game time zone to GMT. This would make the post display "correct", but would f*** up other game experience
What I suggest for posting in the alliance forum:
- Add a new BBCode which allows to specify a unix time stamp ( the number of seconds that have elapsed since 00:00:00 GMT/UTC on 1 January 1970)
for example [unixtime]1672570800[/unixtime] - when displaying the post, it would show the time in local time (according the timezone set up by the viewer in the game).
- SInce converting to a unix time stamp is not very user friendly: in the post form, add a new icon to the menu strip "local time". When clicked the user is prompted for a local time. If approved a [unixtime] BBCode would be inserted to the text
- Player A: writes a post to the alliance: "Help needed: incoming attack at ". He clicks the "local time" icon, enters 6:22, approves and the text is now similar to:
"Help needed: incoming attack at [unixtime]1672570800[/unixtime]".
After he posted that and looks at his post he would see "Help needed: incoming attack at 6:22"
- Player B opens the post and sees "Help needed: incoming attack at 9:22"