[Community puzzle] Timer for Clash of Code

[Grokwik]

Thanks for the help

[Appul]

Hi, i am a bit disturbed, I’ve succeeded all the tests but the first

Same issue here. the ide tests are fine, I haven’t hardcoded anything, but the first validation test (“1 time stamp, timer starts game”) fails.

All tests succeed in IDE but the first submit test (1 timestamp, timer starts game) fails when submitted for C# while all the others succeed.

ich just dont get the 100% because the first one always fails although it is the easiest one …

LoI passed all the test cases, submitted but the first one just didn’t want to validate my code 100%.

After @player_one’s explanation, I’m now at 100% before submitting, but still failing that first test case after submission.

I had the same issues as you CodinBros; my issue was with the case where the input time was within 10 seconds of 256 (4:16). Try debugging your output and manually setting the input time to some values in that range to see what your output is. The edge case issue became clear once I did that.

[PatFrrmth]

oooh thats a good point so my code return 0:4 instead of 0:04 if there are less than 10 seconds left

[atzame]

I had the same issues as you CodinBros; my issue was with the case where the input time was within 10 seconds of 256 (4:16). Try debugging your output and manually setting the input time to some values in that range to see what your output is. The edge case issue became clear once I did that.

This was my issue; needed to pad the seconds if <10. Thanks.

[Nangini]

Many thanks!! My code wrongly displayed 0:9 instead of 0:09. I pass it. Thx

[ChemCoder]

Thanks, my mistake!

[Dogwon]

Never mind.

[Rashik_cs]

Hello everyone first test fails after submitting even if my result matches with the expected one. IDE told me the solution was correct.

[player_one]

my issue was with the case where the input time was within 10 seconds of 256

This was my issue; needed to pad the seconds if <10.

I have added a new test to the end of the suite, called “Down to the last seconds” so that others don’t stumble over this in the future.

• danBhentschel

[kjasghlisuagerhdfn]

Thank you. I’ve been fighting this for weeks. Never crossed my mind that the formatting was off.

[crashtestdummy]

Terrible problem definition.

The time reference is based on a timer counting backwards. It’s not a date, just the count of a timer.
The explanations refer sometimes to an absolute time, sometimes to this floating reference.

“the timer changes based on players joining” is plain wrong. The timer keeps counting toward zero regardless of people joining. What changes is the date at which the game might be started (what I call the “rush date” since it can only make the game start earlier).

I especially wondered at this “set the new time instead of starting the game” directive. I have no idea what that means so I simply ignored it. Luckily for me it didn’t seem to matter neither for tests nor validation.

The tests send you timestamps corresponding to players joining after the game started, as if people could join in mid-game or something. There is not a word said about this in the problem definition.
When that occurs, the rush date has no longer any effect, obviously, but if you still take it into account you’ll most probably produce a wrong result (as if this player joining late had delayed the game start).

[mel-mouk]

Agreed, the problem is nice, but the explanation is really confusing, some sentences are useless ("If a player joins at the same time the game is supposed to start, set the new time
instead of starting the game.”), some other are confusing (“p is the number of players in the room”, yeah, but it’s the number of player in the room before the player join, the explanation leads to believe it’s including the current player), maybe somebody could rewrite it ?

[SPDene]

The problem is fairly straightforward; the hard part is understanding the ambiguous description:

• does “current time” mean the time since the timer started, the time until the game starts, or the time currently displayed on the timer?
• is “p” the number of players in the room before or after the player who is joining?

Most importantly, the purpose of a timer is to count down to when the game will start. If the game starts before the timer reaches 0:00 then the timer is BROKEN! (unless 8 players join)

The challenge of a puzzle should be finding a way to implement a solution, not struggling to understand the badly-written spec.
HATED IT!

[DEFOSSEZ_Clement]

I have a problem I passed all the test in C langage but the fonction malloc can’t found enough place sometimes so my rate when i send my code depend only of this. With the same code, i can get 33% and next a 58%… How can i solve this?