Minor update pushed!
Posted on 29 August 2025 by Aubrey
This update just adds fancy text for the embeds instead of the generic text
for every page. Hope you enjoy!
Welcome to the News page!
Posted on 29 August 2025 by Aubrey
I'm not sure why I hadn't done this earlier. Previously, I simply showed off updates through
Twitter, but obviously, not everyone has Twitter. Any new updates will go here along with a
short Tweet telling people to check the News page to see the changelog.
Other than the news page, this update fixes a bug that caused certain cookies to expire just around 9 hours after their creation.
Despite making MSPA To Go months ago and using it to read then, I don't believe I had ever actually extensively used the Save/Load Game features (which were affected by this bug) until very recently. My school has those shitty Yondr pouches this year, and I am confined to using just the school Chromebook, so I've been reading Problem Sleuth using MSPA To Go while bored in class. At first, I thought the bug was the shitty school-enrolled Chromebooks wiping their cookies after a while, but using other sites made me realize it wasn't that.
So now we are here. I have fixed this incredibly inconvenient bug that slipped past me all these months, simply because I had assumed that JavaScript date functions used seconds and not milliseconds.
Other than the news page, this update fixes a bug that caused certain cookies to expire just around 9 hours after their creation.
Despite making MSPA To Go months ago and using it to read then, I don't believe I had ever actually extensively used the Save/Load Game features (which were affected by this bug) until very recently. My school has those shitty Yondr pouches this year, and I am confined to using just the school Chromebook, so I've been reading Problem Sleuth using MSPA To Go while bored in class. At first, I thought the bug was the shitty school-enrolled Chromebooks wiping their cookies after a while, but using other sites made me realize it wasn't that.
So now we are here. I have fixed this incredibly inconvenient bug that slipped past me all these months, simply because I had assumed that JavaScript date functions used seconds and not milliseconds.