Domain Expansion

Rate this contribution

+14

Work In Progress

The creator is still working on the contribution. Feel free to add remarks and suggestions to improve the contribution before the approval process!

Comments

41 Comments

CodinBot Unnamed CodinGamer

about 13 hours ago

I hope you received enough feedback from the community to improve your contribution. Once you have made the necessary updates, publish your contribution!

Mister_Dinero Unnamed CodinGamer

2 days ago

je suis alluciner par se travailler

Deliner_cctweaked Unnamed CodinGamer

3 days ago

Good code but you could add the count to each player of how many moves are left until the finish.

darkhorse64 Unnamed CodinGamer

3 days ago

If this information can be really computed (which I sincerely doubt), it is anyway irrelevant for writing a bot.

darkhorse64 Unnamed CodinGamer

4 days ago

Almost there but the protocol still needs some improvements. In the current version, there is no way to know at startup if you are the first or second player. You have to wait until the first time in the game loop to have this information. I suggest the following changes: width, height, id (0 or 1) in the first input line. The next two input lines do not change but are interpreted as first and second player initial positions.

Mortis_666 Unnamed CodinGamer

4 days ago

I can easily add that, but don't mind if I ask, what can a player possibly do with that information?

MSmits Unnamed CodinGamer

6 days ago

Finished my bot: - MCTS with eval instead of random sim. - Uses voronoi eval - MCTS solver to solve the game - a little over 50k Rollouts (eval expanded node only) An example: https://www.codingame.com/... Games are relatively long. I don't think the game is too simple for CG constraints. This would be a hard game to solve, which is good. I am not sure about player 1 advantage. It could be large... or not at all. Need more bots!

MSmits Unnamed CodinGamer

6 days ago

Did a couple of games. My bot is very deterministic with only 1 param (exploration), I can vary to get different games. Both players win from time to time, but it's still poor statistics. I also found a draw: https://www.codingame.com/...

MSmits Unnamed CodinGamer

8 days ago

Great game so far. I hope it's an interesting bot game at high levels of play as well. I'll spend some time making a good bot so we'll see how interesting it is in high level play. I'll have fun figuring that out either way, so thanks for this. Small nitpick: cout << "0 0 U" << endl; This is now an illegal move, even on turn 1.

Mortis_666 Unnamed CodinGamer

8 days ago

It's great to know that you are enjoying it! It's my pleasure to bring fun and unique games to top players like yourself. I'm also intrigued to see how a good game will play out. Regarding on the illegal move, it might not be stated in the statement, but the border is now considered as true wall, and it's considered illegal to build on top of it. I have another comment dedicated to update of new rules that I have yet to put in the statement, hope this helps.

Mortis_666 Unnamed CodinGamer

8 days ago

Comment to keep track of new changes - Borders are now considered as true walls, hence it's not buildable - Illegal move will now lose you the game instead of having the referee to fix it - Some changes with the input format, statement is now updated.

darkhorse64 Unnamed CodinGamer

11 days ago

Regarding borders and walls, it would be more logical if borders were considered as true walls ie not buildable

darkhorse64 Unnamed CodinGamer

11 days ago

Regarding the inputs, why not describing walls the same way as outputs, ie cell + direction ? I feel it's much more consistent

darkhorse64 Unnamed CodinGamer

11 days ago

Regarding expert rules, the usual behaviour on most CG multis is that any invalid input like going too far or building on an existing wall should result in a immediate loss with a corresponding error message rather than trying to fix the input.

Mortis_666 Unnamed CodinGamer

11 days ago

I'm aware of that, it's just that while implementing I realise fixing the input would be much easier than throwing an error resulting in some ugly nested try-catch 😅. I will change it if needed.

darkhorse64 Unnamed CodinGamer

11 days ago

I just stumbled on your game. I like it. Is it an original design ? You should consider adding numbers for rows and columns on the left and bottom of your grid.

Mortis_666 Unnamed CodinGamer

11 days ago

Thanks. Unfortunately, this game is not my original idea, I learned it from a TV show and figured it would be perfect for codingame. I would definitely consider adding the coordinates.

5DN1L Unnamed CodinGamer

25 days ago

Rules * Suggest to change "happens in" to "is played on". * Suggest to change "sovereign" to "token" (all instances). * Where is the cell with the coordinates (0, 0)? Is it the top-left corner of the board, or the bottom-left one? * It sounds like each move must be in a single direction. The directions are not really necessary, because only the destination coordinates are required to be output. Suggest to change the *FIRST* sentence of "Movements" to: During a player's turn, the player may either keep their token in its current location, or move it to another cell up to 3 steps away (measured in Manhattan distance). * Suggest to change "a cell with" to "a cell occupied by". * Please change "map" to "board" (twice). * It sounds like a player can only build a wall after moving their token. Suggest to change the *FIRST* sentence of "Wall building" to: After completing their move – or choosing not to move – the player must build a wall on any side of their token: <const>U</const>p, <const>D</const>own, <const>L</const>eft, or <const>R</const>ight. * Please change "of both parties" to "player's token". * Please change "another wall" to "an existing wall". * Suggest to change "see what will happen" to "learn what happens". * Please change "attempted" to "attempt". * Suggest to change "do it" to "do so". * Suggest to change "one player can never" to "neither player can". * Please change "reach to" to "reach". * What does this mean? "Note that the rule with player blocking a cell by standing on it does not count in this condition." Say, if a player builds four walls to block off all the sides where their token is located, then it should still be a "game over" because neither player can reach the other player…? * Please add the sections of Victory Conditions and Defeat Conditions. Please check out the HTML source of any bot programming games for an example. Expert Rules * Please change "another" to "an". * Please change "wall build" to "wall building". * Please change "there's an empty space" to "an available side is found". Example * Is this section required, or can it be removed? Note * Is this section required, or can it be removed? Initial input * Please add "Two space-separated integers" before "width". Input * Line 1: Please add "2 space-separated integers". * Line 1: Please change "your position" to "the position of your token". * Line 2: Please add "2 space-separated integers". * Line 2: Please change "opponent's position" to "the position of your opponent's token". * Line 3: Please add "An integer". * Next numWalls lines: • Please add "4 space-separated integers". • Please change "both" to "the". • Please change "on top or on the left" to "above or to the left". Output * Please change "the cell you wish to go to" to "the position of the cell you wish to move your token to (or its current position if not moving)". * Please delete "after moving to x y" because a token may not necessarily move. Thanks.

Mortis_666 Unnamed CodinGamer

25 days ago

Helpful corrections as always, thanks. > Suggest to change "sovereign" to "token" (all instances). I guess I will put it as token before I find a suitable sprite. > The directions are not really necessary I emphasize on the steps because of walls, there will be cases where the cell seem to be within 3-step Manhattan distance yet still unreachable due to a wall blocking it. > What does this mean? https://imgur.com/... This is just an extreme example, but in blue's POV, even though blue seems to be completely trapped, due to the "body block" rule, when accounting for the winning conditions, both players should be strictly isolated by walls, hence what I'm trying to express there, "body block" rule does not apply, so in that case blue still gets a turn and is forced to commit suicide. So, how could I've phrased it better? > Say, if a player builds four walls to block off all the sides where their token is located, then it should still be a "game over" because neither player can reach the other player…? Precisely > Please delete "after moving to x y" because a token may not necessarily move. I just want to emphasize on the fact that the wall build action is AFTER the move, but I guess the statement before already made it clear enough.

field3 Unnamed CodinGamer

29 days ago

This error is occurring. Shouldn't there be a time limit? The game has crashed. Please contact the author and enclose the following error: java.lang.RuntimeException: Total game duration too long (>30000ms) at com.codingame.gameengine.core.GameManager.addTurnTime(GameManager.java:582) at com.codingame.gameengine.core.GameManager.execute(GameManager.java:192) at com.codingame.gameengine.core.GameManager.execute(GameManager.java:226) at com.codingame.gameengine.core.AbstractPlayer.execute(AbstractPlayer.java:101) at com.codingame.game.Referee.gameTurn(Referee.kt:60) at com.codingame.gameengine.core.GameManager.start(GameManager.java:122) at com.codingame.gameengine.core.RefereeMain.start(RefereeMain.java:67) at com.codingame.gameengine.core.RefereeMain.main(RefereeMain.java:50)

Mortis_666 Unnamed CodinGamer

28 days ago

Thanks, I'm not aware of the total game duration limit.

ABOUT US CAREERS PRIVACY FAQ BLOG

The #1 tech hiring platform

SCREENING INTERVIEWING