This entry point is used by the routine at 35578. StartAttack — action on the " ATTACK " row: queue the combat job — action state 4 (CrewAction4_Handler -> CrewHitsAlien / CrewHitsAndroid) with base countdown 40, replacing any pending action. Then put the special row back to what the room warrants (49 "RmveGrille" or blank, via the grille-state refresh at $B0B8) and move the cursor on.

CrewAction4_Handler — dispatched via CrewActionDispatch entry 4 (combat). Branches a combat-state actor into one of two parallel handlers based on whose sprite-class byte (+1) matches the actor's: 1. If the actor's (IX+1) matches the alien slot's identity at $737F → CALL 37584 (CrewHitsAlien) — message #3 "nets the ALIEN" or #4 "hits the ALIEN". 2. Else, if AlienActiveFlag is non-zero AND the actor's (IX+1) matches the alien-target slot's (IX+1) — i.e. the **Android** slot picked by LongGameInit (42276) via LongGameTargetTable (41390) and pointed to by AlienTargetPtr (33701) — → CALL 40941 (CrewHitsAndroid) — message #31 "nets {target}" or #32 "hits the Android". The Android role: LongGameInit randomly picks one of crew slots {1, 2, 4, 6} (Dallas / Kane / Ash / Parker) and stores it in AlienTargetID (33703). That crew member is dormant at first — they appear and behave like a normal crew member. UpdateAlien (40826) turns them hostile the first frame the alien is loose and the slot is still in its template state (the "first encounter"), stamping them into action state 7 and giving them their sprite-class kin as targets via NearestCrewA/B (see 37876). After activation the Android wounds nearby crew through CrewAction7_Handler (40757); CrewHitsAndroid here is the **player-response branch**, dispatched when other crew engage the Android in combat state 4. CAVEAT: the (IX+1) byte is NOT a unique slot ID in the LongGameCrewInit template (41444) — slots 1/2/3 share +1=6, slots 4/5/6 share +1=27. So branch 2's match fires for the whole **sprite class** of the Android, not strictly the chosen slot: - AlienTargetID ∈ {1, 2}: matches {Dallas, Kane, Ripley} - AlienTargetID ∈ {4, 6}: matches {Ash, Lambert, Parker} Whether that ambiguity is intentional design or a missing per-slot ID write is unresolved — verify on an emulator before extending. The short game hard-wires AlienTargetID = 9 (out of range), so branch 2 never fires there. After dispatch, CALL 44924 clears IX+3 (action state) and returns.

CrewHitsAlien — alien-side combat handler. Called from CrewAction4_Handler (37547) when the actor in state 4 has (IX+1) matching $737F (the alien's identity from CommonGameInit, 42451). The outcome depends on the WEAPON: FindHeldItems (31823) loads the attacking crew member's front-hand item id into HeldItemFront (31248) and the effect dispatches on it. It also houses the Harpoon Gun's kill primitive at 37733. Guards: re-asserts that (IX+1) matches the alien identity, then requires pixel coords IX+4 >= 2 and IX+6 >= 2 (sprite fully placed). Calls 44986 to clear the held-item slots, then FindHeldItems (31823) to fetch the attacker's weapons: 17 (Cat Box) → silent: JP to ClearActionState >= 20 (bare hands) → silent 16 (Net) → "net" outcome: write $FF to $7376 (slot 0 byte +0) to disable the alien, then enqueue message #3 "{actor} nets the ALIEN" else → "hit" outcome at 37646: enqueue message #4 "{actor} hits the ALIEN", then dispatch on the weapon id: - 0-5 Elctrc Prd/Incineratr, 18-19 Spanner: INC alien's wound counter at $73B2 (byte +4 of slot 0). If it reaches the AlienStopCell threshold, JP 44125 (alien- defeated path). - 6-7 Tracker: enqueue msg #5 "Tracker is broken" - 8-11 Fire Extng: decrement the item's charge in ItemCharges; on underflow enqueue msg #6 "extinguisher empty". - 12 Harpn Gun: the kill primitive at 37733 — see AlienKillPrimitive below. - 13-15 Laser Pist: JP 37831 — decrement the charge, then either msg #7 "Laser is exhausted" or JP 41022. This routine parallels 40941 (CrewHitsAndroid) in structure but refers to the alien (slot 0 at $7376) and emits messages #3 / #4 instead of #31 / #32.

"{actor} hits the ALIEN" branch (CrewHitsAlien continued).

AlienKillPrimitive — the Harpoon Gun outcome, reached from CrewHitsAlien (37584) when the attacker's front-hand item (31248) is 12, the Harpn Gun. A harpoon strike is devastating for both sides: 37876 gathers up to three slots (NearestCrewC + NearestCrewA/B) sharing the alien's sprite class; for each, every ItemLocations (29940) entry that the slot carries or that lies in the alien's room is destroyed (set to 255), and if the slot's byte +7 is still zero (alive) it is stamped to 1 (killed) with its byte +4 wound counter cleared. Then the alien's own wound counter is bumped by 5 (harpoon hits push it quickly over the AlienStopCell threshold → dies via JP 44125), the corridor view is rebuilt (CALL 31417) and the per-frame chain continues at AlienScareCheck (37992).

This entry point is used by the routines at 40439 and 40826.

This entry point is used by the routine at 38379.

This entry point is used by the routine at 40826.

This entry point is used by the routine at 44880.

This entry point is used by the routine at 44880.

This entry point is used by the routine at 37018.

This entry point is used by the routines at 38379 and 40826. AddRoomDamage: add A damage points to room E's damage meter — a 2-digit ASCII pair in RoomDamageDigits (30006; tens digit is the severity the engine scan at 39041 compares against). Crossing "30" raises the room-specific alarm messages #22-#25.

This entry point is used by the routine at 38379.

Ship-status dashboard: counters and ASCII digit cells (previously mis-disassembled as code). The digit cells double as the source text drawn on the status bar, and the endgame renderer copies them into the "The Nostromo will explode in .. minutes .. seconds" screen.