Broken Linedef or what?
Just tried to use this linedef with Pusher thing and Wind sector. This is I got:
- Both Effect 4 and Not Climbable don't work (or do nothing).
- The radius of the effect is given by Thing angle. Seems control linedef's length determines the strength of the current.
- The "actual" radius of the effect is limited to 359. For instance, Shrouded Terminal Zone Act 3 requires ~780FU of radius for push effect to work properly (v1.09.4 [but impossible in 2.0]).
If you want, open up the example wad and test it. --
Ezer'Arch
[Example wad can be found here: http://wiki.srb2.org/wiki/Linedef_Type_547]
It seems like Effect 4 indeed doesn't work (I can't say for Not Climbable because it's so hard to test if that has an effect or not). This is kinda weird, because both flags are specified in the source (p_spec.c, line 7112). Unfortunately, I don't know where I can find the function "p_push", which would probably shed a bit of light on this. Does anybody know? --
SpiritCrusher
The Not Climbable flag works in this case, however it behaves a little different from the other pusher linedefs. In here, the force exerted on the player goes beyond sector limits so there's not much "connection between touching target sectors with the same tag", but more "the push/pull thing in this sector has a priority over the push/pull thing on the nearby sector". In other words, if you tag this linedef to multiple sectors and put in each sector one push/pull thing (each thing being within 359 fracunits of another), the game goes by sector number (ugh), from lowest to highest, to tell which one has a push/pull thing that actually affects the player. The rest will not affect the players as long as they're in range of the one with highest priority (lowest sector number).
This gets worse when you use multiple linedefs with this special but with different tags, since the game goes first by linedef number before going by sector number... yeah, I don't think a wiki article should really bother with this kinda stuff.
To make things simpler, and bear in mind that I don't like to hide information from the readers, I think the best would be not even refer the Not Climbable flag since it doesn't seem to have any real use besides making people's heads hurt >_<. Feel free to contradict me, of course, if you have a better solution =) --
Ricardo
