The problem is that setting a color to a dialog button, the button's text and the button's appearance is tinted with that color.

I found a fix to tint a button and keep the text in another color.


1. DON'T modify the color of the dialog button, leave it as it is. Then the text will use the text's own color controlled by color tags within the text. It doesn't seem to be possible to undo the color setting.

2. Use these 2 actions to define the color of your button.


The button keeps turning gray, if you disable it, so there is nothing to worry about that.

As a result, the button is tinted in the desaturation color and the text uses its own color.

The "world console bottom" setting was removed from GameUI in the data module. It has found a new place in the UI module.
UI layout code to set it:


To fix the error with the unread value, make a change in the Game UI in data, save the map, revert the change and save the map again. Then that tab's info in data is updated removing the entries in the xml that aren't used anymore.

The new menu bar uses an anchor frame to determine its position. It has 2 frames located in "GameUI/UIContainer/FullscreenUpperContainer/".

First method to move it is using code in the UI editor like this:

Thanks for Fen1kz for pointing out that this works fine. Seems like I failed pretty hard when I tried to alter it in my map.


Another method is moving the frame via trigger:
Here is an example of trigger actions required to move its position:

This converts a frame from the UI to a dialog item, in this case the panel that contains the menu bar.
You need to know that hooking up UI frames only works once in the game, so I strongly advised you to save the reference to that dialog item in a global variable to be able to edit it at any time during runtime.

This error appears when you are moving frames around with code in the UI module. This appears when you use the 2 opposite anchors of a panel. An example would be moving the minimap from the bottom left anchors of the screen to the top right anchors.
The code is working, but it creates warning messages in the ingame error log window in the top area of the screen.
No fix found, yet. If you are desparate you could hide that frame via triggers executed after a small delay in map initialization as explained by Helral.

Blizzard added actor events for the basic unit actors for that. Sadly this means that your own units might not have these new actor events because you accidentially override it because of the used data structure.

Height changes are now setting a property that somehow alter the death of the unit. Zerg units will die with a blood explosion, Terran & Protoss units in their race's explosion.

In case this is happening for your units, you need to add it to your map or try to fix your actor events. I've no reliable, easy solution, so resetting the actor events and doing them again might be the easiest way in some cases:
1. backup your map, screenshot your actor events
2. reset actor events via right click -> reset to parent value -> first thing in the list that was made by Blizzard (usually the first option)
3. recreate your actor events

Also, this new addition can cause problems with units that you raise (for example for units you raise out of the ground at spawn [uses negative default unit height]):
- raising a unit will make it enter that state
- add a "Validate unit" with "Is Flying" to the event that sets the flying state for the unit.