Title: Quake 2 Source code...
Description: ^_^
Dark_Sonic - June 25, 2003 08:21 AM (GMT)
Have you ever looked at source code of 3d action game? Well look at quake 2! It is pretty complicated... It's made in C but that is pretty close to C++... I suggest you take a look! And it's free :P
For example you can get it from
here , but if you don't have a Game Spy account you can search Google Quake 2source code...
Dragon - June 25, 2003 06:34 PM (GMT)
Yeah, well, what do you expect? It's a professional game made by a team of programmers.
FHCandyman - August 13, 2003 05:11 PM (GMT)
sorry if this is old beyond old but i saw this and had to comment :D I never knew Quake 2 source code was released so this is pretty cool. C actually isnt all that similar to C++ from what I've seen, its got a ton of differences you have to work with. Thanks to whoever posted this so long ago.
Sam Fisher vs Solid Snake - August 13, 2003 05:41 PM (GMT)
actually c++ is an enhanced c, i have checked the code, and it isnt very different
ih8censorship - August 13, 2003 09:24 PM (GMT)
yeah its like incremented with the ++ like an operator.
FHCandyman - August 13, 2003 09:38 PM (GMT)
well ive read through a few books and theres things like global variables and such which really limited C, so it may be very alike but still not too easy to work with when all you know is C++. It is like C, but not to a point where you can learn C++ and completely know C. I just kind of misworded that.
Dark_Sonic - August 14, 2003 06:14 PM (GMT)
Great that someone replied to my post at last! There was only one thogh... And I haven't been very active lately as you might have noticed...
Candyman - August 14, 2003 09:55 PM (GMT)
Cybermaster, where have you been, I was worried sick about you :lol: I'm surprised to see you here, I thought you died or something :blink:
factandfiction101 - September 22, 2003 03:03 PM (GMT)
Dixon - September 22, 2003 10:41 PM (GMT)
I got the Quake source codes once. But since I am still learning Console programing right now I haven't looked at it a lot yet. :(
I have never played Quake but I downloaded Wolvenstien 3D a few week ago.
RichyT - October 27, 2003 07:51 PM (GMT)
I know this post is DAMN old <_<
But ID were planning to release the QuakeIII Engine Source Code - or was I dreaming that? (Read it in PC GAMER)
MonkeyMan - October 28, 2003 12:50 AM (GMT)
This isnt something I would know :D Anyways I looked at the source for the Quake2 and it confused the bubbles out of me so i deleted it :D
RichyT - October 29, 2003 03:55 PM (GMT)
I got the DOOM source code... anyone want :(
:ph43r:
that person - October 30, 2003 01:49 AM (GMT)
YA, I'd like the DOOM source code! That was like the first real game.
Red_Dragon [DooM] - November 12, 2003 07:09 PM (GMT)
This post is probably REALLY old by now (maybe)
but this is the sources thats free (that i know of)
Quake
Quake2
All doom games (no not doom3)
and Quake3 Probably wont go free until another couple of years (its still getting money to them)
yes itr true C and C++ is like eachother alot but the system is different so dont be lored its easy to do mistakes...
just so u dont think im a rookie
Im the lead programmer of a half-life mod named Return To Doom
im working on some other shit like doom doom2 and quake2 sources (for fun)
and ive been a programmer within C++ about 4 years now (im 14 :P)
Ravesaturn - November 25, 2003 02:53 AM (GMT)
This may be irrelevant, but I just did a quick search for Doom Source Code and found the *legal* source code for Doom for the Atari Jaguar (go figure)
here. It's kinda interesting to look at if you're interested in programming for consols.
I doubt anyone has the software to actually turn this into a Jaguar game though. I didn't think anyone besides myself even had a Jaguar, let alone have the software to create a game for it. ;)
ih8censorship - November 25, 2003 06:52 PM (GMT)
i never had a jaguar but i had:
2 - atari 2600's
2 -coleco visions
about 200 games
about 30 controllers
and i thought it was the coolest thing in the world i was playin that when n64 came out....
i wish i still had that stuff.... oh well.
quart42 - January 2, 2004 07:54 PM (GMT)
Just so you all know, YOUR NEWBIES! the main difference between c++ and c are that 1.OOP 2. OOP 3.OOP
I HOPE THAT CLEARS EVERYTHING UP FOR YOU ALL, and that goes for you too mr."IM 14 and a lead programmer in half life wutever shit" <_<
ih8censorship - January 2, 2004 08:17 PM (GMT)
uhh yeah if we werent newbies we wouldent be here :P and he said half life MOD not the half life game itself.....
Reiji - January 4, 2004 07:11 PM (GMT)
Just looked at the QII source... wow, it's complicated...
dr voodoo - January 6, 2004 04:19 PM (GMT)
| QUOTE |
| Just so you all know, YOUR NEWBIES! the main difference between c++ and c are that 1.OOP 2. OOP 3.OOP |
There's aboslutly nothing stopping you from writting a procedural prog in C. C++ is C that allows but is not limited to OOP.
| QUOTE |
| well ive read through a few books and theres things like global variables and such which really limited C |
Depends on which standard you mean C99 has many new things.
Haxor - January 30, 2004 05:16 AM (GMT)
Just thought I'd add .. an FPS called Cube is also open source. It's a freeware game to begin with .. but it's totally awesome. The guy who made it seems to think that he's redefining the world of FPS's as we know it .. I wouldn't go that far but it is a pretty awesome game.
http://www.cubeengine.com
BerlinAssassin - April 3, 2004 07:34 PM (GMT)
Hello... The Wraith tell me to ask... Does anyone here know a VX by the name of SikleCelArmenia??
BloodGhst - April 12, 2004 09:08 AM (GMT)
Yes, again, I realize they is a really, really old thread. I have programmed in C++ for about 6 years now, but never really learned how to program in straight C before. One of my classes required me to program in C, and I had no difficulties. It is true that there are some fundamental differences, but if somebody knows C++, reading C code should be no big deal. Also, I find console apps easier to understand, but that's only because I learned Pascal before C++ or even Java. FYI, I'm 20 and a senior at Oregon State University and have been programming games for about 8 years.
windwakr - April 20, 2004 04:05 PM (GMT)
wtf? BloodGhst's post is inside BerlinAssassin's post? How'd that happen?
edit: Mine is too!
BloodGhst - April 24, 2004 12:18 AM (GMT)
^ I noticed that too... probably a problem with the databasing. Crazy.
brent01 - April 24, 2004 03:07 AM (GMT)
Oooh i think i might dl it(dling)
windwakr - April 24, 2004 02:30 PM (GMT)
i think its the html in BloodGhst's sig
Incubator - April 27, 2004 10:02 PM (GMT)
a little quote from a game developer:
| QUOTE |
If you ever get a peek at the code behind a major commercial game, please do not take it as a treatise on proper software design or coding! Games often start out as well-designed software, and they sometimes even make it to the shelves in a tolerable state of internal organization, but more often than not a game's code falls into disarray during the last few months of development. Why, you might ask? The gaming industry is volatile, dangerous, and extremely competitive. Game studios seem to nd themselves in a perpetual struggle to meet release deadlines, get their games out ahead of their competitors, and implement the features that players demand, lest they be left in the dust with a stack of unsold games. This often results in extremely hurried and sloppy code. Unfortunately, this often causes serious problems if someone later tries to add an expansion pack to the game or port the game to another operating system. - John R. Hall
|
never trust game source :)
ih8censorship - April 27, 2004 10:19 PM (GMT)
i DEFINATLY agree with that-- like i start out with an idea and then i get an idea to make something better, and i add that, and then i add something else and pretty soon i have a huge mess.
BloodGhst - April 28, 2004 05:50 AM (GMT)
I know what that's like. I once developed a GUI (trust me, it was a pain) and before I knew it, I had 3000 lines of code that was completely disorganized. The person I was working with at the time and I devised a way to keep our code cleaner, but we soon didn't stick to that as our deadline loomed (I was planning on going on a cross country trip.) We also cut a lot of corners and didn't try to research ways to better implement what we were doing. If only I had known about inheritance at the time. Also, we ended up with something that only ran on XP. It worked, but barely. We had much debugging to do still.
The moral of my story, everybody does this, and I know frist hand how badly coded some things can be at the end of a production period.
Edit to add: The post inside a post seems to be fixed. Good thing too. That was annoying me.