This software provides a class for game overseers who wish to manage in-MUC games. It allows them to supervise players, games, and outcomes within the game.
In the Frivolity system, a Volity::Server object creates a referee object and automatically sends it to the appropriate MUC when a game starts. The class of referee it creates depends on the server object's referee_class instance variable. However, for most games, the default class is sufficient, and all game logic can reside in a Volity::Game subclass.
After being instanced, your Volity::Game subclass will have a referee object, which can be accessed through the referee() accessor. In many cases, game modules can be programmed without directly referring to the referee, while still having access to its important methods (such as seats()). The referee takes care of all the Volity protocol-level tasks, allowing developers to focus on designing a functional game.
Version 0.7.1: N/A