.modifyAddressLo EQUB &49 \ !&1249= HookSectionFrom EQUB &8A \ !&128A= HookFirstSegment EQUB &CA \ !&13CA= HookSegmentVector EQUB &27 \ !&1427= HookSegmentVector EQUB &FC \ !&12FC= HookDataPointers EQUB &1B \ !&261B= HookUpdateHorizon EQUB &8C \ !&248C= HookFieldOfView EQUB &39 \ !&2539= HookFixHorizon EQUB &94 \ !&1594= HookJoystick EQUB &D1 \ !&4CD1= xTrackSignVector EQUB &C9 \ !&4CC9= yTrackSignVector EQUB &C1 \ !&4CC1= zTrackSignVector EQUB &D6 \ !&44D6= trackSteering EQUB &D7 \ !&4CD7= trackSignData EQUB &E1 \ !&4CE1= trackSignData EQUB &47 \ !&1947= HookFlattenHills EQUB &F3 \ !&24F3= HookMoveBack EQUB &2C \ !&462C= HookFlipAbsolute EQUB &43 \ !&2543= Hook80Percent EQUB &61 \ This byte pads the block out to exactly 20 bytesName: modifyAddressLo [Show more] Type: Variable Category: Extra tracks Summary: Low byte of the location in the main game code where we modify a two-byte addressContext: See this variable in context in the source code References: This variable is used as follows: * ModifyGameCode (Part 1 of 4) uses modifyAddressLo
This is also where the xTrackSegmentI table is built, once the modifications have been done. The block is exactly 20 bytes long, so along with the modifyAddressHi block, there's one byte for each inner segment x-coordinate.