I understand what I say, I know that.
It seems I need to explain it more: trap_spikeshooter works exactly in the way you described, but it shoots too fast. It hard for player pass thru it without getting damage. Trap_shooter shoots slow (as I want), but it shoots always and triggering it just makes it to shoot faster (like trap_spikeshooter does).

So I want to know if it is possible to make it start to shoot only after triggering it and not from the time the has been loaded. 

the has been loaded.
the map has been loaded. 

I take it you are using a trigger_multiple to trigger the trap_spikeshooter, yes?

Just set the trigger_multiple's "wait" field to the time you want to elapse between spike firings. The trigger_multiple's default wait is 0.2 secs, so if you don't set it, the spikes will be launched at a rate of 5 per second. 

I haven't thought about it in a such way. I'm going to check it right now. 

AFAIK, you'll get the vis leaf warning also when the map leaks (which is the normal reason why the amount is so high). Having a sealed map with >8k leafs usually means >24k portals and then you'll have a fullvis nightmare ...

If you can't sort it out, send me the zipped map and I'll take a look at it. 

I have this 'system' that I use when working on a map: I compile regularly (like every 15 minutes) using Qbsp -nofill, and Light, which also saves the work done so far. Every so often I will save the WIP with a new name, in this case SM40_mw1.map, SM40_mw2.map etc. Occaisionally, I will try some major change that I am not sure about and will use the file test.map so if it doesn't work I can just dump it and continue where I left off.

So, I am moving a piece of terrain that is on a grid of 1536 x 1536 x 768 - this is big so I use test.map to try it out first. It's a success and I am so pleased that I continue leak testing (post 2969 above) and resolve every leak. Then I go and have some lunch.

When I come back I load the last map (SM4_mw9.map) and continue polishing. I add my 12 extra brushes, compile and... get the vis_leaf problem. WTF, it worked before lunch? But of course as we all know now, the last map I saved was called test.map and had all of my leak fixing in it - I had forgotten to save it with the usual series name.

Oh well, at least with the system I use, when I retraced my steps back to the last good map and then worked forward, as soon as I got to the need to move the piece of terrain I realised what had happened. Only wasted a couple of hours and now back on track, no leaks, full vised, so polishing continues.

There's a moral there somewhere... 

The moral of the story is: mapping editors need a built-in database system for tracking changes. Something like CVS or Subversion (which are used for tracking changes in big software projects). 

There's a moral there somewhere...

Always Backup Your Maps*










*even if you are easy to confuse 

I am getting to the phase where I should be adding gameplay to apinaraivo.bsp and I am in need of QuakeC help. I need to port the Mega-Enforcer for Zerst�rer and something from Scourge of Armagon over to the ID sources. If anyone would be so kind as to do this for me (should be pretty trivial for a person fluent in QuakeC, which I am not), please get in touch. My eternal gratitude is assured. 

What the heck, I'll sort you out ;) What is it you need from SoA exactly? 

I sent a email to the address mentioned in your profile. 

sorry - could you resend to:

bdwooding - at - gmail - dot - com

thanks :)

/me needs to update his profile 

[nt] 

Have you received my last three emails? 

don't worry, I'm getting round to it (blame christmas ;) 

Just for kicks, try compiling the hipnotic sources with FrikQCC, put a monster_scourge into a map (the mechanical scorpion from SoA), compile and run the map. Notice how after dying, no centripede doesn't have any death animation whatsoever and just "stops" with his body becoming non-solid (as in, you can walk through him). The original hipnotic progs,dat file however, works just fine.

After pulling my hair out for an hour, I realise that what we have here is a bug in THE BLOODY QUAKEC COMPILER! I downloaded some bizarre ProQCC release from 1997, it compiled the code and everything worked as advertised. Ugh. 

I'm currently making a quake sp map and Im quite confident I will finish this as alot of the structure is in place.

Having never really got this far when creating a map, it leaves me not too hot with entities so here goes..

I want two doors to open reveiling a monster behind each (already in place), but I want the doors to only open once the four monsters that your fighting have been killed.

Secondly I want a button to trigger a door open only once two of the buttons have been pressed, I've seen this in some maps and it has an on screen message "1 more left".

Also one other thing, is it possible to make a monster or a set of monsters "spawn" as you pass over a trigger or a button?

If anyone could shed any light over these I would be most greatful. 

I want two doors to open reveiling a monster behind each (already in place), but I want the doors to only open once the four monsters that your fighting have been killed.

Secondly I want a button to trigger a door open only once two of the buttons have been pressed, I've seen this in some maps and it has an on screen message "1 more left".

You need to you use trigger_counter. Create a trigger_counter, give it a targetname (counter1 for example), fill the 'count' field with the number of monsters/buttons you need to activate it (4 (monsters) or 2 (buttons) for you), and then fill the 'target' fill as for usual trigger. Then target buttons or monsters to that trigger (for example 4 monsters should have 'target' field with 'counter1' value.

Also one other thing, is it possible to make a monster or a set of monsters "spawn" as you pass over a trigger or a button?

You need to create a room somewhere, place monster there, cover him with trigger_teleport and give this trigger_teleport any targetname. Then target your trigger or button to that teleport.

I hope it's clear. 

I want two doors to open reveiling a monster behind each (already in place), but I want the doors to only open once the four monsters that your fighting have been killed.
Target each of the four monsters to a trigger_counter, give it a "count" value of "4", and if desirable set spawnflag 1 to make it not print out "there are more to go..." messages when you kill the monsters.

Secondly I want a button to trigger a door open only once two of the buttons have been pressed, I've seen this in some maps and it has an on screen message "1 more left".
Exactly same as above, just set "count" to "2" and target trigger_counter with the buttons instead of the monsters.

Also one other thing, is it possible to make a monster or a set of monsters "spawn" as you pass over a trigger or a button?
You have to make this happen by creating a small box outside the map, place the monsters you want to spawn inside, place individual trigger_teleport over each monster, give the teleporters a common "targetname" like, say, "spawn_monsters" or something, and target each of the teleports to their own info_teleport_destination placed where you want them to appear in the map. Triggering the teleport(s) will now spawn the monsters at the info_teleport_destination(s). 

VPhysics Penetration Error! 

heh 

The counter thing worked great and I can complete some more of the set pieces now, thanks. As for the monster spawning haven't tried that yet but sounds easy enough.

I just wonder if the trigger_counter needs to be an entity that's pressed, passed through or touch by the player or can it reside anywhere within the level? 

I just wonder if the trigger_counter needs to be an entity that's pressed, passed through or touch by the player or can it reside anywhere within the level?

No, it's brush-entity, but you just vreate it somewhere, no matter where, it doesn't need to be touched. 

Is it possible to set it so that once you've hit a certain monster to a cetain % health left, you can make it teleport away before it dies.

e.g. Just like spawning monsters into a level but spawning this particular one to a different location triggered by it reaching a certain set health level, if you know what I mean. 

afaik only death of the monster can trigger anything.