Talk:Move rope

From Valve Developer Community
Revision as of 14:01, 9 May 2021 by Luke18033 (talk | contribs) (Merge with keyframe_rope: new section)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Float values seem to work fine for the rope width value. --JumpCore 21:09, 8 March 2010 (UTC)

Type key

What does Type keyvalue make? --FATAL_ERROR (talk) 07:49, 1 June 2018 (UTC)

Rigid makes the rope less "dangly", and semi-rigid does the same, but on a lower scale. Rope is just plain rope, atleast from my testings. --User:Mechadexic 12:38, September 1, 2018 (EST)

Merge with keyframe_rope

(Copied from Talk:keyframe_rope)

keyframe_rope and move_rope are not different entities, they're both linked to the same class CRopeKeyframe. This is from SDK 2013:

LINK_ENTITY_TO_CLASS( move_rope, CRopeKeyframe );
LINK_ENTITY_TO_CLASS( keyframe_rope, CRopeKeyframe );

In-game testing in various different branches further supports this: a rope chain does not have to start with a move_rope and have every following ent as a keyframe_rope. It can be made entirely of keyframe_ropes, entirely of move_ropes, alternate between the two, etc. and it still appears and works exactly the same. We don't have separate pages for dynamic_prop and prop_dynamic, so why should this be any different? I'd suggest using move_rope as the combined page, since that entity has more keyvalues in the default FGD. It'd still note that keyframe_rope is an alternate classname. - Luke18033 (talk) 14:01, 9 May 2021 (PDT)