QuakeC Bug List

[Dutch]

A while back, I had the entire list of vanilla QuakeC bugs bookmarked. It was a page on Inside3d. Looks like it's dead now, however. I even found a link to the same page that Seven provided in an older thread, confirming it's dead.

Anyone still have this list saved somewhere? Or know of a different website it's posted on? Tried digging around for it on the web but not much luck. Hoping to get it posted up in this thread here so it's easier for others to find.

[Baker]

First you must disable javascript in your web browser.

Then here is the link.

Quake Info Pool - Classic Quake - Quake Bugs

If you have javascript enabled, it will infinitely redirect to itself.

[Dutch]

Hot damn, that worked!

Thanks Baker. Never would have thought of that. I probably should've googled why a page infinitely redirects...I falsely assumed it was the website alone.

At any rate, finding the list just got a bit easier. Someone might stumble on this (now useless) thread. Lol.

[Mugwump]

Not useless if it explains a workaround for a bug. Gotta love the irony of a bug on a page about bugs BTW...

[Dutch]

Gotta love the irony of a bug on a page about bugs BTW...

Hahah yeah, no kidding

[MadGypsy]

You don't have to disable javascript (usually a pain in the ass). Just right click the link and save target as... Then open the saved file in your browser. It's probably something you should download anyway.

[MadGypsy]

I also found the bug. It was simple



urls = new Array('http://www.inside3d.com/qip/');

BUT

if ( check < 0 ) { changeURL(); }
and
function changeURL()
{...
top.location.href = urls[0];
...
}

There's only one problem. The name of the site is insideqc. See the problem? You go to insideqc and it keeps refreshing because it isn't url[0] ~ inside3d. This is really poor code. I mean like super extra terribly poor sad and miserable code. There is zero portability. If you are going to do shit like this there should be one Javascript object that supplies these values site wide OR a PHP file with these things defined and an ajax request can be made for the data. Hard coding stuff like urls into your script is super nooby. And the results of the page that uses this code is why. Using the php method, the site URL could be dynamically coded with PHP functions and changing your domain name wouldn't even require you to change your PHP. Everywhere on the site that is trying to do what the above script is attempting would never break.

[Dutch]

You don't have to disable javascript (usually a pain in the ass). Just right click the link and save target as... Then open the saved file in your browser.

Good to know. That's a neat work-around.

It's probably something you should download anyway.

No kidding lol

his is really poor code. I mean like super extra terribly poor sad and miserable code. There is zero portability.

Ironic, that it's a website dedicated to coding?? Not bagging on inside3d, there's a lot of good stuff over there. I just had to point out the irony

[MadGypsy]

@Ironic, that it's a website dedicated to coding??

It's not dedicated to good web design coding though. Programming for the web is an art. You can just slam a bunch of "it works" javascript together but then you end up with a bunch of shit to fix if you make just one simple change (like your domain name). I'm not bagging on the guys/girls at insideqc. I'm bagging on this terrible code. In the immortal words of Nahuel (with a twist) ~ I'm not trying to be mean but your Javascript is terrible.

@Good to know. That's a neat work-around.

It only works if the javascript embeds are relative paths. If they would have coded the fully qualified path to the javascript downloading the page would have still ended up endlessly refreshing. But with the page downloaded you can simply delete the javascript embed lines.

[enderandrew]

If anyone develops new bug fixes for vanilla bugs, please share them here. I'm trying to put together a good clean, bug-fixed base for future projects.

I see there is URQP as an unofficial patch, but it adds new gameplay modes, skin support, bots, etc. and not just bug fixes. I'll dig through that code, but I wish they had just broken out the bug fixes into individual patches.

[Dutch]

That page baker linked to provides fixes for the majority of bugs...or do you mean alternative fixes?

EDIT: oh I see. Yeah, you don't have to use URQP, just code in the big fixes yourself. They're right there in the right hand column on that page

[enderandrew]

That page baker linked to provides fixes for the majority of bugs...or do you mean alternative fixes?

EDIT: oh I see. Yeah, you don't have to use URQP, just code in the big fixes yourself. They're right there in the right hand column on that page

A couple have specific fixes in the right-hand column. A lot just say "fixed in the URQP".

[Dutch]

A couple have specific fixes in the right-hand column. A lot just say "fixed in the URQP".

Indeed. Been a little while since I looked at the list. Most of those are pretty trivial, some are pretty straightforward. If you have any specific ones you'd like to figure out, I can most likely help.

[Baker]

it adds new gameplay modes, skin support, bots, etc. and not just bug fixes.

I hate it when stuff does that.

Then again, since they did bother to fix the actual problems and do it for free -- it is not a terrible trade-off.

But yeah, sucks when a source code change includes things not related to actual bug fixes. Fortunately that QuakeC 1.01 should mostly stick to the bug-fixes only formula.

[enderandrew]

I hate it when stuff does that.

Then again, since they did bother to fix the actual problems and do it for free -- it is not a terrible trade-off.

But yeah, sucks when a source code change includes things not related to actual bug fixes. Fortunately that QuakeC 1.01 should mostly stick to the bug-fixes only formula.

I don't mind added features, but if your release is supposed to be patches/fixes then focus on that. Have two releases, one that is just fixes, and one with additional features. Or break out the fixes as patches so others can implement them in their codebases.