Playing a Game

The player game tab shows one game panel. It does not show the moderator controls or the Demo top controls.

Player view with available decisions
Player view with available decisions

Game Panel

The game panel shows:

The same shared game-panel code is used for normal play and Demo play. Demo adds separate top controls above the game panel; moderator-launched player tabs do not.

Player Type And Username

The panel distinguishes:

These may be the same in simple games and different in games with roles.

Status Messages

The status row tells you whether an action is needed.

Examples:

If a button or input flashes or changes border after you act, that is feedback that the browser accepted the click or command. The server still decides whether the game advances.

Waiting States

You may wait because:

Usually you do not need to do anything. If the page stays stale for too long, refresh or rejoin with the same player name and PIN.

Decisions By Game Type

Extensive Form games usually ask you to choose an action at a tree node.

Strategic Form games usually ask for a row or column choice in a matrix.

Free Form games may show instructions, input fields, dropdowns, choices, Continue buttons, or auction pages.

Market games may show assets, orders, transaction data, price and quantity fields, and Buy/Sell controls.

Market Dashboard

Market game dashboard
Market game dashboard

Market games use a dashboard-style layout. The player sees participant information, cash, firm value, time remaining, private valuations, an order book, recent trades, open orders, and a place-order form. The exact market data depends on the game definition and current trading state.

Instruction Stages

Some games include instruction-only stages. When instructions are enabled, the player may see an instruction page before a decision page.

Read the instruction and continue when the page asks you to continue. An instruction stage is not the same as submitting a decision.

Submitting A Decision

Submit only once unless the page clearly stays editable after an error.

After a decision:

  1. the browser gives local feedback,
  2. the action is sent to the server,
  3. the server accepts or rejects it,
  4. the page updates when the next state is ready.

Some decisions advance immediately. Others wait for other players or a timer.

Game Finished

At the end you may see:

The server sends the final state. The player tab should not need to manually finish the game.