T
Tamrell
This post is part of a set of 6 posts where I talk about the current meta:
=====================================================
#1: The second jump/airdash: https://rumble.canny.io/suggestions/p/1-the-second-jump-airdash-on-the-current-state-of-the-rumble-meta
#2: Knockback: https://rumble.canny.io/suggestions/p/2-knockback-on-the-current-state-of-the-rumble-meta
#3: Volatile stone: https://rumble.canny.io/suggestions/p/3-volatile-stone-on-the-current-state-of-the-rumble-meta
#4: Stubborn stone: https://rumble.canny.io/suggestions/p/4-stubborn-stone-on-the-current-state-of-the-rumble-meta
#5: Guard Stone: https://rumble.canny.io/suggestions/p/5-guard-stone-on-the-current-state-of-the-rumble-meta
#6: Client/host balancing: https://rumble.canny.io/suggestions/p/6-client-host-balancing-on-the-current-state-of-the-rumble-meta
=====================================================
2 Knockback
With how knockback works right now there are a lot of janky interactions (especially on ring) that make for a frustrating experience
i.e: players getting flung from one side of the arena to all the way on the other side off the platform just because a disc or punch happened at the same time as they get hit by a structure
To adress the problems with knockback I have 2 (3 with the volatile post in #3 ) suggestions:
  • getting hit by a structure should override knockback, not add to it (if a structure breaks on a player, only knockback from the structure will be applied after freeze frames)
  • knockback from hitting structures or spawning a disc should not add to knockback from getting hit by a structure (mainly applicable for delayed activation of poses on client)