Board Game Arena - User contributions [en]

Gamehelpthenetworksprimetime

2026-10-20T03:46:44Z

Augment reality:

__TOC__

== Overview ==

In '''The Networks: PrimeTime''', each player runs a television network for four rounds. You will sign Stars, land Ads, produce Shows, and arrange those Shows in your lineup to attract viewers while keeping your network solvent.

Your final score is the total of your four round scores plus end-game bonuses. The player with the most viewers wins. Tied players share the victory.

== The basic idea ==

Your network has three main areas:

* Your '''lineup''' contains one Show in each timeslot: Daytime, Primetime, and Late Night.
* Your '''green room''' holds Stars, Ads, and Network cards you have acquired but have not attached or used. There is no hand limit, and cards may remain there between rounds.
* Your '''reruns''' contain Shows that have been canceled. They score again at the end of the game.

The shared '''market''' contains the Shows, Stars, Ads, and Network cards available to everyone. Cards taken from the market are not replaced during the round. A completely new market is dealt after the round ends.

Only cards in your lineup count for normal round income, expenses, and viewers. Cards waiting in your green room do not.

== Setup and Pilot Season ==

BGA performs the physical setup automatically. Every player begins with three Starter Shows, one in each timeslot, and receives cash based on starting turn order.

=== Normal Pilot Setup ===

Each player is privately dealt four Pilot Season cards and keeps two.

* Pay the costs of kept Stars and Shows.
* Gain the signing bonuses of kept Ads.
* Put kept Stars and Ads in your green room.
* Produce any kept Pilot Shows and place them in your lineup.

Unchosen Pilot cards are removed from the game.

=== Simplified Pilot Setup ===

Each player receives two Pilot Stars and/or Ads and keeps both automatically. Pilot Shows are not used. This option is intended for a faster first game.

== Playing a round ==

Starting with the first player, players take one action at a time in turn order. A player who passes takes no more normal turns that round. The round ends after everyone has passed.

On your turn, take '''one''' of the following actions.

=== Sign a Star ===

Choose a Star from the market, pay its signing cost, and put it in your green room. A Star cannot be attached immediately unless a card effect says otherwise.

=== Sign an Ad ===

Choose an Ad from the market, immediately gain its signing bonus, and put it in your green room. Signing an Ad does not cost money.

=== Take a Network card ===

Choose a Network card from the market.

* '''Immediate''' cards resolve at once.
* '''Use once''' cards stay in your green room until used, then are discarded or otherwise consumed as shown by BGA.
* '''Ongoing''' cards provide a continuing ability.
* '''Game End''' cards score during final scoring.

Using an available Use Once Network card is a free action and does not replace your normal action. Follow the card text when it conflicts with a general rule.

=== Produce a Show ===

You cannot store an unproduced Show in your green room. When you take a Show from the market, you must be able to complete all of these steps:

# Pay the Show's production cost.
# Attach Stars and Ads from your green room. Every coloured slot is required; grey slots are optional. You may fill any number of optional slots while producing the Show.
# Choose a timeslot in your lineup. Cancel the Show already there, if any, and put the new Show in its place.
# Place the Show's season marker. In a preferred timeslot it begins on the top row; outside a preferred timeslot it begins on the '''X''' row, shortening its useful life as well as reducing its early viewers.
# Advance one space on the matching genre track and immediately resolve any bonus reached.

A half-Star/half-Ad slot can hold either type, but each slot holds only one card.

=== Add or replace a Star or Ad ===

Move '''one''' Star or Ad from your green room to a compatible slot on a Show in your lineup. You may instead replace an attached card with another card that can legally occupy that slot. The removed card is discarded; it does not return to your green room.

When a Show has a wild slot, you may sometimes replace a Star with an Ad or vice versa, provided the final set of attachments still fits all of that Show's slots.

=== Pass ===

Take the leftmost available place on the pass track and choose its cash or viewer reward. Earlier pass positions offer better rewards. Cash is gained immediately; viewers are added to this round's score.

Passing is permanent for the rest of the round. When only one player has not passed, that player may take as many consecutive actions as desired. When finished, that player passes into the last, cash-only space.

== Shows, Stars, and Ads ==

=== Seasons and timeslots ===

Each Show's season marker indicates its current viewers. After round scoring, it moves down one row. If it moves beyond the bottom of the card, the Show is canceled.

Most Shows have a preferred timeslot. Scheduling a Show elsewhere puts its season marker directly on the X row instead of its first row. Starter Shows have no preferred timeslot.

=== Attachment conditions ===

Some Stars and Ads have a condition, such as a genre, timeslot, or number of other attachments.

* If the condition is met when the card is attached, attach it upright and use its normal values.
* If the condition is not met, rotate it and use its grey values.
* The card normally keeps that orientation even if the lineup later changes. Only a card effect can rotate it afterward.

For a timeslot condition, use the timeslot the Show actually occupies, not the Show's preferred timeslot.

'''Promo Ads''' are different: when attaching one, either pay its printed cost to keep it upright or attach it rotated. An upright Promo supplies viewers and income; a rotated Promo supplies only its rotated income.

=== Canceling a Show ===

When a Show is canceled:

# Its season marker returns to your supply.
# All attached Stars and Ads are discarded unless an effect says otherwise.
# The Show goes faceup to your reruns.

You may cancel a Show only when a rule or card effect tells you to do so, such as replacing it, aging it beyond its final season, or being unable to pay upkeep.

== End of the round ==

After everyone has passed, BGA resolves these steps in order.

# '''Upkeep:''' Add all income in your lineup, then subtract all expenses in your lineup. Gain a positive difference or pay a negative difference.
# '''Score the lineup:''' Add the current viewers from your Shows and attached cards, plus pass-track viewers and other applicable bonuses.
# '''Age Shows:''' Move every season marker down one row. Cancel Shows whose markers move off their cards.
# '''Check genres:''' Any genre-track advances and bonuses from Shows produced this round are confirmed.
# '''Clear the pass track.'''
# '''Set next round's first player or turn order.'''
# '''Refresh the market:''' Discard all remaining market cards and deal a full new display.

If you cannot afford upkeep, you must cancel a Show of your choice and recalculate. Continue until you can pay or have no Shows left. A Show canceled during upkeep scores no viewers that round because upkeep happens before scoring.

The '''Forecast''' above your lineup shows what you would earn and score if the round ended now. It does not include choices that would happen only at round end.

== Genre tracks ==

Whenever you produce a Show, advance one space on its genre track. If you have not entered that genre before, place your marker on space 1.

Some spaces award an immediate choice of cards. BGA presents the eligible cards privately in the choice strip. Reaching the top does not give another immediate reward, but it is worth 15 end-game viewers. Further advances in that genre have no effect.

== Game end and final scoring ==

After round 4, resolve upkeep, lineup scoring, and aging normally. Then score:

* '''Genres:''' the value reached on every genre track where you have a marker.
* '''Reruns:''' the rerun value printed on every canceled Show in your reruns.
* '''Network cards:''' all applicable Game End effects.
* '''Cash:''' 1 viewer for every $3M remaining, rounded down.

Add these bonuses to all four round scores. The highest total wins; ties are shared.

== Reading the interface ==

=== Your table ===

* '''Market''' (top): Shows, Stars, Ads, and Network cards available to take, with deck counts. With Telly Time, the pass board sits above it.
* '''Your area''': green room on the left, player board in the middle, and lineup on the right.
* '''Opponents''': use the tabs to inspect another player's area. Lineups, green rooms, and reruns are public.
* '''Scoreboard''': round scores followed by end-game categories. Use the arrow to switch pages.

=== Tooltips ===

* Hover over a card, or long-press it on mobile, to read its printed information in words.
* Hover or long-press the '''Actions''' and '''Round End''' areas of your player board for a reference.
* With Executives, hover or long-press the board for that Executive's abilities and drawbacks.
* With Telly Time, hover or long-press the genre grid for its rules.
* On mobile, tap elsewhere to close a tooltip.

=== Forecast ===

* Above your lineup, '''Forecast''' shows the viewers and upkeep you would receive if the round ended now, before Quiz purchases and other round-end choices.
* Beside each Show, a badge shows that Show's current viewers and upkeep.
* A cube on your board's '''Round Scoring Track''' marks the same forecast total. Past 50, it laps and displays +50.

=== Choices and confirmations ===

* Mandatory choices, such as a genre bonus or Network effect, appear in a strip at the top of the table.
* Cards and Shows that cannot be used for the current action are dimmed.
* Most actions require confirmation in the status bar after a short countdown. Change the delay under '''Action confirmation delay''' in the game preferences.
* At round end, scoring may pause while a player resolves an effect.

== How to read the cards ==

=== Shows ===

# '''Genre''': the track advanced when the Show is produced.
# '''Expenses''': paid during every upkeep while the Show remains in the lineup.
# '''Preferred timeslot''': sun = Daytime, sunset = Primetime, moon = Late Night.
# '''Viewers by season''': the viewers scored on each row.
# '''X row''': the starting row when the Show is outside a preferred timeslot.
# '''Production cost''': paid once when producing the Show.
# '''Attachment slots''': coloured slots are required; grey slots are optional; split slots hold either a Star or an Ad.
# '''Rerun viewers''': scored at game end after the Show has been canceled.

=== Stars ===

# '''Signing cost''': paid when the Star is taken.
# '''Expenses''': paid at upkeep while attached to a Show.
# '''Viewers by season''': added to the Show while upright.
# '''Rotated values''': used when the Star was attached without satisfying its condition.
# '''Condition or special effect''': determines how the card is attached or used.

=== Ads ===

# '''Signing bonus''': gained immediately when the Ad is taken.
# '''Income''': gained at upkeep while attached.
# '''Rotated income''': used when the Ad is attached rotated.
# '''Condition or Promo cost''': determines whether the Ad is upright or rotated.

=== Network cards ===

# '''Timing icon''': ! = Immediate, 1x = Use Once, infinity symbol = Ongoing, eye = Game End.
# '''Icon summary''': a compact picture of the effect.
# '''Rules text''': the full effect in words.

== Game options ==

=== Pilot Setup ===

* '''Normal:''' choose two cards from a private four-card Pilot Season offer.
* '''Simplified:''' automatically keep two Pilot Stars and/or Ads; Pilot Shows are omitted.

=== Turn Order ===

* '''Fixed Order:''' play clockwise; the first-player marker moves one seat after each round.
* '''Low to High:''' after round 1, players act from the lowest previous-round score to the highest. For a tie, the player who was later in the previous order acts earlier.

== Expansion modules ==

Expansion availability depends on the options offered at the table. The modules may be used separately or together.

=== Telly Time ===

Telly Time adds a fourth timeslot, three genres, and a personal Genre Grid in place of the normal genre tracks.

==== Genre Grid ====

* The first Show you produce in a genre fills that genre's square.
* Completing a row, column, or diagonal awards the bonus at the end of that line. One placement can complete more than one line.
* When passing, gain $1M for each empty square in addition to any other eligible pass reward.
* At round end, score 1 viewer for each filled square.
* Normal genre-track end-game scoring does not apply.

==== Timeslots and genres ====

* '''Weekend''' is a fourth timeslot.
* A Show with two preferred timeslots may use either without penalty. '''ANY''' means any available timeslot.
* '''Kids''' Shows cannot air in Primetime or Late Night.
* Each '''Quiz''' Show may spend up to $5M during scoring for 1 viewer per $1M.
* Each '''Chat''' Show gains viewers equal to the current Star viewers on your other Shows.

=== Moguls ===

Moguls are powerful cards with Immediate, Use Once, Ongoing, or Game End abilities. A player normally acquires at most one Mogul.

==== Acquiring a Mogul ====

* A Mogul token begins on space 3 of each genre track.
* The first eligible player to land there takes the token instead of the normal Network-card bonus, draws three Moguls, and keeps one.
* After a token has been removed, that space gives its normal Network-card bonus to later players.
* A player who already owns a Mogul receives the normal genre bonus instead of another Mogul.

Immediate Moguls remain owned after resolving. A used Use Once Mogul flips facedown but still counts as the player's Mogul. Ongoing and Game End Moguls score or operate at their stated timing.

'''With Telly Time:''' the second completed Genre Grid line awards a Mogul instead of its printed reward; draw two and keep one.

=== Executives ===

Executives replace the standard player boards with asymmetric abilities and drawbacks. Each player privately receives two Executives and chooses one, including the preferred artwork side.

* Complexity 1 Executives make relatively small rules changes.
* Complexity 2 or 3 Executives change more of the normal turn, economy, or scoring rules.
* Hover or long-press an Executive board to read its full abilities and drawbacks.
* BGA automatically applies special interactions when Executives are combined with Telly Time or Moguls.

The '''Specialist''' requires the Moguls module and can acquire two Moguls instead of one.

== Strategy tips ==

* Producing a strong Show early lets it score for more rounds. Putting it outside its preferred timeslot both lowers its opening value and makes it age out sooner.
* Attach optional Stars and Ads while producing when practical. A later Add or Replace action handles only one card.
* Watch both cash now and upkeep later. A lucrative Ad can support several expensive Shows and Stars.
* Passing early can secure a strong reward, but leaves more of the shrinking market to the remaining players. The last player may take several consecutive actions.
* Genre bonuses are useful, but repeatedly advancing one genre can compete with building a balanced, profitable lineup.
* Before confirming a Show, check its production cost, required slots, timeslot row, genre bonus, and forecasted upkeep together.

Gamehelpthenetworksprimetime

2026-10-17T15:04:28Z

Augment reality: modified expansion details

== Reading the interface ==

=== Your table ===
* '''Market''' (top): Shows, Stars, Ads and Network cards you can take, with deck counts. With Telly Time, the pass board sits above it.
* '''Your area''': green room (Stars, Ads, Network cards and Moguls you own) on the left, your player board in the middle, your lineup on the right.
* '''Opponents''': use the tabs to view another player's area. Everything in a lineup and in reruns is public.
* '''Scoreboard''': round scores, then endgame scores (Genres, Reruns, Network/Moguls/Executives, Cash). Use the arrow to switch pages.

=== Tooltips ===
* Hover over any card (or long-press it on mobile) to read everything printed on it in words.
* Hover or long-press the '''Actions''' and '''Round End''' areas of your player board for the printed reference.
* With Executives, hover or long-press your board for your Executive's abilities and drawbacks.
* With Telly Time, hover or long-press your genre grid for how it works.
* On mobile, tap anywhere else to close a tooltip.

=== Forecast ===
* Above your lineup: '''Forecast''' shows the viewers and upkeep you would get if the round ended now (before Quiz purchases and round-end choices).
* Beside each Show: a badge with that Show's viewers and upkeep this round.
* On your player board: a cube on the '''Round Scoring Track''' marks the same forecast total (past 50 it laps around and shows +50).

=== Choices and confirmations ===
* When you must choose (a genre bonus, a Network card's effect, a Mogul, a grid line...), the choice appears in a strip at the top of the table. The rest of the table stays visible.
* Cards and Shows you can't use for the current action are dimmed; valid targets stay bright.
* Most actions ask you to confirm in the status bar, with a short countdown. Change this in the game preferences under '''Action confirmation delay''' (0, 3, 5 or 10 seconds, or Off).
* At round end, the game may wait for a player to make a round-end choice (for example Surpriser) before scoring continues.

== How to read the cards ==

=== Shows ===
# '''Genre''': producing the Show advances you on this genre track.
# '''Expenses''': paid every round at upkeep.
# '''Preferred timeslot''': sun = daytime, sunset = primetime, moon = late night.
# '''Viewers by season''': scored each round. The marker moves down one row per round, and the Show is canceled when it runs off the bottom.
# '''The X''': outside its preferred timeslot, the Show starts on this row instead.
# '''Production cost'''.
# '''Attachment slots''': coloured = required, grey = optional. A half Star/half Ad slot takes either.
# '''Rerun viewers''': scored at game end once the Show has been canceled.

=== Stars ===
# '''Signing cost'''.
# '''Expenses''': paid every round at upkeep (if shown).
# '''Viewers by season''': when attached upright.
# '''Rotated values''' (upside down): used when the Star is attached rotated.
# '''Condition''': if met, the Star stays upright; otherwise it is rotated. Some Stars have an effect on a black strip instead.

=== Ads ===
# '''Signing bonus''': gained when you sign the Ad.
# '''Income''': gained every round at upkeep.
# '''Rotated income''': when the Ad is attached rotated.
# '''Condition''': if met, the Ad stays upright; otherwise it is rotated. Promos instead let you pay to keep them upright.

=== Network cards ===
# '''Timing''': ! Immediate (resolves when taken), 1x Use once, ∞ Ongoing, eye = Game end.
# '''The effect''', in icons.
# '''The effect''', in words.

== Expansion notes ==

##Expansions

The game includes three optional modules: **Telly Time**, **Moguls**, and **Executives**. They can be played separately or combined.

###Telly Time

Telly Time changes the base game with a fourth timeslot, new genres, and a Genre Grid that replaces the usual genre tracks.

**Genre Grid**

- Each genre has one space on your grid. Producing your first Show of that genre fills its space.
- Completing a row, column, or diagonal earns the bonus shown at the end of that line. Multiple lines can score at once.
- When passing, gain $1M for each empty space, regardless of your pass bonus.
- At round end, score 1 viewer for each filled space.
- Genre tracks no longer score endgame viewers.

**Timeslots**

- Weekend is a fourth timeslot and works like the original three.
- Shows with two preferred timeslots can use either without penalty.
- Shows marked ANY can use any timeslot without penalty.

**New Genres**

| Genre | Special rule |
|---|---|
| Kids | Cannot air in Primetime or Late Night |
| Quiz | Pay up to $5M when scoring to gain 1 viewer per $1M |
| Chat | Gains viewers equal to the current viewers from Stars on your other Shows |

###Moguls

Moguls are powerful cards that give your network special abilities and scoring bonuses. You can normally acquire only **one Mogul per game**.

**Getting a Mogul**

- The first player to reach space 3 on a genre track takes its Mogul token instead of the usual Network card bonus.
- Draw 3 Mogul cards and keep 1.
- Once you've acquired a Mogul, you receive normal genre bonuses from any remaining Mogul spaces you reach.
- Other players can collect the normal Network card bonus after a Mogul token has been removed.

**Using Moguls**

Moguls work much like Network cards, with a few differences:

- **Immediate:** Resolve the effect, but keep the card for its other abilities.
- **One-time:** Flip the card facedown after use. It still counts as your Mogul.
- **Ongoing:** Provides continuing abilities or round-end viewers.
- **Game End:** Adds viewers to your final score.

**With Telly Time:** Your second completed Genre Grid line awards a Mogul instead of its normal bonus. Draw 2 Moguls and keep 1.

###Executives

Executives replace the standard Player Boards with unique abilities and drawbacks. Each player chooses one of two randomly offered Executives at the start of the game.

**Abilities & Drawbacks**

- Every Executive changes how you play, with special advantages balanced by restrictions or penalties.
- Some affect drafting, production, income, or scoring. Others change your actions or turn order.
- Executives have complexity ratings from 1 to 3, indicating how many unusual rules they introduce.

Your Executive's abilities and drawbacks are displayed on your Player Board.

**Combining Expansions**

Some Executives have special interactions with Telly Time or Moguls. These adjustments are handled automatically by BGA.

The Specialist Executive requires Moguls and can acquire two instead of one.

Gamehelpscovilleseconded

2026-10-16T10:45:42Z

Augment reality: Reworded and formated existing text

UI help: At the bottom of the board is a button to toggle player hand float/anchor. Beneath the trophies is a toggle for award choies. At the bottom right of the field that toggles permanent visiblity of breeding outcomes. The pepper next to the recipes toggles a mode that indicates which peppers you still need before you can fill a recipe.

==Turn Structure==
Every turn, you '''must plant a pepper''' and '''must move your farmer'''.
{| class="wikitable"
!Phase!!Turn order
|-
|Planting||1 → 6
|-
|Harvesting||6 → 1
|-
|Fulfillment|| 1 → 6
|}
===Bidding and Turn Order===
*Tied bids are resolved in favor of the player who planted earlier in the previous round.
*Players who bid nothing are assigned the highest available turn-order positions, using the previous round's order.
==Important Rules==*Only one of each market card, recipe, and planting award may be acquired per round.
*Only one pepper color may be sold per round.
* Peppers acquired from the market may be used to fulfill recipes in the same round.
==Scoring==
{| class="wikitable"
!Item!! Points
|-
| Bonus card||4 VP each
|-
|Coins||1 VP per 3 coins
|}'''Note:''' Bonus cards and coins are hidden in player hands, so their points are not included in the live score displayed during the game.
== Game End Conditions==
End conditions are checked at the end of each round.
===Morning===
If fewer recipes remain than the number of players, one final round is played.
===Afternoon===
*If either the recipe supply or market supply drops below the player count, one final round is played.
*If both supplies drop below the player count, the game ends immediately.
==Board Game Arena Interface==
{| class="wikitable"
!Control!!Function
|-
|Hand toggle||Float or anchor your player hand
|-
| Award toggle||Change award display
|-
| Breeding toggle||Keep breeding outcomes visible
|-
|Pepper icon beside recipes||Highlight peppers still needed for recipes
|-
|Available Cards||View available cards without relying on hover pop-ups
|}The Available Cards button is particularly useful on mobile devices.
==LABS Expansion==
*Adds 12 recipe cards and 12 market cards.
*Each player receives an additional bonus planting token.
*No awards are removed at lower player counts.

Gamehelpthenetworksprimetime

2026-10-03T17:18:34Z

Augment reality: Created page with "== Reading the interface == === Your table === * '''Market''' (top): Shows, Stars, Ads and Network cards you can take, with deck counts. With Telly Time, the pass board sits above it. * '''Your area''': green room (Stars, Ads, Network cards and Moguls you own) on the left, your player board in the middle, your lineup on the right. * '''Opponents''': use the tabs to view another player's area. Everything in a lineup and in reruns is public. * '''Scoreboard''': round scor..."

Gamehelpscovilleseconded

2026-09-20T04:32:37Z

Augment reality: UI help

UI help: At the bottom of the board is a button to toggle player hand float/anchor. Beneath the trophies is a toggle for award choies. At the bottom right of the field that toggles permanent visiblity of breeding outcomes. The pepper next to the recipes toggles a mode that indicates which peppers you still need before you can fill a recipe.

On your turn: You MUST plant a pepper. You MUST move. Turn order is 1 to 6 for planting, 6 to 1 for harvesting, 1 to 6 for fulfillment. If players tie on a bid, the player who previously planted first gets priority. If players bid nothing, they get moved to the highest (1 being highest) open slot in previous turn order (1 to 6).

Only one of each market/recipe/planting award can be acquired each round. Similarly only one color of pepper may be sold. You may use peppers acquired from the market to fulfill recipes in the same round.

Bonus cards are worth 4pts at game end; coins are worth 1pt/3 coins. Since player hands are hidden, neither are part of the score calculated during the game.

Game End Conditions (checked at round end):
Morning: If recipe count < player count, only one more round is played.
Afternoon: If recipe or market count < player count, one more round is played. If recipe AND market count < player count, game ends immediately.

FYI:

The "available cards" button is intended as an alternative to hover-over pop-ups, which aren't as nice in mobile form.

LABS Expansion adds 12 recipe and 12 market cards; players get an additional bonus planting token and no awards are removed at low player count.

Gamehelpscovilleseconded

2026-08-05T05:16:11Z

Augment reality:

On your turn: You MUST plant a pepper. You MUST move. Turn order is 1 to 6 for planting, 6 to 1 for harvesting, 1 to 6 for fulfillment. If players tie on a bid, the player who previously planted first gets priority. If players bid nothing, they get moved to the highest (1 being highest) open slot in previous turn order (1 to 6).

Only one of each market/recipe/planting award can be acquired each round. Similarly only one color of pepper may be sold. You may use peppers acquired from the market to fulfill recipes in the same round.

Bonus cards are worth 4pts at game end; coins are worth 1pt/3 coins. Since player hands are hidden, neither are part of the score calculated during the game.

Game End Conditions (checked at round end):
Morning: If recipe count < player count, only one more round is played.
Afternoon: If recipe or market count < player count, one more round is played. If recipe AND market count < player count, game ends immediately.

UI help: There is a button on the bottom right of the field that toggles permanent visiblity of breeding outcomes. The "available cards" button is intended as an alternative to hover-over pop-ups, which aren't as nice in mobile form.

LABS Expansion adds 12 recipe and 12 market cards; players get an additional bonus planting token and no awards are removed at low player count.

Gamehelpscovilleseconded

2026-08-05T04:45:09Z

Augment reality: added bidding logic

On your turn: You MUST plant a pepper. You MUST move. Turn order is 1 to 6 for planting, 6 to 1 for harvesting, 1 to 6 for fulfillment. If players tie on a bid, the player who previously planted first gets priority. If players bid nothing, they get moved to the highest (1 being highest) open slot in previous turn order (1 to 6).

Only one of each market/recipe/planting award can be acquired each round. Similarly only one color of pepper may be sold. You may use peppers acquired from the market to fulfill recipes in the same round.

Bonus cards are worth 4pts at game end; coins are worth 1pt/3 coins. Since player hands are hidden, neither are part of the score calculated during the game.

Game End Conditions (checked at round end):
Morning: If recipe count < player count, only one more round is played.
Afternoon: If recipe or market count < player count, one more round is played. If recipe AND market count < player count, game ends immediately.

LABS Expansion adds 12 recipe and 12 market cards; players get an additional bonus planting token and no awards are removed at low player count.

Gamehelpscovilleseconded

2026-08-05T04:37:13Z

Augment reality: Created page with " On your turn: You MUST plant a pepper. You MUST move. Turn order is 1 to 6 for planting, 6 to 1 for harvesting, 1 to 6 for fulfillment. Only one of each market/recipe/planting award can be acquired each round. Similarly only one color of pepper may be sold. You may use peppers acquired from the market to fulfill recipes in the same round. Bonus cards are worth 4pts at game end; coins are worth 1pt/3 coins. Since player hands are hidden, neither are part of the score c..."

On your turn: You MUST plant a pepper. You MUST move. Turn order is 1 to 6 for planting, 6 to 1 for harvesting, 1 to 6 for fulfillment.

Only one of each market/recipe/planting award can be acquired each round. Similarly only one color of pepper may be sold. You may use peppers acquired from the market to fulfill recipes in the same round.

Bonus cards are worth 4pts at game end; coins are worth 1pt/3 coins. Since player hands are hidden, neither are part of the score calculated during the game.

Game End Conditions (checked at round end):
Morning: If recipe count < player count, only one more round is played.
Afternoon: If recipe or market count < player count, one more round is played. If recipe AND market count < player count, game ends immediately.

LABS Expansion adds 12 recipe and 12 market cards; players get an additional bonus planting token and no awards are removed at low player count.

Gamehelpkalua

2026-07-08T00:20:09Z

Augment reality:

Each player starts with: 10 families, 1 leader, 5 prayer and happiness at 5.

Place 3 atheist families per player on the Kalua board and each player draws cards from either deck until they have five total.

Turn Sequence:

1. If you're the round leader and have fewer than 5 cards, draw until you have 5. Otherwise, draw 1 card from either deck.

2. Then, beginning with the active player, each player may (if they still have their leader) perform one action:

Increase your Happiness by 1.
Convert 2 atheist families.
Convert 1 family from another player's religion.
Sacrifice your leader to immediately convert up to 5 atheist families.

3. The active player may play any number of action cards. Once they decide to pass, every other player may respond with one card.

4. Resolve cards in the order they were played.

Card types:

Bonus – Helps yourself.
Local Disaster – Targets one religion.
Global Disaster – Affects everyone. Pay extra prayer to protect yourself (avoid) or amplify (double) the disaster.

Cards can affect: Happiness, prayer, families, atheists, force players to discard, recover a sacrificed leader, or create lasting effects (Temples or Amulets)

The cycle can repeat until the active player decides not to play any cards. They then trigger the "convert" phase.

4. Convert Families

Compare each religion's Happiness.

If everyone is equally happy, nothing happens. The unhappiest religion contributes 2 families to the conversion pool.
Middle religions contribute 1 family.
The happiest religion(s) divide the converted families (maximum 3 each).
Any leftovers become atheist families on the Kalua board.

5. Gain Praying Points

Each religion gains:
1 prayer per 5 families (rounded up)
+4 prayer if it is the unhappiest religion; +2 prayer if it is neither the happiest nor the unhappiest

Other Info:

Temple remains in play until destroyed and grants extra prayer each turn.
Amulets may be discarded to prevent losing families from a single card.
The New Leader card replaces a sacrificed or lost leader by promoting one of your families.

Players may purchase additional cards at any time for 5 prayer each.

Winning the Game:

At the end of any round, if only one religion still has families, that religion wins. A religion is not eliminated while its leader survives—the leader can continue recruiting followers and potentially rebuild the religion.

If a Global Disaster eliminates every remaining family simultaneously, the religion that had the most families immediately before the disaster wins. If tied, all tied religions share the victory.

Gamehelpkalua

2026-07-07T22:11:48Z

Augment reality: Added play sequence, win condition and general help

Each player starts with: 10 families, 1 leader, 5 prayer and happiness at 5.

Place 3 atheist families per player on the Kalua board and each player draws cards from either deck until they have five total.

Turn Sequence:

1. If you're the round leader and have fewer than 5 cards, draw until you have 5. Otherwise, draw 1 card from either deck.

2. Then, beginning with the active player, each player may (if they still have their leader) perform one action:

Increase your Happiness by 1.
Convert 2 atheist families.
Convert 1 family from another player's religion.
Sacrifice your leader to immediately convert up to 5 atheist families.

3. The active player may play any number of action cards. Once they decide to pass, every other player may respond with one card.

4. Resolve cards in the order they were played.

Card types:

Bonus – Helps yourself.
Local Disaster – Targets one religion.
Global Disaster – Affects everyone. Pay extra prayer to protect yourself (avoid) or amplify (double) the disaster.

Cards can affect: Happiness, prayer, families, atheists, force players to discard, recover a sacrificed leader, or create lasting effects (Temples or Amulets)

The cycle can repeat until the active player decides not to play any cards. They then trigger the "convert" phase.

4. Convert Families

Compare each religion's Happiness.

If everyone is equally happy, nothing happens. The unhappiest religion contributes 2 families to the conversion pool.
Middle religions contribute 1 family.
The happiest religion(s) divide the converted families (maximum 3 each).
Any leftovers become atheist families on the Kalua board.

5. Gain Praying Points

Each religion gains:
1 prayer per 5 families (rounded up)
+4 prayer if it is the unhappiest religion; +2 prayer if it is neither the happiest nor the unhappiest

Special Rules
Temple remains in play until destroyed and grants extra PP each turn.
Amulet may be discarded to prevent losing families from a single card.
New Leader replaces a sacrificed or lost leader by promoting one of your families.

Players may purchase additional cards at any time for 5 prayer each.

Winning the Game
At the end of any round, if only one religion still has families, that religion wins. A religion is not eliminated while its leader survives—the leader can continue recruiting followers and potentially rebuild the religion.

If a Global Disaster eliminates every remaining family simultaneously, the religion that had the most families immediately before the disaster wins. If tied, all tied religions share the victory.

Tutorial reversi

2025-08-17T04:05:28Z

Augment reality: animation manager needs to be called at top of .js before being used

If you want to use TypeScript, you can '''check out an updated version''' of the [[BGA Type Safe Template: Reversi|Reversi Tutorial]] which uses the [[BGA Type Safe Template]]. '''Important note: BGA Type Safe Template is a project created by a developer that is not part of the BGA team. This is currently not officially supported by BGA.''' {{Studio_Framework_Navigation}}

== Introduction ==

Using this tutorial, you can build a complete working game on the BGA environment: Reversi.

Before you read this tutorial, you must:
* Read the overall presentations of the BGA Framework ([[Studio|see here]]).
* Know the [http://en.wikipedia.org/wiki/Reversi#Rules rules of Reversi].
* Know the languages used on BGA: PHP, SQL, HTML, CSS, Javascript
* '''Setup your development environment''' [http://en.doc.boardgamearena.com/First_steps_with_BGA_Studio First Steps with BGA Studio]

== Create your first game ==

''Note: you should already have created a project following instructions in [[First_steps_with_BGA_Studio#Create_a_new_game_project|Create a new game project]]. While you will find a '''reversi''' directory in your SFTP folder, do not use it for this tutorial. Instead, use the project you have created as an (empty) starting point.''

With the initial skeleton of code provided in your project, you can already start a game from the BGA Studio:
* Go to your [https://studio.boardgamearena.com/controlpanel studio Control panel], then Manage games and select your initial project. ''Note: there are warnings displayed about a missing BGG_ID and presentation text. You can ignore that for now.''
* Click the Play link next to your project name. This will open the Play page and offer to create a new table for your project. ''Optional: click the Heart icon to add your project to your favorite games list.''
* On the Play page, on the top of the page, make sure that your settings are "Simple game", "Real time" and "Manual".
* Click "Create table" to create a table of your project.
* For now, we are going to work with one player only, so use the (-) button to set the number of players to 1. Most of the time it is simpler to proceed with only one player during the early phase of development of your game, as it's easy and fast to start/stop games. If you choose to start with 2 players, you should see two names on the right: testdude0 and testdude1. To switch between them, press the red arrow button near their names; it will open another tab. This way you don't need to login and logout from multiple accounts.)
* Reminder: Always use the "Express Start" button to start the game.

Thus, you can start a "Reversi" game, and arrive on a void, empty game. Yeah.

End the game by clicking on the game options icon on the top right, and then on "Express Stop".

== Editing the game information (Optional) ==

This step is optional and will fix the warnings on the project page (missing BGG_ID and presentation).

==== Edits to fix Errors ====
* Edit your local copy of the <code>gameinfos.inc.php</code> file:
** Change the <code>bgg_id</code> value from <code>0</code> to <code>2389</code> - that's around line 26.
** Add <code>1,</code> to the players array (so you can start 1-player games while testing) - that's around line 29.
* Upload the <code>gameinfos.inc.php</code> file to the SFTP server (see [[First_steps_with_BGA_Studio#Connect_to_your_SFTP_folder|Connect to your SFTP folder]]).

==== Test your Edits ====
* Go back to your project page, and in the "Game Information" section, click "Reload game informations".
* Finally, refresh the project page in your browser (usually CTRL-F5).

===== Not working? =====
Some changes will require bypassing the cache (adding/changing images). It is often worth doing a hard refresh to make sure the latest version is used.

Sometimes the cache will keep your changes from showing. Since this is a possibility, it will be useful to know how to bypass the cache. To do so you may manually clear cache or use a shortcut to refresh and ignore the cached version of the page. Here's how

====== Windows ======
Chrome, Firefox, or Edge: Press <code>Ctrl+F5</code> or <code>Shift+F5</code> or <code>Ctrl+Shift+R</code>

====== Mac ======
Chrome or Firefox: Press <code>Shift+Command+R</code>

Safari for Mac: Press <code>Command+Option+E</code> to empty the cache, then hold down Shift and click Reload in the toolbar

== Make it look like Reversi ==

Let's start with the board. This will give you a good idea of how things will look and where tokens should go.

Be careful designing the layout of your game: you must always keep in mind that players with a 1024px screen width must be able to play. Usually, it means that the width of the play area can be 750px (in the worst case).

For Reversi, it's useless to have a 750x750px board - much too big, so we chose this one which fit perfectly (536x528):

[[File:Board.jpg]]

Note that we are using a jpg file. Jpg files are lighter than png, so they are faster to load. Later, we are going to use PNGs for tokens because they allow for transparency.

==== Add the board ====
use lowercase file names
* upload <code>board.jpg</code> in your <code>img/</code> directory.
* edit <code>reversi.js</code> to add the <code>div</code> for your board at the beginning of the setup function.

Note: If you are building this game by following the tutorial, you will have a different project name than <code>reversi</code> (i.e. <code>mygame.js</code>). The file names in your project will be different than shown in this tutorial, replacing <code>reversi</code> with your project name. Be sure that any code (other than comments) that references <code>reversi</code> is changed to your actual project name.

<pre>
this.getGameAreaElement().insertAdjacentHTML('beforeend', `
<div id="board">
</div>
`);
</pre>

Note: example above use backticks, aka string template literals. This technique used a lot in code of games as it allows to easily create html with strings substitutions, use quotes, doubel quotes and newlines.
If you don't know what it is check here
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Template_literals

* edit your <code>reversi.css</code> file to transform it into a visible board:

#board {
width: 536px;
height: 528px;
background-image: url('img/board.jpg');
}

'''Important: refresh your page.''' Here's your board:[[File:reversi1.jpg]]

If the board does not appear, refresh the page (always do this when you update the CSS file), and check the image filename. Remember file names are case sensitive!

==== Code the Grid ====
Now, we need to create some invisible HTML elements where squares are. These elements will be used as position references for the white and black tokens.

===== Build the grid of squares =====
The board is 8 squares by 8 squares. This means we need 64 squares. To avoid writing 64 individual <code>div</code> elements on our template, we are going to generate the squares on JS <code>setup</code>.

We'll do this in our Javascript <code>setup</code> method under <code>// TODO: Set up your game interface here, according to "gamedatas"</code>.

<pre>
const board = document.getElementById('board');
const hor_scale = 64.8;
const ver_scale = 64.4;
for (let x=1; x<=8; x++) {
for (let y=1; y<=8; y++) {
const left = Math.round((x - 1) * hor_scale + 10);
const top = Math.round((y - 1) * ver_scale + 7);
// we use afterbegin to make sure squares are placed before discs
board.insertAdjacentHTML(`afterbegin`, `<div id="square_${x}_${y}" class="square" style="left: ${left}px; top: ${top}px;"></div>`);
}
}
</pre>

Note: as you can see, squares in our <code>board.jpg</code> files do not have an exact width/height in pixels, and that's the reason we are using floating point numbers here.

===== Style Those Squares =====
Now, to finish our work and check if everything works fine, we are going to style our square a little bit in our CSS stylesheet:

<pre>
#board {
width: 536px;
height: 528px;
background-image: url('img/board.jpg');
position: relative;
}

.square {
width: 62px;
height: 62px;
position: absolute;
background-color: red;
display: flex;
justify-content: center;
align-items: center;
}
</pre>

Explanations:
* With "<code>position: relative</code>" on board, we ensure square elements are positioned relatively to board.
* <code>background-color: red;</code> is used for testing. This allows us to see the invisible elements. (You could instead do something like <code>outline: 2px solid orange;</code> have fun and be creative)
* The display flex with center will place the disc in the center of the square.

Let's refresh and check our (beautiful) squares:

[[File:reversi2.jpg]]

Now that you know the squares are there, you can remove the test line <code>background-color: red;</code> from your <code>.square</code> class in the CSS stylesheet.

===== Not Working? =====
If the styled squares do not appear, inspect and check your css (Chrome DevTools: Application > Frames > top > Stylesheets > reversi.css).

== The Tokens ==

Now, our board is ready for some tokens!

[Note: Throughout this tutorial, sometimes "tokens" is used, and sometimes "discs" is used. They are often swapped if you're looking at code in the reversi example project.]

=== Build the Token ===
There are quite a few steps before the tokens will appear. You may be used to testing after every change, but that won't work well here. The token will '''not''' show until you have add styles to the css, js template to the tpl, utility method in the js, adjusted the php file, and added the token to the board in the js file.

==== Add Token to img directory ====
Here's a new piece of art with the tokens. We need transparency here so we are using a png file:

[[File:tokens.png]]

Upload this image file <code>tokens.png</code> in your <code>img/</code> directory.

Important Fun Fact: we are using ONE file for both tokens. It is really important to use a minimum number of graphic files for your game. This is called the "CSS sprite" technique, because it makes the game load faster and more reliable. [http://www.w3schools.com/css/css_image_sprites.asp Read more about CSS sprites].

==== Style the Tokens in .css file ====
<pre>
.disc {
position: relative;
width: 54px;
height: 54px;
z-index: 3;
transform-style: preserve-3d;
}
.disc .disc-faces {
transform-style: preserve-3d;
}
.disc[data-color="000000"] .disc-faces {
transform: rotateY(180deg);
}

.disc-face {
position: absolute;
width: 54px;
height: 54px;
background-image: url('img/tokens.png');
background-size: auto 100%;
backface-visibility: hidden;
}
.disc-face[data-side="white"] {
background-position-x: 0%;
transform: rotateY(0deg);
}
.disc-face[data-side="black"] {
background-position-x: 100%;
transform: rotateY(180deg);
}
</pre>

With this CSS code, we can set and change the token color by changing the <code>data-color</code> attribute. Using data instead of a class ensures it can be only one of them (the disc cannot be black and white at the same time).
We will create a disc-faces div in the disc containing 2 disc-face divs, to represent each face of the disc. It will allow us to have a nice flip animation!

==== Add Token Utility Method in .js file ====
Now, let's make the first token appear on our board. Tokens are not visible at the beginning of the game: they appear dynamically during the game. For this reason, we are going to make them appear from our Javascript code, using a template string

Let's create a method in our Javascript code (in the <code>reversi.js</code> file) that will make a token appear on the board, using this template. Add under the section <code>//// Utility methods</code>:

<pre>
addDiscOnBoard: async function( x, y, playerId, animate = true )
{
const color = this.gamedatas.players[ playerId ].color;
const discId = `disc_${x}_${y}`;

document.getElementById(`square_${x}_${y}`).insertAdjacentHTML('beforeend', `
<div class="disc" data-color="${color}" id="${discId}">
<div class="disc-faces">
<div class="disc-face" data-side="white"></div>
<div class="disc-face" data-side="black"></div>
</div>
</div>
`);

if (animate) {
const element = document.getElementById(discId);
await this.animationManager.fadeIn(element, document.getElementById(`overall_player_board_${playerId}`));
}
},
</pre>

For this to work, you will also need to initialize the animation manager. Include the function in your .js file by updating as outlined here: [[BgaAnimations]]. Then add this in the setup function:
<pre>

this.animationManager = new BgaAnimations.Manager({
animationsActive: () => this.bgaAnimationsActive(),
});
</pre>

===== Utility Method Explanation =====
* with <code>element.insertAdjacentHTML</code> method, we create a HTML piece of code and insert it as a new child of the square div element.
* Immediately after, using <code>this.animationManager.fadeIn</code> BGA method, we make the disc slide in (with a fade in animation) from the player panel.

Also note the trailing comma - this is needed because there may be other functions defined after this one, making <code>addDiscOnBoard</code> just one element in an array of functions.

==== Set Token Colors in setupNewGame in modules/php/Game.php file ====
Before we can show a token, we need to set the player colors in the <code>setupNewGame</code> function in <code>modules/php/Game.php</code>:

Replace <code>$default_colors = $gameinfos['player_colors'];</code> with the following line:
<pre>
$default_colors = array( "ffffff", "000000" );
</pre>

Note: A few lines below, you may have to remove the line <code>this->reattributeColorsBasedOnPreferences( $players, $gameinfos['player_colors'] );</code>

=== Test the Token ===
Now, to test if everything works fine

==== <code>addTokenOnBoard()</code> in .js file to Test ====
In <code>reversi.js</code>, in <code>setup: function</code>, under the code we added to generate the squares.
this.addDiscOnBoard(2, 2, this.player_id, false);
Now restart the game.

A token should appear and slide immediately to its position, like this:

[[File:reversi3.jpg]]

== The database ==

We did most of the client-side programming, so let's have a look on the other side now. To design the database model of our game, you will need to access the database. You won't need to do anything in database UI, yet.

=== Accessing the Database ===
To access the database, start a game, then click "Go to game database" link at the bottom of our game, to access the database directly with a PhpMyAdmin instance.

After the first time you've access the database, you could skip opening a game and instead, go to https://studio.boardgamearena.com/db/ . Your PhpMyAdmin username/password is in your welcome email.

'''Note''': do not remove existing tables

=== Create Table in .sql file ===
Now, you are able to create the table(s) you need for your game, and report every SQL command used in your <code>dbmodel.sql</code> file.

The database model of Reversi is short: just one table with the squares of the board.

<pre>
CREATE TABLE IF NOT EXISTS `board` (
`board_x` smallint(5) unsigned NOT NULL,
`board_y` smallint(5) unsigned NOT NULL,
`board_player` int(10) unsigned DEFAULT NULL,
PRIMARY KEY (`board_x`,`board_y`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
</pre>

Add the above SQL to <code>dbmodel.sql</code>. Pay special attention to the backtick <code>`</code> character vs. the single quote <code>'</code> when working with SQL.

=== Test the Table ===
Now, a new database with a <code>board</code> table will be created each time we start a Reversi game. This is why after modifying our <code>dbmodel.sql</code> it's a good time to stop your current game & start a new game.

Start a new game and verify a table is created.

== Setup the initial game position ==

'''Note''': From now on, you must launch the game with '''two players''' to get two <code>player_id</code>s within the database. Otherwise, the game will crash.

The <code>setupNewGame</code> method of our <code>Game.php</code> is called during initial setup. This initializes our data and places the starting tokens on the board. At the beginning of the game, there should be 4 tokens on the board.

=== Initialize the Board in modules/php/Game.php file ===
Under <code>// TODO: setup the initial game situation here</code>, initialize the board<pre>
// Init the board
$sql = "INSERT INTO board (board_x,board_y,board_player) VALUES ";
$sql_values = array();
list( $blackplayer_id, $whiteplayer_id ) = array_keys( $players );
for( $x=1; $x<=8; $x++ )
{
for( $y=1; $y<=8; $y++ )
{
$token_value = "NULL";
if( ($x==4 && $y==4) || ($x==5 && $y==5) ) // Initial positions of white player
$token_value = "'$whiteplayer_id'";
else if( ($x==4 && $y==5) || ($x==5 && $y==4) ) // Initial positions of black player
$token_value = "'$blackplayer_id'";

$sql_values[] = "('$x','$y',$token_value)";
}
}
$sql .= implode( ',', $sql_values );
$this->DbQuery( $sql );
</pre>

==== Board Initialization Explanation ====

* We create one table entry for each square, with a <code>NULL</code> value which means "empty square"
* On 4 of the squares, we place an initial token.

After this, we set <code>activeNextPlayer</code> to make the first player active at the beginning of the game (this line is already present in the default code template).

If you didn't do it earlier, you need to remove the call to <code>this->reattributeColorsBasedOnPreferences()</code> in <code>SetupNewGame()</code>. If you don't, player color preferences will try (and fail) to override the two colors supported here.

=== Show the Initial Token Setup ===
Now, we need to make these tokens appear on the client side. The first step is to return the token positions with our <code>getAllDatas()</code> PHP method. <code>getAllDatas()</code> is called during each page reload.

In the <code>getAllDatas()</code> method, after <code>// TODO: Gather all information about current game situation (visible by player $current_player_id)</code>, add the following lines:

<pre>
// Get reversi board token
$result['board'] = self::getObjectListFromDB( "SELECT board_x x, board_y y, board_player player
FROM board
WHERE board_player IS NOT NULL" );
</pre>

Next, you will modify the query that gets player information to also get the player's colors. Above the lines you just inserted in <code>getAllDatas()</code> notice how we've added <code>player_color color</code> to the sql query in the code below.

<pre>
$result["players"] = $this->getCollectionFromDb(
"SELECT `player_id` `id`, `player_score` `score`, `player_color` `color` FROM `player`"
);
</pre>

We are using the BGA framework's <code>getObjectListFromDB()</code> that formats the result of this SQL query in a PHP array with x, y and player attributes. We add it to the result associative array with the key <code>board</code>.

Last, we process this array client side. Let's place a token on the board for each array item. We'll do this in our Javascript <code>setup</code> method under the code we added to generate the squares.

This will result in a removal or edit of the previously added line <code>this.addDiscOnBoard(2, 2, this.player_id);</code>

<pre>
for( var i in gamedatas.board )
{
var square = gamedatas.board[i];

if( square.player !== null )
{
this.addDiscOnBoard( square.x, square.y, square.player );
}
}
</pre>

The <code>board</code> entry created in <code>getAllDatas()</code> is used here as <code>gamedatas.board</code>

=== Test the Game Start ===
Reload... and here we are:

[[File:reversi5.jpg]]

It starts to feel like Reversi here...

== The game state machine ==

Stop your game, again. You're about to start the core game logic.

You already read [http://www.slideshare.net/boardgamearena/bga-studio-focus-on-bga-game-state-machine Focus on BGA game state machine], so you know that this is the heart of your game logic. For reversi, it's relatively simple. Here's a diagram of our game state machine:

[[File:reversi6.jpg]]

=== Build your States ===
And here's our <code>states.inc.php</code>, according to this diagram:

<pre>
$machinestates = [
ST_BGA_GAME_SETUP => GameStateBuilder::gameSetup(ST_PLAYER_PLAY_DISC)->build(),

ST_PLAYER_PLAY_DISC => GameStateBuilder::create()
->name('playerTurn')
->description(clienttranslate('${actplayer} must play a disc'))
->descriptionmyturn(clienttranslate('${you} must play a disc'))
->type(StateType::ACTIVE_PLAYER)
->args('argPlayerTurn')
->possibleactions([
'actPlayDisc',
])
->transitions([
'playDisc' => ST_NEXT_PLAYER,
])
->build(),

ST_NEXT_PLAYER => GameStateBuilder::create()
->name('nextPlayer')
->type(StateType::GAME)
->action('stNextPlayer')
->updateGameProgression(true)
->transitions([
'nextTurn' => ST_PLAYER_PLAY_DISC,
'cantPlay' => ST_NEXT_PLAYER,
'endGame' => ST_END_GAME,
])
->build(),
];
</pre>

We used constants to give an index to the different states. This is to avoid mistakes when we reuse these indexes on the transitions array.

Let's create a file you'll put in <code>modules/php/constants.inc.php</code> :<pre>
<?php

/*
* State constants
*/
const ST_BGA_GAME_SETUP = 1;

const ST_PLAYER_PLAY_DISC = 10;
const ST_NEXT_PLAYER = 11;

const ST_END_GAME = 99;

?>
</pre>

You will also need to add <code>require_once("modules/php/constants.inc.php");</code> at the beginning of the state.inc.php to load these constants.

=== Test Your States ===
... and start a new Reversi game.

As you can see on the screen capture below, the BGA framework makes the game jump to our first game state <code>playerTurn</code> right after the initial setup. That's why the status bar contains the description of <code>playerTurn</code> state ("XXXX must play a disc"):

[[File:reversi7.jpg]]

== The rules ==

We will use the <code>getPossibleMoves</code> PHP method to:
* Indicate to the current player where she is allowed to play by returning a list of coordinates
* Check if the player has the right to play in the spot they choose

<blockquote>
Example of <code>getPossibleMoves</code> here https://gist.github.com/leocaseiro/a8bc2851bd0caddd06685b5035937d15
</blockquote>

This is pure PHP programming here, and there are no special things from the BGA framework that can be used. This is why we won't go into details here. The overall idea is:
* Create a <code>getTurnedOverDiscs(x,y)</code> method that returns coordinates of discs that would be turned over if a token would be played at <code>x</code>,<code>y</code>.
* Loop through all free squares of the board and call the <code>getTurnedOverDiscs</code> method on each of them. If at least 1 token is turned over, this is a valid move.

IMPORTANT: Making a database query is slow! Please don't load the entire game board with a SQL query multiple times. In our implementation, we load the entire board once at the beginning of <code>getPossibleMoves</code>, and then pass the board as an argument to all methods.

If you want to look into details, please look at the "utility method" sections of <code>Game.php</code>. If building the tutorial yourself, copy the functions under "Utility functions" comment from the Reversi tutorial.

== Display allowed moves ==

Now we want to highlight the squares where the player can place a disc.

To do this, we add a <code>argPlayerTurn</code> method in <code>modules/php/Game.php</code>. This method is called on the server each time we enter into <code>playerTurn</code> game state, and its result is transferred automatically to the client-side:

<pre>
function argPlayerTurn(): array
{
return [
'possibleMoves' => $this->getPossibleMoves( intval($this->getActivePlayerId()) )
];
}
</pre>

<strong>Note:</strong> after this modification you will need to modify the <code>onUpdateActionButtons</code> function in your javascript to remove the references to <code>playableCardsIds</code> in order to launch a game, there will be javascript errors in the console as the code will blow up when it tries to loop over that array.

We use the <code>getPossibleMoves</code> method we just developed.

Each time we enter into a new game state, we use the <code>onEnteringState</code> Javascript method (in the <code>reversi.js</code> file, under "Game & client states"). This lets us use the data returned by the method above on the client side.

<pre>
onEnteringState: function( stateName, args )
{
console.log( 'Entering state: '+stateName );

switch( stateName )
{
case 'playerTurn':
this.updatePossibleMoves( args.args.possibleMoves );
break;
}
},
</pre>

So, when we enter into <code>playerTurn</code> game state, we call our <code>updatePossibleMoves</code> method (under the "Utility methods" section). This method looks like this:

<pre>
updatePossibleMoves: function( possibleMoves )
{
// Remove current possible moves
document.querySelectorAll('.possibleMove').forEach(div => div.classList.remove('possibleMove'));

for( var x in possibleMoves )
{
for( var y in possibleMoves[ x ] )
{
// x,y is a possible move
document.getElementById(`square_${x}_${y}`).classList.add('possibleMove');
}
}

this.addTooltipToClass( 'possibleMove', '', _('Place a disc here') );
},
</pre>
Here's what this does. At first, it removes all <code>possibleMove</code> classes currently applied with the very useful <code>document.querySelectorAll</code> method.

Then it loops through all possible moves our PHP <code>updatePossibleMoves</code> function created for us, and adds the <code>possibleMove</code> class to each corresponding square.

Finally, it uses the BGA framework <code>addTooltipToClass</code> method to associate a tooltip to all those highlighted squares so that players can understand their meaning.

To see the possible moves we need to create a CSS class (<code>possibleMove</code>) that can be applied to a <code>square</code> element to highlight it:
<pre>
.possibleMove {
background-color: white;
opacity: 0.2;
cursor: pointer;
}
</pre>

And here we are:

[[File:reversi8.jpg.jpg]]

== Let's play ==

From now, it's better to restart a game with 2 players, because we are going to implement a complete Reversi turn. The summary of what we are going to do is:
* When we click on a square, check if it is a <code>possibleMove</code> and if so, send the move to the server.
* Server side, check the move is correct, apply Reversi rules and jump to next player.
* Client side, change the token position to reflect the move.

First we associate each click on a square to one of our methods using our Javascript <code>setup</code> method:

<pre>
document.querySelectorAll('.square').forEach(square => square.addEventListener('click', e => this.onPlayDisc(e)));
</pre>

Now, our "onPlayDisc" method is called each time someone clicks on a square.

Here's our "onPlayDisc" method below:

<pre>
onPlayDisc: function( evt )
{
// Stop this event propagation
evt.preventDefault();
evt.stopPropagation();

// Get the cliqued square x and y
// Note: square id format is "square_X_Y"
var coords = evt.currentTarget.id.split('_');
var x = coords[1];
var y = coords[2];

if(!document.getElementById(`square_${x}_${y}`).classList.contains('possibleMove')) {
// This is not a possible move => the click does nothing
return ;
}

this.bgaPerformAction("actPlayDisc", {
x:x,
y:y
});
},
</pre>

What we do here is:
* We stop the propagation of the Javascript <code>onclick</code> event. Otherwise, it can lead to random behavior so it's always a good idea.
* We get the x/y coordinates of the square by using <code>evt.currentTarget.id</code>
* We check that clicked square has the <code>possibleMove</code> class, otherwise we know for sure that we can't play there.
* Finally, we make a call to the server using BGA <code>bgaPerformAction</code> method with argument x and y. This call will check that <code>actPlayDisc</code> action is possible, according to current game state (see <code>possibleactions</code> entry in our <code>playerTurn</code> game state defined above). This check is important to avoid issues if a player double clicks on a square.

Now, we have to manage this <code>actPlayDisc</code> action on the server side. Add a corresponding <code>actPlayDisc</code> method in our game logic (<code>Game.php</code>):

<pre>
function actPlayDisc( int $x, int $y )
{
</pre>
(The function will be called when the front-side action is triggered using the Autowire mechanism, if you want to see how it works in details check [[Main game logic: Game.php|https://en.doc.boardgamearena.com/Main_game_logic:_Game.php#Actions_%28autowired%29]] )
<pre>
$player_id = intval($this->getActivePlayerId());

// Now, check if this is a possible move
$board = $this->getBoard();
$turnedOverDiscs = $this->getTurnedOverDiscs( $x, $y, $player_id, $board );

if( count( $turnedOverDiscs ) > 0 )
{
// This move is possible!
</pre>

...now, we are using the <code>getTurnedOverDiscs</code> method again to check that this move is possible.

<pre>
// Let's place a disc at x,y and return all "$returned" discs to the active player

$sql = "UPDATE board SET board_player='$player_id'
WHERE ( board_x, board_y) IN ( ";

foreach( $turnedOverDiscs as $turnedOver )
{
$sql .= "('".$turnedOver['x']."','".$turnedOver['y']."'),";
}
$sql .= "('$x','$y') ) ";

$this->DbQuery( $sql );
</pre>

... we update the database to change the color of all turned over disc + the disc we just placed.

<pre>
// Update scores according to the number of disc on board
$sql = "UPDATE player
SET player_score = (
SELECT COUNT( board_x ) FROM board WHERE board_player=player_id
)";
$this->DbQuery( $sql );

// Statistics
$this->incStat( count( $turnedOverDiscs ), "turnedOver", $player_id );
if( ($x==1 && $y==1) || ($x==8 && $y==1) || ($x==1 && $y==8) || ($x==8 && $y==8) )
$this->incStat( 1, 'discPlayedOnCorner', $player_id );
else if( $x==1 || $x==8 || $y==1 || $y==8 )
$this->incStat( 1, 'discPlayedOnBorder', $player_id );
else if( $x>=3 && $x<=6 && $y>=3 && $y<=6 )
$this->incStat( 1, 'discPlayedOnCenter', $player_id );
</pre>

... now, we update both player score by counting all disc, and we manage game statistics.

<pre>
// Notify
$this->notify->all( "playDisc", clienttranslate( '${player_name} plays a disc and turns over ${returned_nbr} disc(s)' ), array(
'player_id' => $player_id,
'player_name' => $this->getActivePlayerName(),
'returned_nbr' => count( $turnedOverDiscs ),
'x' => $x,
'y' => $y
) );

$this->notify->all( "turnOverDiscs", '', array(
'player_id' => $player_id,
'turnedOver' => $turnedOverDiscs
) );

$newScores = $this->getCollectionFromDb( "SELECT player_id, player_score FROM player", true );
$this->notify->all( "newScores", "", array(
"scores" => $newScores
) );
</pre>

... then we notify about all these changes. We are using for that 3 notifications (<code>playDisc</code>, <code>turnOverDiscs</code> and <code>newScores</code> that we are going to implement on client side later). Note that the description of the <code>playDisc</code> notification will be logged in the game log.

<pre>
// Then, go to the next state
$this->gamestate->nextState( 'playDisc' );
}
else
throw new \BgaSystemException( "Impossible move" );
}
</pre>

... finally, we jump to the next game state if everything goes fine (<code>playDisc</code> is the name of a transition in the <code>playerTurn</code> game state description above which leads to state 11 which is <code>nextPlayer</code>).

To make the statistics work, we have to initialize them in <code>stats.json</code>:

<pre>
{
"player": {
"discPlayedOnCorner": {
"id": 10,
"name": "Discs played on a corner",
"type": "int"
},
"discPlayedOnBorder": {
"id": 11,
"name": "Discs played on a border",
"type": "int"
},
"discPlayedOnCenter": {
"id": 12,
"name": "Discs played on board center part",
"type": "int"
},
"turnedOver": {
"id": 13,
"name": "Number of discs turned over",
"type": "int"
}
}
}
</pre>

A last thing to do on the server side is to activate the next player when we enter the <code>nextPlayer</code> game state (in the <code>modules/php/Game.php</code> file, under "Game state reactions"):

<pre>
function stNextPlayer(): void
{
// Active next player
$player_id = intval($this->activeNextPlayer());

// Check if both player has at least 1 discs, and if there are free squares to play
$player_to_discs = $this->getCollectionFromDb( "SELECT board_player, COUNT( board_x )
FROM board
GROUP BY board_player", true );

if( ! isset( $player_to_discs[ null ] ) )
{
// Index 0 has not been set => there's no more free place on the board !
// => end of the game
$this->gamestate->nextState( 'endGame' );
return ;
}
else if( ! isset( $player_to_discs[ $player_id ] ) )
{
// Active player has no more disc on the board => he looses immediately
$this->gamestate->nextState( 'endGame' );
return ;
}

// Can this player play?

$possibleMoves = $this->getPossibleMoves( $player_id );
if( count( $possibleMoves ) == 0 )
{

// This player can't play
// Can his opponent play ?
$opponent_id = (int)$this->getUniqueValueFromDb( "SELECT player_id FROM player WHERE player_id!='$player_id' " );
if( count( $this->getPossibleMoves( $opponent_id ) ) == 0 )
{
// Nobody can move => end of the game
$this->gamestate->nextState( 'endGame' );
}
else
{
// => pass his turn
$this->gamestate->nextState( 'cantPlay' );
}
}
else
{
// This player can play. Give him some extra time
$this->giveExtraTime( $player_id );
$this->gamestate->nextState( 'nextTurn' );
}
}
</pre>

Now, when we play a token, the rules are checked and the token appears in the database.

[[File:reversi9.jpg]]

Of course, as we don't manage notifications on client side, we need to press F5 after each move to see the changes on the board.

== Make the move appear automatically ==

Now, what we have to do is process the notifications sent by the server and make the move appear on the interface.

In our <code>setupNotifications</code> method in <code>reversi.js</code>, we tell BGA to listen to notifications we will add later (<code>playDisc</code> and <code>turnOverDiscs</code>) using promise-based notifications:

<pre>
setupNotifications: function()
{
console.log( 'notifications subscriptions setup' );

// automatically listen to the notifications, based on the `notif_xxx` function on this class.
this.bgaSetupPromiseNotifications();
}
</pre>

We will associate each of our 3 notifications with a method prefixed with <code>notif_</code>.

Let's have a look now on the <code>playDisc</code> notification handler method:<pre>
notif_playDisc: async function( args )
{
// Remove current possible moves (makes the board more clear)
document.querySelectorAll('.possibleMove').forEach(div => div.classList.remove('possibleMove'));

await this.addDiscOnBoard( args.x, args.y, args.player_id );
},
</pre>

No surprise here, we re-used some existing stuff to:
* Remove the highlighted squares.
* Add a new disc on board, coming from player panel. That's where the async await part of <code>addDiscOnBoard</code> becomes useful.

Now, here's the method that handles the <code>turnOverDiscs</code> notification:

<pre>
animateTurnOverDisc: async function(disc, targetColor) {
const squareDiv = document.getElementById(`square_${disc.x}_${disc.y}`);
const discDiv = document.getElementById(`disc_${disc.x}_${disc.y}`);

squareDiv.classList.add('flip-animation');
await this.wait(500); // for the flip animation to finish

discDiv.dataset.color = targetColor;

const parallelAnimations = [{
keyframes: [ // flip the disc
{ transform: `rotateY(180deg)` },
{ transform: `rotateY(0deg)` },
]
}, {
keyframes: [ // lift the disc
{ transform: `translate(0, -12px) scale(1.2)`, offset: 0.5 },
]
}];

await this.animationManager.slideAndAttach(discDiv, squareDiv, { duration: 1000, parallelAnimations });

squareDiv.classList.remove('flip-animation');
await this.wait(500); // for the flip animation removal to finish
},

notif_turnOverDiscs: async function( args )
{
// Custom sound effect
if (this.getGameUserPreference(this.preference_sound) == 1 && !g_archive_mode) {
this.sounds.play('play');
this.disableNextMoveSound();
}

// Update score
Object.entries(args.scores).forEach(([playerId, newScore]) => {
this.scoreCtrl[playerId].toValue( newScore );
});

// Get the color of the player who is returning the discs
const targetColor = this.gamedatas.players[ args.player_id ].color;

// wait for the animations of all turned discs to be over before considering the notif done
await Promise.all(
args.turnedOver.map(disc =>
this.animateTurnOverDisc(disc, targetColor)
)
);

}
</pre>

The list of the discs to be turned over has been made available by our server side code in <code>args.turnedOver</code> (see previous paragraph). We loop through all these discs, and trigger a single disc animation using <code>animateTurnOverDisc</code>. This function creates a complex animation using [[BgaAnimations]] for the disc in parameter.

We create a chain of 3 animations using await to make the square highlight, then flip the token, then remove the square highlight.

And Also the notification to update the scores:

<pre>
notif_newScores: async function( args )
{
for( var player_id in args.scores )
{
var newScore = args.scores[ player_id ];
this.scoreCtrl[ player_id ].toValue( newScore );
}
}
</pre>

== Add a debug function to help up test the code ==
Add this at the end of your Game.php file :
<pre>
function debug_playToEndGame() {
while (intval($this->gamestate->state_id()) < ST_END_GAME) {
$state = intval($this->gamestate->state_id());
switch ($state) {
case ST_PLAYER_PLAY_DISC:
$args = $this->argPlayerTurn();
$possibleMoves = $args['possibleMoves'];
$possibleXs = array_keys($possibleMoves);
$x = $possibleXs[bga_rand(0, count($possibleXs) - 1)];
$possibleYs = array_keys($possibleMoves[$x]);
$y = $possibleYs[bga_rand(0, count($possibleYs) - 1)];

$this->actPlayDisc($x, $y);
break;
}
}
}
</pre>
This function plays automatically until we reach the end of the game. The functions starting with "debug_" can be triggered in the Studio with a special menu.
Start a new game, click on the Bug icon on the top left then "playToEndGame". You should see the game randomly playing until it reaches the end game, so it helps you check the animations, and you can see if the final scoring is also working as expected.
You can create as many debug function as you like!

== After the tutorial ==
You might want to check another tutorial, or start working on your first real project !

[[Create a game in BGA Studio: Complete Walkthrough]]
[[Category:Studio]]