Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try [email protected] or [email protected]
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
First, use the first 10 bytes of the file as a sanity check. throw in two random bytes like 0x55AA so you know the file isn’t broken. add a loop counter to track how many times you’ve lived the same week (bonus points for crying when you hit loop 9999), toss in a basic checksum to make sure your data isn’t glitched.
Then dedicate like 800 bytes to a super compressed log. Each entry is 8 bytes: a code for what you tried (like action 23 = “mess with the sketchy microwave”), the day and time crammed into 2 bytes, a yes/no/weird result, and a tiny note like “key under rug” but in code. Only keep the last 100 entries so you don’t run out of space.
The leftover 200-ish bytes are for tracking. Use bits to mark places you’ve already checked (like “room D14 done”) and actions you’ve tried (so you stop repeating “throw spaghetti at the wall”).
Every reset, open the file, see your last loop’s fails (like “loop 420: died petting a possum”), Then try something new, focus on unmarked areas and untested actions this is because if you notice a pattern (like “tv static every tuesday”), write it as “tues=F9=glitchinmatrix” or whatever.
After 200 loops, maybe you’ll crack the code (literally) or realize the exit was behind the fridge the whole time.Oor you’ll just accept your fate and start a cult (the 1k chosen ones!) . Either way, you’re out.
tldr: use the 1kb to avoid repeating mistakes, track patterns, and maybe escape before you start talking to a lamp.
How much time are you spending devising this system? Because you're going to have to devise the system anew each week, unless you also store instructions for deciding on a system in the file.
How do you store what killed you? Theoretically you can't edit the log once you die (you'd just start the new loop, with no memory of what killed you).
More importantly, why do you want to escape? This hypothetical time loop sounds awesome.
Heh.
Awesome plan, I like it!