The problem is that this kata disguises the need for special knowledge, and you can only discover that fact by wasting time trying to solve it. After completing over 100 kata this is the only time I have experienced this.

I would also ask that you try to be more constructive in these forums. Disagreement is not a license for rudeness.

Hey thanks for the tips on posting an issue. I didn't realize I was opening a ticket, and thought I was just tagging my comment. However I do believe there is an issue but I can make may writing more clear. I'll post a new comment.

Yeah, My solution from this rank 6 kata also worked for this problem: https://www.codewars.com/kata/checking-groups/csharp

Feature Request: filter out math-based kata. Because sometimes you just aren't in the mood.

Very cool series. Does the IUnitState provided represent a preferred practice in C#? I am learning but I thought having setters was a little strange. Compare to this version.

public interface IUnitState {
    bool CanMove();
    int Damage();
} 

Let me know if that makes sense.

You should remove this text from the description:

"For your convenience, in this kata we will use unbleach() function when evaluating your results. This function replaces whitespace characters with [space], [tab], and [LF]. You can see how it's done in Example Test Cases."

This is a clear signal that those sequences will be allowed in the tests.

The example tests allow [space], [tab], [LF], but the real tests require " ", "\t", "\n". This was for C# version. The tests should be consistent, especially because the spec specifically mentions we can use [space], etc.

If you do lowercase the other letters, the random tests will fail because the include random capitals within strings.

I was very annoyed with this kata because I coded to the spec but was then surprised at the non-standard definition of camelcase. Consider these tests that work with the final solution:

Assert.AreEqual("hELLOWORLD", Kata.ToCamelCase("hELLO-wORLD"));
Assert.AreEqual("THISISNOTCAMELCASE", Kata.ToCamelCase("THIS-IS-NOT-CAMELCASE"));

I looked it up and TitleCase is technically considered to be camelCase, but this is not the definition most developers are used to.

I guess in the end this was a lot like real life requirements, but I get enough of that at work :)

One of my "Command-Enter" submitted the answer instead of rerunning the solution. Close enough!