I don’t think the behaviour of this feature should affect the rest of codingame though. I like to have the latest language used in the IDE for the solo/multi problems I’m updating/modifying. But yeah, a default clash language could be great !
1 Like
In a recent clash the scoring system seemed to lock up when then contest was over and the last player (who didn’t submit) was still pending. The result and score of this clash never appeared. It was as if it never happened…
We need a link to that clash, otherwise it’s nearly impossible to investigate.
One improvement I’d like is the ability to preselect the language while waiting for the clash to start, or maybe at least set a language preference according to the clash size, as switching from whatever what used last takes a lot of time (relatively speaking).
Typically I’m mainly a C++ user and while it’s OK for Coffee break and Reflection, I’d rather use Python or Bash in priority for Flash.
I’m fed up with the copy & paste thing. I’ve started reporting cheaters in the survey at the end of the clash.
3 Likes
We will add new clashes next week, hopefully, that should reduce the number of people that copy/paste. But please, do not use the survey to report the cheaters, the real issues with the clashes will be more difficult to see.
Adding new clashes isn’t going to do anything to help with the copy paste unless you are adding hundreds of them.
1 Like
I am supposedly in a clash right now but I never even got to see the IDE - an error message flashed up before anything happened. I then tried to submit a report where it asks if I had a problem with the clash but that gave an error too. Others seem to be submitting so it must be just me. I will come last out of 8 without even having seen the problem. Not good.
I just had 2 bugs on clash 310107abdbca2949b27df5f56a3d7bd0c4bbf:
- the clash didn’t launch at 00:00:00 but just froze, I had to press F5
- when I submitted, my score wasn’t displayed, it was continuously “loading”, I had to press F5 after a while
This is a very real issue. I hope you are planning on implementing a way to report cheaters for review.
1 Like
If cheaters are to be reported (and supposedly punished), please also implement a way for players who have already seen a clash to leave it without “forfeiting”. 
2 Likes
The feature to suggest new clash is really nice, thank you!
What would be very useful is a page where we could see our contributions and their status (accepted / pending / rejected).
Moreover, I think that developers from CodinGame should be able to comment the contributions in order to shortly explain why it was rejected or what was changed before the validation.
This kind of advice will allow us to improve our future suggestions and prevent same repeated mistakes, in order to facilitate your work.
You know, if you have seen a clash before you can just reimplement it instead of copy & pasting it from somewhere. That is what I do.
If the puzzle is fun or really short, that’s what I do too (copy/pasting is slower than reimplementing most flash puzzles).
But some puzzles, especially in the reflection category… are just long and tedious. No real thinking involved, just a bunch of tests and a lot of room for small mistakes. If I want to write the same tedious code over and over, I might as well not take breaks and keep working! 
Also, we’re only talking about “fastest” puzzles here, right? If you have already seen the statement of a “reverse” clash, even reimplementing it is cheating. And for golfing, what’s complicated is thinking about how to reduce the code, not actually writing it, so remembering the puzzle is already an unfair advantage too.
We are glad that you like the CoC contribution feature
We are actually working on that page. You’ll soon be able to access a list of your contributions and their current status.
At the moment admins have to enter a custom message when they reject a contribution (rejection has not happened already). But we don’t explain what was changed before the validation, and that’s something we should do, thanks for the suggestion!
For your information, we have received around 50 contributions. We are slowly adding them to the pool of questions.
Thanks to all the contributors.
2 Likes
I would love to have the option to know beforehand that a clash will be “shortest” (so i can avoid it when i don’t feel in the mood for shortest …)
As a CodinGamer, I would like to compare my code to the other ones after the clash to see where I can improve.
7 Likes
As a CodinGamer, I would like to have the ability to select a difficulty for a Game Mode suitable for my current skill level and knowledge. (e.g. Coffee Break - Novice, Beginner, Intermediate, Advanced, Expert) It seems there is a plethora of contributed codes and none of the are categorized in difficulty levels, so they end up being served in the general Game Mode pool without being sorted or categorized into different difficulties, so most of them are sometimes too complex for me to understand, and sometimes I feel discouraged that I’m not able to complete an exercise because the code goes beyond my knowledge. In the other hand, it would be nice if CodinGame would have this feature, so whenever I feel ready to keep advancing and competing with more advanced coders/programmers I can do so with knowing I will be ready for the next levels.
Your’s Sincerely,
0xNOP