4 ms·
Consider doing something similar to this for the various toolchain members: qcc, qbsp, vis, etc. Throw in the decompilers (e.g., deacc/reacc, etc.) for good me
by matttproud 5y ago
Consider doing something similar to this for the various toolchain members: qcc, qbsp, vis, etc. Throw in the decompilers (e.g., deacc/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.
I'm sure you're already familiar with it, but I found The Cutting Room Floor very helpful in my research (e.g., https://tcrf.net/Proto:Quake/Qtest1 https://tcrf.net/Proto:Quake/Qtest1).
- jasonb05 5y agoGood suggestion - there were tons of custom tools like extensions to qcc and I've started tracking them down. Expanding to the whole tool chain is a great idea. I've started an "official release" archive along similar lines (includes qtest1 and many other goodies): https://github.com/Jason2Brownlee/QuakeOfficialArchive https://github.com/Jason2Brownlee/QuakeOfficialArchive Yeah, QC for most of the mods was available for extensions, only reaper was closed src where authors resorted to decompilers, at least that's the story that I've put together from research.
- galangalalgol 5y agoQC is where I actually learned to program. I'd already done a lot of c and early c++ but the motivation of seeing my changes in the game world were a lot better than anything I could make in my own.
- jasonb05 5y agoMe too! Turned out learning java/c/cpp at uni was way more boring than coding up quake mods :)