- Status Closed
- Percent Complete
- Task Type Feature Request
- Category
- Assigned To No-one
- Operating System
- Severity Very Low
- Priority
- Reported Version
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
Opened by Elvors Amenoras - 24.05.2008
Last edited by Caarrie - 24.05.2008
FS#1568 - Correlate game date/time and real date/time
This is a suggestion to make it easier to announce the date and time for events such as tournaments, roleplay events, etc.
The date and time is often given as a real-world date/time such as “on Sunday, May 25th 15:00 PST”, which is
(a) difficult to translate to the local time zone for most people and
(b) a real-life reference that damages immersion.
I suggest a conversion tool to remedy this: a window with two selection tools for datetime, one for local datetime, one for Ylliakum datetime. Selecting a datetime in Ylliakum sets the local datetime and vice versa.
When writing announcements, players can select a local time and see the Ylliakum time, ready for typing into the announcement.
When reading announcements, players can select Ylliakum time and see the datetime of the event in their local timezone so they can plan their real life around it.
The selection tool would be a calender and a clock. The clock’s resolution would have to match the resolution of Ylliakum time (i.e. 3 AM, 6 AM, 9 AM, 12 AM, 3 PM, 6 PM, 9 PM, 12 PM).
Future dates/times would depend on how stable Ylliakum date/time is. I.e. after a server crash, Ylliakum time would have to be derived from real time instead of simply continuing from where it stopped (I don’t know whether this is done already, or if the server has any idea of a current date at all).
Alternatively, one could extend the text output routines to accept control codes for Ylliakum time, e.g. [2008-05-24 9:10] anywhere in a string might translate to “5th of Unodin in 937, at 7 o’clock (PM)”. Then Ylliakum times would be automatically readjusted after a server crash. (Translation would have to be done whenever text is stored in a book though, to avoid “auto-updating books”!)
24.05.2008 10:31
Reason for closing:
Additional comments about closing:
Yliakum time right now has no rl
comparison and no weekdays/months
related to rl. this is not a valid
request due to that.
From closing comment: "Yliakum time right now has no rl comparison and no weekdays/months related to rl. this is not a valid request due to that."
The fact that a correlation between real and in-game time is not yet present, does not make this an invalid request. Just one that cannot be implemented until such a correlation exist.
Implementing such a correlation is not really difficult, but I think the idea is that time is not really progressing at the moment (i.e., it will stay year 750 until the game is a bit further in development). Feel free to (ask to) re-open this request when it becomes more relevant :)
Well, relevance is independent of whether the mechanisms exist.
If Lanarel meant "preconditions to implementations": I can't reopen at the right moment because I don't follow development.
I understand Close Wontfix as "we will never implement that, not even in future revisions".
If what Caarrie meant is "we can't implement it right now but will sometime in the future", set the the due version to "Due in any version", and I know the issue won't be forgotten and will be done eventually.
An aside note: I understand the reasoning behind not progressing the year, but if the plan is to do a Big Wipe before the 1.0 version, the year number can be reset.
If players stumble over a discrepancy, they will find ways to explain them away. I'm active in a group where even multiple, independent, contradictory calendars exist, and for those interested in calendar history, it's a source of intense scholarly roleplay trying to clean the mess up.
The passing of time of not just hours (like now) but also days/months/years is right on the top of the list for version 1.0
Be patient until then ;)