It would appear this new entity works from a new .ent file that has to be located in the map folder. Here is the kalt example:

EntText
{
//Allies tunnel
entity
{
"classname" "func_team_wall"
"blockteam" "3"
"origin" "705.379150 4764.189453 127.96711"
"mins" "-40 -10 -64"
"maxs" "40 10 64"
}

//Allies ramp
entity
{
"classname" "func_team_wall"
"blockteam" "3"
"origin" "1411.903076 4750.809570 178.08795"
"mins" "-120 -10 -64"
"maxs" "120 10 64"
}

//Axis right ramp
entity
{
"classname" "func_team_wall"
"blockteam" "2"
"origin" "4737.456055 4266.583496 174.08795"
"mins" "-100 -50 -5"
"maxs" "100 50 100"
}

//Axis left ramp
entity
{
"classname" "func_team_wall"
"blockteam" "2"
"origin" "5501.153320 4251.006836 160.68026"
"mins" "-100 -50 -5"
"maxs" "100 50 100"
}

}

Just a heads up for the future releases that use this system, please include it in pakrat :)

Actually, I think mappers can use it in a regular way with entities inside hammer. It's not required to use .ent files.

I think Valve just made the changes to old maps with .ent files instead of recompiling the whole map, making the update download size even bigger.

Originally posted by skdr
Actually, I think mappers can use it in a regular way with entities inside hammer. It's not required to use .ent files.

I think Valve just made the changes to old maps with .ent files instead of recompiling the whole map, making the update download size even bigger.

yah, i tested it out. it works fine without the ent file. you will also notice these files do not apply for either jagd or colmar (since they use the actual brush)

can someone please explain how this works in more detail? I'm REALLY interested!

"origin" "705.379150 4764.189453 127.96711"
- I assume this is in XYZ form. not customary for brush entities, is it?

"mins" "-40 -10 -64"
"maxs" "40 10 64"

-these specify the limits on..? x-axis, y-axis?

Use brushes in hammer tied to the entities. These are in my map, and functional since b2.

Heres a run through:
func_team_wall tied to a trigger brush (i.e. fill in the space you want to be innacessible with a 1 unit trigger textured brush)

BLOCKING allies: tie the brush entity to team 2
BLOCKING axis: tie the brush entity to team 3 (yes THREE)

well i know how to use the dod_func_wall entity. what I want to know is how the .ent file works, its usage and limitations.