comp_p2_piston_platform

[vrad-exe]

An entity to automate the creation of Piston Platforms in Portal 2, using a modified version of BEEmod's script. I'm not sure exactly what this entity's configuration would look like, but the way I imagine it working is you would specify a number of other entities (movelinears probably) to use as piston segments, which the postcompiler would set up to work with the script.

Ideally, it should:

• Support custom/non-standard platform designs (including things like P1 platforms with brush pistons) - my suggested method accomplishes this
• Support any length, including non-multiples of 128 and heights greater than 512 (if enough piston segments are provided)
• Support moving to any possible position by input, instead of having specific up/down positions set on the entity (though maybe both could be an option)

[TeamSpen210]

Ideally I'd want to make it a bit more generic maybe, so it could be used for other situations too.

[Fennecai]

maybe something like comp_chainlink_spawner or something that, given 2 info_target or something, will spawn enough of a template entity to fit that space between them with as little left-over as possible. could maybe be used to spawn the func_movelinears of a variable-height piston platform- I've thought of doing similarly using script before but never got very far making it happen