Skip to content

Commit 4484545

Browse files
committed
Merge remote-tracking branch 'origin/master'
2 parents 6c0f9f1 + 33fe2d1 commit 4484545

File tree

3 files changed

+4
-6
lines changed

3 files changed

+4
-6
lines changed

playground/core-concepts/core-4-configuration.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -23,12 +23,10 @@ This is the main configuration file. It must be located in the `config` folder a
2323

2424
Example of `config.ini`.
2525
```
26-
title=Game Example
2726
type=multi
2827
min_players=2
2928
max_players=2
3029
```
31-
- **title**: The title of the game, used internally by the platform.
3230
- **type**: The type of the game, must be either `multi`, `solo` or `opti`.
3331
- **min_players**: The minimum number of players to play the game. Must be 1 for Solo and Optimization games, up to 8 for Multiplayer games.
3432
- **max_players**: The maximum number of players to play the game. Must be 1 for Solo and Optimization games, up to 8 for Multiplayer games. Of course, you cannot have max_players < min_players.
@@ -66,9 +64,9 @@ You have the possibility to create several levels (also named leagues). A new le
6664

6765
There is a difference between multiplayer and solo game levels:
6866
- In a **multiplayer** game, your levels become leagues. The players will need to beat your Boss in the leaderboard to access the next league.
69-
- In a **solo** game, they are several questions. Players can switch between the different questions as they wish to.
67+
- In a **solo** game, there can only be on level.
7068

71-
To create new levels, you need to make new folders named `level<number>` in the `config` directory. Their `<number>` must be positive and will be used to display your questions/leagues in the right order. Each level can be configured like the `config` directory, which allow you to have different statements, stubs, titles, etc.
69+
To create multiple leagues, you need to make new folders named `level<number>` in the `config` directory. Their `<number>` must be positive and will be used to display your leagues in the right order. Each level can be configured like the `config` directory, which allow you to have different statements, stubs, etc.
7270

7371
If you want to use the same configuration in several levels, you do not need to copy your files in every directory. If a file is missing in a `level` folder, it will inherit from `config` automatically when uploading your game.
7472

playground/getting-started/tutorial-2-multiplayer.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ Here's the file hierarchy for the project Tic-tac-toe:
5454
│ └── log4j2.properties
5555
```
5656

57-
- **./config:** contains the settings such as the game title, statement, number of players, etc.
57+
- **./config:** contains settings such as the statement, number of players, etc.
5858
- **./src/main/java:** source code of the game itself
5959
- **./src/main/resources:** graphical assets and configuration of the view
6060
- **./src/test/java:** classes used for local development (AI codes to test your game)

playground/getting-started/tutorial-3-solo.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ Here's the file hierarchy for the project Fishy Adventures:
6565
│ └── log4j2.properties
6666
```
6767

68-
- **./config:** contains the settings such as the game title, statement, test cases, number of players, etc.
68+
- **./config:** contains settings such as the statement, test cases, number of players, etc.
6969
- **./src/main/java:** source code of the game itself
7070
- **./src/main/resources:** graphical assets and configuration of the view
7171
- **./src/test/java:** classes used for local development (AI codes to test your game)

0 commit comments

Comments
 (0)