- Jul 19, 2009
- 721
- 254
Func_tracktrain flags (unblockable by player) broken?
Before you read make sure you understand that the map in question, arena_cargo, uses func_tracktrains a bit differently. As it stands there are two trains that slowly move in opposite directions on a straight track on either side of the control point.
Originally in b2 the train would kill upon crush, thus requiring no trigger_hurts. However, the problem that arose caused players to kill each other if they touched one another while standing on the props parented to the func_train.
In b3, I fixed the problem by eliminating the hurt on crush, flagging the train as unblockable by player and making several very small trigger_hurt brushes inside each prop_static and brush that the player could potentially attempt to block the train. This seemed to work as I tested the compiled version on my own listen server. However, once the map was played today at gameday, the trains no longer were unblock able and strange shadows that were not present before were coming from the prop_dynamics.
I know this problem only arose once it was played on the server and since then my own compiled arena_cargo_b3 has the same issue. Does the unblockable flag work with a parented prop_dynamic or was there something odd that happened in the process of uploading the map to the server?
Before you read make sure you understand that the map in question, arena_cargo, uses func_tracktrains a bit differently. As it stands there are two trains that slowly move in opposite directions on a straight track on either side of the control point.
Originally in b2 the train would kill upon crush, thus requiring no trigger_hurts. However, the problem that arose caused players to kill each other if they touched one another while standing on the props parented to the func_train.
In b3, I fixed the problem by eliminating the hurt on crush, flagging the train as unblockable by player and making several very small trigger_hurt brushes inside each prop_static and brush that the player could potentially attempt to block the train. This seemed to work as I tested the compiled version on my own listen server. However, once the map was played today at gameday, the trains no longer were unblock able and strange shadows that were not present before were coming from the prop_dynamics.
I know this problem only arose once it was played on the server and since then my own compiled arena_cargo_b3 has the same issue. Does the unblockable flag work with a parented prop_dynamic or was there something odd that happened in the process of uploading the map to the server?
Last edited: