This is a documentation for Board Game Arena: play board games online !
BGA Studio Migration Guide: Difference between revisions
Victoria La (talk | contribs) (initial commit) |
Victoria La (talk | contribs) m (proper formatring) |
||
| Line 13: | Line 13: | ||
== Structural changes == | == Structural changes == | ||
''gameoptions.inc.php'' => gameoptions.json, gamepreferences.json | '''''gameoptions.inc.php''''' => gameoptions.json, gamepreferences.json | ||
Previously, options and preferences were specified in a single gameoptions.inc.php file. | Previously, options and preferences were specified in a single gameoptions.inc.php file. | ||
Now options and preferences are 2 json files, follow Migration steps on this page https://en.doc.boardgamearena.com/Options_and_preferences:_gameoptions.json,_gamepreferences.json#Migration | Now options and preferences are 2 json files, follow Migration steps on this page https://en.doc.boardgamearena.com/Options_and_preferences:_gameoptions.json,_gamepreferences.json#Migration | ||
''<gamename>.game.php'' => modules/php/Game.php | '''''<gamename>.game.php''''' => modules/php/Game.php | ||
''<gamename>.view.php, <gamename>_<gamename>.tpl'' => | '''''<gamename>.view.php, <gamename>_<gamename>.tpl''''' => remove | ||
''material.inc.php'' => optional | '''''material.inc.php''''' => optional | ||
''states.inc.php'' => modules/php/States | '''''states.inc.php''''' => modules/php/States | ||
'''<gamename>.action.php => remove''' | |||
== PHP migration == | == PHP migration == | ||
| Line 49: | Line 51: | ||
This new object can also return the Real-time/Turn-based information: https://en.doc.boardgamearena.com/Main_ ... exion_time | This new object can also return the Real-time/Turn-based information: https://en.doc.boardgamearena.com/Main_ ... exion_time | ||
Legacy | == Legacy == | ||
New object to access the legacy functions, removing the need to manually decode the JSON result when getting the values. | New object to access the legacy functions, removing the need to manually decode the JSON result when getting the values. | ||
| Line 57: | Line 58: | ||
📌 Use $this->legacy->actionname instead of $this->actionnameLegacy and remove JSON decoding on getters | 📌 Use $this->legacy->actionname instead of $this->actionnameLegacy and remove JSON decoding on getters | ||
Globals of any type | == Globals of any type == | ||
New functions to handle any type variables instead of numerical values only | New functions to handle any type variables instead of numerical values only | ||
https://en.doc.boardgamearena.com/Main_game_logic:_Game.php#Use_globals | https://en.doc.boardgamearena.com/Main_game_logic:_Game.php#Use_globals | ||
Simplify front->back calls | == Simplify front->back calls == | ||
Introduce bgaPerformAction to replace ajaxcall and checkAction combination, with a simpler syntax: | Introduce bgaPerformAction to replace ajaxcall and checkAction combination, with a simpler syntax: | ||
| Line 71: | Line 70: | ||
📌 Replace combination of checkAction/ajaxcall by bgaPerformAction. Beware of the options (3rd param) if it was an ajaxcall without checkAction. | 📌 Replace combination of checkAction/ajaxcall by bgaPerformAction. Beware of the options (3rd param) if it was an ajaxcall without checkAction. | ||
Autowire game actions | == Autowire game actions == | ||
Simplify the action calls by removing the use of the action.php file | Simplify the action calls by removing the use of the action.php file | ||
| Line 81: | Line 79: | ||
When migration is done, the action.php file can be deleted. | When migration is done, the action.php file can be deleted. | ||
Namespaced game class | == Namespaced game class == | ||
Game classes are now namespaced (and moved to modules/php/Game.php) and can autoload other classes of the same namespace | Game classes are now namespaced (and moved to modules/php/Game.php) and can autoload other classes of the same namespace | ||
| Line 97: | Line 94: | ||
All includes with relative path will need to be updated too | All includes with relative path will need to be updated too | ||
IDE Helper & bga-framework.d.ts | == IDE Helper & bga-framework.d.ts == | ||
A new _ide_helper.php file is now provided in every project dir, allowing IDE to provide syntax error highlighting for the framework functions. This file is regularly updated to match the latest framework updates. | A new _ide_helper.php file is now provided in every project dir, allowing IDE to provide syntax error highlighting for the framework functions. This file is regularly updated to match the latest framework updates. | ||
| Line 105: | Line 101: | ||
📌 Sync the files from the FTP dir to your local copy to benefit from it. Most of the IDE like Visual Studio Code should handle _ide_helper.php if you already followed https://en.doc.boardgamearena.com/Setting_up_BGA_Development_environment_using_VSCode | 📌 Sync the files from the FTP dir to your local copy to benefit from it. Most of the IDE like Visual Studio Code should handle _ide_helper.php if you already followed https://en.doc.boardgamearena.com/Setting_up_BGA_Development_environment_using_VSCode | ||
Strict mode set in new project template | == Strict mode set in new project template == | ||
New projects are generated using the strict mode activated (for typings). The examples in the doc have been updated to handle old framework function returning bad typings, for example (int) $this->getActivePlayerId(); | New projects are generated using the strict mode activated (for typings). The examples in the doc have been updated to handle old framework function returning bad typings, for example (int) $this->getActivePlayerId(); | ||
| Line 113: | Line 108: | ||
📌 A global replace should work on the Game.php files | 📌 A global replace should work on the Game.php files | ||
Access template elements | == Access template elements == | ||
New functions getPlayerPanelElement(player_id) and this.getGameAreaElement() | New functions getPlayerPanelElement(player_id) and this.getGameAreaElement() | ||
| Line 121: | Line 115: | ||
📌 Code like dojo.place(html, player_board_${player.id}); would be replaced by this.getGameAreaElement().insertAdjacentHTML('beforeend', html); | 📌 Code like dojo.place(html, player_board_${player.id}); would be replaced by this.getGameAreaElement().insertAdjacentHTML('beforeend', html); | ||
Optional files: action/view/template/material | == Optional files: action/view/template/material == | ||
Action/view/template/material files are now optional and are not generated anymore on a new project. The new project templates demonstrate how to work without them. | Action/view/template/material files are now optional and are not generated anymore on a new project. The new project templates demonstrate how to work without them. | ||
| Line 128: | Line 121: | ||
The template should be built on the JS side to remove the view/template files, so it can be complicated for old projects using them intensively. It would look like this: | The template should be built on the JS side to remove the view/template files, so it can be complicated for old projects using them intensively. It would look like this: | ||
Code: Select all | Code: Select all | ||
this.getGameAreaElement().insertAdjacentHTML('beforeend', `<span>${_('My translated text')}</span>`); | |||
== Easier notification setup == | |||
Easier notification setup | |||
Notifications can now be automatically scanned and called without needing to register them one by one. They'll handle Promises, so they end synchronously when the Promise resolves. | Notifications can now be automatically scanned and called without needing to register them one by one. They'll handle Promises, so they end synchronously when the Promise resolves. | ||
| Line 149: | Line 138: | ||
If you used Dojo animation, make them Promise compatible with "await this.bgaPlayDojoAnimation(dojoAnim);" | If you used Dojo animation, make them Promise compatible with "await this.bgaPlayDojoAnimation(dojoAnim);" | ||
Status bar manipulation | == Status bar manipulation == | ||
Function to change the title from the JS | Function to change the title from the JS | ||
https://en.doc.boardgamearena.com/Game_interface_logic:_yourgamename.js#Title_bar | https://en.doc.boardgamearena.com/Game_interface_logic:_yourgamename.js#Title_bar | ||
| Line 160: | Line 148: | ||
📌 Replace this.addActionButton by this.statusBar.addActionButton. Notice the parameters have changed, so they need to be adapted too! Remove manual setActionTimer or manual confirm with the new parameters. | 📌 Replace this.addActionButton by this.statusBar.addActionButton. Notice the parameters have changed, so they need to be adapted too! Remove manual setActionTimer or manual confirm with the new parameters. | ||
Notification decorators | == Notification decorators == | ||
New notify function that handles decorators, reducing the duplicate code on notification args. | New notify function that handles decorators, reducing the duplicate code on notification args. | ||
| Line 168: | Line 155: | ||
📌 Replace notifyAllPlayers by notify->all and notifyPlayer by notify->player | 📌 Replace notifyAllPlayers by notify->all and notifyPlayer by notify->player | ||
Forbid access to global BGA variables and direct DB access on action/view files | == Forbid access to global BGA variables and direct DB access on action/view files == | ||
A new getCurrentPlayerId() function has been added to those action/view classes for easier migration | A new getCurrentPlayerId() function has been added to those action/view classes for easier migration | ||
| Line 176: | Line 162: | ||
Replace DB calls by $this->game->myFunctionCallingTheDB() | Replace DB calls by $this->game->myFunctionCallingTheDB() | ||
Instant cssPref on user preferences | == Instant cssPref on user preferences == | ||
A reload is not needed anymore to apply cssPref on a user preference change. | A reload is not needed anymore to apply cssPref on a user preference change. | ||
📌 Remove forceReload: true if it was only set to update the cssPref. The player will appreciate to not reload the whole page! | 📌 Remove forceReload: true if it was only set to update the cssPref. The player will appreciate to not reload the whole page! | ||
Dojo usage | == Dojo usage == | ||
Dojo usage has been reduced to minimum in the new project template and the doc, as native JS is now able to do almost the same things, with better performance and more knowledge for newcomers of the native (vanilla) JS. | Dojo usage has been reduced to minimum in the new project template and the doc, as native JS is now able to do almost the same things, with better performance and more knowledge for newcomers of the native (vanilla) JS. | ||
📌 Replace dojo by vanilla JS where possible | 📌 Replace dojo by vanilla JS where possible | ||
Skip a state | == Skip a state == | ||
When you skip a state on PHP side (directly move to another state on the "st" function), the JS is still notified that the skipped state is activated, then it activates the next state just after, but you may see the skipped state buttons being created then deleted. | When you skip a state on PHP side (directly move to another state on the "st" function), the JS is still notified that the skipped state is activated, then it activates the next state just after, but you may see the skipped state buttons being created then deleted. | ||
| Line 198: | Line 181: | ||
📌 Add _no_notify in the args when a state is skipped | 📌 Add _no_notify in the args when a state is skipped | ||
Sound loading | == Sound loading == | ||
New functions load/play have been added for the sounds: | New functions load/play have been added for the sounds: | ||
| Line 212: | Line 194: | ||
📌 Delete the getGameName function in the Game PHP file. | 📌 Delete the getGameName function in the Game PHP file. | ||
GameStateBuilder | == GameStateBuilder == | ||
This new class helps you build the state machine, allowing auto-completion, and avoid typo errors on state types. Complete example: 📌 https://en.doc.boardgamearena.com/Your_game_state_machine:_states.inc.php | This new class helps you build the state machine, allowing auto-completion, and avoid typo errors on state types. Complete example: 📌 https://en.doc.boardgamearena.com/Your_game_state_machine:_states.inc.php | ||
| Line 222: | Line 203: | ||
Note: it's only useful if you don't migrate to State classes described later on. | Note: it's only useful if you don't migrate to State classes described later on. | ||
bgaFormatText | == bgaFormatText == | ||
This function, if defined, will allow you to insert HTML in the logs without overriding format_string_recursive. Example: 📌https://en.doc.boardgamearena.com/BGA_Studio_Cookbook#Define_this.bgaFormatText%28%29_method | This function, if defined, will allow you to insert HTML in the logs without overriding format_string_recursive. Example: 📌https://en.doc.boardgamearena.com/BGA_Studio_Cookbook#Define_this.bgaFormatText%28%29_method | ||
📌 Replace the override of format_string_recursive by bgaFormatText (the last line will change) | 📌 Replace the override of format_string_recursive by bgaFormatText (the last line will change) | ||
Future support of dark mode | == Future support of dark mode == | ||
BGA doesn't support dark mode yet. To have some games compatible when we do, we added a theme data tag you can use as described here: | BGA doesn't support dark mode yet. To have some games compatible when we do, we added a theme data tag you can use as described here: | ||
https://en.doc.boardgamearena.com/Game_interface_stylesheet:_yourgamename.css#Support_of_the_Dark_mode | https://en.doc.boardgamearena.com/Game_interface_stylesheet:_yourgamename.css#Support_of_the_Dark_mode | ||
Framework function for automata player panel | == Framework function for automata player panel == | ||
A new framework function to add a player panel for your game automatas https://en.doc.boardgamearena.com/Game_interface_logic:_yourgamename.js#Adding_a_player_panel_for_an_automata | A new framework function to add a player panel for your game automatas https://en.doc.boardgamearena.com/Game_interface_logic:_yourgamename.js#Adding_a_player_panel_for_an_automata | ||
📌 Replace manually created automata player panel with this new function | 📌 Replace manually created automata player panel with this new function | ||
New JS libraries | == New JS libraries == | ||
We will provide new libraries to help you design your games, especially for components that you will find on numerous games. The first available libraries are: | We will provide new libraries to help you design your games, especially for components that you will find on numerous games. The first available libraries are: | ||
| Line 256: | Line 233: | ||
📌 Try them, and hopefully use them instead of the very old components! Each lib has a demo in the beginning of the wiki page to show what it can do. | 📌 Try them, and hopefully use them instead of the very old components! Each lib has a demo in the beginning of the wiki page to show what it can do. | ||
Notification args consistency | == Notification args consistency == | ||
Previously, when you sent an arg that was transformed by format_string_recursive or bgaFormatText, the args object was mutated and you got the transformed value in the notif_ handler. | Previously, when you sent an arg that was transformed by format_string_recursive or bgaFormatText, the args object was mutated and you got the transformed value in the notif_ handler. | ||
| Line 269: | Line 245: | ||
📌 Do not duplicate the value, as the notif_ handler will now get unmutated args | 📌 Do not duplicate the value, as the notif_ handler will now get unmutated args | ||
Updated Zombie Mode documentation and recommendations | == Updated Zombie Mode documentation and recommendations == | ||
We now recommend making the zombie player playing randomly, instead of passing as a default. A new "Zombie Mode level" field has been added to the Game Metadata Manager, to indicated the Zombie Mode you implemented in your game. | We now recommend making the zombie player playing randomly, instead of passing as a default. A new "Zombie Mode level" field has been added to the Game Metadata Manager, to indicated the Zombie Mode you implemented in your game. | ||
https://en.doc.boardgamearena.com/Zombie_Mode | https://en.doc.boardgamearena.com/Zombie_Mode | ||
State classes | == State classes == | ||
There is now a way to describe each game state in a State class, that will handle all logic and description of the state. It helps splitting the code into multiple files, instead of one big Game.php file. | There is now a way to describe each game state in a State class, that will handle all logic and description of the state. It helps splitting the code into multiple files, instead of one big Game.php file. | ||
| Line 283: | Line 257: | ||
📌 Create a State class for each state of the game (except 1 and 99 if they are still described in states.inc.php), move the state definition in it, and adapt the "st", "arg", "actXXX" and "zombie" functions in the class. When all classes are migrated, you can remove the states.inc.php file in the FTP folder. | 📌 Create a State class for each state of the game (except 1 and 99 if they are still described in states.inc.php), move the state definition in it, and adapt the "st", "arg", "actXXX" and "zombie" functions in the class. When all classes are migrated, you can remove the states.inc.php file in the FTP folder. | ||
Counters | == Counters == | ||
2 new counter classes have been added to easily handle the various counters your game might have. You also have 2 prebuild PlayerCounter: playerScore and playerScoreAux, to handle the scoring values, so you don't need to update manually the DB when setting the scores. | 2 new counter classes have been added to easily handle the various counters your game might have. You also have 2 prebuild PlayerCounter: playerScore and playerScoreAux, to handle the scoring values, so you don't need to update manually the DB when setting the scores. | ||
| Line 291: | Line 264: | ||
📌 Replace setting manually player_score/player_score_aux with new $this->playerScore and $this->playerScoreAux. Remove the notifications, or part of notifications, updating the scoreCtrl counter. | 📌 Replace setting manually player_score/player_score_aux with new $this->playerScore and $this->playerScoreAux. Remove the notifications, or part of notifications, updating the scoreCtrl counter. | ||
Use $this-> instead of self:: by default | == Use $this-> instead of self:: by default == | ||
The new project template has been updated to remove this bad practice (that may be unsupported in a future PHP version) | The new project template has been updated to remove this bad practice (that may be unsupported in a future PHP version) | ||
Revision as of 23:13, 15 October 2025
under construction
This page is only for people who started long time ago and now need to re-write older projects into more modern versions. Also if you trying to fix older game you may have to look here.
See announcement here https://studio.boardgamearena.com/forum/viewtopic.php?f=12&t=45248
📌 This symbol: information about migration, if you want to migrate an old game to the most recent ways
Structural changes
gameoptions.inc.php => gameoptions.json, gamepreferences.json
Previously, options and preferences were specified in a single gameoptions.inc.php file. Now options and preferences are 2 json files, follow Migration steps on this page https://en.doc.boardgamearena.com/Options_and_preferences:_gameoptions.json,_gamepreferences.json#Migration
<gamename>.game.php => modules/php/Game.php
<gamename>.view.php, <gamename>_<gamename>.tpl => remove
material.inc.php => optional
states.inc.php => modules/php/States
<gamename>.action.php => remove
PHP migration
Oct 2025: The migration was made from PHP7.4 to PHP8.4 new syntax and functions. Things to watch: ...
User preferences
Access to user preferences and listener: https://en.doc.boardgamearena.com/Game_interface_logic:_yourgamename.js#User_preferences
📌 If you had a custom function called setupPreferences() reading the <select> values, you can now use onGameUserPreferenceChanged instead.
If you had a copy of the user preferences on a DB table, it's not needed anymore.
Game options
New function to access the table options without needing the old global way: $this->tableOptions->get(int $optionId): int
📌 It was before done with either $this->getGameStateValue or $this->gamestate->table_globals
This new object can also return the Real-time/Turn-based information: https://en.doc.boardgamearena.com/Main_ ... exion_time
Legacy
New object to access the legacy functions, removing the need to manually decode the JSON result when getting the values.
https://en.doc.boardgamearena.com/Main_game_logic:_Game.php#Legacy_games_API
📌 Use $this->legacy->actionname instead of $this->actionnameLegacy and remove JSON decoding on getters
Globals of any type
New functions to handle any type variables instead of numerical values only
https://en.doc.boardgamearena.com/Main_game_logic:_Game.php#Use_globals
Simplify front->back calls
Introduce bgaPerformAction to replace ajaxcall and checkAction combination, with a simpler syntax:
https://en.doc.boardgamearena.com/Game_interface_logic:_yourgamename.js#Actions
📌 Replace combination of checkAction/ajaxcall by bgaPerformAction. Beware of the options (3rd param) if it was an ajaxcall without checkAction.
Autowire game actions
Simplify the action calls by removing the use of the action.php file
https://en.doc.boardgamearena.com/Main_game_logic:_Game.php#Actions_%28autowired%29
📌 Autowired actions needs to start with "act", so it's risky to change them (if you change all actions names in the states.php, game, action and JS file, Real-time players will call the old name until they refresh. So, it needs to be done in two steps with duplicates on back side, or to be deployed when there is no Realt-time table running.
When migration is done, the action.php file can be deleted.
Namespaced game class
Game classes are now namespaced (and moved to modules/php/Game.php) and can autoload other classes of the same namespace
https://en.doc.boardgamearena.com/Main_ ... er_classes
📌 The class file should be moved to modules/php/Game.php and start with this adapted part: Code: Select all
namespace Bga\Games\YourGameName;
class Game extends \Bga\GameFramework\Table All references to non-namespaced classes in this file should be defined on top of the file with "use", for example "use \BgaUserException;" as it is this non-namespaced exception is used in the zombieTurn function.
All includes with relative path will need to be updated too
IDE Helper & bga-framework.d.ts
A new _ide_helper.php file is now provided in every project dir, allowing IDE to provide syntax error highlighting for the framework functions. This file is regularly updated to match the latest framework updates.
Same with bga-framework.d.ts for those using TypeScript.
📌 Sync the files from the FTP dir to your local copy to benefit from it. Most of the IDE like Visual Studio Code should handle _ide_helper.php if you already followed https://en.doc.boardgamearena.com/Setting_up_BGA_Development_environment_using_VSCode
Strict mode set in new project template
New projects are generated using the strict mode activated (for typings). The examples in the doc have been updated to handle old framework function returning bad typings, for example (int) $this->getActivePlayerId();
📌 Make sure the typings are correct on the Game.php file, a global check of the game is recommended
📌 A global replace should work on the Game.php files
Access template elements
New functions getPlayerPanelElement(player_id) and this.getGameAreaElement()
📌 Code like dojo.place(html, player_board_${player.id}); would be replaced by this.getGameAreaElement().insertAdjacentHTML('beforeend', html);
Optional files: action/view/template/material
Action/view/template/material files are now optional and are not generated anymore on a new project. The new project templates demonstrate how to work without them.
📌 See Autowiring to delete the action file. The template should be built on the JS side to remove the view/template files, so it can be complicated for old projects using them intensively. It would look like this: Code: Select all
this.getGameAreaElement().insertAdjacentHTML('beforeend', `${_('My translated text')}`);
Easier notification setup
Notifications can now be automatically scanned and called without needing to register them one by one. They'll handle Promises, so they end synchronously when the Promise resolves.
https://en.doc.boardgamearena.com/Game_interface_logic:_yourgamename.js#Notifications
A wait function has been added to return a Promise when a delay is passed (compatible with fast-replay mode)
A new utility function has been added to support Promises for old Dojo animations
https://en.doc.boardgamearena.com/Game_interface_logic:_yourgamename.js#Animation_Callbacks
📌 Dojo.subscribe calls in setupNotifications must be removed if bgaSetupPromiseNotifications is used. Notif_ function should be async and return a Promise, make sure they wait for the expected amount of time if the sync setup was using a numerical duration
If you used Dojo animation, make them Promise compatible with "await this.bgaPlayDojoAnimation(dojoAnim);"
Status bar manipulation
Function to change the title from the JS https://en.doc.boardgamearena.com/Game_interface_logic:_yourgamename.js#Title_bar
📌 Replace direct title div manipulation with this.statusBar.setTitle(title: string, args?: object), and benefit from replacement of ${actplayer}/${you}/... (see example in the link above).
This also includes a new function to create action buttons, that are more screen-reader compatible than the previous version. The new button parameters also allow you to set a confirm popin or an autoclick for confirmation buttons
📌 Replace this.addActionButton by this.statusBar.addActionButton. Notice the parameters have changed, so they need to be adapted too! Remove manual setActionTimer or manual confirm with the new parameters.
Notification decorators
New notify function that handles decorators, reducing the duplicate code on notification args.
https://en.doc.boardgamearena.com/Main_game_logic:_Game.php#Notification_decorators
📌 Replace notifyAllPlayers by notify->all and notifyPlayer by notify->player
Forbid access to global BGA variables and direct DB access on action/view files
A new getCurrentPlayerId() function has been added to those action/view classes for easier migration
📌 Replace $g_user->get_id() by $this-> getCurrentPlayerId()[
Replace DB calls by $this->game->myFunctionCallingTheDB()
Instant cssPref on user preferences
A reload is not needed anymore to apply cssPref on a user preference change.
📌 Remove forceReload: true if it was only set to update the cssPref. The player will appreciate to not reload the whole page!
Dojo usage
Dojo usage has been reduced to minimum in the new project template and the doc, as native JS is now able to do almost the same things, with better performance and more knowledge for newcomers of the native (vanilla) JS.
📌 Replace dojo by vanilla JS where possible
Skip a state
When you skip a state on PHP side (directly move to another state on the "st" function), the JS is still notified that the skipped state is activated, then it activates the next state just after, but you may see the skipped state buttons being created then deleted.
You can set up the _no_notify flag so that the JS notification of this skipped state is not sent, and from the JS side it considers the state was never loaded. For example, if you have a confirm step and a user preference allows to disable it, the user doesn't need to see the Confirm buttons showing then removed just after.
📌 Add _no_notify in the args when a state is skipped
Sound loading
New functions load/play have been added for the sounds:
https://en.doc.boardgamearena.com/Game_interface_logic:_yourgamename.js#Sounds
📌 Replace template loading of sounds and global function playSound
Useless getGameName function on Game PHP file
The getGameName function is now useless in the Game PHP file and can be deleted
📌 Delete the getGameName function in the Game PHP file.
GameStateBuilder
This new class helps you build the state machine, allowing auto-completion, and avoid typo errors on state types. Complete example: 📌 https://en.doc.boardgamearena.com/Your_game_state_machine:_states.inc.php
States 1 and 99, that must not be changed, are now optional.
📌 Replace the array definition by GameStateBuilder use. You can remove the declaration of states 1 and 99.
Note: it's only useful if you don't migrate to State classes described later on.
bgaFormatText
This function, if defined, will allow you to insert HTML in the logs without overriding format_string_recursive. Example: 📌https://en.doc.boardgamearena.com/BGA_Studio_Cookbook#Define_this.bgaFormatText%28%29_method
📌 Replace the override of format_string_recursive by bgaFormatText (the last line will change)
Future support of dark mode
BGA doesn't support dark mode yet. To have some games compatible when we do, we added a theme data tag you can use as described here:
Framework function for automata player panel
A new framework function to add a player panel for your game automatas https://en.doc.boardgamearena.com/Game_interface_logic:_yourgamename.js#Adding_a_player_panel_for_an_automata
📌 Replace manually created automata player panel with this new function
New JS libraries
We will provide new libraries to help you design your games, especially for components that you will find on numerous games. The first available libraries are:
[bga-animations https://en.doc.boardgamearena.com/BgaAnimations] : a JS component to make animations, compatible with scaled or rotated containers.
bga-cards : a JS component to handle cards.
bga-dice : a JS component to handle dice.
bga-autofit : a JS component to make text fit on a fixed size div.
bga-score-sheet : a JS component to help you display an animated score sheet at the end of the game.
📌 Try them, and hopefully use them instead of the very old components! Each lib has a demo in the beginning of the wiki page to show what it can do.
Notification args consistency
Previously, when you sent an arg that was transformed by format_string_recursive or bgaFormatText, the args object was mutated and you got the transformed value in the notif_ handler.
The solution was to send the values in 2 different names like this: Code: Select all
[ 'roundNumber' => $roundNumber, // number, to update the round counter 'round_number' => $roundNumber, // number that will be transformed to string by bgaFormatText, when shown in bold in the logs ]
📌 Do not duplicate the value, as the notif_ handler will now get unmutated args
Updated Zombie Mode documentation and recommendations
We now recommend making the zombie player playing randomly, instead of passing as a default. A new "Zombie Mode level" field has been added to the Game Metadata Manager, to indicated the Zombie Mode you implemented in your game.
https://en.doc.boardgamearena.com/Zombie_Mode
State classes
There is now a way to describe each game state in a State class, that will handle all logic and description of the state. It helps splitting the code into multiple files, instead of one big Game.php file.
https://en.doc.boardgamearena.com/State_classes:_State_directory
📌 Create a State class for each state of the game (except 1 and 99 if they are still described in states.inc.php), move the state definition in it, and adapt the "st", "arg", "actXXX" and "zombie" functions in the class. When all classes are migrated, you can remove the states.inc.php file in the FTP folder.
Counters
2 new counter classes have been added to easily handle the various counters your game might have. You also have 2 prebuild PlayerCounter: playerScore and playerScoreAux, to handle the scoring values, so you don't need to update manually the DB when setting the scores.
https://en.doc.boardgamearena.com/PlayerCounter_and_TableCounter
📌 Replace setting manually player_score/player_score_aux with new $this->playerScore and $this->playerScoreAux. Remove the notifications, or part of notifications, updating the scoreCtrl counter.
Use $this-> instead of self:: by default
The new project template has been updated to remove this bad practice (that may be unsupported in a future PHP version)