As an old AppleSoft Basic/65C02 assembly language hacker, I actually followed the article from first principles and I remembered how AppleSoft basic was stored

As an old AppleSoft Basic/65C02 assembly language hacker, I actually followed the article from first principles and I remembered how AppleSoft basic was stored in memory - one byte code for each command and each line ended in memory with a pointer to the next line in sequence. But this I got lost in… > Most of the game is handled by the main program "OREGON TRAIL" (written by John Krenz), which loads in modules like "RIVER.LIB" and keeps access to all the variables. AppleSoft basic didn’t have the concept of libraries. Were they just POKEing values in memory, loading the next AppleSoft Basic program calling them LIBs and the next one PEEKing to retrieve the values?