Quake-III-Arena VS permafrost-engine

Quake III Arena

If you know C, you can check this out by comparing the different player movement code of Quake 3 and Quake 1.

You mean this code?

https://archive.softwareheritage.org/browse/content/sha1_git...

Do you see that notice at the top of the file? It says:

==

This file is part of Quake III Arena source code.

Quake III Arena source code is free software; you can redistribute it

The error messages comes from this file in the source code. It looks like the client is trying to parse entities from the server but the readcount is greater than the cursize in the messages. I am not an expert but I believe there could be a mismatch between the versions of your client and the servers you are trying to connect to.

After learning C, one of the first projects I came into contact with, was the ID Tech 3 game engine [1]

On the one hand, it taught me how professional C programmers structure their code (extra functions to remove platform differences, specific code which is being shared between server and client to allow smooth predictions) and how incredible fast computers can be (thousands of operations within milliseconds), but it also showed me, how the same code can result in different executions due to compiler differences (tests pass, production crashes) and how important good debugging tools are (e.g. backtraces).

To this day I am very grateful for the experience and that ID decided to release the code as open source.

[1] https://github.com/id-Software/Quake-III-Arena

Yea, bit annoying to do that, especially in a large project some vectors need to be static some need to be exposed in the API. In my mind the best solution is to add another macro parameter that lets the user change the function scope on the fly. See the vector used in the permafrost engine (a fellow redditor); when I first saw how he wrote his template macros it was a game changing trick.

And the source code for the engine is here on GitHub. I've written like 75k SLOC of C for it. It's a pretty general-purpose RTS engine that could be used for a lot of things - full conversions, remakes of classics, other RTS/citybuilder/ARPG games, and more. It has a Python scripting API for the top-level gameplay logic.

BTW, the engine is fully open-source. So if you want to take a deep dive into the code, it's here: https://github.com/eduard-permyakov/permafrost-engine

I'm into my third year of writing my own RTS game engine in C. Complete with OpenGL rendering, group pathfinding of 1k+ entities, Python scripting, yada, yada, yada.