Archive and genealogy of all Quake 1 bots

Somehow this feels like the part of the Bible that goes on for verses and verses &quot;And Jeshua begat Joiakim, Joiakim also begat Eliashib, and Eliashib begat Joiada...&quot;.<p>A key difference is this is rather interesting.

I&#x27;d love to see how far&#x2F;good bots could get in a deathmatch shooter with reinforcement learning&#x2F;self play (provided we could strongly and intelligently enforce human level reaction times and keyboards&#x2F;mouse inputs). Would be really interesting to see if any crazy new strategies&#x2F;tactics emerge.

Consider doing something similar to this for the various toolchain members: qcc, qbsp, vis, etc. Throw in the decompilers (e.g., deacc&#x2F;reacc, etc.) for good measure. As a side note, I was curious whether the bots had official QuakeC source available or if it was readily decompileable. IIRC, the Reaper bot intentionally obfuscated itself somehow.<p>I&#x27;m sure you&#x27;re already familiar with it, but I found The Cutting Room Floor very helpful in my research (e.g., <a href="https:&#x2F;&#x2F;tcrf.net&#x2F;Proto:Quake&#x2F;Qtest1" rel="nofollow">https:&#x2F;&#x2F;tcrf.net&#x2F;Proto:Quake&#x2F;Qtest1</a>).

FortressOne dev here. Noticed quite a few &#x27;TF&#x27; bots that I hadn&#x27;t heard of. Anyone know more about these? Or even just the vanilla bots? Looking for something that can bunny hop mostly.

Reminds me of my Whitespace Corpus in its organization, especially the table in the README. I cataloged all known implementations of the Whitespace programming language, including interpreters, compilers, and programs. I recorded detailed information about each in projects.json, then generate the table and other documents.<p><a href="https:&#x2F;&#x2F;github.com&#x2F;wspace&#x2F;corpus" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;wspace&#x2F;corpus</a>

Is there way to figure out properties of these bots? Like which one is smart, which one requires the fewest resources etc..

I remember when Frogbot came out, it was pretty amazing.<p>You could train against it and improve very quickly.<p>However it also seemed to accelerate boredom with q1 multiplayer for me.

I’d love to see an in depth tournament between all of the bots, something like the GSL

I worked in a company that was making games like this. Copy&#x2F;past the old game, remove assets and start from there.<p>There was a hierarchy of ancestors, siblings and descendants. So, when a bug is discovered in a game, it was important to trace back its lineage to fix all relatives affected by it.<p>Finally my job was to convert all common code into a library so we could have versioned releases and be able to fix bugs just by upgrading the library version.<p>The copy&#x2F;past was fast for the very few first games, afterwards was a pain in the ass. When I joined the situation was dire. But , it was an interesting study in evolution, thou.

I&#x27;m pretty sure I played with some of these but dont remember the names. Man, I really, really miss the Quake 1 (World) days... what an incredible time that was.

It&#x27;s a shame Slipgate Complex isn&#x27;t still around. That was the original file sharing site for Quake.

did somebody say fast inverse square root algorithm?