gunslinger VS ioq3

Here's a framework that's cool: https://github.com/MrFrenik/gunslinger/. We have a great Discord community, too. Even if you don't end up using it, there are plenty of people who are willing to offer guidance regardless :). Invite link is on the author's YouTube channel: https://www.youtube.com/watch?v=-_HxKDNuCqA

Check out gunslinger, a pure C99 game framework, with a very clean design.

The development has been making huge strides and they have a fairly active discord channel:

https://github.com/MrFrenik/gunslinger

Make your own. If you really want to make a game in C, this may be the best option. Depending on how complex the game is that you want to make, this could be an enormous task, or not too big of a deal, in some cases it could even be easier than learning a game engine. You can use frameworks like Gunslinger to make it easier, as well. If you need guidance, the Gunslinger community is friendly and accepting of beginners :).

That being said, you may have your requirements satisfied with tagged unions which consists in implementing a struct with an anonymous union and label (like an enum) to keep track of what data is inside the union, this works really well when you know beforehand which data types you want to support. Another technique could be using macros, like the containers on the gunslinger framework, however I have never implemented something like this. Lastly you can always use void pointers, however you may need to be more clever to achieve it (I almost never use them).

Some of my favorites are: sokol/pacman.c, Gunslinger, and gb

And here is Github of his game engine of this guy: Gunslinger Game Engine

To install non exotic library from a github repo, specify just the repo-owner/repo-name or the absolute github link to the repo. E.g. to install gunslinger and stb from master branch

Looking quickly at this lib, functions of the API are not static: https://github.com/MrFrenik/gunslinger/blob/d5ebcce0647e97badc9337749d7cd9f5810eecfa/gs.h#L1415, so it might lead to ODR violation.

The bigger thing is that you need to build the binaries (game files like .exe and .dll) yourself off ioQuake3's GitHub. If you're not a programmer, and/or you're lazy, it's easier to grab the files off Quake3e's GitHub instead.

And so is the most popular fork (ioQuake3): https://github.com/ioquake/ioq3

The Quake 3 engine was open sourced and people still make maps for it.

The source code for all of the Quake games is available on GitHub. They are the original source releases, but you might prefer to use a source port which implements more up-to-date platform abstractions (like SDL), supports 64-bit, and doesn't contain any assembly code. I'd recommend ioquake3.

On a more serious note, also check out https://github.com/ioquake/ioq3, which is a modernized version of quake 3!

The only way for you to get a recent build of ioquake3 is to build it yourself from source code hosted on github.