command piping

[Vir-Suppae]

Description

It would be really useful to be able to pipe commands unix-style (i.e. /spawn | tp)

[du82]

why not just /summon entityName ~ ~ ~ or whatever coordinates? This way you don't need to spawn it then teleport it, just spawn it where you want it

[Wunka]

why not just /summon entityName ~ ~ ~ or whatever coordinates? This way you don't need to spawn it then teleport it, just spawn it where you want it

I think you misunderstood what the the issue describes.

/spawn | tp would get the spawn of the player and then teleport the player to it.

I think this is interesting. And should be a far future goal, but there is a lot of other things which are currently in discussion about commands so this issue should only be done when these are resolved

[Argmaster]

It's not exactly how piping works in Unix shell is it?
When you use pipe, you connect stdout of one command to stdin of different one. It doesn't change the argument list (unless you use a special executable).
Firstly, output of most of Cubyz commands is designed to be human friendly, secondly we don't really have a reliable way to capture it.
Moreover we are never using dynamic input to change the behavior of commands.
Overall, I don't see a use case compelling enough to do major refactoring with major changes to command semantics but you can try to prove me wrong.
Our commands are intended to alter the state of the game, not to output data or take extended input, or do multiple steps of processing.
I don't think there are use cases within that scope that will be unachievable without piping.