Angle: 90
Flag: Offset area by angle must be set, offset area by radius is optional (extends radius by unit's radius)
Launch Location: Source Unit (must be the unit that you want to get the angle from)
I can't recreate this mistake, duplicate and copy+paste work for me.
The name editing window from the right panel contains 2 fields: key and name.
The key determines which storage location is used for the name. If 2 texts use the same storage location, they are bound to use the same name because they read the data from the same spot.
To fix that, just alter the key of one of your Marines and enter a proper name.
WoL had approx 28 missions, I believe, and HotS will have 20...
That was revealed a long time ago and was datamined after the current WoL patch presetend by Existor on teamliquid.net...
It has multiple story spoilers, so I stop talking about it. :D
I didn't decide, yet, if I want to have a hardcopy from a store which might have a better price or if I support Blizzard and buy it directly on Battle.net close to midnight...
On WoL release I got it very cheap at a store compared to bnet's price.
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.
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.
at some point its even better, since i had some problems with units amount displayed on minimap so most of them was hidden all the time and now at least you get at times idea that it exist there.
This.
Before it just didn't show other units, now you can have an idea that there are more.
It would still be cool, if we could define the value it uses for our maps (array size or whatever it is), just slap a hint on it that it may decrease performance, if value is greater than 2k.
1. Search "override" in trigger actions.
2. Use the one you find.
3. Execute that action for each player (-> loop) and override the player settings as you wish.
1. ctrl + F to search, then replicate the search window's settings. IMPORTANT: you need to chose "Preset" first and then "color". The editor doesn't output that properly.
2. Use search button until you find a "create dialog label" action.
3. Press replace.
4. Iterate step 2 and 3 until you fixed all labels occuring in your triggers.
0
Angle: 90
Flag: Offset area by angle must be set, offset area by radius is optional (extends radius by unit's radius)
Launch Location: Source Unit (must be the unit that you want to get the angle from)
0
I hope you don't mind that I use your image here to visualize the problem.
0
Bad fix:
Play with grid hotkeys :D
0
I can't recreate this mistake, duplicate and copy+paste work for me.
The name editing window from the right panel contains 2 fields: key and name.
The key determines which storage location is used for the name. If 2 texts use the same storage location, they are bound to use the same name because they read the data from the same spot.
To fix that, just alter the key of one of your Marines and enter a proper name.
0
WoL had approx 28 missions, I believe, and HotS will have 20...
That was revealed a long time ago and was datamined after the current WoL patch presetend by Existor on teamliquid.net...
It has multiple story spoilers, so I stop talking about it. :D
0
I didn't decide, yet, if I want to have a hardcopy from a store which might have a better price or if I support Blizzard and buy it directly on Battle.net close to midnight...
On WoL release I got it very cheap at a store compared to bnet's price.
0
Ask that in Blizzard's forums and hope one of the developers takes a few minutes to explain it to the community.
If no one posts, nobody really knows it.
0
I made a small list of fixes for problems occuring in the 2.0.4 patch.
You can find it here: here
(I linked multiple forums to that page in order to make it easier for me to update it.)
0
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.
0
Override player's gameplay settings via "Override Player Option" trigger action.
0
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.
0
Example map that hides the message log entries in the message window.
Enjoy. :)
0
This.
Before it just didn't show other units, now you can have an idea that there are more.
It would still be cool, if we could define the value it uses for our maps (array size or whatever it is), just slap a hint on it that it may decrease performance, if value is greater than 2k.
0
1. Search "override" in trigger actions.
2. Use the one you find.
3. Execute that action for each player (-> loop) and override the player settings as you wish.
0
I prefer my fix:
1. ctrl + F to search, then replicate the search window's settings. IMPORTANT: you need to chose "Preset" first and then "color". The editor doesn't output that properly.
2. Use search button until you find a "create dialog label" action.
3. Press replace.
4. Iterate step 2 and 3 until you fixed all labels occuring in your triggers.