there is no issue for comment............it used to increase the readability of our code...

Usually we write comments for each block of code for the uses of it. If there is a need to write comment for your block of code, it is probably the written code is bad. And even it is very difficult to write comment for each block of code, and it is not good practice because it increases the unused quantity. Good code should be understandable to everyone without reading any type of comments. Good coding style is about storing all necessary information to understand the problem in code.In a programming style, there is a concept of “self-describing source code” which is a common descriptor for the written source code that follows certain loosely defined conventions for naming and structure. The main goal for self-describing is to make source code easier to read and understand, so that it is very easy to maintain or extend the existing code.

I think comments are helpful when they explain why something was done, not just what the code already says. Clean code should speak for itself most of the time, but good comments can save a lot of confusion for future developers working on complex logic.
Dinosaur Game

I completely relate to this. I used to overload my projects with comments because even I couldn’t understand my own code a week later. Then while working on a small Polytrack -style racing project, I realized cleaner function names and better structure made a bigger difference than huge comment blocks everywhere. Now I only leave comments for really complex logic or unusual decisions, and the code is way easier to maintain.

It is the combination of simple gameplay, high competitiveness, and a clear sense of progression that has made hole io an extremely captivating entertainment game for many players around the world.