Challenges with UMSWE/WEU

[MindWorX]

I frequently get questions about UMSWE/WEU features, which I have been hesitant in implementing.

The issue with UMSWE/WEU is that it adds some changes which can result in maps being dependent on the editor. This makes maintaining your map a problem if any of these features ever gets removed. People have already been experiencing this after JNGP broke and their maps being completely unopenable without it. It also has a negative effect on other systems trying to parse your map, since the map is complete garbage without the UMSWE/WEU changes.

Because of this, I've been hesitant in adding it back in as a default feature.

What I have considered is adding a limited version of it back, with only the non-breaking features, which means it'll mostly just be the UI changes, like raw id in the object editor.

 

[Zwiebelchen]

This is imho not a huge problem. There is no reason ever to use the vanilla editor over WEX or JNGP. The most important feature of UMSWE was the extended tileset.

 

[Daffa]

I don't think it's much of a problem as long as it's in active development
Apparently, I really need UMSWE Trigger Editor right now (oh, might be better if I can get WEU in the package too)

 

[Ezekiel12]

I do not see a big problem with maps becoming dependant on the editor, it's just a requirement for extended features. As Daffa said, if the editor is in active development it's no problem. Open Source is a nice safety net here. I mean if we count VJASS, WEX maps are already dependant on WEX, right?

The problem I see is with the editor unlocking features the game might not support in the future.

Every additional feature should be considered separately how likely it is to break ingame in the future.

Can you name what is on your list?