scripts bish

[gokux33]

Take the Script Editor.
Make it into a .exe by itsself.
Be <3ed for lyf.

[emortylone]

x.X That isn't such a bad idea except for the fact that it still wouldn't have support for the NPC Server commands... and you couldn't test them except for debugging w/ the test button. So it would have VERY little purpose right now.
1) it would halt at all the NPC Server commands
2) you wouldn't know if the script worked or not... so then you just know it doesn't have any grammatical errors.
---Shifter

[R0b1n-NPC]

You should be able to set a flag that makes the editor go into ***** mode such as

//#editor.option-explicit

then it would do this if you had a script such as:

NPC Code:

---

//#editor.option-explicit

if (created) {

  this.num = 5;

  this.light = 0.5;

  this.blah = 30;

  for (this.i=0;this.i<this.num;this.i++) {

    showimg this.bah+this.i,light2.png,x+this.i,y+this.i;

    changeimgcolors this.bah+this.i,this.light,0,0,0.99;

  }

}

---

ERROR: Undefined Variable: this.bah

Notice the spelling mistake of this.blah to this.bah.

And the editor would see that this.bah isnt set to anything, and unlike before it just sets it to 0, it would bring an error.

[SupermanJR]

Originally posted by gokux33
Take the Script Editor.
Make it into a .exe by itsself.
Be <3ed for lyf.

If that dosent use a lot of ram, less then graal.exe, and used less cpu usage, it would be the thing i just need!

[Kaimetsu]

Originally posted by R0b1n-NPC
//#editor.option-explicit

But there isn't a standard way of declaring variables. Every variable that is mentioned in the script is immediately declared on loading the level, and people are used to that. So I might just let this.doobydoo use its default zero value and start manipulating it halfway through the script. It's not an error, it's just a different style. If you wanna check for similar-but-different-so-probably-misspelled names then just open the debugger and look through the listings.

[Tyhm]

A better approach would be
WARNING: Variable "this.blah" is never used!
Or a quick and dirty variable listing window...that'd be handy, another pane for it, maybe on the left side opposite the commands.rtf pane...as you type in a new variable, it adds it to the list of variables, doubleclick a variable to do a search for it automatically...so if you finish your script and realise you have i, this.i, and thisi, you can go directly to the ones you didn't intend and correct them.
In a standalone editor, this would be /very/ handy...
Hey, wasn't there a guy in Bugs or something making a level editor?

[Kaimetsu]

Originally posted by Tyhm
Or a quick and dirty variable listing window...that'd be handy, another pane for it, maybe on the left side opposite the commands.rtf pane...as you type in a new variable, it adds it to the list of variables, doubleclick a variable to do a search for it automatically...so if you finish your script and realise you have i, this.i, and thisi, you can go directly to the ones you didn't intend and correct them.

Agreed, that'd be good. Still possible through the debugger, of course, but this'd be so much quicker.

[Googi]

I don't know if making the script editor as an exe by itself would work, sure, you can make scripts easier with the potential extra features, but you can't test them :-\.

[Kaimetsu]

Originally posted by Googi
I don't know if making the script editor as an exe by itself would work, sure, you can make scripts easier with the potential extra features, but you can't test them :-\.

This is pretty much my concern too.

[R0b1n-NPC]

Originally posted by Tyhm
Hey, wasn't there a guy in Bugs or something making a level editor?

Yeah AmonRa, who wont send it to me