The Solo Run Mechanics
Solo runs in Man 2 work differently than you would expect from the co-op version. The game still calculates lore entries and progression flags, but it handles them on a single-player thread. I spent a week trying to track down why my save file was reporting missing lore tokens after a fresh install. The core issue was that solo mode doesn't broadcast lore acquisitions to the local cache the same way co-op does. You have to actually interact with the terminal or datapad twice in quick succession for the entry to register. The first touch spawns the event flag, the second writes it to your persistent storage. Skip that double-tap and the lore panel shows empty even though you clearly read everything. I ran into this on the Cygnus Station sequence. The final entry wouldn't populate no matter how many times I reloaded. Turns out there is a timing window. If you move too fast between terminals the game registers it as a rapid-fire scan and drops the flag entirely. You have to pause roughly half a second between each interaction or the backend skips the write operation.
What Actually Triggers Lore Entries
Most people assume reading the text is enough. It is not. The game uses a separate validation pass. Your character needs to maintain line-of-sight with the source for three seconds while the interaction timer runs. Hold the button and move away and the entry gets flagged as incomplete. It shows up grayed out in your menu instead of the normal color. The counter-intuitive part is that some entries only trigger when you approach from a specific direction. The developers baked in position-based checks for certain terminals. I spent twenty minutes on the Orion Relay puzzle before realizing I had been standing behind the console instead of in front of it. Face the correct vector and it registers immediately.
Common Pitfalls
Quick travel breaks lore acquisition. If you warp to a new sector the game resets your interaction state for that zone. You have to manually walk back to any uncollected terminals. This is by design rather than a bug. The solo run path is longer precisely because it forces traversal instead of teleporting through story beats. Another issue is the inventory cap on lore items. The solo mode gives you twelve slots versus twenty in co-op. Fill those slots and you cannot pick up new entries until you review or delete existing ones. The game does not warn you when you hit the limit either. I found out the hard way when I missed a rare terminal because my slots were full.
Get the Full Details
Workarounds That Actually Help
Save frequently before entering a new lore-heavy zone. Create a manual save point right outside the room. If you miss an entry you can reload without redoing the entire section. I usually set up four or five saves per area and name them clearly like cygnus_station_1 or relay_corridor. If you want to verify your progress without replaying everything the debug console command lore_check displays all registered entries for your current save file. It is not officially documented but it works in solo mode. Just press the tilde key and type lore_check at the main menu. The game also has a skip mechanic for entries you already know. Press and hold the inventory button for three seconds on a terminal you have already scanned and it auto-fills the entry instead of requiring another full interaction. This saves maybe ten to fifteen minutes per playthrough if you are doing a second run.
When Solo Mode Fails Completely
There are scenarios where solo run simply does not work. If you mod the game files or use unofficial patches the lore tracking breaks entirely. The validation pass is hardcoded and any file alteration bypasses it. I tried running a community texture pack last month and lost about forty entries across three save files. Restored from backup but still missed two that I had not written down. Certain hardware configurations also cause issues. Running the game on integrated graphics instead of a dedicated GPU can cause the line-of-sight check to fail silently. The game thinks you have sight of the terminal but the flag never triggers. Switch to discrete GPU mode in the settings and the problem resolves immediately. If you play on ultrawide monitors the position-based checks become unreliable. The camera angle shifts slightly and the directional validation sometimes misses. I recommend sticking to 16:9 aspect ratio if you want consistent lore acquisition. The game was not tested extensively outside that range.
