BlzCreateUnitWithSkin(player owner, integer baseId, real x, real y, real facing, integer modelId would actually be the base function of CreateUnit, with the latter passing either null or the baseId as the parameter for modelId. This would have unintended effects, (which might have already been stated) such as the merging of ability definitions (ability will functionally be the same, but will have their icons based on the modelId's ability list).BlzSetUnitSkin(unit, integer modelId) appears to transform the unit into the desired unit type, but might not display their model as a consequence.BlzSetDestructableSkin appears to have been commented out in the common.j. (Getting the common.j just requires you to save a map in JASS, and browsing the Documents for a Jasshelper folder in Warcraft Beta folder)
Not recommended to work on a beta or unstable version.
It's how it worked with PTRs and betas are supposed to be even more buggy.
The PTR versions of the editor are not exactly the same as what would go to Release and the difference between the two has caused compatibility issues for people who decided to develop on the PTR version anyway (the most common issue being something that was on the PTR did not make it to Release or changed between that version and Release).
To be honest, I use them as such: I don't even deploy handles/labels. I simply save all data as integer index of integer index in a hashtable and write down indices for each set of data. It helps to avoid confusion (and same numerical value of different handles) when you work with almost a hundred of hashtables.
All new trigger GUI actions I could find:
Events
Player - Button for ability Animate Dead and order Human Peasant - Repair pressed.
Conditions
(Load No sound of string from ) Equal to True
Actions
Cinematic - Set Dialogue Text ID For Sound No sound Dialogue Text ID abc
Game - Set Max Checkpoint Saves to 10
Visibility - Show Terrain: False
Set VariableSet CommandButtonEffectVariable = (Last created Button effect)
Unit - Set Unit Skin of (Triggering unit) to 'Hamg
Item - Set Item Skin of (Last created item) to 'tdx2'
Quest - Destroy Minimap Icon for (Last created minimap icon)
Yeah @lolreported can you switch to Classic and do that?
As far as I am aware with the 1.32 beta one can use both Reforged and Classic graphics. The Reforged graphics have an additional licence check.
1.32 will go live with Reforged or shortly before then. Reforged and classic will use the same client. Just Reforged graphics and campaign will be behind a pay wall/licence.
It should be some sort of hierarchical thing. Say, Tichondrius, Balnazaar has that. Detheroc is too fat and the demon's tail fell off due to constant inflammation.
I'm going to be drafting a long list of comments for Blizz on my input. I think they got so much right (even though most of what we hear is criticism).
That said, what strikes me immediately is how BAD the water graphics look. Both in game and in editor....in the editor it's almost completely translucent and in game it just looks ugly, dull, and doesn't stand out. I feel like even the older water graphics look better. Shallow water in particular looks completely transparent.
This really sucks for maps that want to emphasize water.
Am I alone here?
Pretty sure information here is being ciompiled and relayed to blizzard.
Yes I saw one trigger in the we that answers one of my requests to blizz
Not everyone who preordered has access yet, they are doing it in waves. But make sure you check in the battle.net app under 'region/account' when you click on warcraft 3, and see if it lets you switch to the reforged beta.
Ohhh, it works! Thanks man!
I agree on this, thought it looked kinda weird together
It has laready changed to cascsince 1.31 i think
