- Joined
- Jun 23, 2007
- Messages
- 4,065
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.
Still buggy as hell lmao.
I tried Dark Ranger with Drain Life and a custom unit with Siphon Mana (unit ability) and they seem to be working fine.Are any of you having difficulty with Drain-based skills in your maps? Anything based on drain in my map seems to be draining health from the target AND the caster.
Instead of being harsh and launching out negative things about some features that have problems at the moment and will be soon solved, you could all be thankful to the fact that Blizzard is still f***king working on this game. Released in 2002-2003 and still played and updated and YOU complain about problems that appear from time to time and they are soon solved. Have you ever wondered how hard is to work on a game? How much pressure does that team have upon them? Harsh comments like "it's buggy and it will always be like that" are not helping them. Instead, you could try to point out those problems in a better way with suggestions and proper feedback, unlike "IT DOES NOT WORK, SHOO BLIZZARD". Might get some hate from those that posted things like those but I assume this.
I think you actually might hate yourself.The new patch is the worst thing Blizzard ever released for Warcraft 3.
SAME SAME SAME AND I F***ING HATE IT.
I tried Dark Ranger with Drain Life and a custom unit with Siphon Mana (unit ability) and they seem to be working fine.
Are you talking about the new 1.31.1? According to the patch notes those issues introduced with 1.31 proper should have been fixed.
Map Options: default version, latest melee patch? Check those.Thanks, I copied some of my units and abilities into a fresh map, and the abilities worked fine. But in my own map, these abilities are not working correctly. I'll keep trying to find the bug.
Instead of being harsh and launching out negative things about some features that have problems at the moment and will be soon solved, you could all be thankful to the fact that Blizzard is still f***king working on this game. Released in 2002-2003 and still played and updated and YOU complain about problems that appear from time to time and they are soon solved. Have you ever wondered how hard is to work on a game? How much pressure does that team have upon them? Harsh comments like "it's buggy and it will always be like that" are not helping them. Instead, you could try to point out those problems in a better way with suggestions and proper feedback, unlike "IT DOES NOT WORK, SHOO BLIZZARD". Might get some hate from those that posted things like those but I assume this.
The subject title is not related to DotA.I am maintaining the 6.85ne DotA map for the Battle.net community (fixed 20+ bugs and added some useful features). The last 1.31 patch now caues all DotA maps (even earlier versions which I didn't touch) to crash the game when certain hero (currently 2 are 100% confirmed) abilities are used. The 1.31.1 patch didn't fix it all.
I won't go into details how mad I am ...
The subject title is not related to DotA.
You serious? I know from where DotA originates but he is not "maintaining" 6.85 for the community since that's Dracolich doing.DotA is a game mode in Warcraft. The main point of his post is that several abilities in Warcraft 3, in a DotA map, is failing and causing crashes. I don't know if you knew, but DotA originates from Warcraft 3.
You serious? I know from where DotA originates but he is not "maintaining" 6.85 for the community since that's Dracolich doing.
I'm not hostile.Right, well it's still a Warcraft 3 map which makes it relevant. Cheer up buddy, nobody here killed your cat but you're being overly hostile towards everyone![]()
I don't like that 0 indexed native it's inconsistant.
If you use "get current level of ability" that is level 1 it will get level 1 but for trigger editor level 1 is level 2 so it will affect level 2 of the ability instead of level 1 even though the trigger still consider it the current level of the ability.
Does it normally crash when i actually select any part of the terrain in the editor after i loaded the map in the editor? I can't seem to use the editor properly most of the time (like 85% of the time) It's horrible.
I provided a video below.
Also, the map i opened is created using World Editor from 1.29.
Also another bug i found. This doesn't happen in the old version of world editor (even with JNGP) - both screenshots included.
Honestly i am really pissed with these latest updates, ever since they introduced the CASCs and updates in the World Editor everything i frequently used is just broken (terrraining tools, unit placing, unsorted trigger options etc). I have both versions installed and i think i'll just stay at 1.27b until i see these problems fixed.
Old Version - 1.27B
View attachment 325424
New Version - 1.31.1
View attachment 325423
Proof of me using both versions
View attachment 325425
View attachment 325426
I do not really want to resist updating my game, but if i can't use it properly i can't stay with it.
Edit: I am told that using 32 bit version of World Editor fixes the problem, i might give this one a second chance.
Edit: Based on my testing the items bug is still there (the one i attached here), the one where item can't be selected in the palette, the world editor crashes however is gone.
I am maintaining the 6.85ne DotA map for the Battle.net community (fixed 20+ bugs and added some useful features). The last 1.31 patch now caues all DotA maps (even earlier versions which I didn't touch) to crash the game when certain hero (currently 2 are 100% confirmed) abilities are used. The 1.31.1 patch didn't fix it all.
I won't go into details how mad I am ...
The editor is very laggy now. 2-3 second delay when trying to open up even the trigger editor, and the. 2-3 seconds clicking on folders and individual triggers. The terrain is laggy too. Trying to work with this updated editor would be painful, and I am reverting back down to previous version.
1. I can confirm that the Trigger editor is almost unusable due to extensive lag. It also crashes after you try to access it through the Object Manager (F11).
(System: Intel Core i5-8265, Windows 10 Home, 16 GB RAM.)
2. Menus are still lacking shortcuts, which I have complained about for at least a year. The shortcuts work, they are just not listed.
I am maintaining the 6.85ne DotA map for the Battle.net community (fixed 20+ bugs and added some useful features). The last 1.31 patch now caues all DotA maps (even earlier versions which I didn't touch) to crash the game when certain hero (currently 2 are 100% confirmed) abilities are used. The 1.31.1 patch didn't fix it all.
I won't go into details how mad I am ...
set a = BlzGetUnitAbilityByIndex(GetTriggerUnit(),i)//i is the index for ability I want to get
call BJDebugMsg(BlzGetAbilityStringField(a,ABILITY_SF_NAME))
Why don't you attach the map?With initial 1.31 release, I was unable to save my map. As of this patch, I am unable to OPEN my map in editor. damn.
Looks fine.Has anyone tried using BlzGetAbilityStringField() to get ability's name? It returns (null) instead of the actual ability name
Here's the actual code used. Tell me if I did anything wrong
Nice bullshit right here KKomradeI am the original creator of dota (eul)
..
I am a developer of other cards
Nice bullshit right here KKomrade
