is just a nice light effect.

The effect 3 seems kind of broken. 

Is a combination of 1 + 2.

And I don't think 1 exists? 

The values are 1 (particles), 4 (artifact glow), 8 (muzzleflash glow) 

If this belongs here, but is there a way for me to force an entity to be fullbright without using fullbright textures?

Specifically I want to use it on windows, but using water textures won't work because they have a specific pattern I want to maintain. 

What sort of entity? If it can be modelled with brushes, then an external bsp model will do it. 

i think so??
basically setOrigin() the entity to an area where it is bright, then manually change .origin to the new place.
I've never tried it though. 

It's a func_breakable, or to be precise, various of them. The external bsp should do it,since resting the origin sounds like it'd be fiddly across this many entities.

I forgot about external BSPs, those should do the trick well enough. I suspect there'll be a problem with collision though. At least there was with expanding door triggers when I tried instancing their BSPs a while back.

Thanks guys. 

actually no! external bsps can have perfectly working collision; several of the sarcophagi in ne_ruins were external bsps. 

Like I say, it was only the trigger bbox of the door with a weird offset, the door itself was fine. 

The following keys can be used on any entity with a brush model:
"_minlight" "n"

Set the minimum light level for any surface of the brush model. Default 0.

http://disenchant.net/utils/ 

:} 

Thanks mech, that looks to be an even easier solution. 

Want to know what is the bsp2 standard now? I've read about two versions out. Any place to get the specs. map limits and such? What compilers, engines and editors. The info seems scattered around. A web page with current info would go a long way towards moving things forward. 

https://www.quaddicted.com/tools/bsp2_format

2PSB is deprecated 

Of course the differences between BSP2 and 2PSB are rather tiny so you can still use them as a guideline.

Why is 2psb deprecated when there is very little difference between it and bsp2? Doesn't make sense to me. 

Because BSP2 > 2PSB and supporting 2PSB makes compiler and engine programmers cry in their sleep. 

Because BSP2 > 2PSB and supporting 2PSB makes compiler and engine programmers cry in their sleep.

Is that just your opinion or do you know that for a fact? Have you asked the people who create engines and compilers if they get 2PSB nightmares? :) 

Why support 2 standards that are similar if one will do the job? It's unnecessary overhead and code maintenance. 

Can this be done? I want to cast a Q symbol but I don't want the brush to be seen. 

 

With that new compiler that lets you cast shadows from brush entities, you can give the brushes the classname "info_null" and set "_shadow" "1". Does waste a model precache though... 

You could potentially use a bunch of negative lights too, but that would likely look like ass and be a pain to do. 

I always thought it would be cool if someone made an engine where you could go round the map and "spraypaint" the lightmaps. Basically just go round with a dynamic light that never went away. Then you could add a negative "brush" that subtracted rather than added light, and you could use it to fix up glitches or do weird effects. It'd probably be hard to make it robust in the face of recompiling the map, perhaps you could replay a demo to repeat any painting you performed. Anyway, that's my mad thought for the day... 

 

Um...hesitant to ask, but...

Is there any sort of maybe legal issue with using something from the mission packs? I know Quoth used the Scourge(the scorpion to you heathens who don't know) from hipnotic's pak (hipnothetically, of course), but is this legal? And to what extend? If someone hosts the entire mission pack in the zip along with a custom map so that someone can play it, is it illegal?

Methinks melord thou art a theif. Y/N