HitDelayFix By Karlio

🎉 HitDelayFix v1.1.2 — Release Notes

✨ Added

• ⚠️ SprintReset now classified as HIGH RISK — shows warning popup before activation
  • Title: Aviso / Warning
  • Description: Essa função pode causar banimento por conta que modifica o sprint do jogo
  • Buttons: Cancelar / Continuar
• 🔄 One-time auto-disable migration — if SprintReset was enabled before 1.1.2, it will be automatically disabled only once on first launch (sprintResetMigration_1_1_2 flag) — user can re-enable afterwards with warning

🐛 Fixed

• 🏃 MicroSpeed - Grim Simulation x50+ / Velocidade aplicada (1151)
  • Changed from RenderTick (60-144x/s, 1.05^3 = 15% boost) → ClientTick (20 TPS)
  • 1.05 → 1.008 (0.8%) pulsated 1 tick on / 1 tick off for only 3 ticks after 2 hits — no longer accumulates Simulation
  • Added onGround + [-1,1] clamp to prevent illegal >1.0 input
• 🏃 FluidHits - Grim Simulation on knockback — fixed via removal (see below), before that reduced 0.026 (+30%) → 0.0205 (+2.5%) pulsated 1/8 ticks with hurtTime guard
• 🔄 SprintReset / WTap / WTapDelayFix - Grim AntiKB x6/x7
  • SprintReset no longer zeroes moveForward=0 → 1.0 — now only toggles sprint preserving input
  • WTap 2 ticks → 1 tick
  • WTapDelayFix sprintToggleTimer=0 (bypass 7 ticks vanilla) → 5 — keeps W-Tap but stays legit
• 🎯 ComboDelayFix - Hit flags (NoMiss/Killaura)
  • 30°/45° → 15°/30°, 80ms cooldown between redirects, block redirect during hurtResistantTime>2, score bonus -2000 → -200

🗑️ Removed

• ❌ Fluid Hits — completely removed
  • FluidHitsHandler.java, HitDelayFixConfig.fluidHits, ModLanguage toggle/desc, ClientProxy registration and ConfigScreen toggles
  • Reason: Grim flagged movement when taking KB and going forward (jumpMovementFactor modification during velocityChanged)
  • Legacy fluidHits property is auto-removed from hitdelayfix.properties on next save

🔧 Changed

• SprintReset risk LOW → HIGH
• warningActivate button text Ativar → Continuar (to match Cancelar / Continuar)
• Config persistence now stores sprintResetMigration_1_1_2=true to ensure one-time migration