Here's a tutorial from 69th vlatitude. It tells how to do it and where to get the free software that you need to do it.
http://www.vlatitude.com/tutorials.php?tutID=48
Forum posts
squadmaker? If you are killing monster_human_grunts, you can have each grunts death trigger a separate hidden func_button. Have each func_button trigger the multisource. That works.
Captain P, I tested the trigger_transition; it worked perfectly, and it was easy to use. Just place it over the area where the player will be during the level change and name it the same as the info_landmark. It prevented the other monster entities from being included in the level change. I wish I had known about this earlier.
I had this problem in Minimicus. After you kill the gonarch in the kitchen, the level changes to put the player back in the lab. But sometimes there were baby headcrabs that were still alive and they came through the level change with the player, very annoying... I solved this by fading out and teleporting the player to a hidden pitch-black room in the same map, THEN I triggered the level change.
If you are using a wad called cs.wad in hammer, you also need to place that wad in your cstrike folder.
The Tankrocket tutorial is the one you are looking for.
"If it's not Scottish, it's CRAP!" - quote from an old Saturday Night live skit. Oh, sorry, this thread is about a lab compo....
Did you close hammer first and run your bsp1 from the HL console? Sometimes hammer messes up the level change.
Press F5 in-game when you want the screenshot to be taken. You can take as many as you want. The files show up in your Half-life folder (or cstrike folder for cs). They will be a bmp file and will have the name of your map with some numbers added at the end. for instance mymap0001.bmp. In order to place a screenshot into the map vault you have to convert it to jpg format. To do that, I use MS paint to open the bmp and just save it again as a jpg. Now let us admire your beautiful map. 
Use the scripted_sentence entity and the mouth of the person speaking moves automatically. If you are using your own wav files, you'll need to point to them in your sentences.txt file.
It seems as though your senteces.txt file has a problem, or you are perhaps using a mod that has an altered sentences.txt file. I tried an experiment and deleted the BA_Hello group from my sentences .txt and I got the error you got.
In my case, it did list the wads in the order they are listed in the texture configuration box.
I don't think there is a way to expand that box. However, you can run a compile and your wads are listed in your compile log along with the paths. You actually only need to run the csg part of the compile to get this info, so it can be run very quickly.
Strange problem... I don't have an answer, but here is what i would do: Start your 1st bsp, bring up the console and type 'developer 2' (without the quotes). Then go through your troublesome changelevel area. After the problem happens, bring up the console again and take a look at the messages there. It may point you to where the error is occurring.
You can control the length of the drip by using the env_beam entity instead of the env_blood. It's more work to do it this way though. You'll have to set up the start and end points, find the right sprite to use and trigger the env_beam when you want the drip to happen. You could also look through the example maps, you'll find several ways of dripping in there.
I'm not sure if Vassy said this above or not, but it sounds like you have something triggering the camera a 2nd time. Triggering the camera once turns it on, triggering it again turns it off. Did you have something else triggering the camera before you started targetting it with the multimanager? If so, it is causing the camera to shut off now.
Put it in the map vault. Others will see it and give you comments on your work.
That 'every other time' problem means you need to tick the 'not toggled' flag on your ambient_generic. Then it will fire every time. Also make sure the multithreaded flag is ticked in both your multimanagers.
You need to add just a few things to make this work. Add a trigger_autosave at the beginning of the level, it's a brush based entity; just place it so the player starts within the trigger_autosave. You'll also need a player_loadsaved, which is a point-based entity; just place it anywhere in the map and give it a name. You are already having the player fall through a trigger_once which targets the env_fade. But now you'll need to make the trigger_once target a multimanager instead. Have the multimanager target the env_fade and the player_loadsaved. That way when the player falls through the trigger, it will target the multimanager and the screen will fade and the player will respawn at the last save point.
This is a common problem. Once you name the light, the HL engine ignores the appearance property. One way to solve the problem is to use a multimanager to turn the light on and off to give the effect you are looking for.
More than likely MissioN finished reading the tutorial and figured out why his decals were disappearing in-game. Since that problem was covered in the awesome decal tutorial that TWHL has.
Cool! Leave it to me to find a ridiculous solution that actually works. 
Have each trigger_multiple trigger a separate func_button that triggers the multisource. Let each func_button reset after 2 seconds... or whatever time you want...keep the time short though. When either of the buttons resets, that will turn off your multisource and it will be ready for the next time both trigger_multiples are triggered.
Go for it! yes, you can use it.
My map from the 'trapped' competition had a vending machine that released snarks. The rmf is included in the download if you're interested.
Name the env_shooter to something else and target it from the trigger relay. Having them named the same is probably hosing it somehow.
I've posted some suggestions in the comments for the map you posted. Also check out the multimanager tutorial on this site. Remember, NO CAPITAL LETTERS. Let me know when you've got it working.
It sounds like the model falls out of your map as it's loading. Place it higher off the ground in the rmf.
Double check the names of the lights in both the multimanager and the light entities themselves, make sure they are identical and don't have any capital letters. You'll get this solved, it's just tough at first. Multimanager problems usually mean there is a small detail that's been overlooked. If you still have trouble, post the map in the problem vault and I'll have a look.
Placing a negative value in the x scale box produces a mirror image, not a 180 degree flipped image. Then you just have to center the texture and it looks fine. Align-to-world only works some of the time. But if it worked in this case, that's all you needed.
It's funny because it's true. 
I put an example map in the vault for you. Let me know if you have any questions about it. I liked this challenge; good question.
Caleb, nice avatar! Short surfaces means there are too many surfaces for the engine to draw in software mode. Another symptom of this is black patches that show up in your map, usually in the distance. You can fix it many ways....by taking some detail out of your map, stretching your textures, and vis-blocking. Read the R_speeds tutorial by Andy on this site. That will help.
I found TWHL when I was looking for HL contests and ran across the chopper challenge. Back then we all had wood-fire burning computers not these new-fangled electronic contraptions. And the internet was just tin cans hooked together with string!
BTW, esmajor, all the old contest entries are still available for download on the competitions page.
BTW, esmajor, all the old contest entries are still available for download on the competitions page.
21 The lowest so far! WooHOO!!
Check your configuration in Hammer and your compile log. Your new map isn't getting copied to the right place, or isn't getting compiled at all. Then when HL opens, the old map is still in the maps directory and that's why you don't see your changes.
Example map posted. The door stays open until the player leaves the area. Let me know if you have specific questions about how it's done. Also let me know if you've figured out an easier way.
HEY! Am I going to have to separate you two?!
I figured it out, but I'll be damned if I know why this happens. It seems as though the ammo cannot have a world brush intersecting it anywhere. If that happens, the ammo does not appear. The rifle doesn't have this problem. I was able to get the ammo to show up properly by selecting the cabinet and turning it into a func_wall. Although I had to leave the bottom shelf as a world brush otherwise the ammo kept falling through it. Just make sure the ammo is a little bit above the bottom shelf and it works if the rest of the cabinet is a func_wall.
One problem I've noticed with placing headcrabs on boxes is, you get the yellow things if part of the crab is over the edge of the box (in the top view). Keep him away from the edge and it should fix the problem.
I've wondered about that stuff myself. heh heh It would have made the maps a lot shorter if the grunts stayed big. Anyway, to stay on topic, I will post an example map of how the technique is done for making a door stay open while the player is near it.
You have the 'ignore groups' button active on the tool bar. Turn it off and your func_wall will be OK again. As for the completely invisible problem, your render amount needs to be set high, 255 is the max. If you leave it at zero, the wall is invisible.
That is the HL engine showing you that the monster is placed too close to a wall or inside the floor, or too close too any world brush really.
I was able to solve this problem when making the suit doors in Minimicus. My solution was a little complex. The door is set to 'toggle'. Two trigger_multiples in front of the door, each with their own master, so that only one of them is active at a time. The one closest to the door is active initially. When the active one gets triggered, it targets a multimanager that opens (or closes) the door and switches the masters. The trigger_multiples are set far enough apart so that the player can't touch both of them at the same time. As long as you stay in the area near the door, it will stay open. It only closes when you leave the area and pass through the other trigger_multiple. If you set it up properly, the player can't mess it up no matter how he moves around. I used the same setup for the cricket sound in the basement of minimicus. When you get near the cricket, he shuts up. Then when you walk away, he starts chirping again. I would be willing to post an example map for the doors if anyone is interested.
Does lighting work correctly when running a fast vis? I never tried it. Try turning on full vis and see if that fixes it.
Where can I get a copy of 3D studio Max 6 for free? That would be cool... (Not just the 30 day free trial) :
Worldcraft is free; 3dmax is $3500. I rest my case.
The space could cause problems. Be safe, use the underscore instead of a space and don't use capital letters at all in entity names.
I never knew that... I just tried it and it works great! Always glad to learn something new.
I think it would require coding to do it this way. One thing you could do instead is use the monster's trigger property. You could set it to call the retreat scripted sequence when the monster has received 50% damage...