You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example, adding _BUILD\Worlds\TAT\munge.bat would auto-detect the Munged Files to be tat.lvl instead of tat2.lvl and tat3.lvl. This is because the application currently goes off of the first argument that's supplied to munge_world.bat, e.g.: @call ..\munge_world.bat TAT %1
A solution to this would be to add conditions for munging worlds that auto-detects the LVL outputs based on the world's REQ files. If it works out, might want to do this with sides as well, but that could become tricky since many sides have sub-REQ files that are compiled into a single LVL file.
The text was updated successfully, but these errors were encountered:
Additionally, it would be useful for the user to be able to browse for a REQ file and then auto-detect and add its associated munge batch file to the list.
For example, adding
_BUILD\Worlds\TAT\munge.bat
would auto-detect the Munged Files to be tat.lvl instead of tat2.lvl and tat3.lvl. This is because the application currently goes off of the first argument that's supplied to munge_world.bat, e.g.:@call ..\munge_world.bat TAT %1
A solution to this would be to add conditions for munging worlds that auto-detects the LVL outputs based on the world's REQ files. If it works out, might want to do this with sides as well, but that could become tricky since many sides have sub-REQ files that are compiled into a single LVL file.
The text was updated successfully, but these errors were encountered: