Time zone differences not accounted for

[mcd8604]

I noticed tonight that the history timestamps are saved based on the master looter's timezone. We ran two raids tonight and changed master looter. The second ML happened to have an earlier timezone and the gear drops got interspersed with the prior raid:

The two highlighted items were from BWL and the items in between came from MC which we ran an hour later.

Is it possible to save the timezone along with the timestamp?

[evil-morfar]

I'm working on revamping the time system. I'm treading carefully as it could have some backwards compatibility issues, but I'll most likely change all awards to be based on server time.

[Orphis]

When you do that, make sure to use an ISO format for dates, dd/mm/yy is totally ambiguous when you try to import it in any software and doesn't sort nicely. YYYY-MM-DD works better.
Also, there's no reason to not have the time in the same field for even easier sorting: YYYY-MM-DDThh:mm:ss

[johnbaker]

I've run into this in an external app I am working on that is based on RCLootCouncil exports. The exported timestamps would be more useful they were based on server time or if the timezone information was included with the export.

[johnbaker]

@evil-morfar is this still on the roadmap? Could there be a shorter-term step where the serverTime is added to SavedVariables and handled via import/export so we consume the data? If this is acceptable, I'd even be willing to throw together a PR.

[evil-morfar]

@evil-morfar is this still on the roadmap? Could there be a shorter-term step where the serverTime is added to SavedVariables and handled via import/export so we consume the data? If this is acceptable, I'd even be willing to throw together a PR.

It will be the next "big" thing I'll be working on, but I can't give an eta. I'd be happy to include a server time field (maybe except for in the csv export, as that requires the import to be updated as well). Even better if you'd create it :)