Angry? I just left some snarky replies to your equally ridiculous comments, while trying to point you to the source of the error.

And no, we can't just ban you because we want to (I'm not sure about Hob), but the fact you would just blindly imply it is quite disgusting.

when kata starts adjusting to my decision.

hence why people like me are asking for help.

The issue I see is that people are not, in fact, asking for help. They are dismissing the setup as incorrect right away. Only few users ask "why is my code wrong?" . Instead, majority of complaints is "this kata is wrong". Why?

Okay so I would say that:

• "I can't find a way to get around the problematic one" is not a sign of the kata being wrong. The example is there for a reason, and finding a way to solve it is a part of the solution. Intended way is to figure out how to make this test to work, and not to conclude that it is incorrect.
• I mentioned it somewhere below, and I would repeat here again: the challenge here is to make both forms work: hello() and hello(someName). IF a user solution can handle one way but not the other, tests fail.

What I would be really interested with, and maybe you could help me, is how to make it clear that failing test is a problem with user solution, and not with tests. It's already mentioned in the description. It is in example tests. What is missing? What sohuld I change to make users aware that it is their task to make things work?

Hello, check it out.
Translation Dart

1. yes
2. yes, but I can't find a way to get around the problematic one, hence why people like me are asking for help.
3. YES, but instead of finding answers, I find replies like this that don't help, and just tell us we are wrong but not what we are wrong about to help solve the problem.

Sorry if this comes out rude, but I am getting tired of asking for help or looking at other's cries for help and seeing nothing but "Your code is wrong, read the description again", and marking the issue as solved without addressing what they got wrong to begin with, or what they might have gotten wrong.
This is more of a complaint in general and not with you in particular.
Please take no offense.

EDIT: I realize that was an extremely rude rant. I also realize people like me think the issues area is where to go when WE have an issue with OUR code. It is supposed to be for issues with the Kata itself.
Sorry (Geez, this is embarassing for me)

probably, but i highly doubt that it was so bad that the green pfp guy became angry. i can be angry too, but something tells me if it happens he'll ban me just because he wants. mod guy, thanks for sane answers, i found my mistake.

Did you read the description?
Did you look at example tests to see what is expected?
Did you read questions below in this discourse, and answers to them?

In C#, tests/Fixture.cs(21,24): error CS7036: There is no argument given that corresponds to the required parameter 'name' of 'Kata.Hello(string)'

Isn't receiving input correctly

It can be argued that throwing a comment like "buggy" with no explanation, and no follow-up, which ultimately turns out to be a user error, is also not very friendly, and a poor etiquette at best.

You solution cannot handle the case when no name is given, i.e. when the funciton is called like this: hello(). This is visible also in example tests. You can see example tests, and this should be enough to figure out what is the scenario your solution fails to handle.

It is not a kata issue. Your solution does not implement this part of the specification.

hobovsky, ok, i understand, thank you. But the guy B1ts.. why are you so unfriendly. are you offended by me, why you protect codewars with this toxic foam at the mouth..

do you see my solution to say that?

Yes.

people before me wrote about the errors for many times, just read it.

It's simple: all of them did the same mistake as you.

do you see my solution

Yes, there has been a feature introduced a few years ago that lets you see someone else's current solution, if you solved the kata yourself.

people before me wrote about the errors

And what was your conclusion? That they couldn't possibly be wrong? Did you read the responses and possible solutions to these "errors"?

I would start by logging inputs, like adding print(f"name: {name}") line at the beginning of your function, or downvoting others' comments and pretending codewars is the problem.