Bugs are game specific. However, there are some common things you can do to help the developers.
In order to fix a bug, the testers and developers need to do three things:
1. Figure out exactly how to reproduce the problem.
2. Find the code/data responsible for the problem and attempt to fix it.
3. Test it to make sure it's actually fixed, and make sure nothing else broke due to the change.
You, as a tester, are responsible for helping the developers out with part 1. What you need to do is figure out how to *cause* the bug to occur reliably. Once you've figured out these "repro steps" as we call them, you report them to the developer.
For part 2, the developer then runs the game with a debugger or other diagnostic tools and watches what happens in the code when they follow those steps, and compares the result against what they expect to happen. This frequently lets them find the problem, and lets them work on a fix.
For part 3, the developer tests their fix by following your repro steps again (and any additional tests they have come up with after determining what other problems could happen).
Well that's the problem nobody can figure out what is going on...
If that's true, we can't help you either.
I just wanted to know if somebody had this issue...
Your description of the problem is extremely generic. I'm sure people have all run into a "game didn't let the player do something" bug. The problem is too implementation-specific for us to even begin to speculate about what is wrong. Even if the genre is the same (MOBA), each team implements their code in completely different ways. This is why you need to experiment while playing the game until you figure out what the actual repro steps are, and discuss with the team itself. This kind of bug isn't specific enough for people who aren't working on that game to help with.