Star Fox 64 (the sonicdcer/sf64 decompilation)

In the US 1.1 version of Star Fox 64, the Arwing rolls when Z or R is pressed twice. The first press sets that button's counter to 10, which Player_UpdateArwingRoll counts down once per player update, and a second press while it is above 0 starts the roll, turning the ship 30 degrees an update for 10 updates and then slowing by 5 degrees an update until it stops. barrelRollAlpha falls by 30 every update while it is above 0, and in each update the roll's count is still above 0 after counting down (9 of its 10) it then gains 100, capped at 180, a net rise of 70 an update. While that value is above 0, the enemy-shot update (Effect_EnemyShot_Update) widens the shot's box around the player by 100 units on each axis, sends a shot inside it off in a new direction, and applies no damage. sf64/barrel-roll

About: Star Fox 64 Barrel roll

Value: 10 player updates (the double-press counter and the roll's full-speed count)

Computed, not measured: since the press is read before the counters count down in the same update, a second press up to 9 updates after the first starts a roll, and barrelRollAlpha runs 100, 170, 180 for seven updates, then 150, 120, 90, 60, 30, so it is above 0 for the first 14 updates of a roll. The same value draws the roll's glow (src/engine/fox_display.c#L916). The decompilers' comment on deflectCount reads "counts shots deflected by barrel rolls. never used" (include/sf64player.h#L316). A meteo warp (meteoWarpTimer) also deflects. The Landmaster's roll (Player_UseTankJets) has its own rules and isn't covered here. Player updates haven't been tied to displayed frames.

Cited by: Barrel roll, Star Fox 64

In the US 1.1 version of Star Fox 64, the Arwing's boost and brake share one meter, boostMeter, which counts up from 0 as it is used and stops at 90. Holding the boost button adds 3 a player update on rails and 1.5 in all-range mode (Player_ArwingBoost), and holding brake adds the same amounts (Player_ArwingBrake). Each of the two functions takes back 0.5 a update on rails (0.35 in all-range mode) whenever its own action isn't running, so the meter falls by 1 an update on rails when neither button is held. Reaching 90, holding both buttons with the meter above 0, or letting go of both with the meter above 0 sets boostCooldown, which blocks both actions until the meter is back to 0. sf64/boost-meter

About: Star Fox 64 Boost meter

Value: 90 meter units (full use)

Computed from these rates, not measured: boosting on rails the meter gains 3 and the brake function's else branch takes 0.5, a net 2.5 an update, so a full meter lasts 36 updates and refills in about 90 (1 an update); in all-range mode the net is 1.15, about 78 updates, and the refill 0.7, about 129. The HUD's gauge reading of the field isn't read. Loops, U-turns, and a meteo warp also set boostCooldown (other lines of src/engine/fox_play.c). The Landmaster has its own function, Player_TankBoostBrake. Player updates haven't been tied to displayed frames.

Cited by: Boost meter, Star Fox 64

In the US 1.1 version of Star Fox 64, holding A counts a charge counter up by 1 a player update to a cap of 21, and an update without A held counts it down by 1 (Player_UpdateLockOn). A fresh press of A, whose own update first adds 1 to the counter, fires the charged shot (PLAYERSHOT_LOCK_ON) if an enemy is locked on or the counter is then above 10 (so 10 or more before the press). Either path fires only if the player's charged-shot slot (gPlayerShots[14 - player->num]) is free, holds a shot of another type, or holds a charged shot that has lost its target (the locked path) or grown past scale 1 (the counter path); a press that fires nothing sets the counter to 0. Once the counter is above 20, while A is held, nothing is locked, and Z and R aren't both held, it launches a search shot every fourth game frame, and the first targetable enemy within 300 units of that shot on each axis (200 in all-range mode) is locked on for a count of 20, which counts down only while A is up. Each update while its target stays locked, the charged shot turns toward it (PlayerShot_UpdateLockOnShot). sf64/lock-on

About: Star Fox 64 Lock-on shot

Value: 10 charge counts before the press (a press from this many fires)

The shot fires on a new press of A, not on its release: after a full charge the counter falls from 21 by 1 an update with A up and the press's own update adds 1, so by the atlas's arithmetic a press after as many as 11 updates with A up still fires it. A lock zeroes the charge counter each update (src/engine/fox_enmy.c#L2852), and a search shot dies when A is let go (src/engine/fox_beam.c#L1814-L1816). The turn step unk_50 grows by up to 3 an update toward 360 (src/engine/fox_beam.c#L2226). The 300 and 200 limits are in the game's world units. B fires a smart bomb through the same shot type at a locked enemy (src/engine/fox_play.c#L3263-L3290). The search-shot loop carries the decompilers' comment "bug? should be 11". Player updates haven't been tied to displayed frames.

Cited by: Lock-on shot, Star Fox 64

In the US 1.1 version of Star Fox 64, Player_Setup gives the player 255 shield units (less with a Versus handicap), and healing stops at Play_GetMaxShields: 383 with three or more gold rings, otherwise 255. A hit's damage, doubled in Expert mode, drains from the shield at 2 units an update (Player_UpdateShields), and an enemy laser's damage is 20; a hit while gHasShield is set does none. Each Arwing wing starts at 60 health (10 in Expert mode). A hit the code gives direction 1 or 2 takes 20 from the right or left wing, directions 3 and 4 take 15 from one wing at random, and direction 0, which enemy shots pass, takes none; a wing at 0 breaks. While either wing is broken or absent (WINGSTATE_NONE; the test is <= WINGSTATE_BROKEN), Player_Shoot sets the lasers back to single every update. sf64/shields-and-wings

About: Star Fox 64 Locational damage

Value: 255 shield units at the start

By the atlas's arithmetic, not measured, 255 units take 13 enemy-laser hits and three side hits break a wing. The shield drains over updates, so a hit's damage shows over several updates. The gHasShield branch also sets gShieldAlpha to 2 (src/engine/fox_play.c#L894), and Player_DamageWings skips the wings while that value is 1 or more. What sets gHasShield and how a broken wing is repaired (on rails, and the all-range timer gAllRangeWingRepairTimer) aren't read. Expert mode and the gold-ring cap are named by the decompilers' variables (gExpertMode, gGoldRingCount).

Cited by: Locational damage, Star Fox 64