Patch 1.31 announced

[deepstrasz]

My mind and condolences for those brave enough to upgrade.

It's a PTR.

 

[loktar]

IIRC this is also the case in the live patch though, at least for some? If so I hope they change it back because otherwise it will break a lot of stuff.

 

[Rui]

Not offended at all?

The word you were looking for was "worrying", not "threatening".

 

[Kam]

The zero indexing has been the case since 1.31.0, it was omitted from the notes.

It refers specifically to the new natives in 1.31.

 

[Elbadruhel]

The word you were looking for was "worrying", not "threatening".

Idk what are u talking about, could u quote the other message next time? Jajaja (and i appreciate english lessons )

 

[Cokemonkey11]

New bug (REGRESSION)

The map variable limit has been lowered from ~25k to ~14k (not sure if it's related to memory or variable count)

This causes mapfiles that were previously working to now crash wc3 when selected in the custom game list

CC @WaterKnight @Kam

 

[Wrda]

New bug (REGRESSION)

The map variable limit has been lowered from ~25k to ~14k (not sure if it's related to memory or variable count)

This causes mapfiles that were previously working to now crash wc3 when selected in the custom game list

CC @WaterKnight @Kam

Hope thats temporary.
On second thought, who even uses such a high number of variables over 14k? Does this include the wc3 already existing variables?

 

[Ardenaso]

Did you feel too embarrassed to ask this to your parents or friends? Google it maybe? I mean, you are this old and still ask such a question. Makes me wonder if you live in Antarctica

I mean I had a shortcut but with the update the repair/launch window keeps on appearing with the same shortcut, and yes I did google.

 

[DracoL1ch]

Hope thats temporary.
On second thought, who even uses such a high number of variables over 14k? Does this include the wc3 already existing variables?

apparently 14k of YOURS vars, limit is higher but blz's vars add up
and yeah, there are cases when you may need 10k for sure. idk about 25k, sounds insane

 

[Blarto]

Hope thats temporary.
On second thought, who even uses such a high number of variables over 14k? Does this include the wc3 already existing variables?

Some heavy maps can use some 10,000 variables.

Each struct instance variable vjass-ed into a global array.
Each struct static variable vjass-ed into a global variable.

Reaching 14k isn't that out of the ordinary...

Any serious modding project will surpass it as they move to create object oriented architecture instead of the unscalable GUI/Jass styles.

Not necessarily a problem of WEdit, but of Vexorian dropping the ball and choosing to use array-based architecture for structs instead of heap/table based (tables are 40% slower but it doesn't matter 99% of the time)


.. Although i'm not sure what "variables" are being referred to here in this context...

 

[El Saif]

So, how does all of this natives work? i can see many, most of them is not working. I don't even know which natives are working.

Hidden

native BlzGetAbilityBooleanField                   takes ability whichAbility, abilitybooleanfield whichField returns boolean
native BlzGetAbilityIntegerField                   takes ability whichAbility, abilityintegerfield whichField returns integer
native BlzGetAbilityRealField                      takes ability whichAbility, abilityrealfield whichField returns real
native BlzGetAbilityStringField                    takes ability whichAbility, abilitystringfield whichField returns string
native BlzGetAbilityBooleanLevelField              takes ability whichAbility, abilitybooleanlevelfield whichField, integer level returns boolean
native BlzGetAbilityIntegerLevelField              takes ability whichAbility, abilityintegerlevelfield whichField, integer level returns integer
native BlzGetAbilityRealLevelField                 takes ability whichAbility, abilityreallevelfield whichField, integer level returns real
native BlzGetAbilityStringLevelField               takes ability whichAbility, abilitystringlevelfield whichField, integer level returns string
native BlzGetAbilityBooleanLevelArrayField         takes ability whichAbility, abilitybooleanlevelarrayfield whichField, integer level, integer index returns boolean
native BlzGetAbilityIntegerLevelArrayField         takes ability whichAbility, abilityintegerlevelarrayfield whichField, integer level, integer index returns integer
native BlzGetAbilityRealLevelArrayField            takes ability whichAbility, abilityreallevelarrayfield whichField, integer level, integer index returns real
native BlzGetAbilityStringLevelArrayField          takes ability whichAbility, abilitystringlevelarrayfield whichField, integer level, integer index returns string
native BlzSetAbilityBooleanField                   takes ability whichAbility, abilitybooleanfield whichField, boolean value returns boolean
native BlzSetAbilityIntegerField                   takes ability whichAbility, abilityintegerfield whichField, integer value returns boolean
native BlzSetAbilityRealField                      takes ability whichAbility, abilityrealfield whichField, real value returns boolean
native BlzSetAbilityStringField                    takes ability whichAbility, abilitystringfield whichField, string value returns boolean
native BlzSetAbilityBooleanLevelField              takes ability whichAbility, abilitybooleanlevelfield whichField, integer level, boolean value returns boolean
native BlzSetAbilityIntegerLevelField              takes ability whichAbility, abilityintegerlevelfield whichField, integer level, integer value returns boolean
native BlzSetAbilityRealLevelField                 takes ability whichAbility, abilityreallevelfield whichField, integer level, real value returns boolean
native BlzSetAbilityStringLevelField               takes ability whichAbility, abilitystringlevelfield whichField, integer level, string value returns boolean
native BlzSetAbilityBooleanLevelArrayField         takes ability whichAbility, abilitybooleanlevelarrayfield whichField, integer level, integer index, boolean value returns boolean
native BlzSetAbilityIntegerLevelArrayField         takes ability whichAbility, abilityintegerlevelarrayfield whichField, integer level, integer index, integer value returns boolean
native BlzSetAbilityRealLevelArrayField            takes ability whichAbility, abilityreallevelarrayfield whichField, integer level, integer index, real value returns boolean
native BlzSetAbilityStringLevelArrayField          takes ability whichAbility, abilitystringlevelarrayfield whichField, integer level, integer index, string value returns boolean
native BlzAddAbilityBooleanLevelArrayField         takes ability whichAbility, abilitybooleanlevelarrayfield whichField, integer level, boolean value returns boolean
native BlzAddAbilityIntegerLevelArrayField         takes ability whichAbility, abilityintegerlevelarrayfield whichField, integer level, integer value returns boolean
native BlzAddAbilityRealLevelArrayField            takes ability whichAbility, abilityreallevelarrayfield whichField, integer level, real value returns boolean
native BlzAddAbilityStringLevelArrayField          takes ability whichAbility, abilitystringlevelarrayfield whichField, integer level, string value returns boolean
native BlzRemoveAbilityBooleanLevelArrayField      takes ability whichAbility, abilitybooleanlevelarrayfield whichField, integer level, boolean value returns boolean
native BlzRemoveAbilityIntegerLevelArrayField      takes ability whichAbility, abilityintegerlevelarrayfield whichField, integer level, integer value returns boolean
native BlzRemoveAbilityRealLevelArrayField         takes ability whichAbility, abilityreallevelarrayfield whichField, integer level, real value returns boolean
native BlzRemoveAbilityStringLevelArrayField       takes ability whichAbility, abilitystringlevelarrayfield whichField, integer level, string value returns boolean

// Item 
native BlzGetItemAbilityByIndex                    takes item whichItem, integer index returns ability
native BlzGetItemAbility                           takes item whichItem, integer abilCode returns ability
native BlzItemAddAbility                           takes item whichItem, integer abilCode returns boolean
native BlzGetItemBooleanField                      takes item whichItem, itembooleanfield whichField returns boolean
native BlzGetItemIntegerField                      takes item whichItem, itemintegerfield whichField returns integer
native BlzGetItemRealField                         takes item whichItem, itemrealfield whichField returns real
native BlzGetItemStringField                       takes item whichItem, itemstringfield whichField returns string
native BlzSetItemBooleanField                      takes item whichItem, itembooleanfield whichField, boolean value returns boolean
native BlzSetItemIntegerField                      takes item whichItem, itemintegerfield whichField, integer value returns boolean
native BlzSetItemRealField                         takes item whichItem, itemrealfield whichField, real value returns boolean
native BlzSetItemStringField                       takes item whichItem, itemstringfield whichField, string value returns boolean
native BlzItemRemoveAbility                        takes item whichItem, integer abilCode returns boolean

// Unit 
native BlzGetUnitBooleanField                      takes unit whichUnit, unitbooleanfield whichField returns boolean
native BlzGetUnitIntegerField                      takes unit whichUnit, unitintegerfield whichField returns integer
native BlzGetUnitRealField                         takes unit whichUnit, unitrealfield whichField returns real
native BlzGetUnitStringField                       takes unit whichUnit, unitstringfield whichField returns string
native BlzSetUnitBooleanField                      takes unit whichUnit, unitbooleanfield whichField, boolean value returns boolean
native BlzSetUnitIntegerField                      takes unit whichUnit, unitintegerfield whichField, integer value returns boolean
native BlzSetUnitRealField                         takes unit whichUnit, unitrealfield whichField, real value returns boolean
native BlzSetUnitStringField                       takes unit whichUnit, unitstringfield whichField, string value returns boolean

// Unit Weapon
native BlzGetUnitWeaponBooleanField                takes unit whichUnit, unitweaponbooleanfield whichField, integer index returns boolean
native BlzGetUnitWeaponIntegerField                takes unit whichUnit, unitweaponintegerfield whichField, integer index returns integer
native BlzGetUnitWeaponRealField                   takes unit whichUnit, unitweaponrealfield whichField, integer index returns real
native BlzGetUnitWeaponStringField                 takes unit whichUnit, unitweaponstringfield whichField, integer index returns string
native BlzSetUnitWeaponBooleanField                takes unit whichUnit, unitweaponbooleanfield whichField, integer index, boolean value returns boolean
native BlzSetUnitWeaponIntegerField                takes unit whichUnit, unitweaponintegerfield whichField, integer index, integer value returns boolean
native BlzSetUnitWeaponRealField                   takes unit whichUnit, unitweaponrealfield whichField, integer index, real value returns boolean
native BlzSetUnitWeaponStringField                 takes unit whichUnit, unitweaponstringfield whichField, integer index, string value returns boolean

 

[Th= KA+]

!

I recently updated my Warcraft 3 folder to 1.31 patch. I was looking forward to play some custom maps I downloaded which only allowed 1.30 or now (1.31) patch.
Anyways, I lost all my files I downloaded (Thank God I kept a back-up of them) but when I put it back in the Warcraft 3 folder, it says "This application has encountered a critical error: Not enough memory resources are available to process this command."
Cheers..
- Th= KA+

 

[deepstrasz]

Anyways, I lost all my files I downloaded (Thank God I kept a back-up of them) but when I put it back in the Warcraft 3 folder, it says "This application has encountered a critical error: Not enough memory resources are available to process this command."

Which executable are you running, the one from the x86_x64 or x86 folder? And on which operating system?

 

[Recklessness]

If I update my map to use this patch will it be transferable to forged?

 

[Wrda]

Reforged will be bound to classic, so it will be compatible.
It's been said a thousand times.

 

[kentzeus]

Is 1.31 still PTR, or is it a live version? Because I get the question if I want to update to 1.31 in the game but nothing happens when I do.

 

[deepstrasz]

Is 1.31 still PTR, or is it a live version? Because I get the question if I want to update to 1.31 in the game but nothing happens when I do.

No, 1.31.1 is live for some time.

 

[Jazztastic]

I am finally able to open my (almost finished) map again after half a year of frustration. I never got info that I was supposed to use a different launcher from the one I had been using for 10+ years. Why are there four launchers for WC and WE now??

Is there a spot I can get up to date on fixing my code and map? A bunch of stuff that used to work now goes kaput or crashes game on usage and I'd rather learn the new patch than make 20 something posts in the GUI help category. Also small chance but does anyone know if Bribe's unit indexer + associated packages still work on new patch environment?

 

[Deleted member 238881]

No, 1.31.1 is live for some time.

Is everything fixed or is it still buggy as shit?

 

[deepstrasz]

Is everything fixed or is it still buggy as shit?

Buggy. Wouldn't recommend. Better use 1.30 instead.

 

[Deleted member 238881]

Better use 1.30 instead.

Already reversed to it some time ago, but thx 4 reply anyway.

When I tried 1.31.1 few months ago, there were bugs even in campaigns.

 

[deepstrasz]

When I tried 1.31.1 few months ago, there were bugs even in campaigns.

We'll have to wait for 1.32 when Reforged comes out. Hopefully, most pressing bugs will be fixed.

 

[Deleted member 238881]

They made so many changes in game so I think they altering source code itself. If I'm right they could add legit liquid lava, reverse 1 - 12 player colors to state like they were before 24 players update (brown would again look like brown, not like orange), make all tiles enabled to swap, make possible to add more cliff types, make blight work on cliffs/underwater and alter colors of selection line/circles:

blue - player, AI allies in control & human allies,
green - AI allies,
yellow - neutral,
red - enemies.

 

[Wlizer]

They made so many changes in game so I think they altering source code itself. If I'm right they could add legit liquid lava, reverse 1 - 12 player colors to state like they were before 24 players update (brown would again look like brown, not like orange), make all tiles enabled to swap, make possible to add more cliff types, make blight work on cliffs/underwater and alter colors of selection line/circles:

blue - player, AI allies in control & human allies,
green - AI allies,
yellow - neutral,
red - enemies.

I agree with you so much, I dont like 24 player colors, some colors are too similar. But it could be an extra feature that you could manually add to custom game, but they should revert ladder and all other things have just 12 standart colors.

Hell, I could even think that having multiple players with same color is better than what it is now. You could forexample make 3 player blue color and 2 player red, one white, one dark, and so forth using just standart 15 colors or how much it originally had.

Playing big game with team players having two or three same color doesnt really matter because there are already so many players, just increase the player limit to 24 separately it was good idea.

 

[kentzeus]

Buggy. Wouldn't recommend. Better use 1.30 instead.

What's buggy about it? I've recently updated from 1.30 and I'm very pleased with using 1.31 now. It being very buggy in the beginning and breaking maps and shit is what freightened me from using it earlier, but now it seems smooth to me. It's especially chill when making tooltips

 

[deepstrasz]

What's buggy about it? I've recently updated from 1.30 and I'm very pleased with using 1.31 now. It being very buggy in the beginning and breaking maps and shit is what freightened me from using it earlier, but now it seems smooth to me. It's especially chill when making tooltips

1.31.1 [Bug] Loading saved game breaks some unit events
as well as the melee AI still not working properly and campaign bugs.

 

[Wlizer]

1.31.1 [Bug] Loading saved game breaks some unit events
as well as the melee AI still not working properly and campaign bugs.

I tried most recent version of the editor about couple weeks ago, I only touched some terrain/doodads inside the editor. When it crashed and destroeyd 30min work I decided I will not use that.

 

[deepstrasz]

I tried most recent version of the editor about couple weeks ago, I only touched some terrain/doodads inside the editor. When it crashed and destroeyd 30min work I decided I will not use that.

Yeah, there have been reports that copying terrain would crash the editor.

 

[Wlizer]

Yeah, there have been reports that copying terrain would crash the editor.

I did not copy the terrain. I was doing the most basic things u could have ever done. No triggering, no touch special featuer or anything else than I was just tuning my terrain a little bit by moving some doodads, and reterrain some water parts.

Everything I did had been rock solidly working since the release of the frozen throne: i know the editor, so its new bug.

 

[deepstrasz]

Everything I did had been rock solidly working since the release of the frozen throne: i know the editor, so its new bug.

You should detail this more on the bugs thread: [Feedback] Compiled List of Bugs & Issues for 1.30.1+

 

[UmbraUnda]

I can confirm that when I work on a complex 480x480 map with lots of doodads, terrain variety and units - When selecting or copying terrain... all it takes is an accidental left click drag, selecting a tiny section of terrain, editor immediately crashes if done after the first 5 minutes of using the program.
If it's done at the beginning, right after opening the map, it works fine. I'll post a more detailed on the Bugs and Issues Thread soon.

 

[Wlizer]

You should detail this more on the bugs thread: [Feedback] Compiled List of Bugs & Issues for 1.30.1+

I think I created separate thread before, but its not the point.

The point is that the editor seems to be beyond comprehension broken. Something unthinkable issue that is linked with all kind of other issues and fixing those other issues doesnt fix the root problem.

 

[HIGH_WAR_LORD]

• Scripts can now detect when any unit is damaged
• Scripts can now detect and modify the damage done before armor
• Scripts can now detect and modify the attack type, damage type, and weapon type (Note, modifying these only works in the pre-armor event

Does that means we can use triggers for damage of spells like breath of frost,etc?

 

[Deleted member 238881]

Has anyone cracked .data files yet? There is no .mpq anymore for... one year now?

 

[loktar]

Casc Storages - Main page

 

[Devalut]

@HIGH_WAR_LORD
Still nothing that I can see that could detect individual spell casts, do you need help with that?

 

[Deleted member 238881]

Casc Storages - Main page

Thaaaaaankyyouuuuuu!!

EDIT
Hmm... Since standalone W3 Classic is no more - therefore it won't be updated - I suggest closure of this topic.