Crossfire

Three questions for the mechanic

• Are both sources visible before release?

  Expose the two origins together and distinguish them from decoration. Show complete guide lines or a shared marker early enough that the player can understand one compound attack rather than discovering the second shot late.

• Does the response clear both projectile bodies?

  Test the route against both projectile radii plus the full player radius. A point that leaves one line can enter the other, so sample the complete path through the overlap instead of checking only the destination.

• Does the intersection pass before the next decision?

  Keep both trajectories fixed until the shots cross and exit. Recovery should begin only after the moving overlap no longer constrains the player, leaving the successful route observable and reusable.

Design mistakes

• The second source appears after the response begins

  A late reveal converts spatial planning into an ambush. If sources enter at different times, announce their order and timing as an explicit sequence rather than calling it simultaneous crossfire.

• Each line is fair alone but their overlap has no route

  Independent clearance tests miss the combined geometry. Verify the whole player path across time, including close crossings where the two projectile radii nearly merge.

• One source retargets after commitment

  Late steering moves the intersection and invalidates both previews. If one projectile tracks, separate that behavior and communicate its cutoff before combining the rules.

Tune the attack

• Use one crossing plan

  Store both source points, both locked directions, speed, radius, and release time in a single plan. Render guides, projectiles, safety checks, and the preview from that plan so the crossing cannot drift.

• Tune synchrony against travel distance

  Different source distances require different speeds or release offsets to meet at the intended point. Test actual arrival times rather than assuming simultaneous launch creates simultaneous crossing.

• Protect the diagonal escape

  Crossfire often removes the obvious horizontal and vertical choices. Measure the remaining diagonal path against arena edges, camera projection, and the player’s slowest supported movement.

• Escalate with sequence, not hidden density

  Later variants can move the crossing point or alternate source pairs. Keep each pair readable and preserve a gap between crossings before adding another layer.

Arena

• What the mechanic communicates

  Crossfire makes Kern feel as though the arena itself is coordinated against Tavi. The threat comes from the relationship between sources, so the encounter can express control and planning without filling every space with projectiles.

Player upgrades

• Adapt it to the player verbs

  For ordinary movement, preserve a diagonal route wide enough for the complete body. If the player can block, reflect, or destroy a projectile, decide whether neutralizing one source intentionally opens the other route and communicate that consequence.

Do not confuse this with

• Keep the mechanic distinct

  Crossfire requires at least two spatially distinct sources whose paths intersect. A fan spreads lines from one origin, a volley repeats shots over time, and converging threats may use non-projectile geometry. Preserve the two-source relationship.