As far as I know problem 1 is caused by a bug in RtC that slipped in in version 5c. So make sure that RtC is turned off or use v5b.
Also if you're running on a war3 version higher than 1.21b make sure that war3err etc. are disabled.
I really hope those suggestions were a joke.
Anyway, yeah, the JassHelper thread would be the best place to post your ideas, although I'm sure Vexorian won't consider any one of them.
No offense meant of course.
We've changed how the dll injection works from 1.4 to 1.5 because for many people the old method didn't work after the 1.21 warcraft III patch.
If 1.4 works for you then that should be ok.
PS: If you're worried about viruses, you can check the source code at...
Well, it's technically not a downgrade since they didn't add anything nor change anything in the 1.22 editor.
Only thing they did is recompile it with a different compiler.
Here's an upate for you. I hope it fixes most of the problems with 1.22. War3err and japi are still not up to date, but I've included details on how to get them work with a dual install of War3.
Here's the changelog anyway:
$ works for 1.22 (except war3err/japi)
$ most recent JassHelper...
Just change the path in the registry to your first installation and apply patch 1.22, then change the registry path to your other installation and install the other patch.
I just posted a small Hotfix for the ObjectMerger and UMSWE here: http://wc3campaigns.net/showpost.php?p=1025512&postcount=942
Attention, this does NOT fix the 1.22 problems.
Make sure that JassHelper is enabled in the menu.
If it is disabled the vJass code doesn't get compiled and the script can't be read in game.
To check if it's enabled correctly you can put an intentional error in your jass and see if pjass brings up an error window.
The types Unit, Item and Destructable are all derived from Widget, so if it asks for a widget you can pass in any of those.
For example try
call GroupTargetOrder(g, "attack", myunit)
where myunit is a unit variable.
You do not need to know python, you just need it installed to run the debugger.
There is also a standalone version that doesn't require Python here
The Grimoire manual explains how to install and use it.
Switching editors is really no problem as long as you get rid of the advanced WEU triggers.
Nolimits has to be enabled in NewGen, it is disabled by default.
For damage detection you're better off with one of those damage detection systems that can be found in the resource database of wc3c.
Cliff tiles are doable in the NewGen editor as well. (Extensions\Edit Tileset) Check out the Grimex manual for more details.
Well the thing about crashes it a myth. If a map crashes it is not caused by WEU but by bad coding or by an error in the game or editor that was there in the first place. People just think because they are using some tool, everything bad that happens to them is because of said tool.
It is true...