Menu Options:

1: Scan the Full Heist Plan

• Use with open("ioi_heist.txt", "r") and .read() to display the entire file contents at once. 

• Print it under the dramatic header "=== Intercepted Transmission ===" to simulate discovering a secret IOI communication dump. 

2: Decode Line by Line 

• • Use with open("ioi_heist.txt", "r") and .readlines() to load the contents into a list. 

  • For each line, ask the user if it’s suspicious with the prompt: Is '[line]' suspicious? (yes/no). 

  • If the user answers yes, print Flagged: [line] and store the flagged line in a list. 

  • After reviewing all lines, print the full list of flagged steps with Suspicious Steps: [list]. 

  • This mirrors the kind of threat analysis an OASIS rebel would conduct when decoding corrupt IOI missions.

3: Deploy a Counter Move 

• Prompt the user for a strategy to sabotage IOI, such as “Lock the vault tight.” 

• Use with open("resistance_moves.txt", "a") to append this to a resistance file, formatting it like Resistance Move: [user’s input]. 

4: Log the Loot at Stake 

• Ask the user how many coins IOI is targeting with the prompt: How many coins is IOI targeting?. 

• Use with open("loot_risk.txt", "w") to write this number to a file, formatted as IOI Target: [amount] coins. 

• This simulates tracking high-value digital currency targets, similar to bounty tracking or leaderboard hacking in the OASIS.

5: Scramble IOI’s File

• Use open("ioi_heist.txt", "r") and .readlines() to load the file. 

• Count how many lines contain the words "coins" or "vault". If any are found, overwrite the file using 'w' mode and replace the contents with the message SYSTEM ERROR – FILE CORRUPTED. 

• Print Sabotage Successful! to confirm. 

6: Abort Mission 

• End the program loop and print the cinematic exit line Disconnecting from OASIS... Mission Terminated. to simulate logging out of the system like a true Gunter finishing their recon.

7: Rewire the Terminal (Bonus) 

• Use open("ioi_heist.txt", "r") to read the first line with .readline(), and print the current file pointer position using .tell(). 

• Then ask the user: Enter a byte position to seek to:. 

• Use .seek() to jump to that position and read the next line or data from that spot. 

• Print the result as Terminal Rewired! Data scrambled. to simulate poking around IOI’s code or memory bank to discover or manipulate hidden data.

Before you launch any countermeasures, Parzival insists you verify the file’s integrity. One wrong move and the entire OASIS terminal could crash—or worse, trigger an IOI trace. As the Resistance's stealth-tech expert, your next task is to inspect the file object properties and confirm everything is safe to read, write, or append.

You'll tap into the system's internal diagnostic function to learn about:

• file.name: Are you targeting the correct file?

• file.mode: Are you writing, reading, or appending?

• file.closed: Is the file safely closed or still in use?

• file.readable(): Can you actually read the contents?

• file.writable(): Will this file accept your sabotage or counter move?

🔁 Bonus Variation

For students who finish early:

• Run diagnostics on any file (e.g., resistance_moves.txt, loot_risk.txt) by prompting for a filename instead of hardcoding it. 

• Add error handling in case the file doesn’t exist.