My script isn't working, what to do. A step by step guide.

[xAndrewx]

Originally Posted by adam

So.. you misunderstood the point of the entire post, and now your still not going to let it go?

I did misunderstand the origional post, however can show me how to debug a script without showing an example.

[Crow]

Originally Posted by xAndrewx

I did misunderstand the origional post, however can show me how to debug a script without showing an example.

This guide is for starters. Try to explain this concept/idea to somebody who is a complete newbie to scripting/coding, without any examples.

[xAndrewx]

Originally Posted by Crow

This guide is for starters. Try to explain this concept/idea to somebody who is a complete newbie to scripting/coding, without any examples.

Exactly- thank you.

[Inverness]

I'll offer some things that I do when I need to debug something:

1. Be explicit, less chance for weird GS2 stuff to happen that way. What this means, prefix variables and function calls appropriately. Avoid ambiguity with variable names, make sure they don't conflict with existing things, etc. And don't do things like putting code outside of a function definition.

2. Echoes. I put echoes everywhere so I can tell where the script is executing, what parameters and objects exist at a certain point, etc. type() and objecttype() functions are useful for checking the state of objects.

3. Formatting. I'm anal about script formatting and adhere to strict methods of spacing and naming. Doing this means less chance of screwing up because you forgot a bracket or something. I also stick to using lower-case variable names in all but object names.

[cbk1994]

Using Jerret's debugger can be very helpful.

[Crow]

Originally Posted by cbk1994

Using Jerret's debugger can be very helpful.

Originally Posted by Crow

Doesn't matter, he's just trying to show how he debugs his code. I'd say it'd be easier (better even) to use a this.var instead, and then monitoring it with Jerret's debugger.

Duh