Announcement
Collapse
Forum Rules
- No flaming or derogatory remarks, directly or through insinuation.
- No discussion, sharing or referencing illegal software such as hacks, keygen, cracks and pirated software.
- No offensive contents, including but not limited to, racism, gore or pornography.
- No excessive spam/meme, i.e. copious one liners in a short period of time, typing with all caps or posting meme responses (text/image).
- No trolling, including but not limited to, flame incitation, user provocation or false information distribution.
- No link spamming or signature advertisements for content not specific to Dota 2.
- No Dota 2 key requests, sell, trade etc.
- You may not create multiple accounts for any purpose, including ban evasion, unless expressly permitted by a moderator.
- Please search before posting. One thread per issue. Do not create another thread if there is an existing one already.
- Before posting anything, make sure you check out all sticky threads (e.g., this). Do not create new threads about closed ones.
- It is extremely important that you post in correct forum section.
- Balance discussion only in Misc.
- All art related (such as hero model) feedbacks go to Art Feedback Forum.
- All matchmaking feedback should go here: Matchmaking Feedback
- All report/low priority issues should go here: Commend/Report/Ban Feedback
- No specific workshop item feedback. These should go to workshop page of that item.
- When posting in non-bugs section (such as this), use [Bugs], [Discussion] or [Suggestion] prefix in your thread name.
- Before posting any bug, test it in latest DotA map or Latest DotA Test Map and make sure it is actually a bug.
You can also find references in PlayDota Guides and PlayDota Mechanics. - Follow Bug Reporting Guide when reporting bugs.
In case you object some action by a moderator, please contact him directly through PM and explain your concerns politely. If you are still unable to resolve the issue, contact an administrator. Do not drag these issues in public.
All rules are meant to augment common sense, please use them when not conflicted with aforementioned policies.
See more
See less
[Confirmed] Rubick can be seen by the enemy from the ground during Tree Dance
Collapse
X
-
-
Bug with rubick and tree dance
Rubick with stolen tree dance is visible from low ground to enemy without having any hg vision , again rubick is visible to enemy while a monkey king with tree dance at the same situation will be out of sight.
I tested it with enemy rubick + enemy mk on same tree i could have seen the rubick w.o hg vision and i could not see the mk on the same tree both stood.
I gave away a kill in a game cus of this bug
-
Tree Dance on Rubick isn't hidden from sight while MK is
Repro:
1. Pick Rubick and steal Tree Dance and cast it on any tree without any vision protect (like other trees).
2. Let enemy grant vision over that tree.
Comparision:
1. Let MK jump to the same tree and let enemy grant the same vision.
Result:
Rubick isn't hidden from trees. Instead, once enemy grant vision over the tree, Rubick is revealed, while MK is still hidden.
Expected:
Rubick should be hidden from it as well.
@AZ~WOY8HQAT{``BN0F)5YJ.jpg
Comment
-
[Rubick] Stolen Tree Dance doesnt properly hide Rubick
An enemy can see a Rubick that is sitting on a Tree, if aforementioned enemy comes too close to Rubick (similar to how melee units can see/deward uphill).
This does not apply to Monkey King sitting on a Tree.
It seems that Tree Dance is simply bugged for Rubick. It isnt fully hiding him.
Current behaviour: Enemy heroes are able to see a Tree Dance'd Rubick via proximity, despite not having flying vision.
Intended behaviour: Rubick should not be visible/attackable, unless the enemy team has flying vision. Tree Dance should work for Rubick as it works for Monkey King.
Video showcase:
I am usually located at the end of the Alphabet.
Comment
Comment