Assignment Settings Reference

Assignment defines how participants become Player Types or named strategic Players, how sessions repeat, and how results are rounded and synchronized.

Participants

Players per session is the target number of participants in one session.

• A positive number creates fixed-size sessions. Execution waits until the required number has joined.
• 0 means open. The runtime does not use a fixed fill count.
• Rooms may expose an adjustable participant count when the definition permits it. That run-specific value does not rewrite the saved definition.

Player Types

Player Types describe participant categories used by Pages, Auctions, Markets, and formulas.

• Order changes the type order. The first row is marked as the start type.
• Player Type is the author-facing name.
• Number or Weight controls allocation.
• Condition is an optional formula restricting when the type is eligible.
• plus adds a type; Trash removes it after confirmation.

Removing or renaming a Player Type can affect Audience rules, Market accounts, and other references. Review Validation after structural changes.

Allocation Mode

• Number treats each allocation value as a requested participant count. The values should fit the configured Players per session.
• Weight treats values as relative proportions. The runtime derives counts while preserving the configured distribution as closely as possible.

An allocation value of zero prevents ordinary allocation to that type unless another game-specific mechanism changes the participant's type.

Strategic Players

Extensive and Strategic Form games can define named Players separately from Player Types. A Player is a role inside the game structure, such as the actor at a tree node or matrix dimension.

• Order determines the stable role order; the first is marked as start.
• Name is the author-facing strategic role.
• Condition can restrict eligibility.
• adding or removing Players synchronizes tree and matrix payoff structures where possible.

One participant may be assigned to a Player Type while the game mechanism refers to a strategic Player. The two concepts should not be treated as interchangeable.

Rounds And Timing

• Number of rounds is the configured maximum number of rounds and must be at least one.
• Probability to continue is a formula used when continuation between rounds is probabilistic.
• Game duration is a formula returning the game duration in seconds. Empty means unlimited.

Stage-level time limits remain separate from overall game duration.

Randomization

• Shuffle Player Types randomizes Player Type allocation rather than always following configured order.
• Shuffle subjects across sessions randomizes how participants are grouped across repeated sessions.
• Shuffle Players randomizes assignment to strategic Players in Extensive and Strategic Form games.

Randomization changes allocation, not the identity or order of the definitions themselves.

Round Completion

• Synchronize rounds holds sessions at the round boundary until the required peer sessions are ready.
• Summary after each round presents Results after each completed round.
• Final summary immediately presents the final Results as soon as the final round completes.

These policies control when summaries appear. They do not define the content of the Results Pages.

Execution And Output

Execution order selects one of the execution protocols supported by the current definition. Incompatible choices are shown as unavailable rather than silently accepted.

Fraction digits controls the standard numeric rounding used by execution and presentation. Individual fields or table columns may define more specific precision.

Preview Assignment

Preview assignment evaluates the current Assignment without starting a run. Use it after changing counts, weights, conditions, or shuffling to verify that the resulting allocation is plausible.

Preview does not save the definition and does not create a session.