Archian
Site Director
- Joined
- Jan 1, 2006
- Messages
- 3,206
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Maybe they finally got a world editor engineer. This seems like a positive update.
- The following features can now be found under Map Options
- Added the ability to force players to use a specific zoom level
- Added the ability to remove the ‘!’ from denying appearing
- Added a new ability [Amgi]. This ability prevents bouncing missile attacks from bouncing to and from structures
- Users will be able to modify the Targets Allowed field in this ability to modify which unit type will stop the bounces.
- Added a new ability [AUa2]. This ability is the new version of Animate Dead that allows units to carry over their abilities
That seems potentially quite useful, right? If I understand correctly, the main issue with using Orb-based abilities to proc other abilities on attack was that they only worked when the unit was issued an attack command. This is simple but important fix for that.
- Orb effects will now properly proc when units auto acquire targets.
Examples would help in case there is something related to how models and their portraits are made (integrated or do they have a separate portrait model to go with) and possibly other technical things.The portrait bug has unfortunately not been entirely fixed it seems.
In some cases yes, in many others not.
Could you please be a bit more explicit?they broke the quick cast mod
@Ralle?I wonder if maps saved on this patch could have some problems being uploaded on Hive. I tried uploading my map (saved on fresh 2.0.3) yesterday and today and I get http error 500 every time.
Out of Blizzard's scope and not a part of the original game. I guess it's something for the mod developer to fix/update.this patch broke quenching mod and its textures, any way to fix it ??
I wrote to both him and Archian, awaiting response.
1. Changing fields of passive now works instantly and doesn't require increasing/decreasing level of the ability?1. The following changes affect many natives and fields, and are an attempt to fix some broader systems instead of individual bugs. Please report any bugs (or new fixes!) related to these changes:
2. BlzSetUnitIntegerField now supports UNIT_IF_PRIMARY_ATTRIBUTE
- Fixed dozens of broken BlzSetAbility____Field natives
- BlzSetAbility____LevelField natives now attempt to forcibly refresh the ability’s data so changes are reflected. For example, orb of fire (AIf2) now has its damage bonus properly updated due to this change
Could you please be a bit more explicit?
Any specific custom or default model/unit in question ? i'd suggest a report in the PTR bug report section since they seem to be specifically paying attention to bugs that they are attempting to fix. Like me and Lycan managed to get them to fix and re-fix new abilities being added with the orb of slow and Animate Dead. So reason stands to suggest if you tell them "hey this is still not fixed here are examples" they might listen.The portrait bug has unfortunately not been entirely fixed it seems.
In some cases yes, in many others not.
call BlzSetAbilityStringLevelField(ability, ABILITY_SLF_TOOLTIP_NORMAL_EXTENDED, GetUnitAbilityLevel(unit, id) - 1, I2S(GetHandleId(unit)))
Can you put in the Blizzard forums that they should send you the new version of Warcraft 3 Previewer for their new game build?On another note, the lighting in Warcraft 3 Previewer broke.
There's a setting called "Stats - Hide Minimap Display" in the Object Editor that prevents units from showing up on the minimap.Does the Hide Minimap feature actually work? In my map, dummy units keep showing up on the minimap and it’s giving me a headache.
Dummy units (meaning a unit with the Locust ability) have never showed up on the map afaik.Does the Hide Minimap feature actually work? In my map, dummy units keep showing up on the minimap and it’s giving me a headache.
Yes, but I'm not sure however what exactly broke it. We can only wait for Blizzard to fix it.It seems like the new patch broke my Lock Camera on Unit, does this also happened to you guys?
or rather investing in and finding someone who could/wouldIt only took them 5+ years or something
Did they change the indexing on BlzSetUnitWeaponIntegerField?After the failed attempt on yesterday, it seems proper now.BlzSetUnitWeaponIntegerField now works properly with the following fields:
One day manipulating abilities will become obsolete, when all the integer and real natives work.
- UNIT_WEAPON_IF_ATTACK_MAXIMUM_NUMBER_OF_TARGETS
- UNIT_WEAPON_IF_ATTACK_DAMAGE_NUMBER_OF_DICE
- UNIT_WEAPON_IF_ATTACK_DAMAGE_SIDES_PER_DIE
- UNIT_WEAPON_IF_ATTACK_DAMAGE_BASE
Was it index 1-2 before?Did they change the indexing on BlzSetUnitWeaponIntegerField?
It seems all my old code that was using it no longer sets anything properly?
Actually, attack range works. [Snippet] Set unit range partial fix & Set unit AoE Small fix
