Loading collection data...
Collections are a way for you to organize kata so that you can create your own training routines. Every collection you create is public and automatically sharable with other warriors. After you have added a few kata to a collection you and others can train on the kata contained within the collection.
Get started now by creating a new collection.
The kata is available: Snooker Break.
Because it would require the black ball twice potted in a single shot, it cannot be in 1 shot. I'll explain these rules in the challenge. I will not add restrictions. Theoretical breaks, for instance where all balls are potted in a single shot, will be included.
I like this setup. But I don't understand why the lowest break is 1 in your example. In theory, all 7 balls could be potted in one shot. Or do you want to restrict the maximum number of potted balls?
What do you guys think of this setup? A list of strings is given, representing the break. The user needs to find out which of all possible shot sequences results in the highest scoring break. Not only you need to think about how each next shot gets nominated, but also possible free balls and fouls. Potential penalty points awarded to your opponent are to be discarted from calculation.
I will ask for removal of this kata when you create a new one.
Ok, I'll create one.
I would prefer to get a new more comprehensive kata. This kata (C# only, 68% satisfaction) can be retired.
This challenge shows potential but has significant limitations. A more comprehensive and nuanced challenge about snooker breaks would greatly benefit the platform. Developing a replacement that captures the full complexity of snooker rules would be a valuable contribution. Should I have a go at creating a new challenge, aimed at replacing this one, or can this existing one be effectively resurrected and improved?
unless you like solution as this
Player class should be preloaded.
This comment is hidden because it contains spoiler information about the solution
Not an issue
1 test is not enough.
The Pink test is already problem. The test waits for exception here. :(
Implememted thanks
Loading more items...