Wish I could help a bit, and very maybe will do under anonymous gh account but here smol review:
- for * char that doesn't get mutated use const char * instead (. E.g. arguments)
- clrscr is very slow (too slow) to do a regresh every frame. There's an ansii code for that, thousand times faster. Like the way you do your colors
- \033 / \x1b / \x1B / are the same. \e also. It means escape. I would replace all prefixes with \e. I think C doesn't like \033. Do you compile with -Wall -Werror?
- use unsigned int instead of int if value shouldn't be negative

But nice stuff! Good luck!

Why isn't clrscr PascalCase like the rest? That's discrimination 😮

I made an terminal multi-player "game" a while ago with 500 bots active. Server could handle easily. State of game was at server and bots just said the direction they want to go.

Also, think about rendering, one whole string goes way faster than many times printf / putchar. Probably you need store buffer somewhere and make custom printf or putchar function or smth. Custom flush to print and reset buffer to zero. But maybe you've better idea

@retoor Thanks really

@retoor cuz I overthinked about crossplatform and this command was a problem until I found this solutiojn.

@FBDev64 ah yes. You could wrap it with #ifdef _WIN32 so at least on linux it works fast and slow method for windows

@retoor 🤣