1d93642094
Arrows flew through water with a point check for the 0.6 drag and nothing else: no bubbles, no splash, no currents, no bubble columns, and the stuck arrow logic (nudging back by the normalized motion, no falling out, a 1200-tick age) was not AbstractArrow's. Port AbstractArrow.tick for arrows (arrows.rs, state in Projectile::arrow): the in-block check, the water inertia from the last base tick's wasTouchingWater with four bubbles behind it, crit trails, lerped rotation, the COLLIDER clip with entity hits first, the effects of the blocks along the path (bubble columns push, water extinguishes), air drag and gravity, then the base tick's updateFluidInteraction (currents while not stuck, splash sound/particles), sticking 0.05 back along each moving axis with the arrow's own random for the hit sound, falling out when the block goes, and despawning 1200 ticks after sticking. New harness tools/test_arrow_parity.py drives real vanilla Arrow entities (VanillaArrowOracle) and Horizon's arrows::tick (examples/arrow_probe.rs) over the resident scene. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>