Script not working? Use the -showScriptErrors parameter!

[Celery]

If you're encountering a mysterious malfunction in your scripts, the first thing you should do is put the -showScriptErrors parameter in your Arma 2 shortcut's target line. It will enable you to see script error output in the top part of your screen. An error message will a) help you solve the problem yourself, or b) help us solve it for you without needless guessing and elaborate proofreading.

[Katipo66]

Yes, I'm no scripter but this parameter pretty much tells you where it's failing and maybe sometimes what's needed to fix it, I.e. Missing ; or ] catches me out a lot

[Tankbuster]

Celery speaks the truth!

Team -showscripterrors with SBSMACs Squint and you're well on the way to being a scripter. Sort of.

[kylania]

Used to use this all the time, but so many people made missions with script errors that I couldn't play without being annoyed all the time. Now I just have it on my "editing" shortcut, but i'm too lazy to restart most of the time heh

It is however a wonderful tool and should always be used while editing.

[Zipper5]

Yes. Please, everyone - start using this parameter. So many missions and scripts released every day aren't working properly because people aren't using it.

[Big Dawg KS]

Not everyone can be good enough to spot errors right away like I can.

But really, I do use it (I think; I can't really remember the last time I got any errors ).

[Koni]

I use it, though I hate it, possibly because it highlights my scripting inadequacies

[chicago]

Celery speaks the truth!

Team -showscripterrors with SBSMACs Squint and you're well on the way to being a scripter. Sort of.

Thanks for info, Tankbuster. Long time I'm looking for a good script editor

[Tankbuster]

Thanks for info, Tankbuster. Long time I'm looking for a good script editor

I don't use squint as an editor, though it does do that. What squint is really good at is counting brackets and checking variable names.

[-=Borz=-]

If you're encountering a mysterious malfunction in your scripts, the first thing you should do is put the -showScriptErrors parameter in your Arma 2 shortcut's target line. It will enable you to see script error output in the top part of your screen. An error message will a) help you solve the problem yourself, or b) help us solve it for you without needless guessing and elaborate proofreading.

excuse my ignorance, I put the -showScriptErrors parameter in my arma Arma 2 shortcut's target line after ...\arma2.exe", and i get a message saying the te text is not valid.

Help please!!