Highly evolved engine based on id Software technology, available under dual license (GPL, proprietary licensing for commercial use available).
Description
Quake 'one' 1.06 .qc files with qc++ enhancements - fteqcc required - see docs / compiled.txt
Preview
Post a comment
Mod SDK & Community
Built a game for DarkPlaces engine and want to support mods? Try mod.io, a cross-platform mod SDK created by ModDB which makes it easy to get a mod community up and running in-game. Currently seeking games to integrate and promote
Related Games
Quake
First Person Shooter
Related Engines
Quake Engine
GPL
Related Groups
Dark Places engine team
Developer with 15 members
id Software
Developer & Publisher
qc
Hardware & Tech with 31 members
QuakeDB
Fans & Clans with 219 members
Tags
Requirements - fteqcc
For a precompiled binary try:
Sourceforge.net
fteqcc source can be found here:
Sourceforge.net
on page:
Sourceforge.net
In the archive the qcc source is in the qclib directory.
What is v1.06 RECODED ?
A redesigned v1.06 quake-c with an intense focus on:
Reducing compiled resource usage - less bytes, less globals, less functions, less statements.
Simplify source code - less statements means less to debug - unused code is removed (commented out or #ifdef blocked) Repeated code has been folded into fewer functions.
Maintain as much of the v1.06 function as possible. Some code fixes and minimal upgrades have been included - these can be reversed / removed by commenting a few #define.
Easier use in mods - the frikbot module is included as an example - it can be removed by commenting out one #define.
Future expansion - plans to include hipnotic, ritual, painkeep, etc.
if you could a basic scratch source with main fps features would be desirable.
I'm working towards making all major sections exclude-able modules...
So if you have a DM only mod, you could turn off the monster modules. Want new weapons - turn of the weapon module.
This is a similar idea, but not quite from scratch.
If you turn off all the modules, you would have a basic framework with all the major engine calls and some of the run code.
I'm also heading towards re-writing a lot of the old code with mod easy counterparts that simplify and make new things easier.
This hard part about this is the hill you have to climb to add existing code, like the mission packs.
Most modders just bolt everything right into v1.06. The opposite would be frikbot. If all the mission packs and other addons were like frik, it would be a dream.
What would be nice is if the editor could exclude bits based on what #ifdef block it was in. I'd also like the compiler to output the code it actually compiled. The #ifdef stuff tends to be busier and you have to watch that you are looking at the right piece of code.
very nice, i never thought you can do such things in qc :D
Wow, thanks!
I've actually just discovered how to make a "true" local variable - that does NOT affect the global counts!!
What amazes me is that after what is fast approaching 20 years...I'm still learning things about qc.