Thanks for answers

2. I understand, but I would like to know if it's acceptable to leave it like it is. I didn't observe any problems with sound during the game

4. Can monster walk without path_corner? That would be interesting to me. 

2. You can leave it like it is, but you will have for sure some sound problems. For example, when I had this warnings, some teleporters, or exploding grenades, have no sounds... so the game loose a part of its functionality, and it dicrease its quality..

4. No no no, walking monsters cannot walk without path_corner items. I mean, that path_corner are perhaps not correctly placed: I don't know if I'm right, but for example in a "L like" corridor, you need at least 4 path_corner (1 at each end of the corridor, and 1 or 2 at the L angle... it depends if you want the monsters to turn back at the end, and return at it starting position, etc.. etc.). If you missed the L angle path_corners, monsters should try to path throught the wall from "end to end"...As far as walls are solid, it's obviously impossible, but I'm not sure of the way some engine work...
Well, this last problem seems to be tricky to solve, and maybe I don't have the good knowledges.... I was just trying to have some constructive idea in order to help you. 

If you get an error unique to one particular (obscure) custom engine - in this case 'ezquake' - don't worry about it, just don't use that engine. No-one around here will use a custom engine anyway if they can help it (with the exception of maybe FitzQuake, and a couple of others). 

Define custom engine. I'd wage that the vast majority of people here would NOT be using vanilla gl/soft quake. 

Thanks for your suggestions: I'll let you know what happens. 

Jago: Are you fucking retarded? The vast majority do. And those that don't are either morons or use FitzQuake. 

In that case the vast majority *IS* fucking retarded because vanilla software- and glquake don't run all that well (and in many cases not at all) on modern hardware and operating systems and lack a shitload of features I and many other people take for granted. And there is more than 1 engine port worth using. 

oh, ugly 24 bit textures and blue lighting effects on lightning bolts are features? 

I use Fitzquake because I cannot use the original Quake engine with WinXP and I would not want go back to Win98 or earlier. I am surprised that so few(?) users are with WinXP: I accept that everyone else maybe Mac or Linux.

Has anyone got original Quake to work with WinXP? I am sure I have asked this before and got negative replies.

Mind you, I am deleriously happy with Fitzquake (until I have problems). I am also using aguirRe's GLQuake - I threw 46,000 clip nodes at it yesterday and it didn't bat an eyelid. 

i have winxp pro and glquake works perfectly fine. all you have to do is delete the outdated opengl.dll file. 

glquake is uglyquake 

YOU are ugly. 

that came with the game will not run (after the later releases). GLQuake always had a horrible water-warp, but as I said, I have used aguirRe's GLQ. But I will stick to Fitzquake at present. 

You know the famous E2M2 bug, whereby if you shoot one button and then bunnyhop across the gap, the trigger inside the door will hang quake if you are on easy skill?

Well, this is a request for some hardcore engine coder dude to give me as detailed as possible an explanation as to what exactly is happening here, as this situation is rather relevant to what I am doing atm.

I know it may have been posted on this board before, but in the absence of a search function, I'm a bit clueless sadly. 

in fitzquake at least, that door's trigger forces bridge to extend, and the other button is still red...
w3rd indeed 

I think it's something like the trigger wakes up a fiend which isn't present on the map in skill 0. I've seen a detailed write up somewhere, but I can't find it :-( 

Take a look here: http://forums.quakesrc.org/viewtopic.php?t=3664&highlight=e2m2 

aguirRe, yes there's some helpful info in that link :)

I guess this is related to the QC "rule" that you shouldn't call remove() inside a touch function. What I don't get is why this rule is broken in several places in the QC, eg. in spike_touch(), remove(self) is called directly inside the function.

Is this effectively a "bug" in the original QC, or are there situations where remove() is legal to call inside a touch function? Is it only SOLID_TRIGGER entities that you're not allowed to remove() inside touch functions? 

i've removed many ents from within their touch functions and never noticed a thing.
where is this rule from? 

it happens a lot in triggers.qc; here's an extract from the multi_trigger() function:

// we can't just remove (self) here, because this is a touch function
// called wheil C code is looping through area links...

self.touch = SUB_Null;
self.nextthink = time + 0.1;
self.think = SUB_Remove; 

now that you quoted that, i do remember seeing that. i would assume it only applies to triggers since i've seen it done and have done it countless times on non trigger entities. 

i would assume it only applies to triggers

Great, if we can definately confirm this, then I will be a happy camper ^_^ 

01:32:12 Jago : My map has 1 instance of item_spikes and it shows up ok
01:32:23 Jago : I try adding 1 more, it doesnt show up
01:32:37 Jago : I try moving it around the map, doesnt help
01:32:54 Jago : I try copying the existing and working entity and move it around, no good
01:33:00 Jago : WTF? 

02:00:00 Jago : figured it out
02:00:43 Jago : apparenltly, item_spikes doesnt like being only 16 units above the floor
02:00:57 Jago : moving it up to 32 units above floor fixed it
02:02:28 Jago : weird that it works fine for item_shells 

odd because i usually put item_* 0 units off the floor.

are you using worldcraft? maybe you need the fixed entities list thing.