/playtime screwed up - Have not used a portal, at all.

[Aeris 3894]

Since the update on September 3rd where the "fix" for the screwed up /playtime command went in my /playtime has become messed up instead. I am not alone with this problem, and it is possible that everyone has become affected - So far everyone I have asked has been affected by it. It is set to Day of the Ant, week 1 of the starfall of Diamonds, 980. As far as I know this date is out of bounds, as the earliest player registration date would be on week 3. Irrelevant to the problem at hand, but worth noting nevertheless.

 

What happened?

I typed /playtime to find that my starting date has become screwed up, and now says "You entered through the portal to Wurm on day of the Ant, week 1 of the starfall of Diamonds, 980". This is incorrect. From what I can tell, my time lapsed since the start date is displayed correctly (so far...).

 

What I expected to happen:

That the correct /playtime would be displayed.

 

Steps to reproduce

Exist, apparently.

 

Additional notes

- My /playtime was correct on September 2nd

- I have logs containing my original playtime, in case it would become relevant

- I have never used any of the new portals, on any account that I own

- No one has ever used any of the new portals on my computer or network

- I have not crossed any server border, either by boat or by swimming, since my latest correct /playtime check

- I have yet to cross a border to see if that will fix it, but that did not solve it for the friends of mine who have tried it. Neither has going through a portal: They still have incorrect playtimes, despite trying to shake it loose

- I cannot cross over to the cluster where my account was created to attempt to fix this, as it no longer exists

- Several people not only have the start date bungled, but also the amount of time that's gone by since then. When they've compared the current time stated with the one in their logs (and with their known start dates) they don't match up

[Synjor 519]

The team are aware of the issue and working on a fix, thank you for reporting!