Currently working on a system that is inspired by this, only being quite the opposite: instead of doing a single action the entire time over a long period of time, how about requiring a large number of actions over a long period of time?
I’m sure someone would be able to beat it in less actions than I would, as well as find the quicker solution. I’ve put in two fail-saves that will prevent some issues, but not all issues that could arise. Once I finish, I will need some help deciding which ones to remove to improve security while making it much more… puzzling.
Update: It’s close to being completely done, but I might stick with what I currently have. There’s plenty of open space to add something else, but at the same time, I’d like to work on other ideas that I have.
Note: I don’t plan on making this last too long, but long enough to cause confusion and cause someone to fail to hack the system in the process. There are already multiple ways that one could take much longer in an attempt to speed up the process, as well as some traps that aren’t obvious as well.
Visible key: Saves you from a potential trap that could be fallen into early on.
Invisible key: Takes you straight to the end. However, revealing it is an arduous process, let alone obtaining it.