The +7 Balance Engine™ requires only loose coupling with production game servers. Data analysis is all performed offline, triggered independently from production game events. Changes recommended by the +7 Balance Engine™ can be integrated back into the production servers via automation or manually, as desired.

The +7 Balance Engine™ only needs certain abstract player data. +7 Systems employees never need to see any player data directly, nor any source code. +7 Systems consultants need only to understand game mechanics.

The component model is loaded once, at design-time. It is updated when new content is released, but not when Balance Engine adjustments are made. Player action data is loaded at run-time, and can be either incremental over the course of a balance interval, or all-at-once at the close of a balance interval. Adjustment data is generated at intervals, and can either be accessed via a web report and performed manually, or propagated via an XML transaction to game servers. The intervals where balance adjustments are made are tuned according to the specifics of a particular game.

The +7 Balance Engine™ is built on J2EE Architecture, allowing deployment on a variety of hardware, depending on the maintenance preferences of the IT department. Hardware sizing is based on the size of the component base and player base in a particular game, but is not subject to severe performance limitations.

  Back to Main Page  |   Continue to Next Topic