Earlier quoted context omitted.
Not saying I never conjure the spaghetti but whoever coded that really was deep into the tail end of a caffeine, coding and sleep deprivation binge ;)
>whoever coded that really was deep into the tail end of a caffeine, coding and sleep deprivation binge ;) That's most indie game devs of the period, but more so at id Software which splintered the team during Quake's development due to internal squabbles, causing John Romero and others to leave id. You can even tell that from the quality of Quake's levels which start with beautifully crafted and intricate levels, an…
Quake's lightning gun bug explained [video]
91–100 of 218 posts
Re: Quake's lightning gun bug explained [video]
#92Quake was the first PC game I played and still in my top 10 favorite games of all time. The movement STILL feels fresh!
Re: Quake's lightning gun bug explained [video]
#93Earlier quoted context omitted.
Good chance it was John Carmack, probably one the top 10 programmers of all time. He basically built the Quake engine himself. There is a pretty decent analysis of it here: * https://fabiensanglard.net/quakeSource/index.php I recommend checking it out. EDIT: i was thinking of the analysis done on Quake 2, which is more about the engine: * https://fabiensanglard.net/quake2/index.php while the one about is regarding th…
I loved the video, I love this type of analysis of bugs and glitches. This comment, however, just makes me nervous. It's like my innermost worry. I spend so much time trying to do a good job which I can be proud of and yet I always know there are bugs and I just hope not too many players notice and get annoyed by them. And here we are, pointing out poorly written code in practically ancient software and attributing i…
-- "We Make Shitty Software... With Bugs!"
http://scripting.com/davenet/1995/09/03/wemakeshittysoftware...
I think it is a good mindset to have. We must all assume that software is an imperfect thing done by imperfect beings. Even celebrate it.
On this particular case, I recommend concentrating not on the fact that there was a bug, but on the fact that the code written so many years ago is still relevant for someone today. Focus on that. Try to make something that someone will find a bug in 30 years from now.
Re: Quake's lightning gun bug explained [video]
#94Earlier quoted context omitted.
Probably to busy off doing new things to worry about this. ;)
Possible, but not necessarily. I've just seen Romero playing a Doom mod this week for example: https://youtu.be/gIl_TqFJNO8
Re: Quake's lightning gun bug explained [video]
#95Earlier quoted context omitted.
I'm not sure if it would've been John Carmack in this particular case. He was more concerned with the engine and rendering side of things, less with the gameplay logic stuff. More likely it would've been either John Romero or John Cash who wrote this code, but it's hard to say for sure. Best thing we can hope for is that John Romero pitches in with his impeccable memory :D
So the only requirement to work at iD back in the day was to be called John?
Re: Quake's lightning gun bug explained [video]
#96Earlier quoted context omitted.
Good chance it was John Carmack, probably one the top 10 programmers of all time. He basically built the Quake engine himself. There is a pretty decent analysis of it here: * https://fabiensanglard.net/quakeSource/index.php I recommend checking it out. EDIT: i was thinking of the analysis done on Quake 2, which is more about the engine: * https://fabiensanglard.net/quake2/index.php while the one about is regarding th…
>probably one the top 10 programmers of all time By what metric? Popularity? PR? Net worth? Complex software? Competitive programming? Impact? For every "top" SE there are tens of similarly skilled engineers that you have never heard of
He's very good. Enough people agree. I recommend letting it at that.
Re: Quake's lightning gun bug explained [video]
#97Earlier quoted context omitted.
Good chance it was John Carmack, probably one the top 10 programmers of all time. He basically built the Quake engine himself. There is a pretty decent analysis of it here: * https://fabiensanglard.net/quakeSource/index.php I recommend checking it out. EDIT: i was thinking of the analysis done on Quake 2, which is more about the engine: * https://fabiensanglard.net/quake2/index.php while the one about is regarding th…
> Good chance it was John Carmack, probably one the top 10 programmers of all time. Where would you rank Linus Torvalds?
Re: Quake's lightning gun bug explained [video]
#98Earlier quoted context omitted.
Good chance it was John Carmack, probably one the top 10 programmers of all time. He basically built the Quake engine himself. There is a pretty decent analysis of it here: * https://fabiensanglard.net/quakeSource/index.php I recommend checking it out. EDIT: i was thinking of the analysis done on Quake 2, which is more about the engine: * https://fabiensanglard.net/quake2/index.php while the one about is regarding th…
> Good chance it was John Carmack, probably one the top 10 programmers of all time. Where would you rank Linus Torvalds?
Re: Quake's lightning gun bug explained [video]
#99Earlier quoted context omitted.
That should be a known bug on a specific teleport that exists on the DM2 map. Not sure if it's also present on "regular" Quake but it's been on QuakeWorld for as long as I can remember. On the backroom (where there is Red Armor and Mega Health) there is a teleport that goes to the main (BIG) room of the map. If you jump just before the teleport and "aim" your jump so you go in the top left corner of the teleport, you…
Yes, IIRC it was exactly that teleport. I'll try to repeat this using hint from you :) I was really confused when I hit that.
Re: Quake's lightning gun bug explained [video]
#100Earlier quoted context omitted.
I loved the video, I love this type of analysis of bugs and glitches. This comment, however, just makes me nervous. It's like my innermost worry. I spend so much time trying to do a good job which I can be proud of and yet I always know there are bugs and I just hope not too many players notice and get annoyed by them. And here we are, pointing out poorly written code in practically ancient software and attributing i…
Honestly why care? Everyone writes bugs -- the thing is that Quake works fine -- if some quick runners want to exploit a bug 32 years later to impress each other with runs, after having dissected the code to bits to find glitches, is that really a bad mark on anyone? I don't remember anyone complaining about lightning gun glitches when Quake was being played.
I’m not an elegant coder. My code isn’t perfect. It does run however and is pretty efficient mostly bug free. It does it’s useful thing and I can be proud of that.
Having gone through enough code reviews to know there is a huge amount of polish one can give code. It’s a trade off between perfect and Good enough.
I’m hopeful new languages and patterns leveraging libraries help make our code better or at least let us write more if it.