A round about theory could be to keep the monster in the same place, use a trigger_once covering the enemy to count the damage and to trigger the item spawning, and then pass the damage to the monster with a trigger_hurt. It doesn't seem to be feasible but its an idea. 

...can it be set to follow it, so that if the monsters move, when he dies the item spawns on him? 

http://en.wikipedia.org/wiki/NaN 

http://en.wikipedia.org/wiki/Naan 

you would RTFM. Necros and I went through a lot of trouble to provide TB with proper docs. The autosave is clearly explained in there.

Crashes: Well, shit. There's your explanation. 

 

 

I was careful enough with the other items which showed up this time by placing them somewhere else or giving them more space, but I tried the same thing for the quad damage (located inside a corridor between 2 closed doors)by extending a little bit the width of the corridor, but still no dice.

Is it related to entity limitations? 

letting someone else have a look at the map file. 

http://www.mediafire.com/download/25ey4kv1v9q1vz4/gravelwep.rar 

But its just down to the bbox. The drop call from items.qc really sucks and should only have been applied to bsp items like ammo.

It's still too close to a wall is first guess - effectively they're fatter than a player in id1. 

 

That should have been the first thing to try before resizing the space if only because it was the easiest fix. Unless it's in the players view right as the level starts it's a good idea to raise everything inside a bounding box well off of the floor (even more than 16 units if you can) because of how Quake deals with them. Sometimes the item gets put in before the clipping hull is put in (just by milliseconds) but items will start to fall right away until they hit that hull and if it's past that hull by even one unit it will fall through and disappear.

It has to do with where they are in the .map file that the BSP compiler will use to determine the order of placement and most editors do that sort of randomly (I'm sure that there is some sort of logic to it but damned if I know what it is). 

Hi, I use QuArK but when I compile map with TyrUtils qbsp, the textures are upside-down. I tried -oldaxis option but it doesn't seem to have any effect.

Maps compiled with Bengt Jardrup qbsp and hmap look OK, but these tools don't have func_detail, which I need. Is there some way to flip the textures back in TyrUtils qbsp or some other way to get around this problem? 

Lawrence
use these tools:
voidspark.net/projects/bjptools_xt/

They have all you need. 

-oldaxis 

Jury-Rigged BJP Tools work OK. Thank you. 

1) How does one make a crusher in standard Quake (i.e. no Quoth, etc.)?

I tried to do it with a func_door, but the door seems just to stop when there is a monster in its way, instead of, well, crushing said monster.

Then I changed the func_door into a func_train and placed two path_corner entities in the map, but I cannot get that setup to work properly at all -- when the crusher gets triggered, it just disappears instead of moving downwards. Plus I cannot figure out exactly where to put those path_corners in TrenchBroom (I found some online guides, but they all refer to other editors, with 2d views, e.g. this one).

2) Also, how do I get something trigger-able with two buttons, i.e. that both buttons are required to trigger the thing? I've got two buttons set up with the same target, but now they trigger the target separately (i.e. if I push one I don't need to push the other).

Thanks in advance! 

Targeted func_door and give it a 'dmg' value.

Enjoy! http://quakewiki.org/wiki/Getting_Started_Mapping 

Thanks very much ijed. That clears up the first issue.

I still cannot figure how to make two (or more) buttons work together, though (there's nothing about that on quakewiki.org -- not that I can see, anyway). 

Trigger_counter does the trick, it�s all explained in the wiki. 

Thanks, mfx.

There is no entry for "trigger counter", though (just a blank template) and no mention of trigger_counter on the func_button or func_door pages. I would never have thought of looking up "trigger counter" if you had not mentioned it.

And I still don't know what to do with it... 

2 buttons, both targeting the counter.

Trigger_counter is a point entity, and has the following keys:

targetname: Used to target the counter.

count: Numerical value of how many buttons do i need to press, to activate(in your case 2). Basically how many events it needs to be activated.

target: What should be "fired" when count is reached. In your case the targetname of the door.

message: This text is printed on the screen when the counter fires. Like: A door opens nearby, hoohoho..

delay: delay in seconds before the counter fires.

Spawnflag 1 turns off the messages of the count. (Only one more to go) 

Thank you so much. You have just made my life a whole lot easier.

I've been scratching my head over this for a couple of hours now, trying various things that did not work and trying to find the answers elsewhere before asking here.

What is on quakewiki.org is great and has helped me tremendously before (the Getting Started Mapping guide is great), but there are many gaps... 

is now you create an account there an update the wiki.
I suck at formatting.