adds serverTime and field on json export #262
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The following issue details the current issue with the date and time field in the data:
#187
This pull request doesn't solve the display issue as care would need to be taken with old data (without the actual serverTime value) and could lead to confusion. However, as a short-term solution for applications that may either parse the RCLootCouncil.lua saved variable or use the Json export, this pull request adds a "serverTime" field to the loot data using the GetServerTime() function which is synchronized across clients and not effected by the current user's system clock or time zone.
I didn't include the EQXML export as the and timestamps are only based on the day (and not time) and dynamically swapping between the date/time epoch and the actual server epoch based on its existence may not desired. I can add this if requested.