Log Book: Sprint Release

Yay! Maybe I will get friends to click on those links now!

2015-11-12 Sprint Release

  • Update “Contribution”: Pending contributions are displayed in a dedicated page where CodinGamers can comment contributions and vote for well made and interesting ones. You can also track your previous contributions from this page.
  • Update “Puzzle”: Statements are currently reworked. Easy, Medium, Optimization and some Hard puzzles have been updated.

  • Fix “Default language templates”: A few auto generated code were not compiling for some clashes or puzzles.
  • Fix “Perl packages”: Moose is now installed, as it was advertised on the FAQ.
  • Fix “Clash of Code score computation”: When the time was up, the score was computed before one had the time to decide to push its current code or their previous one.
  • Fix “Avatar”: It was not possible to create or update your avatar when registering to a contest.
  • Fix “Email accepted”: Email with more than 4 characters in their top level domain are now accepted on the platform.

  • Fix minor bugs

  • TOP SECRET STUFF :blush:
2 Likes

A monospace font for the Input/Output of a clash contribution would be awesome.

2 Likes

There is a bug ticket created for that, and it also suggests to add a scrollbar when needed :).

1 Like

2015-11-24 Sprint Release


  • Update “Contribution”: Use of a monospace font for Input/Output of clash contributions.
  • Update “Puzzle”: Statements are currently reworked. More than 50 statements have been reworked as of now.
  • Update “Contest registration”: A new registration page will be available after Code vs Zombies.

  • Fix “Contribution”: Comments date were not correct.
  • Fix “Contribution”: IDE tests were not correctly loaded when testing a contribution.
  • Fix “Find friends”: It was impossible to use the tool if one of your friend had a too long email or name.
  • Fix “Achievements”: Having between 49% and 50% on a puzzle was not giving the 50% achievement related to the game, while displaying 50%.

  • Fix minor bugs

  • BIG STUFF INCOMING VERY SOON :blush:
  • TOP SECRET STUFF :blush:
3 Likes

The new IDE is awesome!!!

Very good job guys!

3 Likes

2015-12-16 Sprint Release


  • Update “IDE”: The fresh new IDE is now live! Tell us what you think!

  • Fix “Contribution”: When following a codingamer from the contribution page, it does not open the contribution in addition to the action of following that codingamer.
  • Fix “Code vs Zombies”: There were issues with the viewer on old Chrome versions, preventing us from releasing the contest as a game. We reworked tests and validators a bit to make hardcoding more difficult and to prevent being able to win all points on a single test.

  • Fix minor bugs

  • TOP SECRET STUFF :blush:
1 Like

Good job for the new IDE. But is it possible to add a feature to change background color bescause with all in “White them” I think you want us to became blind ^^
For me, just a darker theme and it’s perfect

2 Likes

+1 for night coders

1 Like

Like I said in the PM I sent you, I think some details of the new IDE shouldn’t be as white as it is now, to make it look more condingame-esque, with touch of black and yellow maybe. Now it’s too much white, and the rest of the site isn’t, so I doesn’t fit well as of now.

Apart from that, I love the new features, especially the submit that doesn’t change the page, love it!

1 Like

Being able to load a game into IDE from “last battles” in multiplayer games is amazing too.

1 Like

Yup, it trully is. The only problem with that is that it doesn’t overwrite the IDE manual parameters with the ones from the fight.

Apart from that, that the feature we’ve all been waiting for a long time :slight_smile: Gz CG team.

@Neumann, issue reported. It works fine when you parameters are in ‘auto’ mode.

As a work around, you can go in your settings in the IDE to activate the expert mode. Then in the option tab that appear only in expert mode, select the ‘auto’ mode (that’s the default value though).
Then load a game from last battle and in the option tab select the ‘manual’ mode. Hence, parameters are overwrite and you can replay them with the players you want :slight_smile:

Nope, the one you are surely expecting the most should come next week :stuck_out_tongue: (if it’s ready before chirstmas, otherwise it will be postponed to next year).

@yohannjardin Yup it works, thanks.

@MaximeC Ohh the teasing !
Let me guess …
“Retrieve code from Arena” button ?
Or better, a full history of pushed AIs with score/stats of each one.
I may be dreaming about the last one :stuck_out_tongue:
Anyhow, I’ll be looking forward this :slight_smile:

2015-12-16 Sprint Release


  • New feature “History”: You can now access your previous code on a game inside the IDE. Click on “RESULTS” and you will find the history tab. You can see the score of your previous submissions per language, and access the code associated to that submission as well.
  • New feature “Hint”: If you have a hard time solving a puzzle, you can now unlock hints to help you. This is already available for the tutorial and 5 easy puzzles.

  • Update “Clash of Code points”: The formula used to determine the Coding Points distributed for your performance on Clash of Code does not attribute points to those who stopped playing a long time ago. And because there are less ranked codingamers, our formula distributes less Coding Points, so you may have experienced a loss of points recently.
    By the way, it is no longer possible to win tons of points by playing a single clash.

  • Fix “Send to IDE”: When viewing a previous match in a bot programming game, sending the parameters of that match into the IDE didn’t always work.
  • Fix minor bugs

  • TOP SECRET STUFF :blush:
3 Likes

What is the formula used to determine coding points for Clash of Code ?

The formula remains unchanged: https://www.codingame.com/forum/t/how-is-the-coding-rank-calculated/790

However, we only reward CP to those who played recently. More precisely, we reduce the “trust” we give to the score of each player every day by increasing the variance and if the variance is too high we do not give coding points. Playing one game reduces a lot the variance.