Easy to read

would approve

Normally I find codes here that are much better than mine but the first thing I noticed about your code is that it doesn't cover all possibilities if for example a result is above 5.x or y:5 or more then your code fails.

maybe you just did that out of boredom but really the worst code i have seen here so far sry

Very bad code. Hard to read and doesn't apply well to other restrictions.
Do not do this.

Should the parameters of the code change in future, for example scores could reach up to 10:0, then this would result in a large amount of code needing to be written. While this does solve the task at hand, you may want to consider how else you could solve this so that it could be adapted to different scorelines.

Wtf is this solution?!

@Lician
For example finding fib(5):
Work through it from the top down as per the tree diagram below. When the function returns a value at the bottom, work your way back up replacing each function call with the value it returns and you will reach the answer which is 5.

                                  fib(5-1)                     +                      fib(5-2)
                  fib(4-1)           +          fib(4-2)                 fib(3-1)        +        fib(3-2)
      fib(3-1)       +     fib(3-2)       fib(2-1) + fib(2-2)       fib(2-1) + fib(2-2)               1
fib(2-1) + fib(2-2)            1              1     +    0              1     +     0               
    1    +    0  

Just perfect

You must and should think about the time complexity for this code, if you can think of that, it would be great, but this is not the best practice mate

I don't understand how it should work...

I dont think this is a good idea.

on fingers

how did you calculate it?)

thx) i'll remember this.

if the number is 100, then in this way the calculation will be 50,000 years