You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To reproduce:
Run a script on a server
Change the source code of the script to use different arguments or print something new
Close the game
Open the game
Result:
The supposedly still running process uses the updated script, not the old script from when it was run the first time (before game close)
Expected:
That the overwritten file would be saved in the background, until all processes using it are gone. And that old version of the script would be used when the Steam game opens.
This is how the game works. Whenever you launch a script (including on page reload), the game loads the saved script. If you have overwritten the saved script, then of course that's what it's now going to load when you reload the page, because you have destroyed the previous script.
"By design" is a choice. I was pointing out how the game differs from the fake reality it portrays, and the fix seemed simple to me. Guess your username is earned.
It would work the same on your own computer. If you had a file set to run whenever you start up your computer, and you launch it, and then you edited that file before restarting, it would load the version that you edited, it wouldn't magically remember the version that you overwrote. If you don't want the game to forget the contents of your file, don't overwrite it, just like real life
To reproduce:
Run a script on a server
Change the source code of the script to use different arguments or print something new
Close the game
Open the game
Result:
The supposedly still running process uses the updated script, not the old script from when it was run the first time (before game close)
Expected:
That the overwritten file would be saved in the background, until all processes using it are gone. And that old version of the script would be used when the Steam game opens.
Steam's Bitburner v2.1.0 (8f4636c)
The text was updated successfully, but these errors were encountered: