Is there a way to open a map edited with Reforged WE on an older version WE?

Status
Not open for further replies.
Level 2
Joined
Nov 2, 2016
Messages
13
Well, title. I also tried to export and import the data individually but that crashes the old editor. I want to be able to host my map on Reforged as well as Gameranger where everyone still uses version 1.24. I would really really appreciate your help.
 
Level 2
Joined
Nov 2, 2016
Messages
13
I think there are tools that can be used to port to older versions. However be aware that any content requiring newer features of the editor may be lost in the process.
Can you direct me to them? And yeah I plan to handle the inconsistencies, it's just so much easier if I can port everything first. Btw thank you :)
 
Level 33
Joined
May 14, 2021
Messages
1,492
Well, title. I also tried to export and import the data individually but that crashes the old editor. I want to be able to host my map on Reforged as well as Gameranger where everyone still uses version 1.24. I would really really appreciate your help.
Can you direct me to them? And yeah I plan to handle the inconsistencies, it's just so much easier if I can port everything first. Btw thank you :)
Check out this thread, it might help you:
Map Adapter
 
Level 2
Joined
Nov 2, 2016
Messages
13
The description was outdated so I updated it, since v1.0.0 you can target any patch as long as you have the required game files.

Hello developer! :)

I cannot figure out how to select older patches. Can you help?

Oh also, do these errors mean I won't be able to port any trigger and object editor data?
 
Last edited:
Level 19
Joined
Jan 1, 2018
Messages
739

Hello developer! :)

I cannot figure out how to select older patches. Can you help?

Oh also, do these errors mean I won't be able to port any trigger and object editor data?
Have you set up the appsettings.json file? The target patch in v1.0.0 of the tool only shows the patches that you added to this file, and if there's only one option the dropdown is disabled.
The errors may be caused by your appsettings. If you click on the files you can see what the error is.
 
Level 2
Joined
Nov 2, 2016
Messages
13
Have you set up the appsettings.json file? The target patch in v1.0.0 of the tool only shows the patches that you added to this file, and if there's only one option the dropdown is disabled.
The errors may be caused by your appsettings. If you click on the files you can see what the error is.
Sorry if I am missing something, but how do I set up appsettings?
 
Level 19
Joined
Jan 1, 2018
Messages
739
Sorry if I am missing something, but how do I set up appsettings?
Since you want to target patch 1.24, you should first use an MPQ extractor to get the required game files ("units\unitdata.slk", etc).
Then you change the appsettings.json file to this, where the GameDataPath is the location to where you extracted the game files:
JSON:
{
  "TargetPatches": [
    {
      "Patch": "v1_24e",
      "GameDataPath": "C:\\PathToExtractedMpq"
    }
  ]
}

Then the tool will search for the files it needs, for example at "C:\PathToExtractedMpq\units\unitdata.slk".
 
Level 2
Joined
Nov 2, 2016
Messages
13
Since you want to target patch 1.24, you should first use an MPQ extractor to get the required game files ("units\unitdata.slk", etc).
Then you change the appsettings.json file to this, where the GameDataPath is the location to where you extracted the game files:
JSON:
{
  "TargetPatches": [
    {
      "Patch": "v1_24e",
      "GameDataPath": "C:\\PathToExtractedMpq"
    }
  ]
}

Then the tool will search for the files it needs, for example at "C:\PathToExtractedMpq\units\unitdata.slk".

Am I doing all correctly? I extracted the map data and set the path on appsettings + browsed to the same map on Map Adapter. There still are ParseErrors and AdapterErrors. While trying to open the adapted map, Worldedit seems to get stuck loading the triggers.
 
Level 19
Joined
Jan 1, 2018
Messages
739

Am I doing all correctly? I extracted the map data and set the path on appsettings + browsed to the same map on Map Adapter. There still are ParseErrors and AdapterErrors. While trying to open the adapted map, Worldedit seems to get stuck loading the triggers.
The world editor cannot open the triggers (war3map.wtg) because due to the error it couldn't be parsed and adapted. To parse the file you need to have "ui\triggerdata.txt", can you check that this file exists? (at C:\Users\...\x64\Work\ui\triggerdata.txt)
EDIT: And can you show what the error is when you click on the files which have an error?
 
Level 2
Joined
Nov 2, 2016
Messages
13
The world editor cannot open the triggers (war3map.wtg) because due to the error it couldn't be parsed and adapted. To parse the file you need to have "ui\triggerdata.txt", can you check that this file exists? (at C:\Users\...\x64\Work\ui\triggerdata.txt)
EDIT: And can you show what the error is when you click on the files which have an error?

triggerdata.txt doesn't exist. Why?
war3map.wtg is there.
There's an error message for ParseErrors and I can also click on them to open another window, but there's nothing for AdapterErrors.
 
Level 19
Joined
Jan 1, 2018
Messages
739

triggerdata.txt doesn't exist. Why?
war3map.wtg is there.
There's an error message for ParseErrors and I can also click on them to open another window, but there's nothing for AdapterErrors.
Might have to do with the game data structure being different on older patches, I only have 1.31 myself so that's what I used to determine the relative paths.
Can you show me the contents of the folder where you extracted the mpq?
I think older patches also had multiple mpq files, you could try extracting a different one to see if triggerdata.txt and the other files are in there.
 
Level 2
Joined
Nov 2, 2016
Messages
13
Might have to do with the game data structure being different on older patches, I only have 1.31 myself so that's what I used to determine the relative paths.
Can you show me the contents of the folder where you extracted the mpq?
I think older patches also had multiple mpq files, you could try extracting a different one to see if triggerdata.txt and the other files are in there.
The map I'm trying to adapt to 1.24e was edited on the latest version of Reforged (or well some months ago)
I tried extracting a few more maps but none of them have triggerdata.txt
Edit: Both 1.24e and latest version maps don't have triggerdata.txt files when extracted, as far as I can see
 
Level 19
Joined
Jan 1, 2018
Messages
739
The map I'm trying to adapt to 1.24e was edited on the latest version of Reforged (or well some months ago)
I tried extracting a few more maps but none of them have triggerdata.txt
Edit: Latest version maps also don't have triggerdata.txt files when extracted
You extracted the map (which my tool already does for you), not the game files. You have to extract the mpq of 1.24 in program files (or wherever you installed it).
 
Level 2
Joined
Nov 2, 2016
Messages
13
You extracted the map (which my tool already does for you), not the game files. You have to extract the mpq of 1.24 in program files (or wherever you installed it).
So, I need to convert the map to mpq, then set the GameDataPath to that mpq, then also browse to the mpq on the application?
Or do I set GameDataPath to mpq and then browse to the w3x?
Or do I set GameDataPath to the extracted mpq and then browse to the w3x? Or browse to the mpq?

Sorry it's a bit confusing :)

Edit: Ohh I get it now sorry, the mpq does not have anything to do with the map. It's the War3Patch.mpq right?
 
Level 19
Joined
Jan 1, 2018
Messages
739
So, I need to convert the map to mpq, then set the GameDataPath to that mpq, then also browse to the mpq on the application?
Or do I set GameDataPath to mpq and then browse to the w3x?
Or do I set GameDataPath to the extracted mpq and then browse to the w3x? Or browse to the mpq?

Sorry it's a bit confusing :)
An mpq file is basically a .zip file. Your map file (.w3x, .w3m) are also mpq files. You don't have to extract the .w3x/.w3m because my tool already does this (because it needs to show you what files are inside).
So outside of my tool, you don't do anything with the map file. Instead you need to find your 1.24 installation and extract the mpq file that's in there. I can't show you what it looks like because I only have 1.31, which uses CASC instead of MPQ.
Then you set the GameDataPath to the folder to which you extracted the game files.
EDIT: Posted before I saw your edit, yes you need to extract War3Patch.mpq
 
Level 2
Joined
Nov 2, 2016
Messages
13
An mpq file is basically a .zip file. Your map file (.w3x, .w3m) are also mpq files. You don't have to extract the .w3x/.w3m because my tool already does this (because it needs to show you what files are inside).
So outside of my tool, you don't do anything with the map file. Instead you need to find your 1.24 installation and extract the mpq file that's in there. I can't show you what it looks like because I only have 1.31, which uses CASC instead of MPQ.
Then you set the GameDataPath to the folder to which you extracted the game files.
EDIT: Posted before I saw your edit, yes you need to extract War3Patch.mpq

I did that and now there's one ParseError left. How can I take care of that?


WE still gives an error regarding triggers.
 
Level 19
Joined
Jan 1, 2018
Messages
739

I did that and now there's one ParseError left. How can I take care of that?


WE still gives an error regarding triggers.
Since war3map.wtg did get parsed now I'm guessing common.j is in a different location on older patches.
You could try locating it and then moving it to the location that my tool expects.

The object data files probably have the same issue where one or more required files cannot be found, it just doesn't show the file it cannot find.
The required files are found here: War3App/PathConstants.cs at master · Drake53/War3App
For example, to adapt war3map.w3a it requires the files "units\abilitydata.slk" and "units\abilitymetadata.slk".

The world editor can't open the map/triggers because the war3map.wtg file is incompatible. My tool only handles changing the format to an earlier version so older patches can read it, but this file also requires triggerdata.txt to be read. triggerdata.txt defines for every trigger event/condition/action how many parameters it should have and what type they should have, for example the wait action has a single parameter of type real, and display text has two parameters, the first is a player group, the second a string. On newer patches, new events, conditions, and actions have been added, but these are not defined in the triggerdata.txt of older patches, so the war3map.wtg file can't be read on the older patch even if the format version is made to be compatible (note that because triggerdata.txt is incompatible, my tool doesn't actually adapt the file, so it still has the new format version. if the file were adapted you'd get a different error in the world editor, you can try this by replacing the triggerdata.txt from 1.24 (don't forget to make a backup) with the one from 1.32 (found here: https://raw.githubusercontent.com/D.../War3Net.Build.Core/Resources/TriggerData.txt)).
 
Last edited:
Level 2
Joined
Nov 2, 2016
Messages
13
Since war3map.wtg did get parsed now I'm guessing common.j is in a different location on older patches.
You could try locating it and then moving it to the location that my tool expects.

The object data files probably have the same issue where one or more required files cannot be found, it just doesn't show the file it cannot find.
The required files are found here: War3App/PathConstants.cs at master · Drake53/War3App
For example, to adapt war3map.w3a it requires the files "units\abilitydata.slk" and "units\abilitymetadata.slk".

The world editor can't open the map/triggers because the war3map.wtg file is incompatible. My tool only handles changing the format to an earlier version so older patches can read it, but this file also requires triggerdata.txt to be read. triggerdata.txt defines for every trigger event/condition/action how many parameters it should have and what type they should have, for example the wait action has a single parameter of type real, and display text has two parameters, the first is a player group, the second a string. On newer patches, new events, conditions, and actions have been added, but these are not defined in the triggerdata.txt of older patches, so the war3map.wtg file can't be read on the older patch even if the format version is made to be compatible (note that because triggerdata.txt is incompatible, my tool doesn't actually adapt the file, so it still has the new format version. if the file were adapted you'd get a different error in the world editor, you can try this by replacing the triggerdata.txt from 1.24 (don't forget to make a backup) with the one from 1.32 (found here: https://raw.githubusercontent.com/D.../War3Net.Build.Core/Resources/TriggerData.txt)).
So, if there's stuff in the object and trigger editor that the old version won't recognize, is it at all possible to port the map? I was thinking to delete the incompatible parts within the old editor.
 
Level 19
Joined
Jan 1, 2018
Messages
739
So, if there's stuff in the object and trigger editor that the old version won't recognize, is it at all possible to port the map? I was thinking to delete the incompatible parts within the old editor.
For the object editor it may be possible, but the triggers cannot be read if the file is incompatible, so you'd have to delete the incompatible parts using the 1.32 editor.
 
Level 2
Joined
Nov 2, 2016
Messages
13
For the object editor it may be possible, but the triggers cannot be read if the file is incompatible, so you'd have to delete the incompatible parts using the 1.32 editor.

Does this mean I can actually make it compatible by removing the special effect scale altering triggers? Even though there are also cooldown altering triggers as well and I know they aren't there in 1.24 WE.

I'll give it a try.
 
Level 19
Joined
Jan 1, 2018
Messages
739

Does this mean I can actually make it compatible by removing the special effect scale altering triggers? Even though there are also cooldown altering triggers as well and I know they aren't there in 1.24 WE.

I'll give it a try.
Only the first error is shown so there may be more incompatible functions than the special effect scale. If you remove them all then let the tool adapt the file to also make the format version compatible, then it should work.
 
Status
Not open for further replies.
Top