[Solved] Modify Map Bounds.

[Azgarzîr]

What is going on? Since this update the Modify Map Bounds keep on crashing.
I tried to make the map 32x32 so I don't have to make it 224x224 if I want to get to that length I would just increase 32x32 to 224x224.

-The problem is everytime I try to make it bigger it keeps on crashing the editor. Does anyone found a solution to this annoying crash?
It does not matter if I go from 32x32 to 64x64 or from 32x32 to 224x224 the result is the same.

I am just asking because maybe someone found a way around this great "Feature" of the new patch.

 

[A]mun]

Weird finds:
Open the map, immediately close it -> open it again -> then make your changes and save.
I could get from 32 to 192 this way.

However:
Somehow i can't get to 224. Trying some things now.
No luck so far, tried making a 224 map, keep it open and then adjust my 192
^It actually works when going to 256, then reduce it to 224 in the next step.

 

[Elprede]

The following method worked each time without crashing: First, modify the map bounds to the dimensions that you desire, and then modify the Camera Bounds to the limit of the new dimensions.

 

[Peacehagen]

Elpredes suggestion is probably easiest solution if it works, I havnt tried.

What worked for me was a suggestion from another post where I had to:

1. Export all triggers, then remove them from the map.
2. Select all Regions in the map and ctrl+x
3. Change map boundaries to desired size.
4. Ctrl+v and place the regions back
5. Import the triggers again.

Triggers will however lose all references so you need to fix those.

If I need to do this again though I will try Elpredes method first

 

[Azgarzîr]

-Thank you all for the replay.
I have also found a way after I tried your suggestions.

-The solution I found is that when you create a map just make it big enough 480x480 and then make it smaller from all sides and it will not crash anymore.
You can make it 32x32 and then increase it and would not crash anymore.

 

[Ben128]

I got the same problem and none of the solutions provided worked.

But another thing worked for me :

• Make sure camera bounds and map bounds are exaclty the same (it's a bit different on map creation) . Click ok.
• When you want to change maps bounds you then have to change the camera bounds at the same time, to make sure it's the same before cliking ok.
• You then can change the camera bounds (only) to adjust it as you want.

 

[Datnes]

If you cant change map bounts, you can atlast change bounds when creating new map. Which works.

 

[Macielos]

Greetings from mid 2024, Blizz still hasn't fixed their shit. It definitely happens in several different edge cases. So far I encountered two scenarios:

A crash in a single map - here A]mun's solution (open -> close -> open -> extend) worked for me.

A crash when extending a campaign map with custom assets - it happens every time in my case. I know it's not your case, but maybe it'll help someone. Plus the solution is so damn hilarious that I just can't help describing it somewhere .
1. Export custom object data from your campaign and import to the same map, but in object editor.
2. Export a map (without saving it).
3. Close a campaign/restart editor and open the exported map. You'll see missing custom objects, but their references will be fine.
4. Now you can freely extend your map.
5. Save and close the map.
6. Clean up the custom object mess - open a map with e.g. mpqmaster and remove custom data files:
war3map.w3a
war3map.w3d
war3map.w3d
war3map.w3h
war3map.w3q
war3map.w3t
war3map.w3u
war3mapSkin.w3a
war3mapSkin.w3d
war3mapSkin.w3d
war3mapSkin.w3h
war3mapSkin.w3q
war3mapSkin.w3t
war3mapSkin.w3u
7. Then finally you can import your map back to your campaign.