the zombie's pain function (zombie_pain) always resets it's health to 60 when it's damaged (unless of course that's fatal damage).

you could do the armor hack if you want it to be tougher, add the keys "armortype" "1" and "armorvalue" "60", and it'll have 60 extra health... it won't regen that health though. 

and negative damage is still treated as 'taking damage' as far as the code is concerned, which is why it uses it's pain function 

thanks 

those are interesting to note!

I think as the game progresses a lot of encounters are made easier due to the extra power of the weapons you have. Would be fun to be put into a room with a bullet sponge enemy to create extra panic. 

it can be difficult to sell to the player why monsters are more beefy than normal, and that doesn't always make enemies more difficult, pain animations will still play and lock the enemy from retaliating... so they just take more ammo than usual.

I think it's best done on single enemies with something like "effects" "3" (i think 3 is the golden particles?) that gives a visual cue that the enemy is special 

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.