Coding Games and Programming Challenges to Code Better
Send your feedback or ask for help here!
Created by @Unsupervision,validated by @darkhorse64,@Anonymous_7 and @JustForFun123.
If you have any issues, feel free to ping them.
1 Like
Hello. The game seems fantastic, however i don’t get the motivation for the last stage of the game, with a randomization that cut the size of up to half. (down to 16…32 right from 32x32 from the previous phase). Only the first phase and the last phase really have bots, so the 32x32 stage is just teased briefly before vanishing. But for me that’s the most interesting one. Stage 4 should be bigger, not smaller. There is already randomization of the targets, so the size modification don’t bring much on the strategic side, and even kinda butcher it i believe. I would argue that stage 3 should be the last one, and please get rid of stage 4.
5 Likes
You’re right. It seems suboptimal to shrink the game for the last league.
4 Likes
In some (relatively rare) games the rewards are too close to the players, with none in the contested central area, like this one :
Coding Games and Programming Challenges to Code Better (example game 1)
Coding Games and Programming Challenges to Code Better (example game 2)
Coding Games and Programming Challenges to Code Better (example game 3)
The top of the grid is connected to the bottom of the grid but there are walls on the right and left, is that okay?
Hello all!
Thank you for the feedback. I’ve decided to do what you and others have suggested which is to get rid of the variable grid size on the final league. Unfortunately the constraints of the codingame platform don’t allow for a grid size larger than 32x32 due to the amount of data that has to be passed to the viewer each frame, so instead I simply increased the number of goal cells in the final league while keeping the grid size at 32x32.
Thanks again for playing and hopefully this makes the final league more enjoyable!