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

Quick casts

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

  • Quick casts

    Double click for self-push with force staff doesn't work when quick cast is allowed. I am just getting text "No target". With quick cast turned off double click works again properly.


    And double click for self-cast for eul scepter will be handy too :P (just a little suggestion)

  • #2
    It's more-or-less intended that quickcast doesn't work with double-tap.
    Fizz on dev.dota2.com / Jimmy M on Youtube (a pseudonym)

    Comment


    • #3
      This is nonsense because then is quick cast in fact slower than regular cast. This action distract you and you have to select your character which is definitely slower than just pressing 2 times the same button.

      Comment


      • #4
        Well Quickcast tries to execute it after the first button press, why should it wait for a second input? You are already trying to cast the forcestaff at the position of your cursor.
        This gets more obvious with ground targeted abilities, let's say blink dagger. A double click blinks you towards your fountain but with smart cast it blinks you to your cursor because you activate the dagger after the first click. If it would wait everytime for a certain time (like .1 or .2 sec) just to see if it becomes a double click, it would truely be slower, even if you dont want to double tap. The default double click timing on windows is .5sec, do want to introduce an aditional .5 casting delay on all abilites with double click feature (while smart cast is enabled)?
        Or what if you want to use force staff on a unit, miss it the first time and directly click on it a second time (which happens in hectic fights). with double tap you would force yourself
        Last edited by Belarion; 09-15-2013, 06:26 AM.

        Comment


        • #5
          I get it what you wanna say but hey .. e.g. you are chasing enemy hero and you are clicking lets say at the right edge of the screen to follow him now you wanna force yourself in the direction as the enemy hero is and you have to go with your cursor across the whole screen and be with your cursor above your character or have cursor at your portrait to force yourself. With regular cast you can press 2 times your bind button and everything is OK - your hero is forced. If you wanna push your teammate with regular cast you have to select him with selecting cursor with little arrows but with quick cast you can only have your cursor above him - simple, faster, more efficient. So conclusion? From my point of view forcestaff double-click doesnt work with quick casts because you have to select your hero with cursor (be with cursor above him) with regular cast you dont have to select hero and its faster than "QUICK" cast. And on force staff is said "Double click to self-cast." So for me this is broken.

          Comment


          • #6
            Then tell me your solution how to implement double-click. adding a reaction delay?

            Comment


            • #7
              Thing is, there's huge potential for targeting screwups with double-tap combined with quickcast: either accidental self-casts when trying to target another unit (e.g. if you miss-clicked and need to press the key again) or accidental targeted casts when self-cast was intended.

              Everything has both costs and benefits - if you find quickcast inferior then the old system is still available. Or you could do what I do and have both types of binds (using alt-something for binds you seldom use may help if you're running out of keys).
              Fizz on dev.dota2.com / Jimmy M on Youtube (a pseudonym)

              Comment


              • #8
                Solution: fast double click > normal click OR just add double click (like at regular cast) for self-push is much more easier and faster to avoid someone from your team then select your character with quick cast. Its like .. yea I can move with my cursor across the screen to select my hero .. no problem but holy sh*t I cant avoid my teammate while I am pressing 2x button for self push. And you wanna to complain about random teammate fail pushes (instead of self-push [with quick cast]) but random fail sheep or cyclone with regular cast is OK.

                Zero potential .. just fails from unlucky players. I dont wanna sound rude but I think this solution for forcestaff/quick cast is rly stupid.

                Comment


                • #9
                  If you try to detect double clicks, you actually need to WAIT if you normaly quick cast, meaning quick cast gets a delay. THAT would be realy stupid.
                  If you think I've closed or deleted a post unjustified, feel free to PM me and I'll explain it to you/discuss it with you further.

                  Comment


                  • #10
                    Originally posted by Kryil- View Post
                    If you try to detect double clicks, you actually need to WAIT if you normaly quick cast, meaning quick cast gets a delay. THAT would be realy stupid.
                    Yeap I know trying to detect rly fast double click isnt best option but still we have 2nd option - adding regular double click for quick cast.

                    Comment


                    • #11
                      Originally posted by H0ney View Post
                      Yeap I know trying to detect rly fast double click isnt best option but still we have 2nd option - adding regular double click for quick cast.
                      You can't.
                      Forcestaff, you click once. Due to quick cast, it has to cast. Impossible to click another time because you're already casting. If you have no target, the message has to appear. Adding the possibility here to simply detect double casting after a "fail" message would be stupid as crap.
                      The only possibility is to add a delay.
                      Click -> wait for another click -> quick cast (or self cast if another click comes). That delay is stupid to. Something that activates upon a single click isn't ment for double clicking.
                      If you think I've closed or deleted a post unjustified, feel free to PM me and I'll explain it to you/discuss it with you further.

                      Comment


                      • #12
                        Moved to brainstorming.
                        Please, just call me buny.

                        Comment


                        • #13
                          Second click could replace the need to have the cursor above your hero. Is that really too hard to understand this? Everything else is unchanged. Too damn hard to understand ..

                          Comment


                          • #14
                            You simply don't understand it. There is no second click, you are already casting it after the first click. The game doesn't wait to see if there ever comes a second click as it already is casting the ability

                            Comment


                            • #15
                              The first press already casts the spell...you can't make the second press cast the spell if you make the first press already cast it by Quick Cast, because Force Staff (and most items) have a cooldown.

                              Comment

                              Working...
                              X