• 🏆 Texturing Contest #33 is OPEN! Contestants must re-texture a SD unit model found in-game (Warcraft 3 Classic), recreating the unit into a peaceful NPC version. 🔗Click here to enter!
  • It's time for the first HD Modeling Contest of 2024. Join the theme discussion for Hive's HD Modeling Contest #6! Click here to post your idea!

Using vJass after the latest patch

Status
Not open for further replies.
Level 9
Joined
Jul 20, 2018
Messages
176
Made a simple guide to bypass the issue with JassHelper after the latest patch, so people can still develop and test their maps.

How to test a map

  1. (Optional) Update pjass.exe (watch vid for details). Note: you cannot replace the default pjass.exe, otherwise the game and the editor will not launch.
  2. Save your map ignoring all errors and close it in the editor.
  3. Open PowerShell in the JassHelper directory and launch jasshelper.exe with it:
Code:
./jasshelper.exe path_to_common.j path_to_blizzard.j path_to_map.w3x

If you want to enable debug mode use:
Code:
./jasshelper.exe --debug path_to_common.j path_to_blizzard.j path_to_map.w3x
More details in the attached manual.​

Then you can test your map in WC3. You can also relaunch the editor, this will force it to forget that the map had script errors, and you can even press test button successfully.

The attached vid demonstrates all steps above.

How to check a script

  1. (Optional) Update pjass.exe (watch vid for details). Note: you cannot replace the default pjass.exe, otherwise the game and the editor will not launch.
  2. Save your map ignoring errors. Do not close it.
  3. In Terrain Editor press File -> Export Script. Select any convenient place.
  4. Open PowerShell in the JassHelper directory and launch jasshelper.exe with it:
Code:
./jasshelper.exe --scriptonly path_to_common.j path_to_blizzard.j path_to_input.j path_to_output.j
path_to_input.j - it is your exported script.
path_to_output.j - any other path, I suggest temp.j.

If you want to enable debug mode use:
Code:
./jasshelper.exe --scriptonly --debug path_to_common.j path_to_blizzard.j path_to_input.j path_to_output.j
More details in the attached manual.​

This will run JassHelper over your script and report all errors found.

Notes

  1. PowerShell exists in every Windows build, however it can be deleted manually in the latest Windows builds. If it is deleted, use cmd instead. You can also have the latest PowerShell which can be run with pwsh keyword.
  2. Press Up Arrow key in PowerShell or cmd to insert the latest run command.
  3. To copy a path to the file, hold Shift and press Right Mouse Button over file (or press context menu button on your keyboard). This opens a context menu with additional options like "Copy as path".
  4. Debug mode was not working in WE since 1.31 due to incorrect integration.
  5. If you forget, debug mode disables vJass optimization.
 

Attachments

  • jasshelpermanual.zip
    63.4 KB · Views: 124
  • Use vJass after patch.mp4
    45.4 MB · Views: 307
Last edited:
Status
Not open for further replies.
Top