This is a documentation for Board Game Arena: play board games online !
الفرق بين المراجعتين لصفحة: «Studio file reference»
Victoria la (نقاش | مساهمات) |
|||
(٧ مراجعات متوسطة بواسطة مستخدمين اثنين آخرين غير معروضة) | |||
سطر ١: | سطر ١: | ||
This is a quick reference for the files used to implement a game. For more information, | This is a quick reference for the files used to implement a game. For more information, follow the wiki links. | ||
=== | === img/ === | ||
This directory contains the images for your game (the game art). | This directory contains the images for your game (the game art). | ||
See [[Game art: img directory]] | |||
=== gameinfos.inc.php === | === gameinfos.inc.php === | ||
In this file you describe the meta-information for your game: game name, publisher name, number of player, game categories, etc... | In this file you describe the meta-information for your game: game name, publisher name, number of player, game categories, etc... | ||
See [[Game_meta-information:_gameinfos.inc.php]]. | |||
=== dbmodel.sql === | === dbmodel.sql === | ||
File for creating specific database tables that you will need to persist data during the game (for example a table for cards). | File for creating specific database tables that you will need to persist data during the game (for example a table for cards). | ||
See [[Game database model: dbmodel.sql]] | |||
=== gameoptions.inc.php === | === gameoptions.inc.php === | ||
File for describing your game options ( | File for describing your game options (or game variants). | ||
See [[Game options and preferences: gameoptions.inc.php]]. | |||
=== <gamename>.action.php === | === <gamename>.action.php === | ||
File used to describe methods that can be called from the client interface through javascript, get parameters and call the appropriate game functions. | File used to describe methods that can be called from the client interface through javascript, get parameters and call the appropriate game functions. | ||
See [[Players actions: yourgamename.action.php]]. | |||
=== <gamename>.css === | === <gamename>.css === | ||
CSS styles specific to your game. | CSS styles specific to your game. | ||
See [[Game interface stylesheet: yourgamename.css]]. | |||
=== <gamename>.game.php === | === <gamename>.game.php === | ||
This is the main file for your game logic. Here you initialize the game, persist data, implement the rules and notify changes to the client interface. | This is the main file for your game logic. Here you initialize the game, persist data, implement the rules and notify changes to the client interface. | ||
See [[Main game logic: yourgamename.game.php]]. | |||
=== <gamename>.js === | === <gamename>.js === | ||
سطر ٣٥: | سطر ٤٩: | ||
* which actions on the page will generate calls to the server | * which actions on the page will generate calls to the server | ||
* what happens when you get a notification for change from the server and how it will show in the browser. | * what happens when you get a notification for change from the server and how it will show in the browser. | ||
See [[Game interface logic: yourgamename.js]]. | |||
=== <gamename>.view.php and <gamename>_<gamename>.tpl === | === <gamename>.view.php and <gamename>_<gamename>.tpl === | ||
Files used to set up the page layout ('view') for the game. | Files used to set up the page layout ('view') for the game. | ||
See [[Game layout: view and template: yourgamename.view.php and yourgamename yourgamename.tpl]]. | |||
=== material.inc.php === | === material.inc.php === | ||
File used to describe all the game material (cards with their description, dices, tokens...). You can also use it to define game constants. | File used to describe all the game material (cards with their description, dices, tokens...). You can also use it to define game constants. | ||
See [[Game material description: material.inc.php]]. | |||
=== states.inc.php === | === states.inc.php === | ||
This file describes the game states machine of your game (all the game states properties, and the transitions to get from one state to another). | This file describes the game states machine of your game (all the game states properties, and the transitions to get from one state to another). | ||
See [[Your game state machine: states.inc.php]]. | |||
=== stats.inc.php === | === stats.inc.php === | ||
File used to list statistics that you want to update during the game to be presented to players at the end of the game. | File used to list statistics that you want to update during the game to be presented to players at the end of the game. | ||
See [[Game statistics: stats.inc.php]]. | |||
=== version.php === | |||
Don't edit this file. It is used internally by the build system. | |||
=== modules/ === | |||
Modules directory can contain additional php files which can be included in main game.php via include or require. This directory is checked in version control. | |||
=== misc/ === | |||
Directory containing files you would like to keep with project but not needed on production server. This directory is checked in version control. Total limit is 1 Mb for this directory. | |||
=== <other files> === | |||
You can use other files but they won't be checked in source control and published in production. That includes any additional .js or .php files. If you need them use modules/ directory. |
المراجعة الحالية بتاريخ ١٤:٤٥، ٦ يناير ٢٠١٨
This is a quick reference for the files used to implement a game. For more information, follow the wiki links.
img/
This directory contains the images for your game (the game art).
gameinfos.inc.php
In this file you describe the meta-information for your game: game name, publisher name, number of player, game categories, etc...
See Game_meta-information:_gameinfos.inc.php.
dbmodel.sql
File for creating specific database tables that you will need to persist data during the game (for example a table for cards).
See Game database model: dbmodel.sql
gameoptions.inc.php
File for describing your game options (or game variants).
See Game options and preferences: gameoptions.inc.php.
<gamename>.action.php
File used to describe methods that can be called from the client interface through javascript, get parameters and call the appropriate game functions.
See Players actions: yourgamename.action.php.
<gamename>.css
CSS styles specific to your game.
See Game interface stylesheet: yourgamename.css.
<gamename>.game.php
This is the main file for your game logic. Here you initialize the game, persist data, implement the rules and notify changes to the client interface.
See Main game logic: yourgamename.game.php.
<gamename>.js
This is the main file for your game interface. Here you will define:
- which actions on the page will generate calls to the server
- what happens when you get a notification for change from the server and how it will show in the browser.
See Game interface logic: yourgamename.js.
<gamename>.view.php and <gamename>_<gamename>.tpl
Files used to set up the page layout ('view') for the game.
See Game layout: view and template: yourgamename.view.php and yourgamename yourgamename.tpl.
material.inc.php
File used to describe all the game material (cards with their description, dices, tokens...). You can also use it to define game constants.
See Game material description: material.inc.php.
states.inc.php
This file describes the game states machine of your game (all the game states properties, and the transitions to get from one state to another).
See Your game state machine: states.inc.php.
stats.inc.php
File used to list statistics that you want to update during the game to be presented to players at the end of the game.
See Game statistics: stats.inc.php.
version.php
Don't edit this file. It is used internally by the build system.
modules/
Modules directory can contain additional php files which can be included in main game.php via include or require. This directory is checked in version control.
misc/
Directory containing files you would like to keep with project but not needed on production server. This directory is checked in version control. Total limit is 1 Mb for this directory.
<other files>
You can use other files but they won't be checked in source control and published in production. That includes any additional .js or .php files. If you need them use modules/ directory.