Getting back into coding
IF-Node. March 2014: (Readme last updated December 2014)
*** This game is live and running at: http://mvta.herokuapp.com/ ***
The original desire was to allow one (or more) users to enter a single room in a game, and enter commands which would be pushed to a "watcher" queue. Another player or watcher would then pull the user commands from the queue and write responses asynchronously.
The idea came from a game that ran for a number of weeks in the office where a glass wall next to the coffee machines became a for a free-form text adventure using a brain-writing / consequences style with an unwritten rule that a person may enter a command but someone else would define what the response was.
Invariably the adventure would descend into silliness around Justin Bieber riding a flaming Aardvark or similar but the concept seemed a neat way of (re)learning development.
In the end, it's become just another text adventure engine at the moment but I still have a desire to add that real-time interaction back in (one day).
Another key part of this was simply to get back into coding properly. But by deliberately creating a legacy codebase to start with in order to truly understand what most of my dev teams really face. Understanding the difference between cramming one more feature in in a spare hour vs being disciplined and writing tests first. Seeing that tipping point where complexity gets to the point where you can't just hack things in without a regression risk any more. The need to rework poor design decisions but not having the support of working tests.
Having to cram in unit and integration tests to prize seams apart and facing the pain of adding coverage analysis (still to do!)
*** Update: December 2014 - I finally reached that tipping point in the last month and have had to start adding large regression tests back in in order to continue working relatively safely. All the simple works is done (other than adding more game data) and all most of what's left is invasive and risky. This is a great place to have ended up but it does mean there's a strong chance it's getting buggier. Welcome to the world of legacy code! ***
I know it's not the "right" way but it's how a lot of projects end up under pressure. In some way therefore, the commit history on this will be a history lesson in how to not write good software and then how to recover from it (or survive) later.
As the game currently stands it's on course to becoming quite an advanced text adventure engine. It has a dynamic aggression/affinity system that's rather novel, support for multiple NPCs and missions and directly understands well over 100 verbs but there's a load of work to do.
Other than loads of additional game mechanics, features and sample content, the other major components to work on are:
- a means of managing and editing game maps, documenting all the attributes and placeholder subtleties. The map is currently a single (large) json file and the set of attributes available for everything isn't documented. Eventually I'd like players to choose, extend and reuse maps. Right now, there's just the one.
- a means of saving and loading game state. If the server goes down or a player state is lost and if a player closes their browser, they can't recover their game. done - if the player has achieved enough to save their game
- implementing sensible object composition (1500 to 2000 line god classes prove a point but they're bleeding all over each other and not well-designed and structured. That's hurting now.)
- implementing server throttling to prevent overloading (see server config, some performance profiling and testing and finding a public host. done
- limiting the number of saved game files on the server to ensure hosting space isn't consumed. partially done - only "real" games can be saved
- server-side throttling to limit resource usage. done
- the game really needs a battery of tests but that's after the legacy code "peak" is reached (I'm nearly there I think).
- finding somewhere simple that I can get this hosted for free that doesn't require mountains of manual config. done - yay for Heroku!
1: Ensure NodeJS is installed and the relevant module dependencies are installed unsing NPM.
2: Set the following server environment variables to configure the application hostname and port
- HOSTNAME (e.g. mvta.herokuapp.com)
- PORT (e.g. 1337)
Note, if the game is running on port 80, you don't need to explicitly set port number as an environment variable.
3: MVTA is written to use either .json files or Redis (as a non-file data store) to save player game data and timed-out games.
If you're running in an environment that doesn't offer filesystem support (such as Heroku), you'll need to set up your own Redis data store (and it'll need to be password authenticated). Once you have a store available, set the following environment variables for your Redis data store
- REDISSERVER (the addressable hostname of your redis server)
- REDISPWD (the auth password of your redis server in plain text)
- REDISPORT (the port number of your redis host)
4: NodeJS may still have a default limit on the number of active http connections to 5. In order to support more connections, you'll need to set another environment variable (I think)...
- NODE_ENV: production I've not verified this bit yet though.
Running the server
MVTA has a predefined Procfile that should allow easy deployment on Heroku however if you want to run locally on a windows machine (as I have done for the last 6 months), whilst there are "better" ways to run the server the simplest is to write a batch file that sets the working directory to
- <your installation location>\js\server
Once at the working location, the game runs from the file "main.js". E.g.
- node main.js
I generally include a "pause" at the end of the batch file so that should there be a bug that causes the game to crash you can see the diagnostic output before the window quits.
The client consists of an index.html page in the root of the project and a series of referenced JS files under the js/client folder. There's also a css folder with some very basic layout and styling. The express server coded into the server.js file will automatically serve static files from the root of the node project (where the index.html file lives).
The client runs over http (but will support https) and assumes the game is running from the "root" of the node server on the node listening port.
In order to support some of the scripted calls, the client needs to know it's paired with the server. This means you need to edit a client file...
1: Modify /js/client/main.js to set the node Server name and port number:
var serverHost = 'Your-Server';
var serverPort = 1337;
The values for these 2 variables should match the corresponding environment variables on your server. If the server is running on port 80, leave serverPort undefined (but keep the variable).
These must match the entries supplied in config.js on the server.
You can also enable client "console" output by setting
- var debug = true; in the client main.js file
That's it. You're ready to go!
Launching the client
Use your favourite browser to navigate to the webroot and port of the node server: e.g. http://your-server:1337/ Upon successful launch, the console of the client should show the client and UI successfully initiated. (Sometime I'll add a server communication test here so that we can see the server is accessible and running)
This game is deliberately developed on Windows and as a result, will not use any UNIX/LINUX-only Node features or packages.
Whilst the game was originally developed in Visual Studio 2012, when I'm not in the office I've been updating and testing from a standard Windows laptop running Sublime Text or a similar basic JS editor plus command-line tooling.
For editing the game data files, I heartily recommend "JSON Editor Online" for editing the large JSON game data file - it's fast, syntax checks and formats easily. (way better than Visual Studio). (see http://www.jsoneditoronline.org)
For each server class, there is (or will be) a corresponding NodeUnit test file. these are found in \IF-Node\js\server\test\
The file naming convention for these tests is test-.test.js This allows optimum doscoverability from the VS testRunner whilst being very clear what they are.
When writing new tests, please ensure every test has its metadata correctly set to define which class it is running tests for and the set of traits being tested. This makes running subsets of tests much easier and allows us to see when a "family" of tests or traits has a problem. (you'll notice some of the existing tests have copy-paste errors in these - surprise!!!)
Please use one test file per class as much as possible and please keep these passing and growing. The tests in here are a mix of unit and functional regression tests - sad but realistic!
The game is designed to run on Node version 0.10.33 (this is the latest version that is also available on Windows) but runs fine on 0.10.34 on Linux too.
Node Module dependencies are defined in \IF-Node\package.json As of 21st September 2015 they are...
For the server:
For running NodeUnit:
End. Thanks for reading! ;)