Yes there are nobot and nohuman keys you can set for info_player_deathmatch to prevent either bots or humans from spawning there.

The "5 frags opens a door" think is an interesting one. Any idea how he did this?

Well, I tested it out on another map as well - meant for TDM a la King of the Hill (where the teams would attempt to control a certain area in the center of the map that would cause them to score a point if there was a player from the team within that area). It worked in vanilla 1.32 q3, so I say give it a try.

Something like a controllable timer that activates or deactivates other entities would also be great. This would allow to create - for example - jumppads that are disabled and activate every 20 seconds for 5 seconds.

Add new key 'type' to func_rotating, func_bobbing and func_pendulum. Configures the type of movement, allowed values 'linear', 'sine' and 'gravity'.

You're welcome to pull the most recent version out of SVN, import it into some github account somewhere and explain to me how that shit works

Funnily I've been playing around with those TR_GRAVITY, TR_LINEAR and TR_SINE constants as well for func_rotating but if I set

ent->s.apos.trType

to anything other than TR_LINEAR weird things happen. With TR_SINE the brush simply disappears, with TR_GRAVITY my brush starts spinning around a different axis like a madman.

So I'm not exactly sure how that's supposed to work...

- func_conveyor - Self-explanatory, makes brushes move along the func_conveyor in a mapper-specified direction and speed. Could be great for warehouse environments.

This is just great.

Can I trigger something from a bots death and/or spawn?

So, when I spawn him, I can disable the spawn. And when I kill him, I can open a door?

Also, a "key" item would be super, that can be spawned, picked up and used for triggering something.

love it! its great work eraser. One thing: I get huge lags when a bot spawns.

An entity that would force holdable_teleporter to a specific spot would be fun.

- When you first approach the jump pad, it`s not playing it`s flashy effect, which is cool when you turn it on and it starts flashing. However, if you restart the map (which some players will inevitably do if they are stuck) it`s still playing the effect even when it is off. It`s a pretty minor visual issue but I thought I`d let you know.

- The green armor skin is way too bright and oversaturated. Reduce the brightness and saturation a bit, so that it resembles QL`s green armor entity a bit more. (of course don`t rip the actual skin from QL, you might get into some legal trouble for that) Once again, purely aesthetic.

If you spawn the bots and you restart the level, the bots will still be there, fighting. Probably won`t always be a bad thing but in some cases this could be unwanted if the player is supposed to backtrack and shouldn`t meet the monsters until after he comes back.

Here`s some more suggestions, once again you don`t have to use them, these are just to spark your creativity:

If someone wants to make a multi-level mission where the player may have to travel back and forth between maps, ala Quake 2, I think it would be neat to make it so that it would be possible to go back to a map and have all the entities be what they were as you left, i.e dead bots are still dead, weapons that you collected don`t respawn (unless you specify them to), etc. I`m not sure how difficult it would be to implement though - if this is out of reach you could always do a info_player_checkpoint entity which saves your current position so you don`t have to start all the way over if you die / get stuck.

What if you want a bot to fight on your side, as with the case of assisted missions? Perhaps have a goodguy spawnflag similar to the one in Lazarus. It could use code similar to what makes teams in TDM / CTF function, but without the ugly blue / red skins, etc.

- func_conveyor - Self-explanatory, makes brushes move along the func_conveyor in a mapper-specified direction and speed. Could be great for warehouse environments.

- func_pushable - Basically a brush in which force can be applied to make it move; affected by gravity. Level designer can specify the mass of the brush, which will affect how fast it can be pushed. Perhaps you can "recycle" the code that makes gravity work upon the player and apply it to brush geometry. You can also specify whether getting hit on the head by a falling func_pushable will result in death. (indiana jones style? lol)

- Cooperative mode?

Good luck with your project, I just know it`s going to be the next big thing.

The mod needs a display text thing too... or maybe that's already possible.
like info_text or something.

I always found the key/value triggerFirst for triggers very handy in SP. It is simply a condition where this trigger doesn't fire until the trigger specified in the key/value pair has been tripped.