Hi folks,
I used tampermonkey for this, but there are other alternatives available which I'm sure you can use.
TamperMonkey:
The script can be copied in by clicking the tampermonkey extension icon and 'Create a new script'.
Comments in the script explain how it works and what you need to know. Copy paste the below script into your new tampermonkey script and then click File -> Save.
FURTHER DEVELOPMENT INTERESTS:
1. Get this working on chrome. Chrome has a limited stack size issue that seems to revolve around the FS (file system) JS object. Any command sent to it seems to be recorded in some stack somewhere which Chrome doesn't seem to clear correctly. As such we cannot spam file creation commands without filling this stack and the game crashing.
2. Enhanced garbage collection. Possibly related to the above - the longer you play the game the slower it gets, likely due to retaining previously loaded resources. Currently exporting saves, reloading the page and importing saves (as per the instructions in version_2) speeds the game back up to a certain extent. Initial investigations into this have also revealed that each save file retains a log file of every action and command fired during the entire game. Loading and updating this log file as its size increases may be whats causing the slowdown or at least contributing somewhat.
I used tampermonkey for this, but there are other alternatives available which I'm sure you can use.
TamperMonkey:
You must be registered to see the links
The script can be copied in by clicking the tampermonkey extension icon and 'Create a new script'.
Comments in the script explain how it works and what you need to know. Copy paste the below script into your new tampermonkey script and then click File -> Save.
You don't have permission to view the spoiler content.
Log in or register now.
You don't have permission to view the spoiler content.
Log in or register now.
FURTHER DEVELOPMENT INTERESTS:
1. Get this working on chrome. Chrome has a limited stack size issue that seems to revolve around the FS (file system) JS object. Any command sent to it seems to be recorded in some stack somewhere which Chrome doesn't seem to clear correctly. As such we cannot spam file creation commands without filling this stack and the game crashing.
2. Enhanced garbage collection. Possibly related to the above - the longer you play the game the slower it gets, likely due to retaining previously loaded resources. Currently exporting saves, reloading the page and importing saves (as per the instructions in version_2) speeds the game back up to a certain extent. Initial investigations into this have also revealed that each save file retains a log file of every action and command fired during the entire game. Loading and updating this log file as its size increases may be whats causing the slowdown or at least contributing somewhat.
Last edited: