Clash of Bits : explode another day

Rate this contribution

+229

Make the contribution public (lvl 20+)

The contribution was not moderated in time so the system automatically rejected it.

Comments

197 Comments

CodinBot Unnamed CodinGamer

about 7 months ago

Hey CodinGamer! Your contribution has unfortunately not been moderated on time and will temporarily be removed from the system... But no worries! You can republish it anytime to give it another chance! :)

win1702 Unnamed CodinGamer

about 7 months ago

that's okay

anochastic Unnamed CodinGamer

about 8 months ago

The input need a rework.They are near impossible to use without buffering. And they seems very inefficient : which might be a problem if the bot timing takes into account some of its reading the input. for (int i = 0; i < botCount; i++) {..} This first loop is okay, we simply read the state of the game. for (int i = 0; i < allyBotAlive; i++) {..} for (int j = 0; j < botCount; j++) {..} This quadratic visit of the game state is not okay. Also all the information it could give should already be given by the first visit of the game state. For example if the first loop gave an actual position for the bots, all the information would already be there to be used. If you need to keep it, make at least clearer. For example "i" would be a loop on your drones and would enable you to get the associated ID, and "j" on the opponent's drone, and enable you to get his drone ID. As it is, it's really hard to figure out how to extract the useful information out of it. String action = in.next(); // action executed by the bot last turn String targets = in.next(); // list of the targets id targeted by the bot last turn ("id1;id2;id3...") if the bot is a bot, else -1 (the target for IDLE is the bot itself) Strings tends to be inefficient, and might also be a bother to compare in some language, i suppose /!\ALWAYS 0 FOR THE FIRST LEAGUE/!\ Why ? The first league is just there to bundle together weak bots. Its awfully hard, to change the rules to make the first league "easier" on the programmers side. In most cases it's way better to have the exact same rules/input in all leagues. Here the code reading the input of the first league is the same for all league (which is good), but the information you give is butchered for the lower league ... ?? Why. I mean, if they don't want to use this information, they won't. You don't need to artificially make it hard on the lower league, with nothing to make up for the handicap.

anochastic Unnamed CodinGamer

about 8 months ago

Here is a bit more detail about why i believe randomness and hidden state might not be the best way to start collecting feed-back. i don't know how other people feel about it, but i for one would be more confident into investing a bit of time in a bot, if i had full knowledge of the world. I imagine a lot of bot writing codinggame players are in the habit of re-implementing the world from the description of the rule, and then testing that their world model actually match the raw data. Much harder to do, if the engine hides the raw world state data (either voluntarily or through randomness). The more simple the game, the more easy it is to quickly write a bot that does stuff. In other word, i feel like world-engine transparency is really important, especially in the early testing phase. You could always put back randomness/hiden-state after you already have a few people engaged with your engine, if they agree to it.