Talk:Move rope: Difference between revisions
m (→Type key: forgot to add signature) |
(→Merge with keyframe_rope: new section) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 4: | Line 4: | ||
What does '''Type''' keyvalue make? --[[User:Max30335|FATAL_ERROR]] ([[User talk:Max30335|talk]]) 07:49, 1 June 2018 (UTC) | What does '''Type''' keyvalue make? --[[User:Max30335|FATAL_ERROR]] ([[User talk:Max30335|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]]'') | |||
<code>keyframe_rope</code> and {{ent|move_rope}} are not different entities, they're both linked to the same class <code>CRopeKeyframe</code>. This is from SDK 2013: | |||
<pre> | |||
LINK_ENTITY_TO_CLASS( move_rope, CRopeKeyframe ); | |||
LINK_ENTITY_TO_CLASS( keyframe_rope, CRopeKeyframe ); | |||
</pre> | |||
In-game testing in various different branches further supports this: a rope chain does not have to start with a <code>move_rope</code> and have every following ent as a <code>keyframe_rope</code>. It can be made entirely of <code>keyframe_ropes</code>, entirely of <code>move_ropes</code>, alternate between the two, etc. and it still appears and works exactly the same. We don't have separate pages for {{ent|dynamic_prop}} and {{ent|prop_dynamic}}, so why should this be any different? I'd suggest using {{ent|move_rope}} as the combined page, since that entity has more keyvalues in the default FGD. It'd still note that <code>keyframe_rope</code> is an alternate classname. - [[User:Luke18033|Luke18033]] ([[User talk:Luke18033|talk]]) 14:01, 9 May 2021 (PDT) | |||
Latest revision as of 14:01, 9 May 2021
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)