Spring RTS Engine

It is always on my last }

And, on every script I have, newly modified or not recently touched at all, why is my scriptor messed up...?

just restart scriptor, this some times happens./

I've restarted both scriptor and my computer, and reinstalled scriptor, also. (ReDL'ed, actually, it doesn't have an actual install)

Snipawolf wrote:I've restarted both scriptor and my computer, and reinstalled scriptor, also. (ReDL'ed, actually, it doesn't have an actual install)

post the script, let's see what is wrong with it.

Did you change anything in a file which is being included by all of your scripts?

this is occasionally an issue with #included files. I don't know why, but there are times when scriptor absolutely refuses to let a properly #included .h file work, and crashes on every compile without an error. The only solution I've found is to take all the code out of that include and plug it into the main script. then it works fine.

No, there is nothing wrong with my script, it is something wrong with ALL of my scripts, or scriptor has some kind of error... It won't compile anything.

And, the only thing I include is argh's standard commands, but I already did a test where I copied the defined number and removed the include, but nothing works

Is 1.0 at file universe the most recent, are there any others, or perhaps an older version I could try...?

Try just moving functions around, changing the order, etc. One time a 'get' in a certain place was making it crash on compile...I swapped that with the line above it (a turn or something irrelevant) and it worked.

Yes, but, it is an issue prevalent in ALL of my scripts, I am fairly sure it is a scripter issue...

Or you broke all of your scripts at once. More likely than you think... :P
Does scriptor set any registry keys? If it does, delete them and try again.


I've had the error Peet described too... well, once. Never happened again and I fixed it by moving a line as well..

So, it does use registry..

Damn, I didn't think it would use registry. I had adware, and lots of it. So, I used a lot of anti-adware programs, and half of them didn't delete the stuff, but gave me the key locations, so I did it myself.

Well, lemme try again, then. Come here scripter reg. keys...

Edit: Found it, now testing.

Works! Thanks a ton! KalvKhalash or something like that, name of the creator, thus name of the keys.

I need to type faster so that I don't have to go back and edit posts...
Small fonted for bans and giggles.
Scriptor does set some registry keys, but you don't want to delete all of them. Two of them are scriptor's constants, which are a pain to realize are no longer set right after hours of wondering why your newly compiled scripts aren't animating your units properly. Umm, just watch for the section that has settings.

Outside of that, I've got nothing. I remember it happening to me once, but can't recall how I fixed it, if I even did, might have just started magically working again. Maybe try random stuff, like compiling empty scripts, scripts with just empty functions, deliberately broken scripts, setting your computer up on a pile of rocks and sacrificing the fat of a lamb to it. Who knows.

Just wondering though, did you try to fatted sacrifice before getting it to work?

yes, I deleted all of them, but there are no issues, and I even opened regedt32 again to see, and all of it (or most of it, how would I know what all is supposed to be there) is there, and my script I recompiled works just fine...

rattle to the rescue

Heh heh heh heh. I would never get anywhere without outside help

Did you re-enter the constants then or just left them blank (they are in Scriptor's otions somewhere in menu)? Your script may compile just fine without them, but the unit won't animate properly if your script has anything like turn something to x-axis <10> or move something to x-axis [1].

What makes Scriptor set these values up in first place? There's got to be a trigger that makes it write the initial values.

It probably does it when it finds no registry entries for them.

I am guessing that Rattle hit it, due to the fact I just deleted the whole folder of reg entries. Also, it took about twice as long to open that first script than it normally does, so I would guess that that is what it does for the first time.