I meant 'I can hear it' regarding teleporter sounds 

for #3, func_illusionary will look solid but let everything pass through (players monsters projectiles). adding a clip brush will block players and monsters. (add a brush to the world and give it the texture "clip") 

you can('t) hear it, but you shouldn't?

You can dimm your shotgun light, but then tou'll need to alter the weapon.qc

You can use teleporting /players only, or /silent. 

thanks guys! editing quake c files beyond my level of expertise, but 2 out of 3 will do :) thanks 

I can hear it but I shouldn't (...) my gun is being lit from behind the closed door
Would thickening the walls and doors solve the issue? Is there any doc on minimum thickness to prevent that? 

You basically have to light around doors so that it looks good whether the door is open or closed. Alternate: for one-time doors, toggle the light on when the door opens. 

Oh and since you might not know this -- guns (and other models) are lit based on the floor below them. So the problem you actually want to solve is what light is casting onto the floor in front of the closed door. 

@metlslime dude! thanks :) worked like a charm. I made lights 'initially dark' and then linked them with the door switch. great stuff!

@Mugwump idk. google isn't very helpful when it comes to 20 yo tech with misleading terminology :) 

Heh, I was actually asking to the knowledgeable guys around here.

metl, great tips! 

This has been happening for awhile, and I found ways around it. Now, I need it more then ever, and I cannot for the life of me figure out why this suddenly is refusing to work.

No matter what I set -sunlight_mangle to from the command line, or from the world map properties, tyrqbsp always outputs:"sunlight_mangle" was set to -0.126998 -0.720243 0.6681998 from commandline" and I get no sunlight in game. No matter what I try, that always happens. tyrlight just flat out refuses to set the sunlight angle to what I want, and it happens on every single map I compile, and I can't figure it out. I've used the latest tyrlight, the previous version, and the previous version before that, and its always the same thing. I've even used aguiRe's jury-rigged light tool and it too is giving me weird sunlight angle problems.

Does anyone have any idea why this could be happening? Ask me any additional information that you may need, I'll answer it. 

Volume is pretty obvious – the volume of the sound, on a scale of 0 to 1. Attenuation basically means whether or not you want the sound to be played across the whole map, or to fade out over distance from where the sound is based.

float ATTN_NONE = 0; //no sound.
float ATTN_NORM = 1; //throughout the whole level.
float ATTN_IDLE = 2; //monster idle, pain.
float ATTN_STATIC = 3; //diminish very rapidly with distance. 

put it in worldspawn.

worldspawn

"_sunlight" "100" //light intension
"light" "15" //minlight
"_sun_mangle" "227 -57 0" //surround height 0 

watch examples of ericw!

http://ericwa.github.io/tyrutils-ericw/ 

Sorry, the diagnostic message is misleading ("sunlight_mangle" was set to -0.126998 -0.720243 0.6681998 from commandline").. it's printing out an internal version of the mangle vector, that's different than the format it expects from the worldspawn / commandline.

Here are is the proper format from:
http://ericwa.github.io/tyrutils-ericw/doc/light.html

"_sunlight_mangle" "yaw pitch roll"
or
"_sun_mangle" "yaw pitch roll"

Yaw specifies the angle around the Z-axis from 0 to 359 degrees and pitch specifies the angle from 90 (shining straight up) to -90 (shining straight down from above). Roll has no effect, so use any value (e.g. 0). Default is straight down ("0 -90 0"). Hope that fixes it! 

Compiling tools and TB2 coding!

Can I get an Amen? 

As I said, I already tried both options, from the command line and through worldspawn, and the result is the same. 

If you have entered compile settings in your editor options, they may be overriding your map's worldspawn parameters. 

Thank you Eric for explaining that, I see now what I have been doing wrong. It's not a lighting tool bug, it was entirely me. You would think having been mapping all these years I should have caught on to this from the start.

My embarrassing mistake was, the pitch angle was positive, not negative, so it was always shining straight up.

This is what happens when you become overly frustrated, you start to make little mistakes and begin to think its something huge.

Anyways, thank you again madfox and Eric, all is well. 

Is there a way in vanilla Quake to change where a message is printed to the player? The 'message' field on an entity normally prints to the middle of the screen, which is great for information about locked doors and things like that, but I'm looking for a way to make it print to the console/top left corner instead, like the ammo/armor/powerup messages. 

Not without a custom progs.dat (QuakeC, probably items.qc) unless I am mistaken. 99% sure. 

Somewhat surprising as well given the amount of things that are apparently possible through various entity hacks. Thanks for the quick reply, though. 

What do you need this for, anyway? Centerprints don't exactly hinder view and Quakespasm also prints centerprints to the console. 

There is a hack. Using the ammo_touch</a> as touch function in a custom info_notnull trigger, it will print "You get the" + whatever is in the netname field in the top left corner of the screen. This will not override the pickup message of the original item, so you'd have to make sure the trigger fires after picking up the item. Additional steps may be possible to hide the original message entirely. 

@Mugwump
I'd had a couple ideas for making a map somewhat unique without needing its own -game switch; just small things like alternate item pickups outside of the standard gold/silver keys and ammo boxes through either stationary brush entities that are killed upon touching it or fancier, rotating brushes (cloned from a func_wall using this fantastic hack) to imitate the actual spinning keys.

@negke
That's fantastic, exactly what I was looking for! Getting rid of the 'You get the X' part of the message isn't a priority, as I would have ended up typing it in anyway; using ammo_touch as the touch field on a DIY-brush-entity makes a one-time trigger that not only gives you the message with your choice of 'X', but also plays the ammo pickup sound and screen flash. A little bit of fiddling shows that if you use key_touch instead, it allows you to use the noise field to play any (precached) sound you want instead, including the various key/armor pickup noises. 

It says Radiant now has Quake support (I know Eric made is, I tested it) but when I download it, I can't configure it for Quake. It doesn't show up in the list of supported games and there's no separate gamepack to download because the site claims it's built in.

What gives?