Move during a hard knockback.

Discussion in 'Closed' started by CreamGoddess, Jun 7, 2022.

  1. CreamGoddess
    Offline

    CreamGoddess Donator

    Hi, I don't believe the hard knockback should work how is working now.

    on Example A, I was using WindiaMS since it's ""almost"" like royals (same version and I had a high lv char there) and knockback wasn't bugged there.
    on Example B, was a video uploaded by: @raftel on General Map Fixing Thread, using the current client possible 12/05/2022.

    Another example that make me believe that hard knockback is definitely bugged:

    Example A run was recorded in 07/11/2021 (before bug) and Example B was recorded 07/06/2022 (during bug)
    Note: auf used this attack that push you (like typhon and other mobs/bosses)
    [​IMG]
    you also can say that I was faking my moves on Example A, but there's another example:

    luckly I found an auf run video from a random MR player and we had the same time reaction after leave corner.

    I call it a simple KB or just push YES, YOU CAN CLIMB

    I call it a Hard KB NO, YOU CAN'T CLIMB


    My final note: I once said it's a bug or was intentional and not mentioned on patch notes, but I believe it's a bug, old typhon feather farmers or old auf daily runners can confirm the change.

     
    LichWiz, Jooon, raftel and 5 others like this.
  2. raftel
    Offline

    raftel Well-Known Member

    Thanks for the clarification.
    As I said, never done auf so I can't compare to another knock-back.
    Let it be a feature not a bug :D!
     
    CreamGoddess likes this.
  3. ImVeryJelly
    Offline

    ImVeryJelly Donator

    I thought that was how they fixed the “cannot move after hard knock back into smoke screen” bug. It started on the same update where that bug was fixed. They removed the part where hard knock back immobilized you for short amount of time, and it now actually registers your inputs.
     
    Last edited: Jun 8, 2022
    CreamGoddess likes this.
  4. boredxz
    Offline

    boredxz Well-Known Member

    I think on the old client, in Tree PQ, you couldn't hold up during the hard kb. Now you can catch the rope and not fly across the map, which is nice :D
     
    MoldySoup, CreamGoddess and Rielle like this.
  5. CreamGoddess
    Offline

    CreamGoddess Donator

    yes, to be honest, even it's a bug I would like to let be a feature, but it's up to developers :PBGasp:

    exactly, it's painful af when u farm typhon feather.

    anyway it shouldn't be fixed [​IMG], I just wanted show to @raftel and @LichWiz what exactly I was talking about, but since I saw it as a bug, I posted here.
     
    Punk and LichWiz like this.
  6. Dann
    Offline

    Dann Donator

    :v
     
    Punk and CreamGoddess like this.
  7. Zancks
    Offline

    Zancks Donator

    I checked it with the devs. It’s indeed a bug caused by the fix of the Smokescreen bug in update 78.
    During regular knockbacks you could always move and catch ropes. This is often used in jump quest eg. Zakum prequest stage 2.
    Prior to update 78 super knockbacks that eg. tryphons and Auf Haven do gave a movement penalty which was a part of the „getting stuck in smokescreen bug“. To fix it the devs had to get rid of that movement penalty from super knockbacks. This lead to the current state of being able to react to super knockbacks and catch ropes afterwards.
    The devs won’t fix this bug for the time being. Can’t promise they will never do it tho.
    Thanks for the bug report!
     
    raftel, CreamGoddess and LichWiz like this.
  8. personal1
    Offline

    personal1 Well-Known Member

    Hi I don't mean to bump an old thread but I believe this is something I experience in Chao occasionally. is there any fix or any reason why it only happens occasionally? Does it make sense for it to only be random at best?
     
  9. Green Mind
    Online

    Green Mind Donator

    I don't know the cause, but it will go away if you change channel at least once before doing anything.
     
  10. personal1
    Offline

    personal1 Well-Known Member

    Thanks! I saw @Sylafia 's reply to another thread and was told the cause is the first time you log onto a client instance and that relogging was a solution but thanks again for confirming ccing works too :D
     

Share This Page