+/* Load each of our game mini-apps.
+ *
+ * Each "engine" we load here must have a property .Game on the
+ * exports object that should be a class that extends the common base
+ * class Game.
+ *
+ * In turn, each engine's Game must have the following properties:
+ *
+ * .meta: An object with .name and .identifier properties.
+ *
+ * Here, .name is a string giving a human-readable name
+ * for the game, such as "Tic Tac Toe" while .identifier
+ * is the short, single-word, all-lowercase identifier
+ * that is used in the path of the URL, such as
+ * "tictactoe".
+ *
+ * .router: An express Router object
+ *
+ * Any game-specific routes should already be on the
+ * router. Then, LMNO will add common routes including:
+ *
+ * / Serves <identifier>-game.html template
+ *
+ * /player Allows client to set name or team
+ *
+ * /events Serves a stream of events. Game can override
+ * the handle_events method, call super() first,
+ * and then have code to add custom events.
+ *
+ * /moves Receives move data from clients. This route
+ * is only added if the Game class has an
+ * add_move method.
+ */