lets take your example first row "90 >= score <= 100", lets say score is 95.

90 >= 95 <= 100

it will read as 90 is bigger or equal to 95, which is less or equal to 100. 90 is not bigger or equal to 95.

Your gunners for each test case are 2, 3 or 4.
This line is extremely confusing, I think you meant
There are always 2, 3 or 4 gunners.

Idk renis, your ego seems to be a bit bigger then it needs to. I just looked at your solution and it is hard to read and follow, its just one big block of code and also strings are hardcoded. I mean nothing catastrophic but best practices wise having to change code in 2 places to change "A good fight" for example is not 'best' (problem only grows with the growth of code).

Blind4Basics code on the other hand I really like. It's so easy on the eye and as far as I can tell follows all the modern Java conventions. Everything camelCase, consts are upper with underscore, everything is properly marked as final or private, code blocks and logic blocks are nietly separated. That is a code of somebody I would be happy to work with on single codebase.

empty input should still return [0, 0];

Well I checked if input is null, still gives nullPointerException, works completlely fine in my IDE if I send null as input. And even if it works because of some exceptions with streams etc and I should somehow catch it with try cath then it has no business being in 8kyu category...

Java is broken.

Hahaha, made me laugh, good one xd