InsideQC Forums

I still have a CD of the full version of QED2, but it crashes on XP so I don't know if it's going to be of any use to you.

It's possible for stock ID Quake to have up to 4 games loaded simultaneously - glquake.exe -rogue -hipnotic -game mygame will load ID1, rogue, hipnotic and whatever mygame is into the filesystem. Now, some may think this is a cool feature, but it makes me shudder with revulsion. There are all sorts ...

Actually, I think I may have misunderstood the original post. :oops: :lol: But the ability to host multiple server instances is something intriguing, don't you think? Yes it is, and I'm going to do it because it works :D :D http://www.quakeone.com/forums/showthread.php?t=3803 I'm really tired of se...

Actually, I think I may have misunderstood the original post.

But the ability to host multiple server instances is something intriguing, don't you think?

You'd need a rewrite of the server code in the engine to properly support this. Right now there are a couple of structures that hold server info, with only one instance of each being active at a time. Ideally, all of the sv_*.c files would need to convert to C++ (not difficult, I've personally alrea...

I've never been entirely convinced that SoA was better. All the consecutive base levels at the start seem to have dated incredibly quick (TBH they felt dated by the time I'd bought it, when I'd already played Q2), and a lot of the new features are gimmicky hacks more than anything else. The weapons ...

There's definitely at least one in hip1m2 that's a pool you can jump into - the room with the rotating "bridges".

Errrrm - doesn't Hipnotic have moving water brushes?

xcode or something similar, I'd say, would be the IDE of choice, although given OS X's roots gcc or a mac-specific variant (I imagine there is one) should work fine too.

That confirms my suspicions that a lot of those updates weren't really necessary. I do hope you caught the parentheses I'd left out above, by the way...

With Objective C and Cocoa you're looking at either a rewrite or an emulation layer.

I think this slight sidetrack has highlighted one absolute must-have for any proposed new protocol. Whatever comes out of this discussion absolutely NEEDS to be documented properly. It might be the greatest protocol in the world, but if it can't be implemented quickly and easily in existing codebase...

Point me at the info and documentation on CSQC and I'll happily support it. :D Right now I'm having a hard time finding anything useful; the best I can find is this: http://www.fteqw.com/wiki/index.php?title=EXT_CSQC which looks like a journey through trial and error - not my idea of fun. :( Same ap...

Let me revisit it, it was late at night!

The intention is to let the previous state on the server get a little bit out of date, so that when the next update comes along it's forced roughly 3 times a second for each critical item.

I'd tend to favour keeping as close to protocol 15 as possible. It may not be the best option technically, but it does (hopefully!) have the advantage of making widescale adoption a lot simpler, and therefore more likely.