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.



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

Icarus Dive shouldn't trigger Wall of Replica

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • The Nomad
    replied
    Although I haven't played D1 (nor have it installed), from my understanding it's been like this since the dawn of time
    Honestly ever since 6.79 I am not sure if D1 matched D2 that much anymore. Especially back then when Brood had free movement all over the map and Blood had 999999999999999999999 movement speed. I assume after the latest balance changes it matches it more (except for the Intended Changes List, of course)

    Still, on-topic, I don't see why ability movements shouldn't trigger WoR. (I meant to say as an intended change, of course)

    Leave a comment:


  • bu3ny
    replied
    Originally posted by The Nomad View Post
    Replying to this context alone (not your op) I'd say it's the same as CM's Frostbite vs Firefly on Batrider.

    There is a possibility that IceFrog's vision of the game and how it works was limited by the engine. Now that he has something to work with from scratch where he has total control, he might want to balance them the way he intended them. I don't see the problem here...
    You can easily fix Firefly frostbite/overgrowth interaction in DotA1.

    Leave a comment:


  • The Nomad
    replied
    Originally posted by wachon1992 View Post
    so you are saying the limitations on wc3 engine are being corrected on source engine?

    all the stuffs that were "bugged" on wc3 are gona be "fixed" here?

    i dont understand how valve deals with wc3 engine limitations, do they keep it like they were or they considere it as a bug/limitation and fix it here.
    Replying to this context alone (not your op) I'd say it's the same as CM's Frostbite vs Firefly on Batrider.

    There is a possibility that IceFrog's vision of the game and how it works was limited by the engine. Now that he has something to work with from scratch where he has total control, he might want to balance them the way he intended them. I don't see the problem here...

    Leave a comment:


  • igo95862
    replied
    Force staff was not being castable on self then magic immune throught double click. It was confirmed as intended by Icefrog but after some time it was changed to Dota 1 behavior. He left this message:
    Originally posted by IceFrog View Post
    Nothing is set in stone, if there are things we confirm as intended for whatever reason, you guys are still free to debate the pros and cons.
    and soon completely stopped posting on forum. If you seen Valve conference videos in one of them they say that no communication is better then bad. I guess Icefrog decided to adopt this strategy and now we doomed to never know his intentions.

    Leave a comment:


  • ned_ballad
    replied
    Force staff incident?

    Leave a comment:


  • igo95862
    replied
    Originally posted by wachon1992 View Post
    so you are saying the limitations on wc3 engine are being corrected on source engine?

    all the stuffs that were "bugged" on wc3 are gona be "fixed" here?

    i dont understand how valve deals with wc3 engine limitations, do they keep it like they were or they considere it as a bug/limitation and fix it here.
    Usually Icefrog (some Valve developer, core tester) confirms what is bug and what is not but because he went full silent mode after force staff incident we might never know. And this WC3 limitation can be avoided as the way I stated above. Most of the spells use that way of detection except some old coded like static remnant or Wall of replica.

    Leave a comment:


  • wachon1992
    replied
    Originally posted by igo95862 View Post
    All those bugs because TriggerRegisterUnitInRange cannot detect then unit is moved in its range by triggers. You can test with static remnant. So I would say it is WC3 engine error.
    so you are saying the limitations on wc3 engine are being corrected on source engine?

    all the stuffs that were "bugged" on wc3 are gona be "fixed" here?

    i dont understand how valve deals with wc3 engine limitations, do they keep it like they were or they considere it as a bug/limitation and fix it here.

    Leave a comment:


  • igo95862
    replied
    Actually instead of using TriggerRegisterUnitInRange you can check for enemy units in needed AoE every small fraction of seconds. This will fix this issue

    Leave a comment:


  • igo95862
    replied
    All those bugs because TriggerRegisterUnitInRange cannot detect then unit is moved in its range by triggers. You can test with static remnant. So I would say it is WC3 engine error.

    Leave a comment:


  • bu3ny
    replied
    I think we can count these all as intended. Nowhere is said that certain speed should make the wall ineffective.


    Also it makes little to no sense for the wall to not affect those.

    Leave a comment:


  • Noo
    started a topic Icarus Dive shouldn't trigger Wall of Replica

    Icarus Dive shouldn't trigger Wall of Replica

    placeholder
Working...
X