64 tiles and BlizSetAbility fixes

[Barade]

Warcraft III: Reforged Patch Notes - Version 2.0.3

Warcraft III: Reforged Patch Notes Version 2.0.3 Build 23101 September 15, 2025 General Ctrl + C Camera lock will no longer track units that leave a players vision. Performance Added hints for AMD and Nvidia drivers to use discrete GPUs. World Editor Fixed an issue with BlizSetAbility____...

us.forums.blizzard.com

"Increased the Tileset limit from 16 to 64."

am I dreaming?

 

[Panda]

I feel like 64 is over doing it but it is rather nice to have more options.. Even for a bigger longer type maps.

• Added an option under the Advanced Tab: Preserve Copied Object Height. When enabled, the editor will remember the height an object was copied at when it is pasted.

This right here is amazing, so many doodads have to be resized all the time and it would be nice to freeze them and copy them to other areas...

 

[A]mun]

After some testing, the tilelimit seems to work pretty well (they even fixed the bug Retera reported

Spoiler: link

 

[Panda]

After some testing, the tilelimit seems to work pretty well (they even fixed the bug Retera reported

Spoiler: link

How are you able to test in the editor? When i update War3 in the App it says up to date..but, in my edtior it does not have Advanced Tab: Preserve Copied Object Height.

 

[Barade]

I really like this update but they could have fixed the rendering of more than 2 cliff types. The preserving feature is awesome, too but I did not need it in my map. Different water colors in the same map would be great too. Big multiplayer map feature many different locations. You can use fake water with models but they could also store a color flag.

Hopefully, some more improvements will come in the future

 

[Drake53]

I'm slightly annoyed by their decision to keep the version at 2.0.3 even though they're making changes to file structure for the tileset limit change

 

[deepstrasz]

I'm slightly annoyed by their decision to keep the version at 2.0.3 even though they're making changes to file structure for the tileset limit change

They've already skyrocketed from 1.36 to 2.0. I feel it's a meaningless detail and would actually help if you commented on the actual updates rather than bureaucracy dossier numbering.

 

[Panda]

Spoiler

View attachment 549311
View attachment 549312

Ahh okok.

I really like this update but they could have fixed the rendering of more than 2 cliff types. The preserving feature is awesome, too but I did not need it in my map. Different water colors in the same map would be great too. Big multiplayer map feature many different locations. You can use fake water with models but they could also store a color flag.

Hopefully, some more improvements will come in the future

I also would like more colored water types.. i see that as a nice feature to have. Would be nice if they had a suggestion box for such things but im sure they dont considering the amount of hate mail they would have.

 

[Drake53]

They've already skyrocketed from 1.36 to 2.0. I feel it's a meaningless detail and would actually help if you commented on the actual updates rather than bureaucracy dossier numbering.

Don't wanna derail the thread with my nitpick, but if you're working on library that has to implement these changes it gets confusing when 2.0.3 is the patch that introduced changes to the war3map.w3i file format, and patch 2.0.3 is also the patch that introduced changes to the war3map.w3e file format, but these are not the same patches.

 

[deepstrasz]

After some testing, the tilelimit seems to work pretty well (they even fixed the bug Retera reported

He made a proper post on the official site with explanations: Instead of Tile Limit Increase, Easier Faster Better Feature

 

[Homor]

My thoughts on this:

The original tileset limit was annoying but not gamebreaking. But I'm interested in seeing what people can do with less limitations.