Board Game Arena - User contributions [en]

File:Bga button play online.png

2025-09-17T08:51:17Z

Lymon Flowers: Lymon Flowers uploaded a new version of File:Bga button play online.png

Production issues reporting

2025-05-26T16:22:55Z

Lymon Flowers: Add redirect

#REDIRECT [[Studio logs]]BGA implemented several production issues reporting tools:

* Syntax errors reporting
* Unexpected errors reporting
* Backend & frontend issues reporting

All of these are available at the bottom of your game studio page. Access your game studio page (for instance: [https://studio.boardgamearena.com/studiogame?game=medina https://studio.boardgamearena.com/studiogame?game=xxx]) and scroll to the "'''Errors in production'''" block:

[[File:Error_reporting.png|frameless|600x600px]]

== Syntax errors reporting ==
This is the simplest reporting tool. It only reports PHP syntax errors. When clicking on the button, you will be redirected to a page that lists all game servers and will display any syntax error. Any of these is a fatal error and should be addressed with a new release.

== Unexpected errors reporting ==
Same as the previous tool. It redirects to another report page that shows recent PHP (backend) errors. Only an error message with a PHP stack trace is shown for each message. For instance:
18/05 20:07:17 [error] [TXXX] [A.B.C.D] [XXX/YYY] Error (1213) while processing SQL request: Deadlock found when trying to get lock; try restarting transaction - Request: SELECT global_id, global_value FROM global WHERE 1
18/05 20:07:17 [error] [TXXXX] [A.B.C.D] [XXX/YYY] Unexpected exception: mysql_deadlock_restart_transaction (BGA service error 1747591637)
#0 /var/tournoi/release/tournoi-250505-1448-gs/www/Bga/GameFramework/Old/APP_DbObject.php(34): Bga\Services\Db->query('...')
#1 /var/tournoi/release/tournoi-250505-1448-gs/www/Bga/GameFramework/TableInfos.php(125): Bga\GameFramework\Old\APP_DbObject::DbQuery('...')
#2 /var/tournoi/release/tournoi-250505-1448-gs/www/Bga/GameFramework/TableInfos.php(91): Bga\GameFramework\TableInfos->getGlobalsFromDB(false)
#3 /var/tournoi/release/tournoi-250505-1448-gs/www/Bga/GameFramework/TableInfos.php(69): Bga\GameFramework\TableInfos->db_load(false)
#4 /var/tournoi/release/tournoi-250505-1448-gs/www/Bga/GameFramework/GameAction.php(80): Bga\GameFramework\TableInfos->get(false)
#5 /var/tournoi/release/tournoi-250505-1448-gs/www/Bga/GameFramework/GameAction.php(31): Bga\GameFramework\GameAction->initGameTableObjects()
#6 /var/tournoi/release/tournoi-250505-1448-gs/vendor/php-di/php-di/src/Definition/Resolver/ObjectCreator.php(129): Bga\GameFramework\GameAction->__construct()
#7 /var/tournoi/release/tournoi-250505-1448-gs/vendor/php-di/php-di/src/Definition/Resolver/ObjectCreator.php(56): DI\Definition\Resolver\ObjectCreator->createInstance(Object(DI\Definition\ObjectDefinition), Array)
#8 /var/tournoi/release/tournoi-250505-1448-gs/vendor/php-di/php-di/src/Definition/Resolver/ResolverDispatcher.php(62): DI\Definition\Resolver\ObjectCreator->resolve(Object(DI\Definition\ObjectDefinition), Array)
#9 /var/tournoi/release/tournoi-250505-1448-gs/vendor/php-di/php-di/src/Container.php(354): DI\Definition\Resolver\ResolverDispatcher->resolve(Object(DI\Definition\ObjectDefinition), Array)
#10 /var/tournoi/release/tournoi-250505-1448-gs/vendor/php-di/php-di/src/Container.php(184): DI\Container->resolveDefinition(Object(DI\Definition\ObjectDefinition), Array)
#11 /var/tournoi/release/tournoi-250505-1448-gs/www/include/webActionCore.inc.php(201): DI\Container->make('...')
#12 /var/tournoi/release/tournoi-250505-1448-gs/www/index.php(262): launchWebAction('...', '...', '...', false, false, NULL, true, false)
#13 {main}
Errors are unformatted and no statistics whatsoever are made. This tools is pretty raw but very low level without any filtering.

== Backend & frontend issues reporting ==
This is the next generation reporting tool. It is based on Sentry, a tool that aggregates any frontend and backend errors encountered by users. It allows modern statistics and gives more context.

When clicking on this button, you will be redirect to another interface that allows basic Sentry querying.

=== Sentry concepts ===
When an error or a warning is caught, information is sent to Sentry in the form of an event, which is processed. Sentry then as the following concepts:

* '''Event''': an error or warning that triggered either in the user browser or in one of BGA servers
* '''Issue:''' all events are attached to an issue. Sentry figures out how to merge then depending on the place the event has taken place in the code. Hence, false positive could happen
* '''Issue ID''': a unique value assigned to an issue.
* '''Project:''' a software module. We currently have two projects that are exposed to the studio developers: ''gameserver-js'' (frontend) and gameserver (''backend'')
* '''Tags:''' metadata associated to an event, like browser version, user ID, etc. They are used to provide statistics in the issues page.
* '''Release:''' a release is a package name and a version name. It helps knowing when an issue appears, then narrowing down its cause. There are two releases set on BGA: mainsite release (our code) and game release (your code)

==== Views ====
The sentry viewer offer several views.

===== Issues list view =====
This is the landing view, it shows an issue list after a brief query on the Sentry server.

It is possible to filter out the project, depending on when you want to obtain frontend, backend or both errors (left red rectangle on the screenshot).

In the event of more than 25 issues, it is possible to paginate over them (right red rectangle). Ordering can also be changed, it can be:

* '''number of events:''' the more, the more impactful this issue is.
* '''last seen:''' last time an event has been added to this issue. The more ancient, the more likely it is fixed.
* '''first seen:''' first time an event has been recorded into this issue. This is valuable to understand when a bug was introduced (for instance, if that matches a release date)
* '''trend:''' Sentry "magic" ordering to determine which issues are currently gaining momentum.

[[File:Issues list.png|frameless|600x600px]]

Issues contain the following fields:

* '''ID:''' Sentry internal ID regarding this event. It is unique and starts with the project name. Hence, "<code>GAMESERVER-JS-XXX</code>" is an error related to frontend (javascript)
* '''Type:''' error, warning or sometimes, it contains the name of the exceptions raised
* '''Description:''' short description, normally the same error as the user experienced if that was not a silent error
* '''Seen:''' first and last times this issue has been encountered
* '''Status:''' number of events (🏴) and users (👤) affected by this.

Please note that we tried hard to limit false positives into this list, but, mainly for frontend errors, some errors can be "ours" and not your code. This can be guessed in the next screen if the stack is empty.

===== Issue detail view =====
This view shows the details of an issue. As every "specific" data is attached to an event and not an issue, this view chooses by default an event (latest one) and uses its data to fill in some fields (for instance, tags). If you navigate between events (see next view), this data is subjected to change.

[[File:Issue details.png|frameless|785x785px]]

This page is separated into several blocks.

====== Main information ======
[[File:Issue main informations.png|frameless]]

This contains the main information of the issue, as seen in issues list:

* '''Type of error''' (warning, error, exception name, etc.)
* '''Description of error'''
* '''Error ID'''
* More detailed information and counters:
** '''Priority:''' Sentry estimate of the criticality of this issue
** '''Count:''' number of events
** '''User count:''' approximate number of users impacted by this issue
** '''First seen'''
** '''Last seen'''

====== Culprit ======
[[File:Issue culprit.png|frameless]]
This summarizes where and the issue happens, with a source file position and a release.

====== Stack trace ======
[[File:Issue stack trace.png|frameless]]

This block contains information particularly useful to debug an issue. By default, only stack trace elements pertaining to the game code are shown. It is possible for frontend errors to toggle this behavior and show BGA frontend stack trace elements.

Every element of the stack trace is clickable to see a hint on exactly when the execution was. Please note that some of this code is minified and hence is not very readable. However, it can still provide useful information. We plan to perhaps unminify this code later.

====== Request ======
[[File:Issue request details.png|frameless]]
This block contains details on the request, namely:

* '''URL:''' complete URL of the request, but without the query string
* '''Method:''' could be <code>GET</code> or <code>POST</code>
* '''Query:''' all query parameters if any

====== Tags ======
[[File:Issue tags.png|frameless]]

List any relevant tags regarding this event.

====== Statistics ======
[[File:Issue statistics - histogram.png|frameless]]

This block contains an histogram of the issue events depending, either during last day or last month. Every bar is clickable.

[[File:Issue statistics.png|frameless]]

Then, we have donuts-like statistics with a breakdown of the first 10 occurrences for:

* browsers
* device family
* OSes
* users
* tables

The more a stats impacts a browser, user or device brand, the more it is suspect that the issue is specific to them.

===== Events list view =====
[[File:Issue events list.png|frameless]]

When clicking on the "Other events" tab, you will see the following view, which allows you to inspect a specific event. Usually, it is not needed since default event provides enough context, but it can still be used to compare several events.

Studio logs

2025-05-26T16:22:18Z

Lymon Flowers: Merge with Production issues reporting

{{Studio_Framework_Navigation}}

BGA implemented several production issues reporting tools:
* Syntax errors reporting
* Unexpected errors reporting
*Backend & frontend issues reporting
All of these are available at the bottom of your game studio page. Access your game studio page (for instance: [https://studio.boardgamearena.com/studiogame?game=medina https://studio.boardgamearena.com/studiogame?game=xxx]) and scroll to the "'''Errors in production'''" block:
== BGA request&SQL logs ==

This log is useful:
* When you want to check what SQL requests has been built during a request.
* When you want to debug your PHP code using "self::trace"
* When you want to know why a request takes too much time.

On this log, you can see:

=== Your requests ===

Example:

20/06 21:50:56 [info] [T403] [4/mytest0] /cinco/cinco/exchange4Cards.html?id=4&lock=97d1c7a1-903a-4d1f-8206-de39ce8204fc&table=403&testuser=4&dojo.preventCache=1371757856044

Note that the best way to check your Ajax request is to read the [[http://en.doc.boardgamearena.com/Tools_and_tips_of_BGA_Studio#Input.2FOutput_debugging_section Input/Output section]].

=== Request responses ===

Example:

20/06 21:50:56 [notice] [T403] [4/mytest0] OK-0 169 d141 c8 e0 I9 A158 V0 T0 /cinco/cinco/exchange4Cards.html?id=4&lock=97d1c7a1-903a-4d1f-8206-de39ce8204fc&table=403&testuser=4&dojo.preventCache=1371757856044

You can recognize a response because it contains [notice]. Usually, there is one response for each request.

Let's details the beginning of the log:
* 20/06 21:50:56: the date
* [notice]
* [T403]: this is a log from table 403
* [4/mytest0]: this is use "mytest0", with id 4
* OK-0: it means that the request ended up successfully, with no exception (expected or unexpected).
* 169: this is the time taken to process the request (169ms).
* d141: this is the total Database time used to process the request (141ms).

=== SQL requests ===

Example:
20/06 21:50:56 [info] [T403] [4/mytest0] 0.26 SELECT player_tokenColor FROM player WHERE player_id ='4'

All requests to Database are traced in this log. You can see here the time take by the request (0,26ms).

=== Custom trace ===

You can use special PHP methods in your PHP code to left some trace in this log:
* $this->trace( "your message here" ); // Display "your message here" in the log
* $this->dump( "My variable", $variable_to_dump ); // Display the content of $variable_to_dump in the log

== BGA unexpected exceptions logs ==

In this log you can check the last Unexpected exceptions from your game.

Exceptions management on PHP side [[http://en.doc.boardgamearena.com/Main_game_logic:_yourgamename.game.php#Managing_errors_and_exceptions is described here]].

The log displayed the complete stacktrace of the exception, so you can debug it.

The SQL log is very verbose and sometimes it too hard to extract your tracing from it, in this case you can use error log for tracing temporarily.
You can add debug statement using self::warn() which will appear in that the log. Do not leave these tracing method calls after you done debugging unless they
are real warnings or errors (only the error log level will appear in production).

== BGA Production Logs ==

=== How to access production server exception logs ===

# Navigate to your game page on the Studio website
## e.g. <nowiki>https://studio.boardgamearena.com/studiogame?game=YOURGAMEID</nowiki>
# Scroll to the bottom of the page
# Click the `Display recent errors from production` button
## [[File:How-to-access-bga-production-server-logs.png|500px]]
==Backend & frontend issues reporting==
This is the next generation reporting tool. It is based on Sentry, a tool that aggregates any frontend and backend errors encountered by users. It allows modern statistics and gives more context.

When clicking on this button, you will be redirect to another interface that allows basic Sentry querying.
===Sentry concepts===
When an error or a warning is caught, information is sent to Sentry in the form of an event, which is processed. Sentry then as the following concepts:
*'''Event''': an error or warning that triggered either in the user browser or in one of BGA servers
*'''Issue:''' all events are attached to an issue. Sentry figures out how to merge then depending on the place the event has taken place in the code. Hence, false positive could happen
*'''Issue ID''': a unique value assigned to an issue.
*'''Project:''' a software module. We currently have two projects that are exposed to the studio developers: ''gameserver-js'' (frontend) and gameserver (''backend'')
*'''Tags:''' metadata associated to an event, like browser version, user ID, etc. They are used to provide statistics in the issues page.
*'''Release:''' a release is a package name and a version name. It helps knowing when an issue appears, then narrowing down its cause. There are two releases set on BGA: mainsite release (our code) and game release (your code)
====Views====
The sentry viewer offer several views.
=====Issues list view=====
This is the landing view, it shows an issue list after a brief query on the Sentry server.

It is possible to filter out the project, depending on when you want to obtain frontend, backend or both errors (left red rectangle on the screenshot).

In the event of more than 25 issues, it is possible to paginate over them (right red rectangle). Ordering can also be changed, it can be:
*'''number of events:''' the more, the more impactful this issue is.
*'''last seen:''' last time an event has been added to this issue. The more ancient, the more likely it is fixed.
*'''first seen:''' first time an event has been recorded into this issue. This is valuable to understand when a bug was introduced (for instance, if that matches a release date)
*'''trend:''' Sentry "magic" ordering to determine which issues are currently gaining momentum.
[[File:Issues list.png|frameless|600x600px]]

Issues contain the following fields:
*'''ID:''' Sentry internal ID regarding this event. It is unique and starts with the project name. Hence, "<code>GAMESERVER-JS-XXX</code>" is an error related to frontend (javascript)
*'''Type:''' error, warning or sometimes, it contains the name of the exceptions raised
*'''Description:''' short description, normally the same error as the user experienced if that was not a silent error
*'''Seen:''' first and last times this issue has been encountered
*'''Status:''' number of events (🏴) and users (👤) affected by this.
Please note that we tried hard to limit false positives into this list, but, mainly for frontend errors, some errors can be "ours" and not your code. This can be guessed in the next screen if the stack is empty.
=====Issue detail view=====
This view shows the details of an issue. As every "specific" data is attached to an event and not an issue, this view chooses by default an event (latest one) and uses its data to fill in some fields (for instance, tags). If you navigate between events (see next view), this data is subjected to change.

[[File:Issue details.png|frameless|785x785px]]

This page is separated into several blocks.
======Main information======
[[File:Issue main informations.png|frameless]]

This contains the main information of the issue, as seen in issues list:
*'''Type of error''' (warning, error, exception name, etc.)
*'''Description of error'''
*'''Error ID'''
*More detailed information and counters:
**'''Priority:''' Sentry estimate of the criticality of this issue
**'''Count:''' number of events
**'''User count:''' approximate number of users impacted by this issue
**'''First seen'''
**'''Last seen'''
======Culprit======
[[File:Issue culprit.png|frameless]] This summarizes where and the issue happens, with a source file position and a release.
======Stack trace======
[[File:Issue stack trace.png|frameless]]

This block contains information particularly useful to debug an issue. By default, only stack trace elements pertaining to the game code are shown. It is possible for frontend errors to toggle this behavior and show BGA frontend stack trace elements.

Every element of the stack trace is clickable to see a hint on exactly when the execution was. Please note that some of this code is minified and hence is not very readable. However, it can still provide useful information. We plan to perhaps unminify this code later.
======Request======
[[File:Issue request details.png|frameless]] This block contains details on the request, namely:
*'''URL:''' complete URL of the request, but without the query string
*'''Method:''' could be <code>GET</code> or <code>POST</code>
*'''Query:''' all query parameters if any
======Tags======
[[File:Issue tags.png|frameless]]

List any relevant tags regarding this event.
======Statistics======
[[File:Issue statistics - histogram.png|frameless]]

This block contains an histogram of the issue events depending, either during last day or last month. Every bar is clickable.

[[File:Issue statistics.png|frameless]]

Then, we have donuts-like statistics with a breakdown of the first 10 occurrences for:
*browsers
*device family
*OSes
*users
*tables
The more a stats impacts a browser, user or device brand, the more it is suspect that the issue is specific to them.
=====Events list view=====
[[File:Issue events list.png|frameless]]

When clicking on the "Other events" tab, you will see the following view, which allows you to inspect a specific event. Usually, it is not needed since default event provides enough context, but it can still be used to compare several events.
[[Category:Studio]]

Production issues reporting

2025-05-21T15:57:43Z

Lymon Flowers: /* Events list view */ Add event list page

BGA implemented several production issues reporting tools:

* Syntax errors reporting
* Unexpected errors reporting
* Backend & frontend issues reporting

All of these are available at the bottom of your game studio page. Access your game studio page (for instance: [https://studio.boardgamearena.com/studiogame?game=medina https://studio.boardgamearena.com/studiogame?game=xxx]) and scroll to the "'''Errors in production'''" block:

[[File:Error_reporting.png|frameless|600x600px]]

== Syntax errors reporting ==
This is the simplest reporting tool. It only reports PHP syntax errors. When clicking on the button, you will be redirected to a page that lists all game servers and will display any syntax error. Any of these is a fatal error and should be addressed with a new release.

== Unexpected errors reporting ==
Same as the previous tool. It redirects to another report page that shows recent PHP (backend) errors. Only an error message with a PHP stack trace is shown for each message. For instance:
18/05 20:07:17 [error] [TXXX] [A.B.C.D] [XXX/YYY] Error (1213) while processing SQL request: Deadlock found when trying to get lock; try restarting transaction - Request: SELECT global_id, global_value FROM global WHERE 1
18/05 20:07:17 [error] [TXXXX] [A.B.C.D] [XXX/YYY] Unexpected exception: mysql_deadlock_restart_transaction (BGA service error 1747591637)
#0 /var/tournoi/release/tournoi-250505-1448-gs/www/Bga/GameFramework/Old/APP_DbObject.php(34): Bga\Services\Db->query('...')
#1 /var/tournoi/release/tournoi-250505-1448-gs/www/Bga/GameFramework/TableInfos.php(125): Bga\GameFramework\Old\APP_DbObject::DbQuery('...')
#2 /var/tournoi/release/tournoi-250505-1448-gs/www/Bga/GameFramework/TableInfos.php(91): Bga\GameFramework\TableInfos->getGlobalsFromDB(false)
#3 /var/tournoi/release/tournoi-250505-1448-gs/www/Bga/GameFramework/TableInfos.php(69): Bga\GameFramework\TableInfos->db_load(false)
#4 /var/tournoi/release/tournoi-250505-1448-gs/www/Bga/GameFramework/GameAction.php(80): Bga\GameFramework\TableInfos->get(false)
#5 /var/tournoi/release/tournoi-250505-1448-gs/www/Bga/GameFramework/GameAction.php(31): Bga\GameFramework\GameAction->initGameTableObjects()
#6 /var/tournoi/release/tournoi-250505-1448-gs/vendor/php-di/php-di/src/Definition/Resolver/ObjectCreator.php(129): Bga\GameFramework\GameAction->__construct()
#7 /var/tournoi/release/tournoi-250505-1448-gs/vendor/php-di/php-di/src/Definition/Resolver/ObjectCreator.php(56): DI\Definition\Resolver\ObjectCreator->createInstance(Object(DI\Definition\ObjectDefinition), Array)
#8 /var/tournoi/release/tournoi-250505-1448-gs/vendor/php-di/php-di/src/Definition/Resolver/ResolverDispatcher.php(62): DI\Definition\Resolver\ObjectCreator->resolve(Object(DI\Definition\ObjectDefinition), Array)
#9 /var/tournoi/release/tournoi-250505-1448-gs/vendor/php-di/php-di/src/Container.php(354): DI\Definition\Resolver\ResolverDispatcher->resolve(Object(DI\Definition\ObjectDefinition), Array)
#10 /var/tournoi/release/tournoi-250505-1448-gs/vendor/php-di/php-di/src/Container.php(184): DI\Container->resolveDefinition(Object(DI\Definition\ObjectDefinition), Array)
#11 /var/tournoi/release/tournoi-250505-1448-gs/www/include/webActionCore.inc.php(201): DI\Container->make('...')
#12 /var/tournoi/release/tournoi-250505-1448-gs/www/index.php(262): launchWebAction('...', '...', '...', false, false, NULL, true, false)
#13 {main}
Errors are unformatted and no statistics whatsoever are made. This tools is pretty raw but very low level without any filtering.

== Backend & frontend issues reporting ==
This is the next generation reporting tool. It is based on Sentry, a tool that aggregates any frontend and backend errors encountered by users. It allows modern statistics and gives more context.

When clicking on this button, you will be redirect to another interface that allows basic Sentry querying.

=== Sentry concepts ===
When an error or a warning is caught, information is sent to Sentry in the form of an event, which is processed. Sentry then as the following concepts:

* '''Event''': an error or warning that triggered either in the user browser or in one of BGA servers
* '''Issue:''' all events are attached to an issue. Sentry figures out how to merge then depending on the place the event has taken place in the code. Hence, false positive could happen
* '''Issue ID''': a unique value assigned to an issue.
* '''Project:''' a software module. We currently have two projects that are exposed to the studio developers: ''gameserver-js'' (frontend) and gameserver (''backend'')
* '''Tags:''' metadata associated to an event, like browser version, user ID, etc. They are used to provide statistics in the issues page.
* '''Release:''' a release is a package name and a version name. It helps knowing when an issue appears, then narrowing down its cause. There are two releases set on BGA: mainsite release (our code) and game release (your code)

==== Views ====
The sentry viewer offer several views.

===== Issues list view =====
This is the landing view, it shows an issue list after a brief query on the Sentry server.

It is possible to filter out the project, depending on when you want to obtain frontend, backend or both errors (left red rectangle on the screenshot).

In the event of more than 25 issues, it is possible to paginate over them (right red rectangle). Ordering can also be changed, it can be:

* '''number of events:''' the more, the more impactful this issue is.
* '''last seen:''' last time an event has been added to this issue. The more ancient, the more likely it is fixed.
* '''first seen:''' first time an event has been recorded into this issue. This is valuable to understand when a bug was introduced (for instance, if that matches a release date)
* '''trend:''' Sentry "magic" ordering to determine which issues are currently gaining momentum.

[[File:Issues list.png|frameless|600x600px]]

Issues contain the following fields:

* '''ID:''' Sentry internal ID regarding this event. It is unique and starts with the project name. Hence, "<code>GAMESERVER-JS-XXX</code>" is an error related to frontend (javascript)
* '''Type:''' error, warning or sometimes, it contains the name of the exceptions raised
* '''Description:''' short description, normally the same error as the user experienced if that was not a silent error
* '''Seen:''' first and last times this issue has been encountered
* '''Status:''' number of events (🏴) and users (👤) affected by this.

Please note that we tried hard to limit false positives into this list, but, mainly for frontend errors, some errors can be "ours" and not your code. This can be guessed in the next screen if the stack is empty.

===== Issue detail view =====
This view shows the details of an issue. As every "specific" data is attached to an event and not an issue, this view chooses by default an event (latest one) and uses its data to fill in some fields (for instance, tags). If you navigate between events (see next view), this data is subjected to change.

[[File:Issue details.png|frameless|785x785px]]

This page is separated into several blocks.

====== Main information ======
[[File:Issue main informations.png|frameless]]

This contains the main information of the issue, as seen in issues list:

* '''Type of error''' (warning, error, exception name, etc.)
* '''Description of error'''
* '''Error ID'''
* More detailed information and counters:
** '''Priority:''' Sentry estimate of the criticality of this issue
** '''Count:''' number of events
** '''User count:''' approximate number of users impacted by this issue
** '''First seen'''
** '''Last seen'''

====== Culprit ======
[[File:Issue culprit.png|frameless]]
This summarizes where and the issue happens, with a source file position and a release.

====== Stack trace ======
[[File:Issue stack trace.png|frameless]]

This block contains information particularly useful to debug an issue. By default, only stack trace elements pertaining to the game code are shown. It is possible for frontend errors to toggle this behavior and show BGA frontend stack trace elements.

Every element of the stack trace is clickable to see a hint on exactly when the execution was. Please note that some of this code is minified and hence is not very readable. However, it can still provide useful information. We plan to perhaps unminify this code later.

====== Request ======
[[File:Issue request details.png|frameless]]
This block contains details on the request, namely:

* '''URL:''' complete URL of the request, but without the query string
* '''Method:''' could be <code>GET</code> or <code>POST</code>
* '''Query:''' all query parameters if any

====== Tags ======
[[File:Issue tags.png|frameless]]

List any relevant tags regarding this event.

====== Statistics ======
[[File:Issue statistics - histogram.png|frameless]]

This block contains an histogram of the issue events depending, either during last day or last month. Every bar is clickable.

[[File:Issue statistics.png|frameless]]

Then, we have donuts-like statistics with a breakdown of the first 10 occurrences for:

* browsers
* device family
* OSes
* users
* tables

The more a stats impacts a browser, user or device brand, the more it is suspect that the issue is specific to them.

===== Events list view =====
[[File:Issue events list.png|frameless]]

When clicking on the "Other events" tab, you will see the following view, which allows you to inspect a specific event. Usually, it is not needed since default event provides enough context, but it can still be used to compare several events.

File:Issue events list.png

2025-05-21T15:56:38Z

Lymon Flowers:

Issue events list

Production issues reporting

2025-05-21T15:53:03Z

Lymon Flowers: /* Issue detail view */ More screenshots on issue details

File:Issue statistics.png

2025-05-21T15:51:18Z

Lymon Flowers:

Issue statistics

File:Issue statistics - histogram.png

2025-05-21T15:50:10Z

Lymon Flowers:

Issue statistics - histogram

File:Issue tags.png

2025-05-21T15:49:02Z

Lymon Flowers:

Issue tags

File:Issue request details.png

2025-05-21T13:17:30Z

Lymon Flowers:

Issue request details

File:Issue stack trace.png

2025-05-21T13:14:40Z

Lymon Flowers:

Issue stack trace

File:Issue culprit.png

2025-05-21T13:11:46Z

Lymon Flowers:

Issue culprit

File:Issue main informations.png

2025-05-21T13:09:05Z

Lymon Flowers:

Issue main informations

Production issues reporting

2025-05-21T13:05:55Z

Lymon Flowers: /* Views */ Add more details

File:Issue details.png

2025-05-21T12:16:30Z

Lymon Flowers:

Issue details in the Sentry viewer.

File:Issues list.png

2025-05-21T12:03:10Z

Lymon Flowers:

Sentry issues list

Production issues reporting

2025-05-21T10:45:41Z

Lymon Flowers: Add more context

Production issues reporting

2025-05-21T10:14:05Z

Lymon Flowers: Basic layout

File:Error reporting.png

2025-05-21T10:13:01Z

Lymon Flowers:

Error reporting as seen in any studio game page.

Studio

2025-05-21T10:09:08Z

Lymon Flowers: /* BGA Studio user guide */ Add new link

{{Studio_Framework_Navigation}}

[[File:Bga_studio_small.jpg|frameless|300px]]

Note: Please DO NOT translate Studio Documentation, so that there can be one place where you can find the latest information available.

__TOC__

== What is Board Game Arena Studio? ==

'''Board Game Arena Studio''' is a platform to build online board game adaptations using the Board Game Arena platform.

It is open to any gamer with software development skills :)

BGA Studio website: https://studio.boardgamearena.com

Original announcement on BGA forum: https://forum.boardgamearena.com/viewtopic.php?f=10&t=1973

== Discover BGA Studio in 5 presentations ==

Why, how, what... to start discovering BGA Studio, we prepared 5 "powerpoint" presentations for you:

* [http://www.slideshare.net/boardgamearena/5-reasons-why-you-should-use-bga-studio-for-your-online-board-game 5 reasons why you should use BGA Studio for your online board game] (or [http://en.doc.boardgamearena.com/images/5/58/1-why-developing.pdf ‎Download as PDF])
* [http://www.slideshare.net/boardgamearena/the-8-steps-to-create-a-board-game-on-board-game-arena The 8 steps to create a board game on Board Game Arena] (or [http://en.doc.boardgamearena.com/images/1/1e/2-8-steps-to-realize.pdf Download as PDF])
* [http://www.slideshare.net/boardgamearena/the-bga-framework-at-a-glance The BGA Framework at a glance] (or [http://en.doc.boardgamearena.com/images/7/79/3-thebgaframework.pdf Download as PDF])
* [http://www.slideshare.net/boardgamearena/bga-studio-focus-on-bga-game-state-machine Focus on BGA game state machine] (or [http://en.doc.boardgamearena.com/images/9/98/4-gamestates.pdf Download as PDF])
* [http://www.slideshare.net/boardgamearena/bga-studio-guidelines BGA developers guidelines] (or [http://en.doc.boardgamearena.com/images/7/76/5-guidelines.pdf ‎Download as PDF])

== How to join the BGA developer team? ==

Please see this page: [[How to join BGA developer team?]]

== Great, I'm in! ... How should I start? ==

If you didn't already, check the presentations at the top of this page to get the basics.

Then, you should checkout the [[First steps with BGA Studio]] to make sure that runs fine.

After that, we strongly advise you to take one of these game creation tutorials:
* [[Tutorial reversi]] ('''recommended''', closest to the actual BGA implementation and maintained by the BGA team) - an abstract strategy game played on an 8×8 uncheckered board for 2 players
* [[Tutorial gomoku]] - an abstract strategy game tic-tac-toe style for 2 players
* [[Tutorial hearts]] - a card game for 4 players

Then start editing files and see what happens! ;)

Once you're done with tutorials, you can start a real game (or join existing project)
* [[Create a game in BGA Studio: Complete Walkthrough]]

If you have any questions, please check out the [[Studio FAQ]] or [[Contact BGA Studio]].

To search wiki pages on studio enter this text in search bar:
"Category:Studio" white rabbit
That is if you want to search for white rabbit

== BGA Studio documentation ==

=== BGA Studio Framework reference ===

This part of the documentation focuses on the development framework itself: functions and methods available to build your game.

[[Studio file reference|File structure of a BGA game]]

==== Game logic (Server side) ====

* [[Main game logic: yourgamename.game.php]]
* [[Your game state machine: states.inc.php]]
* [[Game database model: dbmodel.sql]]
* [[Players actions: yourgamename.action.php]]
* [[Game material description: material.inc.php]]
* [[Game statistics: stats.inc.php]]

==== Game interface (Client side) ====

* [[Game interface logic: yourgamename.js]]
* [[Game art: img directory]]
* [[Game interface stylesheet: yourgamename.css]]
* [[Game layout: view and template: yourgamename.view.php and yourgamename_yourgamename.tpl]]
* [[Your game mobile version]]

==== Other components ====

* [[Translations]] (how to make your game translatable)
* [[Options_and_preferences:_gameoptions.json,_gamepreferences.json|Game Options and Preferences]]
* [[Game meta-information: gameinfos.inc.php]]
* [[Game replay]]
* [[3D]]

=== BGA Studio game components reference ===

Game components are useful tools you can use in your game adaptations.

JS:

* [[Counter]]: a JS component to manage a counter that can increase/decrease (ex: player's score).
* [[Scrollmap]]: a JS component to manage a scrollable game area (useful when the game area can be infinite. Examples: Saboteur or Takenoko games).
* [[Stock]]: a JS component to manage and display a set of game elements displayed at a position.
* [[Zone]]: a JS component to manage a zone of the board where several game elements can come and leave, but should be well displayed together (See for example: token's places at Can't Stop).
* [[Draggable]]: a JS component to manage drag'n'drop actions.
* [[ExpandableSection]]: a JS component to manage a rectangular block of HTML than can be displayed/hidden.
* [[Anti-Stock]]: Code snippets in vanilla JS/HTML5 to do what stock does (that is if you cannot beat Stock into submission)

PHP:
* [[Deck]]: a PHP component to manage cards (deck, hands, picking cards, moving cards, shuffle deck, ...).

Reference for classes in game class hierarchy

* [[Table]]: a PHP class that you inherit from for the game php

=== BGA Studio user guide ===

This part of the documentation is a user guide for the BGA Studio online development environment.

Lifecycle

* [[BGA game Lifecycle]]
* [[BGA Game licenses]]
* [[Create a game in BGA Studio: Complete Walkthrough]]
* [[Pre-release checklist]] - Go throught this list if you think you done development
* [[Post-release phase]]

Tools and Advice
* [[BGA Studio Guidelines]]
* [[Tutorials checklist]]
* [[I wish I knew this when I started]] - one liners on most common missed features, mistakes, etc with further doc references
* [[Tools and tips of BGA Studio]] - Tips and instructions on setting up development environment
** [[Setting up BGA Development environment using VSCode]]
** [[Practical debugging]] - Tips focused on debugging
** [[Testing by developer]]
** [[Studio logs]] - Instructions for log access
** [[Troubleshooting]] - Most common "I am really stuck" situations
* [[Production issues reporting|Production issues reporting tool]]
* [[BGA Studio Cookbook]] - Tips and instructions on using API's, libraries and frameworks
** [[Using Vue]] - work-in-progress guide on using the modern framework Vue.js to create a game
** [[Using Typescript and Scss]] - How to auto-build Typescript and SCSS files to make your code cleaner
** [[BGA Type Safe Template]] - Setting up a fully typed project using typescript and more!
** [[Bots and Artificial Intelligence]] - How to add AI/Bots to the game
* [[Studio FAQ]]

Sharing
* [[Common board game elements image resources]] - Dice, meeples, cubes, etc
* [[BGA Code Sharing]] - Shared resources, projects on git hub, common code, other links

== Software Versions ==

Versions currently used by BGA framework:

* Dojo Toolkit 1.15
* PHP: 8.2
* SQL: MySQL 5.7
* JS/CSS/HTML: limited by what minimization tools support: [[Game_interface_logic:_yourgamename.js#Javascript_minimization_.28after_July_2020.29|JS minimization]]
* Font Awesome: 4.7 https://fontawesome.com/v4.7/icons/ (available as <code><nowiki><i class="fa fa-clock" /></nowiki></code>)
* Font Awesome: 6.4.0 https://fontawesome.com/v6/search?o=r&m=free (available as <code><nowiki><i class="fa6 fa6-clock" /></nowiki></code>)

=== PHP Extensions Used ===

The following PHP extensions are - as of May 8th, 2022 - in use in BGA Studio and available:

date, libxml, openssl, pcre, zlib, filter, hash, Reflection, SPL, session, standard, sodium, apache2handler, mysqlnd, PDO, xml, apcu, bz2, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext, gmp, iconv, igbinary, json, exif, msgpack, mysqli, pdo_mysql, apc, posix, readline, shmop, SimpleXML, sockets, sysvmsg, sysvsem, sysvshm, tokenizer, v8js, xmlreader, xmlwriter, xsl, zip, Phar, memcached, Zend OPcache

== Other resources ==

[http://forum.boardgamearena.com/viewforum.php?f=12 Development forum]

[https://studio.boardgamearena.com/bugs Bug tracking system FOR STUDIO issues and APIs]

DISCORD chat server/room invite link https://discord.gg/YxEUacY if it does not work check this topic https://forum.boardgamearena.com/viewtopic.php?f=12&t=17403&hilit=discord

Developer BLOGS https://bga-devs.github.io/blog/

[[Contact BGA Studio]]

[[Category:Studio]]

Gamehelpmedina

2021-04-02T14:41:53Z

Lymon Flowers:

== Introduction ==

In Medina, players must place two pieces on the board (except when allowed to skip this with a tea tile), either augmenting an existing building (or starting a new building if the current building of that color is finished), or expanding one of the other features of the city, like the market or the walls. Each player will claim one building of each of the four colors by the end of the game, giving one point per wooden piece attached to the building.

Also, if you own the largest building of a particular color you get a bonus for that color. Finally, there are bonuses for palaces around the well, as well as for the player who most recently connected one of their buildings to the walls, which grow from the four corners of the city.

== Setup ==

Depending on edition selected and players number, each player receives a number of blocks that they will place on the board in turn:

* in a 2 players game
** buildings: 8
** rooftops: 4
** neutral rooftops: 2 (if applicable)
** stables: 4
** merchants: 12
** walls: 15
* in a 3 players game:
** buildings: 6
** rooftops: 4
** neutral rooftop: 1 (if applicable)
** stables: 4
** merchants: 8
** walls: 12
* in a 4 players game:
** buildings: 5,
** rooftops: 4
** stables: 3
** merchants: 6
** walls: 9

A merchant is placed randomly on the board as well as a well if applicable.

A first player is randomly chosen.

=== Game options ===

The following options can be selected or deselected prior to a game:

==== Fountain ====
If this option is activated, a well will be created on a random field on the game board before the start of the
game. For each part of the palace that is directly orthogonally adjacent to the fountain, there are 4
additional points. The fields for which there are 4 points each are marked in blue on the game board.

==== Tea tiles ====
If this option is activated, there are 6 purple tea tiles in the game. If you take possession of the first purple
palace, you receive 3 tea tiles. The player who takes possession of the second purple palace receives 2 tea
tiles. And the third player receives 1 tea tile. If a player owns tea tiles, he can take tea breaks. He then only
has to build a piece of wood in his turn and can then, instead of playing another piece of wood, give a tea
tile.

==== Merchants on the tower tiles ====
When this option is activated, 6 additional merchants come into game. There are 3 merchants on the 1
tower tile, 2 merchants on the 2 tower tile and 1 merchant on the 3 tower tile. The player who wins such a
tower tile first receives additional 1, 2 or 3 merchants.

==== Neutral rooftops ====
If this option is activated in the game with three people, each player also receives a neutral grey roof. If a
neutral, grey roof is placed on a palace, this palace does not belong to any player.
In a two-player game, each player always receives 2 neutral roofs. In a game for two, the neutral roofs
cannot be deactivated. The first edition of Medina could only be played by three or four players. With the
neutral roofs, the game on a slightly smaller game board also works very well for two. In a four-player
game, the neutral roofs are not available.

== Blocks ==

=== Buildings ===
These are the blocks received in the largest quantity. They come in four colors: white, purple, maroon, orange.

Adjacent buildings constitutes palaces, which grow in time. A building can be placed only adjacent orthogonally to an unfinished palace of this color or anywhere on the board if no palace of this color is unfinished.

Buildings cannot be placed adjacent orthogonally or diagonally to another palace, meaning there is always room for an alley between two palaces.

=== Rooftops ===
Rooftops are used to claim palaces. A player can only claim ONE palace of a given color. Once they have placed a rooftop on a palace, this palace is finished and cannot be expanded further by buildings.

Also, if a player claims the largest palace they will get the palace tile of this color for additional points. Palace tiles can change hands several times.

In 2nd edition game, players will also receive neutral rooftops used to finish palaces and thwart opponents plans. Palace tiles can be claimed by the "neutral" player and be placed back onto the board.

=== Stables ===
Stables can be used only to expand existing palaces. They must be placed orthogonally adjacent to a palace (finished or not). As buildings, they must not be placed orthogonally or diagonally to another palace.

=== Walls ===
Walls are placed next to a tower (there is one on each corner of the board) or to another wall. Chains of walls are then created from each corner, but corners must be separated by an empty places (a gate) between the chains of walls.

When a wall is placed orthogonally adjacent to a finished palace (including stables), the owning player receives a watcher tile for additional points. Also, when a finished palace is expanded with a stable to connect to an already existing wall, the owner player receives a watcher tile.

Neutral player can claim watcher tiles.

=== Merchants ===
Merchants can only be placed next to an existing merchant in order to create a string of merchants (the market). A merchant can only be placed orthogonally to one and ONLY one existing merchant in either ends of the market. If both ends of the market are blocked, new merchants can be placed anywhere save adjacent to existing merchants, creating a new market.

=== Tea tiles ===
If applicable, the first players to claim purple palace will receive tea tiles. Playing a tea tile will allow a player to pass by clicking on it in their inventory. It is not possible to pass twice in a turn.

Neutral player can claim tea tiles (which are removed from play).

== End game and scoring ==
When a player is unable to play they pass until they can play again. When all players are unable to play, game ends and the winner is the player with the most points. Points are awarded as follows:

* each building or stable constituting a palace: 1 point
* each wall adjacent to a palace: +1 point to that palace
* each merchant adjacent to a palace: +1 point to that palace (a single merchant may be scored multiple times if adjacent to two or more palaces)
* each palace orthogonally separated two spaces away from the well (see water icons): 4 points
* each palace tile: 1-4 points
* each watcher tile: 1-4 point

In case of ties, the player with the largest palace wins. In case of another tie, the player owning the largest palace that has been claimed first wins.

== Differences between editions ==
There are significant differences between the two editions of the game. Only the second edition is implemented there, with the possibility to disable some of the 2nd edition features.

=== Well ===
In second edition, a palace that has a building or stable that is separated orthogonally by one space from the well grants four more points to its owner.

This can be disabled.

=== Merchants on watcher tiles ===
In second edition, merchants are placed on watcher tiles. The first player to claim a watcher also receives the merchants. If the neutral player claims this watcher tile, the merchants are removed from play.

This can be disabled.

=== Tea tiles ===
In second edition, the first players to claim purple palaces will receive tea tiles (3, then 2, then 1). Playing a tea tile will allow a player to pass by clicking on it in their inventory. It is not possible to pass twice in a turn.

This can be disabled.

=== Last player with rooftops ===
In first edition, if there is only one player with rooftops left they MUST play at least one rooftop each turn if possible. The game will refuse to finish a turn if that constraint is not satisfied. Once this player does not have rooftops anymore, they can still continue to play normally.

This behavior is not present in this game adaptation.

=== First turn ===
In a second edition game, the first player of a two players game only plays one block in their first turn (and also the second player in a three or four players game).

This behavior is not present in this game adaptation

=== Neutral roofs ===
In a first edition game, there is no neutral rooftop and hence no neutral player to claim tiles.

This can be disabled in 3 player games and no neutral rooftop is available in a 4 players game.

=== Number of blocks ===
In a first and second edition game, the number of blocks received during game setup is different.

Gamehelpmedina

2021-03-04T15:42:01Z

Lymon Flowers: Remove useless linefeeds

== Introduction ==

In Medina, players must place two pieces on the board (except when allowed to skip this with a tea tile), either augmenting an existing building (or starting a new building if the current building of that color is finished), or expanding one of the other features of the city, like the market or the walls. Each player will claim one building of each of the four colors by the end of the game, giving one point per wooden piece attached to the building.

Also, if you own the largest building of a particular color you get a bonus for that color. Finally, there are bonuses for palaces around the well, as well as for the player who most recently connected one of their buildings to the walls, which grow from the four corners of the city.

== Setup ==

Depending on edition selected and players number, each player receives a number of blocks that they will place on the board in turn:

* in a 2 players game
** buildings: 8
** rooftops: 4
** neutral rooftops: 2 (if applicable)
** stables: 4
** merchants: 12
** walls: 15
* in a 3 players game:
** buildings: 6
** rooftops: 4
** neutral rooftop: 1 (if applicable)
** stables: 4
** merchants: 8
** walls: 12
* in a 4 players game:
** buildings: 5,
** rooftops: 4
** stables: 3
** merchants: 6
** walls: 9

A merchant is placed randomly on the board as well as a well if applicable.

A first player is randomly chosen.

== Blocks ==

=== Buildings ===
These are the blocks received in the largest quantity. They come in four colors: white, purple, maroon, orange.

Adjacent buildings constitutes palaces, which grow in time. A building can be placed only adjacent orthogonally to an unfinished palace of this color or anywhere on the board if no palace of this color is unfinished.

Buildings cannot be placed adjacent orthogonally or diagonally to another palace, meaning there is always room for an alley between two palaces.

=== Rooftops ===
Rooftops are used to claim palaces. A player can only claim ONE palace of a given color. Once they have placed a rooftop on a palace, this palace is finished and cannot be expanded further by buildings.

Also, if a player claims the largest palace they will get the palace tile of this color for additional points. Palace tiles can change hands several times.

In 2nd edition game, players will also receive neutral rooftops used to finish palaces and thwart opponents plans. Palace tiles can be claimed by the "neutral" player and be placed back onto the board.

=== Stables ===
Stables can be used only to expand existing palaces. They must be placed orthogonally adjacent to a palace (finished or not). As buildings, they must not be placed orthogonally or diagonally to another palace.

=== Walls ===
Walls are placed next to a tower (there is one on each corner of the board) or to another wall. Chains of walls are then created from each corner, but corners must be separated by an empty places (a gate) between the chains of walls.

When a wall is placed orthogonally adjacent to a finished palace (including stables), the owning player receives a watcher tile for additional points. Also, when a finished palace is expanded with a stable to connect to an already existing wall, the owner player receives a watcher tile.

Neutral player can claim watcher tiles.

=== Merchants ===
Merchants can only be placed next to an existing merchant in order to create a string of merchants (the market). A merchant can only be placed orthogonally to one and ONLY one existing merchant in either ends of the market. If both ends of the market are blocked, new merchants can be placed anywhere save adjacent to existing merchants, creating a new market.

=== Tea tiles ===
If applicable, the first players to claim purple palace will receive tea tiles. Playing a tea tile will allow a player to pass by clicking on it in their inventory. It is not possible to pass twice in a turn.

Neutral player can claim tea tiles (which are removed from play).

== End game and scoring ==
When a player is unable to play they passe until they can play again. When all players are unable to play, game ends and the winner is the player with the most points. Points are awarded as follows:

* each building or stable constituting a palace: 1 point
* each wall adjacent to a palace: 1 point
* each merchant adjacent to a palace: 1 point (NOT counted double it adjacent to two or more buildings)
* each palace orthogonally separated two spaces away from the well (see water icons): 4 points
* each palace tile: 1-4 points
* each watcher tile: 1-4 point

In case of ties, the player with the largest palace wins. In case of another tie, the player owning the largest palace that has been claimed first wins.

== Differences between editions ==
There are significant differences between the two editions of the game. Only the second edition is implemented there, with the possibility to disable some of the 2nd edition features.

=== Well ===
In second edition, a palace that has a building or stable that is separated orthogonally by one space from the well grants four more points to its owner.

This can be disabled.

=== Merchants on watcher tiles ===
In second edition, merchants are placed on watcher tiles. The first player to claim a watcher also receives the merchants. If the neutral player claims this watcher tile, the merchants are removed from play.

This can be disabled.

=== Tea tiles ===
In second edition, the first players to claim purple palaces will receive tea tiles (3, then 2, then 1). Playing a tea tile will allow a player to pass by clicking on it in their inventory. It is not possible to pass twice in a turn.

This can be disabled.

=== Last player with rooftops ===
In first edition, if there is only one player with rooftops left they MUST play at least one rooftop each turn if possible. The game will refuse to finish a turn if that constraint is not satisfied. Once this player does not have rooftops anymore, they can still continue to play normally.

This behavior is not present in this game adaptation.

=== First turn ===
In a second edition game, the first player of a two players game only plays one block in their first turn (and also the second player in a three or four players game).

This behavior is not present in this game adaptation

=== Neutral roofs ===
In a first edition game, there is no neutral rooftop and hence no neutral player to claim tiles.

This can be disabled in 3 player games and no neutral rooftop is available in a 4 players game.

=== Number of blocks ===
In a first and second edition game, the number of blocks received during game setup is different.

Gamehelpmedina

2021-03-04T15:29:48Z

Lymon Flowers:

== Introduction ==

In Medina, players must place two pieces on the board (except when allowed to skip this with a tea tile), either augmenting an existing building (or starting a new building if the current building of that color is finished), or expanding one of the other features of the city, like the market or the walls. Each player will claim one building of each of the four colors by the end of the game, giving one point per wooden piece attached to the building.

Also, if you own the largest building of a particular color you get a bonus for that color. Finally, there are bonuses for palaces around the well, as well as for the player who most recently connected one of their buildings to the walls, which grow from the four corners of the city.

== Setup ==

Depending on edition selected and players number, each player receives a number of blocks that they will place on the board in turn:

* in a 2 players game
** buildings: 8
** rooftops: 4
** neutral rooftops: 2 (if applicable)
** stables: 4
** merchants: 12
** walls: 15
* in a 3 players game:
** buildings: 6
** rooftops: 4
** neutral rooftop: 1 (if applicable)
** stables: 4
** merchants: 8
** walls: 12
* in a 4 players game:
** buildings: 5,
** rooftops: 4
** stables: 3
** merchants: 6
** walls: 9

A merchant is placed randomly on the board as well as a well if applicable.

A first player is randomly chosen.

== Blocks ==

=== Buildings ===
These are the blocks received in the largest quantity. They come in four colors: white, purple, maroon, orange.

Adjacent buildings constitutes palaces, which grow in time. A building can be placed only adjacent orthogonally to an unfinished palace of this color or anywhere on the board if no palace of this color is unfinished.

Buildings cannot be placed adjacent orthogonally or diagonally to another palace, meaning there is always room for an alley between two palaces.

=== Rooftops ===
Rooftops are used to claim palaces. A player can only claim ONE palace of a given color. Once they have placed a rooftop on a palace, this palace is finished and cannot be expanded further by buildings.

Also, if a player claims the largest palace they will get the palace tile of this color for additional points. Palace tiles can change hands several times.

In 2nd edition game, players will also receive neutral rooftops used to finish palaces and thwart opponents plans. Palace tiles can be claimed by the "neutral" player and be placed back onto the board.

=== Stables ===
Stables can be used only to expand existing palaces. They must be placed orthogonally adjacent to a palace (finished or not). As buildings, they must not be placed orthogonally or diagonally to another palace.

=== Walls ===
Walls are placed next to a tower (there is one on each corner of the board) or to another wall. Chains of walls are then created from each corner, but corners must be separated by an empty places (a gate) between the chains of walls.

When a wall is placed orthogonally adjacent to a finished palace (including stables), the owning player receives a watcher tile for additional points. Also, when a finished palace is expanded with a stable to connect to an already existing wall, the owner player receives a watcher tile.

Neutral player can claim watcher tiles.

=== Merchants ===
Merchants can only be placed next to an existing merchant in order to create a string of merchants (the market). A merchant can only be placed orthogonally to one and ONLY one existing merchant in either ends of the market. If both ends of the market are blocked, new merchants can be placed anywhere save adjacent to existing merchants, creating a new market.

=== Tea tiles ===
If applicable, the first players to claim purple palace will receive tea tiles. Playing a tea tile will allow a player to pass by clicking on it in their inventory. It is not possible to pass twice in a turn.

Neutral player can claim tea tiles (which are removed from play).

== End game and scoring ==
When a player is unable to play they passe until they can play again. When all players are unable to play, game ends and the winner is the player with the most points. Points are awarded as follows:

* each building or stable constituting a palace: 1 point
* each wall adjacent to a palace: 1 point
* each merchant adjacent to a palace: 1 point (NOT counted double it adjacent to two or more buildings)
* each palace orthogonally separated two spaces away from the well (see water icons): 4 points
* each palace tile: 1-4 points
* each watcher tile: 1-4 point

In case of ties, the player with the largest palace wins. In case of another tie, the player owning the largest palace that has been claimed first wins.

== Differences between editions ==
There are significant differences between the two editions of the game. Only the second edition is implemented there, with the possibility to disable some of the 2nd edition features.

=== Well ===
In second edition, a palace that has a building or stable that is separated orthogonally by one space from the well grants four more points to its owner.

This can be disabled.

=== Merchants on watcher tiles ===
In second edition, merchants are placed on watcher tiles. The first player to claim a watcher also receives the merchants. If the neutral player claims this watcher tile, the merchants are removed from play.

This can be disabled.

=== Tea tiles ===
In second edition, the first players to claim purple palaces will receive tea tiles (3, then 2, then 1). Playing a tea tile will allow a player to pass by clicking on it in their inventory. It is not possible to pass twice in a turn.

This can be disabled.

=== Last player with rooftops ===
In first edition, if there is only one player with rooftops left they MUST play at least one rooftop each turn if possible. The game will refuse to finish a turn if that constraint is not satisfied. Once this player does not have rooftops anymore, they can still continue to play normally.

This behavior is not present in this game adaptation.

=== First turn ===
In a second edition game, the first player of a two players game only plays one block in their first turn (and also the second player in a three or four players game).

This behavior is not present in this game adaptation

=== Neutral roofs ===
In a first edition game, there is no neutral rooftop and hence no neutral player to claim tiles.

This can be disabled in 3 player games and no neutral rooftop is available in a 4 players game.

=== Number of blocks ===
In a first and second edition game, the number of blocks received during game setup is different.

Gamehelpmedina

2021-03-04T15:26:53Z

Lymon Flowers:

== Introduction ==

In Medina, players must place two pieces on the board (except when allowed to skip this with a tea tile), either augmenting an existing building (or starting a new building if the current building of that color is finished), or expanding one of the other features of the city, like the market or the walls. Each player will claim one building of each of the four colors by the end of the game, giving one point per wooden piece attached to the building.

Also, if you own the largest building of a particular color you get a bonus for that color. Finally, there are bonuses for palaces around the well, as well as for the player who most recently connected one of their buildings to the walls, which grow from the four corners of the city.

== Setup ==

Depending on edition selected and players number, each player receives a number of blocks that they will place on the board in turn.

A merchant is placed randomly on the board as well as a well if applicable.

A first player is randomly chosen.

== Blocks ==

=== Buildings ===
These are the blocks received in the largest quantity. They come in four colors: white, purple, maroon, orange.

Adjacent buildings constitutes palaces, which grow in time. A building can be placed only adjacent orthogonally to an unfinished palace of this color or anywhere on the board if no palace of this color is unfinished.

Buildings cannot be placed adjacent orthogonally or diagonally to another palace, meaning there is always room for an alley between two palaces.

=== Rooftops ===
Rooftops are used to claim palaces. A player can only claim ONE palace of a given color. Once they have placed a rooftop on a palace, this palace is finished and cannot be expanded further by buildings.

Also, if a player claims the largest palace they will get the palace tile of this color for additional points. Palace tiles can change hands several times.

In 2nd edition game, players will also receive neutral rooftops used to finish palaces and thwart opponents plans. Palace tiles can be claimed by the "neutral" player and be placed back onto the board.

=== Stables ===
Stables can be used only to expand existing palaces. They must be placed orthogonally adjacent to a palace (finished or not). As buildings, they must not be placed orthogonally or diagonally to another palace.

=== Walls ===
Walls are placed next to a tower (there is one on each corner of the board) or to another wall. Chains of walls are then created from each corner, but corners must be separated by an empty places (a gate) between the chains of walls.

When a wall is placed orthogonally adjacent to a finished palace (including stables), the owning player receives a watcher tile for additional points. Also, when a finished palace is expanded with a stable to connect to an already existing wall, the owner player receives a watcher tile.

Neutral player can claim watcher tiles.

=== Merchants ===
Merchants can only be placed next to an existing merchant in order to create a string of merchants (the market). A merchant can only be placed orthogonally to one and ONLY one existing merchant in either ends of the market. If both ends of the market are blocked, new merchants can be placed anywhere save adjacent to existing merchants, creating a new market.

=== Tea tiles ===
If applicable, the first players to claim purple palace will receive tea tiles. Playing a tea tile will allow a player to pass by clicking on it in their inventory. It is not possible to pass twice in a turn.

Neutral player can claim tea tiles (which are removed from play).

== End game and scoring ==
When a player is unable to play they passe until they can play again. When all players are unable to play, game ends and the winner is the player with the most points. Points are awarded as follows:

* each building or stable constituting a palace: 1 point
* each wall adjacent to a palace: 1 point
* each merchant adjacent to a palace: 1 point (NOT counted double it adjacent to two or more buildings)
* each palace orthogonally separated two spaces away from the well (see water icons): 4 points
* each palace tile: 1-4 points
* each watcher tile: 1-4 point

In case of ties, the player with the largest palace wins. In case of another tie, the player owning the largest palace that has been claimed first wins.

== Differences between editions ==
There are significant differences between the two editions of the game. Only the second edition is implemented there, with the possibility to disable some of the 2nd edition features.

=== Well ===
In second edition, a palace that has a building or stable that is separated orthogonally by one space from the well grants four more points to its owner.

This can be disabled.

=== Merchants on watcher tiles ===
In second edition, merchants are placed on watcher tiles. The first player to claim a watcher also receives the merchants. If the neutral player claims this watcher tile, the merchants are removed from play.

This can be disabled.

=== Tea tiles ===
In second edition, the first players to claim purple palaces will receive tea tiles (3, then 2, then 1). Playing a tea tile will allow a player to pass by clicking on it in their inventory. It is not possible to pass twice in a turn.

This can be disabled.

=== Last player with rooftops ===
In first edition, if there is only one player with rooftops left they MUST play at least one rooftop each turn if possible. The game will refuse to finish a turn if that constraint is not satisfied. Once this player does not have rooftops anymore, they can still continue to play normally.

This behavior is not present in this game adaptation.

=== First turn ===
In a second edition game, the first player of a two players game only plays one block in their first turn (and also the second player in a three or four players game).

This behavior is not present in this game adaptation

=== Neutral roofs ===
In a first edition game, there is no neutral rooftop and hence no neutral player to claim tiles.

This can be disabled in 3 player games and no neutral rooftop is available in a 4 players game.

=== Number of blocks ===
In a first and second edition game, the number of blocks received during game setup is different.