...a couple of the original studies for his egypt texz set should do it. 

Or at least be muted. Nothing worse than lying in bed and hearing their buzzing near one's head. 

So true neg|ke. But the worst I have ever seen is while camping in sweden/norway, during summer near a lake, it�s like the end scene of �300�, only with mosquitos instead of arrows :( 

That's what you get for camping! 

to add to death match, stay in one area
for more then five seconds mosquitoes buzz around you and nip hit points. 

In well-designed maps, camping is discouraged just by the fact that it is an inferior strategy. If camping is a good strat on a map, then it probably needs worked on :o 

does anyone know/remember how this was done in doom?

was it only pure wall following code, or did monsters actually search through sectors to work out paths? 

it was sector based. Google "nodes," "ssegs," and "reject" with regards to doom wads, there's probably a good explanation.

This explains it cursorily:
http://www.gamers.org/dhs/helpdocs/dmsp1666.html 

you're right though, it doesn't really go into much detail about it. but thanks all the same. :) 

it always just looked like they walked towards to the player and that was about it to me.

If you run through a level with noclip mode (idspispopd in doom or idclip in doom 2) and then look at the automap with all objects displayed (iddt - type multiple times on automap screen until monsters are visible) then you will notice the monsters just seem to walk towards the wall closest to the player and stumble around a little bit. A monster far away will pretty much never find the player unless a straight corridor exists that connects the monster's location to that of the player. It doesn't seem any different to Quake in that regard. 

i'm actually more curious to know how pathfinding works in quake, tbh. in doom, lines and sectors were put down as part of the map file, in quake, none of that exists, and all quake has to work with is a giant, flattened mesh... it's like magic. :( 

There isn't much to it in Quake. As has been said already, they pretty much just head straight for the player... even if there are walls in the way.

Sure, this means they're headbutting walls and trying to burrow through solid geometry half the time, but the fact is the player doesn't actually see that most of the time, so it doesn't really matter. 

I always thought the Nehahra solution was nicely done; the monsters head for the last place they have seen the player, instead of where the player currently is. 

...following the interest generated at my local e-cafe, during our two coop sessions through Travail, the owners are considering putting Quake on their LAN permanently (but especially for a retro marathon). Seems people are craving some of the coop action missing from newer games. What's the story with licenses? Do they need to purchase a registered copy of the game for each machine in use? Is one for the "server" enough? 

I strongly suspect there needs to be one license per machine. Otherwise, people in 1997 would have downloaded the whole game from a single netquake server, legally!

It'll cost about... 5 USD per seat, I think. :)

You could have them contact id, too. 

and pose as netcafe owners whose customers are always complaining that no games released since 1997 have stood up to quake coop. 

There's alot of interest in Q1 lately - new faces, servers and forums, not to mention mods.

Not exactly a ressurection, but nice to see that the wealth of SP and COOP material made by the community over the years is still earning kudos. 

Again I've got this problem where I can't login with opera. :(

Cookies are enabled for www.celephais.net, all other sites work fine.

Pressing the login button always just brings me back to the login page. 

that was me :/ 

Did you make sure "referer logging" is enabled? 

Of course not. You should write a notice on the log in page about cookies & the referer.

Thanks for the help though 

You should have read the FAQ page. 

and never had trouble with func, at least if I remember correctly. I guess I haven't toyed with the settings enough.
I wish they would fix a couple of long standing bugs though.

For example when closing tabs it very often lags and then closes the tab I switched to after "closing", leaving the tab I tried to close in front. Luckily there is the trashcan but it's annoying still...
The other "feature" is the lack of possibility to change to the left tab after closing the current tab. It just switches to last open, which sucks if you like to open lots of windows and then go through them, for example when browsing a forum.
And then of course are the random 15 sec freezes every 10 minutes or so.
Overall it's still ahead of firefox, the tabs=windows approach is just so much more natural. 

hm, don't have that lag influencing what tab gets closed - then again, i think im using the beta builds.

might try setting prefs > tabs > c-TAB order to something different than recently used for the left of closed tab issue. or just use 1 & 2 to cycle left and immediately right before closing�

no freezes at all here


the most annoying bugs are that it takes ages to save prefs and the localhost cookie bug for me. also, with 50+ tabs open, it seems to hang sometimes for split seconds, which is still annoying. 

have a Q1SP pack called Building or a link to it? It was reviewed at tenfour in 2002 but it seems broken.