Combat tuning: lift sluggish chasers toward kiteable band + snappier dash (research-backed)
Deep-research-backed ratios (GDKeys, gamedeveloper.com twin-stick study, Hades/RoR, critpoints i-frames): enemies should sit ~0.5-0.85x of player move speed (kiteable but pressing), telegraphs >= ~250ms. - Enemy move speed (on the RIGGED prefabs the directors actually spawn - verified the live ZoneEnemy/Wave rosters at runtime: Grunt=EnemyWerewolf, Charger=EnemyChargerMuscle, Spitter=EnemySpitter, Swarmer= EnemySwarmerUndead): Grunt 3.0->4.2 (0.70x base), Charger walk 2.6->3.0, Spitter 2.8->3.0. The 0.43-0.50x cluster was trivially out-walked by the 6.9 Ranger; lifted to credible pressure while still kiteable. Swarmer kept at 6.5 (intentional surround/rush). Telegraph windups unchanged (already research-aligned). - Dash (live TuningConfig defaults): IFrameWindowTicks 12->14 (0.20->0.23s, covers a reacted telegraph), DashCooldownTicks 45->36 (0.75->0.60s, horde-kiter cadence). Dash distance/arc unchanged. Play-verified the baked rosters: Grunt 4.2 / Charger 3 / Spitter 3 / Swarmer 6.5; dash 14/36. 390/390 EditMode. All are live-tunable (dash) or one re-bake (enemy speeds). Investigation: wf_c6c87dc5-9c3 (tuning lane). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
@@ -65,9 +65,9 @@ namespace ProjectM.Simulation
|
||||
public static TuningConfig Defaults() => new TuningConfig
|
||||
{
|
||||
DashDistance = 4.0f,
|
||||
IFrameWindowTicks = 12f,
|
||||
IFrameWindowTicks = 14f, // tune: was 12 (0.20s) -> 0.23s, i-frames better cover a reacted telegraph
|
||||
RecoverTailTicks = 9f,
|
||||
DashCooldownTicks = 45f,
|
||||
DashCooldownTicks = 36f, // tune: was 45 (0.75s) -> 0.60s, snappier horde-kiter cadence
|
||||
DashSharpness = 200f,
|
||||
ChargerWindupTicks = 30f,
|
||||
ChargerLungeSpeed = 16f,
|
||||
|
||||
Reference in New Issue
Block a user