![]() |
scripts bish
Take the Script Editor.
Make it into a .exe by itsself. Be <3ed for lyf. |
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 |
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: 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. |
Re: scripts bish
Quote:
|
Quote:
|
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? |
Quote:
|
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 :-\.
|
Quote:
|
Quote:
|
| All times are GMT +2. The time now is 11:48 PM. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
Copyright (C) 1998-2019 Toonslab All Rights Reserved.