A winset() edit is persisting between sessions even when the code is removed, dream maker is restarted, the code is recompiled, the code is clean-compiled, the .dmb is deleted and then recompiled, or all of the above at once.
Additionally, the error seems to persist between entirely distinct projects, and has persisted in spite of computer reboots and byond open/closures. I only realized that it was not my fault when I realized the .dmf file in the sidebar was not ticked, and traced it back to the following.
Numbered Steps to Reproduce Problem:
Make an empty test project with the following code:
mob/Login()
..()
winset(src,"input","command=.test")
mob/verb/t(var/s as text)
set name = ".test"
src << "test: [s]"
Compile and run, enter random text into the default input bar to prove it works. Delete all the above code and recompile. Enter nonsense into the input bar and notice that is still trying to call the .test verb, in spite of removing the winset call.
Create a new test project, compile and run it without adding any code at all. Enter nonsense into the input bar and notice that it is still trying to call the .test verb.
Note that the same or similar effects happen if you use an alternate layout .dmf and a different control in the winset (input1, etc); however, it persists only between controls with the same name, eg, input1 will not inherit input .command, etc.
Expected Results:
winset() would observe default behavior when not called
Actual Results:
winset() alteration persists unusually.
Does the problem occur:
Every time? Or how often? Testing suggests every time
In other games? Works on dedicated test project
In other user accounts? Untested
On other computers? Untested
When does the problem NOT occur? When the name of the control differs
When I first tested it, it was running the .dmb directly from DM, without logging into BYOND. Running it from DD required logging in, so I can confirm that the change persists after logging in. I am not sure whether it is the .dmb/a compilation error, or something internal to this install of byond (a configuration/cache error?)