needs to be able to be enabled / disabled for phase changes. infinity had one that was on all the time and funky things happened when you dropped the flag within the zone. (hence the enable / disable)

__________________
11:29 p.m. - ☢ AZgAg: did the fgd was moved?

It's why whenever I used it for a flag cage I'd make it hollow.

edit: you can also filter it to only affect blocks (prop_physics as of 1.9.2, but I doubt the basic way blocks are represented has changed).

__________________
Not in cruelty, \ not in wrath, \ the Reaper came today.\ An angel visited \ this gray path, \ and took the cube away.

Weird, thought I had already posted here.

I just set up filters on the physics clip, for each type of entity. Props, grenades, blocks etc. Realistically, enable/disable doesn't appear to have any problems. But if the buildphase included anything else other than blocks, you'd need to use the filters method.

Keeping it active to blocks in combat phase has the advantage of preventing you from leaving blocks in a nofreeze during build then filling your flag d with a physics lock stack when the clipping goes away.

__________________
Not in cruelty, \ not in wrath, \ the Reaper came today.\ An angel visited \ this gray path, \ and took the cube away.

Then you could just place a toggling disposer, slightly smaller than the flag clips.

are toggleable disposers working?

you guys need to have a big media thing for the dev section so we can hear wtf is going on. you guys also need to update sf/the fgd so it only uses the new blocks and not the old ones for the view models in hammer. re: red would be skin 0 instead of 3 and blue would be 6 instead of 2. that way you could save a bit of weight on sf

__________________
11:29 p.m. - ☢ AZgAg: did the fgd was moved?

Bear in mind that I haven't mapped since 192. Also disposers would be bad b/c you don't want to penalize people for accidentally clipping the flag zone with a block, just prevent them from putting one in.

__________________
Not in cruelty, \ not in wrath, \ the Reaper came today.\ An angel visited \ this gray path, \ and took the cube away.

See Flare's method in fieldtrip two.

I would help do that, if I actually gave a shit about SF any more. Completely wasted my time making stuff like that example map, so call me if this mod ever goes any where again, then I'll think about helping out. Put enough time into something, to see or play fuck all in return. I know what you're talking about though, that fgd was seriously half assed who ever made it.

We seem to be at a misunderstanding here.
I was talking about having a physics clip, set up with filters to only prevent blocks getting into the flag area in the build phase, say eight units thick per side. Then inside of that hollowed out cage, you have a block removing disposer (Obviously the trigger brush would be a couple of units smaller than the clip cage.) which turns off in the combat phase. People can try to build in the flag cage during combat, won't work during build phase though. I honestly doubt you'd have enough time to construct an entire flag d from scratch, in the size of the maps 1.9.X has.

Just a thought.

Ah. They could easily have enough time to construct a physics locked stack, though. Then in build phase all those blocks get disposed and they set up to do it again. Doesn't quite work.

__________________
Not in cruelty, \ not in wrath, \ the Reaper came today.\ An angel visited \ this gray path, \ and took the cube away.

You can never really prevent a physlocked stack with out going over the top to be honest. Apart from the clip and filters method.