I agree, having more examples would help with decoding while not taking away from the problem.

8D

True -- feel free to fork it :-)

:D

Agreed, I initially implemented a recursive function (in C++) and had to back away from it because of the strange edge case.

Added "Can someone explain" to the end ~half the time. Also added case sensitivity ('can someone explain' appears randomly), and a test for the suggestion above ("Can someone explainable", e.g. is invalid).

I agree.

Well the intention there is to show all of the possible cases that the future random tests will expect as answers. What would you suggest I do differently to make them less redundant?

But just because the task is different (which it definitely is, no dispute), doesn't mean it is not "almost exactly the same" (when looking at tasks' gist) ;) Anyway, closing the issue is fine by me, it's just that your original 3-character answer made be laugh... :)

:o

Just because the task is different? ;p (sufficiently to close the issue, at least).

@Blind4Basics, why "No."? :)

Fixed

Looks good to me except the line:
f=[[names.sample, rand(999), rand(99)], [names.sample, rand(999), rand(99)]]

Can both fighters have the same name? If so, it's an invalid test case!

Oh man, sorry for the late reply. Let me take a look!

Agreed, thanks for the comment.