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

[Intended?] Chronosphere is instant

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • [Intended?] Chronosphere is instant

    Description: In dota, chronosphere is applied in 0.1 seconds intervals, in dota 2 it is as soon as you enter the AoE


    Repro steps:
    Pick Void
    Lvl up to 6
    Get an Ally
    Make Ally buy dagger
    Make Ally start to TP to tower and shift queue a blink
    Cast chronosphere to where he is tping

    Result: Ally will be caught in chronosphere
    Expected: Ally to blink away

  • #2
    i'd consider this as an intended change.
    added to intended fix list.
    Make sure to read the Forum Rules as well as the stickied Threads of the Forum Section you are posting in.

    Contributions i'd like to highlight:
    My Suggestion: Coaching System
    My Sticky: Intended Changes List
    My Challenge: Completely Fixed Hero Challenge: Skywrath Mage

    Comment


    • #3
      Originally posted by blash365 View Post
      i'd consider this as an intended change.
      added to intended fix list.
      On what basis?

      Comment


      • #4
        yep, intended since units are not meant to be able to do anything in chronosphere (same for black hole and you can also see icefrog trying to improve the consistency of blackholes disable in dota 1, expect that the same goes for chrono)
        specs for bugreports:
        i5-4200U
        AMD Radeon HD 8750M
        win 7

        Comment


        • #5
          Originally posted by gergeux View Post
          On what basis?
          on the basis of common sense.
          Make sure to read the Forum Rules as well as the stickied Threads of the Forum Section you are posting in.

          Contributions i'd like to highlight:
          My Suggestion: Coaching System
          My Sticky: Intended Changes List
          My Challenge: Completely Fixed Hero Challenge: Skywrath Mage

          Comment


          • #6
            [Intended] Chronosphere is instant (should have 100ms buildup delay)

            As found out in this thread here: http://dev.dota2.com/showthread.php?t=81535 (the reason why my Phoenix didn't kill the Void btw is also the reason why I don't play DotA 1 anymore: Input delay without feedback).

            Void's ultimate Chronosphere should have a 100ms buildup time before it affects any units. That means it is possible (in DotA 1) to escape chronosphere while it builds up (Icarus Dive, Force Staff, etc; the 100ms is added to the cast time of Void). There is also a nice animation for it to build up in DotA 1.
            Currently it is instant after Void's cast time.

            Comment


            • #7
              need to read the code to confirm
              nvm, saw the discussion in that thread
              Last edited by Eric37073; 11-13-2013, 01:26 AM.

              Comment


              • #8
                Added.
                Please, just call me buny.

                Comment


                • #9
                  This is rigged at the moment because you don't have time to turn when Void jumps at you from the side, which means you can't rely on being able to use Ethereal Blade or Heaven's Halberd on him just as he casts it unlike in the old game. The only way you can for sure cast such items on him is if you don't get caught and that isn't consistent with the old game at all nor is it fair.
                  I will mercilessly add to my ignore list anyone that makes an incredibly annoying signature.

                  Comment


                  • #10
                    So all this time it wasn't just me that thought SIlencer's ulti can never disable Void after he jumps in...

                    Is this actually a bug because of the cast time or his casting animation ?
                    Explanations on the normal, high and very high brackets in replays: here, here & here
                    Why maphacks won't work in D2: here

                    Comment


                    • #11
                      Originally posted by The Nomad View Post
                      So all this time it wasn't just me that thought SIlencer's ulti can never disable Void after he jumps in...

                      Is this actually a bug because of the cast time or his casting animation ?
                      Neither. It's a bug of Chronosphere itself. It has a buildup time in DotA 1. I suggest you check out the thread linked in the OP.
                      Last edited by Typhox; 04-13-2014, 04:19 PM.

                      Comment


                      • #12
                        It might make more sense to call it a minor delay rather than a buildup time, but I suppose both descriptions are good.
                        I will mercilessly add to my ignore list anyone that makes an incredibly annoying signature.

                        Comment


                        • #13
                          Originally posted by hoveringmover View Post
                          It might make more sense to call it a minor delay rather than a buildup time, but I suppose both descriptions are good.
                          I like buildup time, because within that time the chronosphere already builds up its animation which is an important part, since it makes it clearly visible that Void is casting his spell.

                          Comment


                          • #14
                            I can confirm:

                            Spoiler: 

                            function Func2883 takes nothing returns nothing
                            local unit loc_unit01=GetTriggerUnit()
                            local integer loc_integer01=GetUnitAbilityLevel(loc_unit01,('A0J 1'))
                            local location loc_location01=GetSpellTargetLoc()
                            local real loc_real01=GetLocationX(loc_location01)
                            local real loc_real02=GetLocationY(loc_location01)
                            local unit loc_unit02=CreateUnit(GetOwningPlayer(loc_unit01), ('u00L'),loc_real01,loc_real02,0)
                            local timer loc_timer01=CreateTimer()
                            local integer loc_integer02=GetHandleId(loc_timer01)
                            local group loc_group01=Func0030()
                            if loc_integer01==0 then
                            set loc_integer01=GetUnitAbilityLevel(loc_unit01,'A1D7 ')
                            endif
                            call SaveUnitHandle(hashtable001,(GetHandleId(loc_timer 01)),(19),(loc_unit02))
                            call TimerStart(loc_timer01,0.8,false,function Func2877)
                            set loc_timer01=CreateTimer()
                            set loc_integer02=GetHandleId(loc_timer01)
                            call SaveUnitHandle(hashtable001,(loc_integer02),(19),( loc_unit02))
                            call SaveUnitHandle(hashtable001,(loc_integer02),(14),( loc_unit01))
                            call SaveGroupHandle(hashtable001,(loc_integer02),(220) ,(loc_group01))
                            call SaveInteger(hashtable001,(loc_integer02),(28),(0))
                            call SaveInteger(hashtable001,(loc_integer02),(5),(loc_ integer01))
                            call TimerStart(loc_timer01,0.1,true,function Func2882)
                            call RemoveLocation(loc_location01)
                            endfunction
                            Known Tooltips and UI information Issues List
                            Unreleased heroes data:

                            Hero Balance Compilation 6.48 onwards
                            Items and Other Balance compilation 6.48 onwards
                            Dota 1 6.81c Test Map

                            Comment


                            • #15
                              You need to also consider that in WC3 the spell affects units in 0.1 seconds intervals while in dota 2 is instant, it is pretty much intended to work the way it currently is and IceFrog is just to lazy to add the fix in WC3 which is super simple to do.

                              Comment

                              Working...
                              X