Should we make [unreal-editor] a synonym of [unreal] tag?

Question

Last year, we've discussed if it would be a good idea to remove the tags unity-editor and inspector (the latter mainly referring to a tool from Unity) because they did not add anything significant to the site.

As such, unity-editor as been defined as a synonym of unity, and inspector has simply been blacklisted.

Should we do the same thing with unreal-editor: make it a synonym of unreal-4? Or does it really add value to the site?

At the same time, should the tag blueprints be kept or should we also make it a synonym of unreal-4? I understand that someone could be very knowledgeable with the feature, but it seems like a very specific part of a single engine, and where the search feature of the site would do just about the same job as the tag.

Answer 1

I think it is reasonable to alias unreal-editor to unreal.

I think blueprints is worth leaving alone, though, because it's a fairly complex sub-domain of the Unreal ecosystem and I can definitely see a place for a set of users who use Blueprints in Unreal extensively wanting to peruse those questions (and similarly for people who use Unreal exclusively with C++ to want to hide them).