It must be really cringey, when you have coded this in a normal procedural way, and then you're like hey let's do it again this time with list comprehensions so i can look smart.

Python:
I passed all tests except one. It's the the third one from the fixed tests.

• 'The fight was a draw.' should equal 'Missile Bob has won the fight.'

Weird cause after each attack i check if somebody has won (and if somebody reached health==0, i print the other guy won). Please check the test case. Thanks :)

we get it you know OOP :D

Attention: If the number has leading zeros the amount of digits should be considered.

That means you should preserve the amount of digits unless you need to add 1. In those error messages, the first value is what your function wrongly returned, instead of the expected value, print the input to see it.

Python test cases failed (all other passed):

• '000010' should equal '00010'
• '0010' should equal '010'
• 'foobar001000' should equal 'foobar01000'

So should we decrement the amount of zeros before the actual number by 1 if they are more than 2? I guess not, cause when i implement that, then i fail some test cases that state i should have the same amount of zeros before and after, previous to the actual incremented number. I think your test cases should be more consinstent.

For example in this one, this clearly doesnt happen:

• Test.assert_equals(increment_string("foobar001"), "foobar002") i passed that btw.

https://github.com/codewars/codewars.com/wiki/Troubleshooting-your-solution#how-can-i-see-which-input-causes-my-solution-to-fail

Can you elaborate more on "print the input"?

Print the input.

Nahhh. Been coding in many languages.

For some reason i thought about the tree data structure, and brought to my mind that you have to take a certain path to reach a point in the row, knowing the first or last number. Crazy how overthinking can screw you up sometimes.