Just a tool I made.
It finds if there are 2 consecutive returns in a script, and if there are, gives you the line number. (You still must fix it yourself. For instructions on how refer to this: http://forum.wc3edit.net/viewtopic.php? ... 09#p142909)
You have to use it on the script, not the warcraft map file.
This has been extremely useful to me when finding return bugs. Hope it helps.
If you want the source, pm me.
Just use the browse button to fill in the path to the code you want checked, and press the check button.
2.0 updates:
-There is now a window to open the .j file and edit it via there. This saves you having to JASSCraft the map to fix it.
-You can now open .w3x files to check.
-You now need MPQLib.dll in the folder where the application is.
-Stealers suggestion has been implemented - the errors now show in a listbox, not in messageboxes. (Comments will be ignored later.)
-w3e won't let me upload .dlls, so I packed it into a .zip.
call DisplayTextToPlayer(Player(0),0,0,"This is some text
And this is some more text"
Its on planty of hard-to-crack maps
Only way I found (I don't remember where I placed that damn thing) is it checks if the line doesn't start with:
call
loop
endloop
function etc....
Re: Return Bug Finder
Posted: April 12th, 2011, 8:43 pm
by owner123
I will make this later (Unless you're planning to ofc.)
@vegas I don't really know enough about leaks. If you gave me infos I would try
Very often the thing that it took was not its return value. also some of the functions according to jassCraft seem to not exist when i do a syntax check but if i use find it finds them.....
"Undeclared Function FJ" is what i mean by syntax check thinks they don't exist.
Same map as the one i used for the text out of line.
Re: Return Bug Finder
Posted: April 30th, 2011, 5:10 pm
by owner123
I've used the method before, and it works.
It doesn't find 1 then stop. Example is attached, run it through that.
There might be some sort of other error if it can't find it.
I dunno about the jasscraft errors. Try de-obfuscating the script with RMPQEx first.
Re: Return Bug Finder
Posted: May 1st, 2011, 2:37 pm
by stealer
I didn't explain very well.
your program finds the first error it sees and reports it and then pauses.
when you hit the x or ok(?) it then finds the next error it sees and then pauses.
rise and repeat.
haven't tried using rmpqex yet, my internet is pretty bad as of the past week.