You don't. Badspots syntax error finder works 5% of the time.
Use TorqueDev. It's best free IDE for Torque that I could find.
yeah if a human couldn't figure out the problem, surely this program will do much better
also, that's the stock syntax checker that runs when the script is compiled. if you know just a simple thingy about how those parse syntax and run code you would be better off
it works 100% of the time, if you're too dumb to figure out a painfully simple algorithm (loop through all characters one at a time) then you should practice more
ps: last I checked you aren't supposed to distribute .exe's on the forums, particularly not
youon the other hand the
file appears clean (but that doesn't mean jack stuff if you're even just a
little bit good at hacking) and
the legit website is downall of the above
if you forget up a package like this guy:
http://forum.blockland.us/index.php?topic=241268.0you'll note he only got one ## and it was way the hell at the end of the package
he could've had dozens of if statements in between and torque wouldn't've been any the wiser
i can't think of a time when I've seen ##error## but i'm positive it's out there
typically the error is directly after the problem: if you forget a ; it'll tell you on the next line
basically, it runs through parsing all of the data. if it runs into something it didn't expect (like a new thingy without a ; on the line before) then it'll stop and crap out an error
at the new thingy not where the error actually was
