This is a simple, read-only, terminal experience for tabletop RPGs. You can fork the project and change the code for your own configurations, like terminal name (or sector/station/node if sci-fi), image and messages.
The database is a simple set of JSON files.
You can host it on Github Pages for a free and fast experience and can share the link for your friends and players to use.
You can now configure and access extra servers at network.json
to login via ssh
.
Each server will treat their respective users (and mail messages) separately.
You can now configure custom software at software.json
to use it.
They're just simple simulations, but I hope you enjoy it!
The help
command has been improved.
You can now show further help instructions for internal commands.
The following command will launch a HTTP server serving the project files:
npm start
You can upload it to Github Pages or try it on your computer. You will find instructions for both options below.
You will want to customize the terminal depending on the game setting you're playing. You just have to edit the manifest.json
file.
More configuration files will be added when more functionality shows up.
The main server, which is where the terminal will start, is located as localhost
at config/network
.
The network
folder is where every server available needs to be. This is where you can configure new servers to be accessed via the ssh
command.
You need to create a folder with the name of the server address if you want to connect to custom servers.
Each server will have a distinct user list, mail messages, and server files.
That is, you can't access data of a user configured on mailserver.json
while you're at another server.
The basic configuration at manifest.json
is what you need to change to customize your terminal.
You can change the terminal year date, the server name, a customized icon, the terminal identification
(this is what is written just before the cursor), as well as the default user id and name (normally this will be "user",
but it can be whatever you want).
Note however that, once you login to the server, the username will change.
{
"year": "2377",
"serverAddress": "localhost",
"serverName": "Node Y56 Intranet",
"iconName": "Moon-icon.png",
"terminalID": "Y56",
"defaultUser": {
"userId": "user",
"password": "",
"userName": "anonymous"
}
}
{
"year": "1972",
"serverAddress": "127.0.0.1",
"serverName": "FBI: X-Files Division",
"iconName": "fbi.png",
"terminalID": "fbi",
"defaultUser": {
"userId": "user",
"password": "",
"userName": "anonymous"
}
}
The userlist.json
file is where you will add your players as users of the main server, or the NPC users of other servers.
The basic structure of the file is as follows:
You can register as many users and mail messages as you want. You just need to put a comma (,
) right after the correct enclosing }
. If you're in trouble, you can check a basic JSON tutorial, it's easy.
[
{
"userId": "8A73B5",
"password": "trustno1",
"userName": "Mulder, Fox"
},
{
"userId": "admin",
"password": "admin",
"userName": "root"
}
]
This is where you will register the server mails.
You can register as many mail messages as you want by adding a comma (,
) right after the correct enclosing }
.
You can register the same email for multiple users at once.
Note that user
will display the message for visitors if the defaultUser
userId
is registered as user
in the respective server manifest.json
.
In the body, you can break the line with a double space.
[
{
"from": "admin",
"to": ["8A73B5", "user"],
"title": "Maintenance in all servers",
"body": "This message is for all divisions of the Bureau. Starting today, the servers may suffer instability due to the latest maintenance measures. - admin"
},
{
"from": "Mike",
"to": ["admin"],
"title": "wtf are you kidding me?",
"body": "Are you kidding me? Why don't you change your password? The system is entirely compromised until you correct it. You're the sysadmin, if you're this dumb the corporation is at risk."
}
]
You can create your own custom software. At the moment you can just create simple software that will output some messages simulating an operation.
You just need to create a software.json
file describing your programs (example):
message
: the actual message to be displayed as an emulation of the software runninglocation
(optional): specify which servers will have access to the software (= where it is installed)protection
(optional): this is where you specify who can have access to the software, that is, which users have it installedhelp
(optional): a description of what the program does, that will be displayed by the help
commandclear
(optional): clear the screen before displaying the program outputdelayed
(optional): this will create an effect to each message to be slowly printed at terminal, the number is in millisecondssecretCommand
(optional): if set, the program won't be listed in tab-completion & global help
command output{
"analyze": {
"help": "Perform a sanity check of the system",
"clear": true,
"message": "System successfull analyzed!"
},
"cdata.exe": {
"protection": ["admin"],
"delayed": 2000,
"message": [
"Corrupting data.",
"Corrupting data..",
"Corrupting data...",
"0% complete",
"11% complete",
"47% complete",
"98% complete",
"System successfully corrupted!"
]
}
}
You can also include images among the content displayed:
"message": [
"We will conquer...",
"<img src='config/network/111.222.3.4/world.svg' style='width: 10rem'>",
"THE WORLD!"
]
Special effects can be added to images by adding the glitch
or particle
CSS classes:
"message": "<img src='config/network/11.152.9.6/tech.jpg' style='width: 10rem' class='glitch'>"
The config/software.json file provided includes demonstrations of those effects in the demo.exe
command.
A subtle "sync glitch" effect can be added to text by adding the desync
CSS class:
"message": "<p class='desync'>SHADY TROUBLING MESSAGE</p>"
A "glow" effect can be added to text by adding the glow
CSS class:
"message": "<p class='glow' style='font-size: 3em'>⚠ ACHTUNG ⚠</p>"
A subtle "shimmer" effect can be added to text by adding the shimmer
CSS class:
"message": "<p class='shimmer'>Zombie ipsum reversus ab viral inferno, nam rick grimes malum cerebro. De carne lumbering animata corpora quaeritis. Summus brains sit, morbo vel maleficia?</p>"
A progressive "hackish" reveal effect can be added to text by adding the hack-reveal
CSS class:
"message": "<p class='hack-reveal'>All your base are belong to us</p>"
The animation can be fine-tuned through data-
attributes:
"message": "<p class='hack-reveal' data-alphabet='uppercase' data-iterations-before-reveal=0 data-preserve-spaces='true'>All your base are belong to us</p>"
Software programs defined through software.json
are relatively dumb: they always display the same thing.
In order to make programs that can read & check players input for example, programs can also be defined in Javascript. Here is how to do so:
software.json
, but omit the message
fieldsoftware.js
that matches the name of your software programThat's it!
The Javascript function will receive command-line options in an optional args
parameter,
and this function output will define what gets printed on the terminal after its execution.
Example:
software.json
:
{
"hello": {
"help": "Say hello to someone"
}
}
software.js
:
function hello(args) {
const userName = args[0] || 'stranger';
return `Nice to meet you ${ userName }!`;
}
You can now type this in the terminal: hello Lucas
Detailed examples are available in config/software.js.
The identify
program demonstrates how to handle interactive user input by having a function returning this type of object:
{
message: // (optional) message to display above the prompt
promptText: // (optional) message to display on the left of the prompt (defaults to '>')
onInput: // Function to call once the user has submitted their input
}
The main functions are the mail
and read
terminal operations.
Once you login
, you can call the mail
function to list the user emails, and you can read
the mails you want by entering the index code (the correspondent number, letter, or string).
As this is a simple terminal emulation, you can't delete mails or mark as read. We may be able to work it out in the future, but those basic functions are enough to send some cool mysterious mails to your players' agents, or emulate a character hacking into a company to investigate a clue or something.
To login you need to enter user@password
Note the change in the terminal username
How to list and read mails
Each command a logged-in user submit is stored in an history. This history of commands can be accessed with the UP & DOWN arrows.
Virtually, each user on each server has a distinct history.
By default, the history of commands of each user is initialy empty.
You can however specify its initial command in the manifest.json
, per userId
:
"initialHistory": {
"user": [
"login admin@admin"
],
"admin": [
"ping fbi.gov"
]
}
In reality, the history of commands a player enters is only saved in their browser localStorage.
You can try help
to see a list of other functions available. The clear
function may be a useful one.
As I've said, you can use Github Pages to do that for you. If you're not used to Github, first create a Github user by registering in Github, so you can "fork" the project to your account by accessing the project page email_terminal and by clicking in the "fork" button.
Note that those two in red are the only two steps you need to take to get your terminal up and running. You need to click the Fork button, and after a few seconds, the project will be there as one of your own repositories, and then you click the Settings button.
In the settings page, scroll down to the Github Pages section and select the source as the master branch.
After a few seconds, you will be able to access your terminal at username.github.io/email_terminal (i.e. jacksonbenete.github.io/email_terminal).
Note that you can create multiple repositories and name those repositories in the Settings for each of your game tables. That way you can have one terminal ready for each setting (or for each organization your players will hack into), ex:
You just need to share the correct link with your players and wait for them to read the clues and investigate.
This is really a simple terminal emulation, as I've said. But, there are some things that could be also good to explore, like the creation of some local files or executable programs for the players to interact with.
If you want to, drop some ideas into my Github repository or send me some messages at Reddit (u/jacksonbenete) and we can work out something else.
This section lists ideas to craft the perfect terminal for your game!
telnet SERVERNAME
on the online terminalPlease suggest additions to this list based on your own usage, through a GitHub issue/PR or by contacting the author on Reddit.