@ConditionalCoder It's mostly an organizational issue. There's nothing to enforce what script stores what data statically and where mutations can come from (any code can modify any static variable at any time). For simple things like "give me the active player character" where the gameplay design reinforces the program state (a game which promises to never have more than one player-controlled character simultaneously), it's fine. But it can quickly fall apart when you then have, say, character stats, positions (such as across scenes), inventory, etc. strictly limiting your program's growth and modularity.