tylerhcarter / codename-shutdown Goto Github PK

Should have a user id, username, password, and administrative flag.

This will allow players to create new users that they can use to log into the service.

Leave clues in commits or find other ways of making the github history or file browser part of the game. This requires that some of the game mechanics not be easily unlockable just by browsing the source code, however the point where this concept is added to the game should be past the point where they've figured out how to look up answers easily.

Basically, any unlocks after this should not be simple password solving.

This would allow for users to come back and play the game later better.

Questions should be locked from being answered unless the lock is removed through the terminal. These locks could be time locks or some other form of lock to make it realistic.

There needs to be more questions to push the user forward.

One of the command line tools that should be available is the find_answers command. This should be unlockable via doing some other things in the command line.

The command should allow the user to look up answers to questions in the system. However, some questions might require a password.

This will let us query the informations later on when the user gets to the command line experience.

Each question should have a question id, an answer, and an optional password field. This password field will be used if viewing the answer via the commandline is restricted.

The player needs to encounter the element that there is a purpose behind the playground they weren't aware of. At this point, it will probably be that the site team3128.org will be destroyed if they don't take action.

The big question is how will that element be introduced?

This allows for terminal commands to translate into server commands.

After the first login, there should never be another opportunity to log in via the tyler user.

For a single player environment, this could just be a check if there are any users in the database. A better solution might be a $_SESSION variable that is turned on when the user first encounters the database error and allows the login once.

Add in various commands like favorite_books and favorite_people etc to create room to explore on the tyler account.