Changes for version 0.7.1
- volityd no longer requires that you provide a Volity::Game subclass name if you're starting a bot factory and not a game parlor
- Volity::Bot instances now track the status of other seats at the table, and offer an occupied_seats method.
- Bots now always request state on joining tables, and generally have more complete default behavior for various Volity-level RPCs that the referee might send.
- Referees now send game records to the bookkeeper only if the game is configured to be recorded.
- Referees more cleanly handle game configuation information, and keeping this infomation around between plays.
- Volity::WinnersList objects now offer a clear() method.
- More correct handling of game abandonment.
- Volity::Jabber (and its myriad subclasses) now require - and are compatible with - POE::Component::Jabber v2.
Documentation
A daemon that runs a Volity parlor or bot factory
Modules
A Perl implementation of the Volity game platform
A framework for creating automated Volity players
Tic tac toe bot module for Volity
A Volity bot factory.
base class for Volity game modules
Tic tac toe game module for Volity
Information about a completed Volity game.
a base class for Jabber-speaking Volity objects
Volity players, from a referee's perspective.
Class for in-MUC game overseers.
A Volity seat, containing some players.
A Volity game parlor.
class for Volity game record winners lists
Provides
in lib/Volity/Jabber.pm
in lib/Volity/Jabber.pm
in lib/Volity/Jabber.pm
in lib/Volity/Jabber.pm
in lib/Volity/Jabber.pm
in lib/Volity/Jabber.pm
in lib/Volity/Jabber.pm
