(edited to add more info) It seems letting it sit overnight resolved it. Was making sure it was ok a while before confirming it here. But last night letting it get to shutting down due to activity did not seem to help, at first I thought it was. I even let it 'idle' with no one in it for a hour, and same issue so went to bed and tried it a while ago and it seems to have fix it. And no, the saving button went from "saving" and "saved" fine. but never a log 'restarting due to changes', or 'spinning up new sandbox'. It would respond to !commands after it lagged out the first time..but any changes i made didn't reflect. I could go edit a script that had log("check"); to log("test"); and save (which gave no data in log window it saved or started back up), and still get just "check" in log window until I let it idle out and rejoin. Even disabling any script would still fire until it closed due to inactivity, on next rejoin it would be disabled. As for the the on ready, it wouldnt send the "API started" sendchat when hitting save. It was like it was caching whatever previous scripts it had in it. and only reloading them on shutting down ..to be stuck on them until idling out again. And yes, I was doing a lot of saving: make a few changes, save, test, few more changes, save, test..etc. I was saving maybe once every minute or 2 playing with the new dev server functions. seeing how I could use them and tweaking it. I believe it might be an issue of saving while a setTimeout() is running? Say you have a set timeout set to X time and save it before X time is up? seemed to crop up once I added one that was 60 seconds and started saving, but it wasn't every time because I saved and edited a few time with it in place and no weird results...could be coincidence, the whole correlation vs causation illusion :).
