Merge branch '2StepsFr0mHell'

Author: Julien

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

@@ -37,7 +37,7 @@ max_players=2
 
 You may add to the config/ folder a text file named `stub.txt`. If the contents of this file is a syntaxically valid **CodinGame Stub Generator** input, the IDE will be prefilled with input/output code.
 
-See [Stub Generator Syntax](https://github.com/CodinGame/codingame-game-engine/blob/master/stubGeneratorSyntax.md) for details.
+See [Stub Generator Syntax](https://www.codingame.com/playgrounds/40701/contribute---help/stub-generator-syntax) for details.
 
 ### Loading assets <a name="loading-assets"></a>
 
@@ -120,6 +120,8 @@ Within the `.tpl` file, you may place special comment blocks to indicate whether
 
 Optionally, you can tranlate your statements in French using `statement_fr.html` files.
 
+Learn more about how to write a statement for sdk games in the [CodinGame contribution documentation](https://www.codingame.com/playgrounds/40701/contribute---help/writing-the-statement#game-statement)
+
 #### Example
 
 This `statement_en.html.tpl`:

playground/getting-started/tutorial-1-introduction.md

@@ -16,10 +16,11 @@ The entry point of the game is the class `SoloGameManager` or `MultiplayerGameMa
 
 ![Main classes](resources/schema-sdk.svg)
 
-# Resources
+# Useful Resources
 
 - [Javadoc](https://codingame.github.io/codingame-game-engine/)
 - [SDK source](https://github.com/CodinGame/codingame-game-engine)
 - [Free to use graphical assets](https://github.com/CodinGame/codingame-sdk-assets)
 - [Game Skeleton](https://github.com/CodinGame/game-skeleton)
-- [Contribute Page](https://www.codingame.com/contribute/)
+- [Contribute Page](https://www.codingame.com/contribute/)
+- [Contribution Documentation](https://www.codingame.com/playgrounds/40701/contribute---help)

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

@@ -77,7 +77,7 @@ Use this page to see the rendering of your game. It also allows you to export a
 
 ## Deploy on codingame
 
-Go to [www.codingame.com](https://www.codingame.com), then click on **Contribute** > **Create a new puzzle** > **Multiplayer Game** (This section is not available to anyone yet, please contact us if you want the access).
+Go to [www.codingame.com](https://www.codingame.com), then click on **Contribute** > **Create** > **Multiplayer Game**.
 
 Then, import on CodinGame the game you have exported during the previous step. The game will be compiled on our servers and a preview link will appear if the compilation succeeded and if the configuration is correct.
 

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

@@ -80,7 +80,7 @@ Use this page to see the rendering of your game. It also allows you to export a
 
 ## Deploy on codingame
 
-Go to [www.codingame.com](https://www.codingame.com), then click on **Contribute** > **Create a new puzzle** > **Solo Game** (This section is not available to anyone yet, please contact us if you want the access).
+Go to [www.codingame.com](https://www.codingame.com), then click on **Contribute** > **Create** > **Solo Game**.
 
 Then, import on CodinGame the game you have exported during the previous step. The game will be compiled on our servers and a preview link will appear if the compilation succeeded and if the configuration is correct.
 

playground/misc/misc-1-guidelines.md

@@ -1,50 +1 @@
-# Guidelines
-
-When creating your game, we suggest you follow these guidelines in order to improve both its performance and players experience.
-
-## Technical Guidelines
-
-- The game should be noob friendly. Can make a workable AI with a bunch of ifs. 
-- If it is a game with limited output options per turn, send those options in the protocol (e.g. the first player of chess has 20 possible actions).
-- Viewer should be enough to understand most of the rules.
-- Gameplay based around rounds/turns. Only perform checks (collision, presence, etc.) at the end of a turn.
-- End player’s program when it outputs an unrecognised command. Continue player’s program when it outputs a recognised but invalid command and add error message to summary.
-- Stop game early if players aren’t doing anything or are otherwise stalemated.
-- Stop game early if the ranking is decided whatever the players may do.
-- Always minify png and jpg assets.
-- The Referee must not crash, make sure all possible exceptions are caught, especially during the parsing of a Player’s actions, where most errors occur.
-- Minimum font size: 36px.
-
-## Soft Limits
-
-The following limits will make your game run faster, but they are not strict limitations.
-
-- Statement length: less than 6k characters
-- Total entity creations: less than 200.
-- Max total time alloted to the players: 25s.
-
-## Protocol:
-
-The following lines will help most players to get into your game. Try to simplify things when possible. 
-
-- Two loops max for input.
-- Variables to read per loop: less than 10.
-- Stub generator must not exceed: 45 lines of Java.
-- If the player is given an ID, it is always 0.
-
-## Graphics:
-
-- Privilege the use of Sprites over Shapes (Rectangle, Circle, etc.)
-- Use less than 2Mb total for assets.
-
-## Games with leagues
-
-- Stubs should, if possible, be the same for every league.
-- If a game needs at least 1 data structure to make an AI that doesn’t crash, it needs an easier league.
-
-## Rules
-
-When contributing on CodinGame, you must accept and apply these rules:
-
-- Your game must not contain any kind of inappropriate content.
-- Write a stub generator. The documentation can be found in the [CodinGame SDK repository](https://github.com/CodinGame/codingame-game-engine/blob/master/stubGeneratorSyntax.md). Any non-explicit variable must be explained with a comment.
+Guidelines and best practices for coding games can be found in the documentation ["Contributing to CodinGame"](https://www.codingame.com/playgrounds/40701/contribute---help/coding-games#guidelines)