script editing broken in MacOS client

I reported this bug and was told it had been entered, but I'd really like to know when it'll be fixed. Since 1.3, after editing scripts for a while I get "syntax error" for every script, even the default one. Before today I'd found that quitting and restarting resolved the issue, annoying but doable. Now I find even that doesn't work: immediately after logging in, all scripts including the default one give an error when saved.

I know development for the MacOS client isn't handled in-house so client issues specific to it may take longer to resolve. That said, I'd like to know how long I'll have to wait until scripting isn't a pointless exercise.

We're looking into it right now, but no ETA on when it'll get fixed. We'll try to get it working by our next patch, if possible.

- Doug

Hope no coders in the game dev comp are using Macs.

It hits anyone, not just Macs. Hit me a couple days ago.

Yup. I'm the main coder for our game dev project, and I use both PC and Mac to do it, and I get this all the time on both machines.

Once it happens, you HAVE to relog. No way around that.

Without it happening ALL the time, I can only guess if my current way of avoiding the problem works or not. The editor only ever gets into this locked-up state if I compile, get and error, fix that error, and compile again. So when I DO get an error, I not only fix it, but I jump to some other place in the code and make a small change. Even just typing a space and deleting it seems to be enough. Since I started doing that, I haven't gotten the lock-up. (Except sometimes when I forget, of course.)

Your Milage May Vary. (But let us know if it does.)

You sure about that? Mine cleared up after about 10 minutes or so.

Edit: They just reproduced this bug on the PC client, according to my tech support person. I gave 'em the steps to reproduce it, apparently.

No idea if this will work consistently, but it's working for me.

For the first time today, I got the syntax error at 0,0 when compiling. I'd seen something like this once before in another life, so just cut all the global declarations (variables and functions), attempted to compile (of course if failed, but not with the syntax 0,0 error), then I pasted all the global variables back. A couple of other errors showed up but they were legit, then I got the syntax at 0,0 again, did the global cut compile paste thing, and it worked again, so I didn't have to log.

Try it see if it works...

- Get syntax error at 0,0
- cut all global variables/functions (default now at top)
- compile
- past them all back in
- compile

My testing (PC) shows that Tcoz is basically right, but its a little easier than that. If you get a syntax error (all errors? some specifc errors?) you get some extra queued errors as well. Saving about 2 or 3 more times (add and remove a space) will clear those and you will be able to compile without rebooting.

I don't know about the Mac, but it sounds like they may be unrecoverable without a reboot.

thank you!! phew! glad it's not just me!