You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like a remote control protocol for plots, where users can
read/write/observe block using a TCP client(somewhat like RCON, but for
redstone/block changes, not chat commands).
This feature would be cool for all sorts of hacks.
You could easily create external memory(which is what I desperately want this for),
external high-res displays, a real-world internet connection for a Minecraft build, etc.
The idea is that you can easily interface a Minecraft build with an external program.
Some thought should also be put into a useful, high-performance capable protocol,
and how multiple connections are handled, specifically how to build a protocol that doesn't
miss block changes, but delays the main plot thread as little as possible.
Also pausing, single-stepping etc. from external commands could be useful in all sorts of other
debugging and peripheral scenarios.
I also have a (somewhat) working prototype, but it's very bad as this is my first time using Rust.
I'll try to come up with a better implementation, but this would be a great feature "upstream", and I'm really out of my depth as a first-time Rust user with all this multi-threaded Rust code.
The text was updated successfully, but these errors were encountered:
I'd like to suggest a feature.
I would like a remote control protocol for plots, where users can
read/write/observe block using a TCP client(somewhat like RCON, but for
redstone/block changes, not chat commands).
This feature would be cool for all sorts of hacks.
You could easily create external memory(which is what I desperately want this for),
external high-res displays, a real-world internet connection for a Minecraft build, etc.
The idea is that you can easily interface a Minecraft build with an external program.
Some thought should also be put into a useful, high-performance capable protocol,
and how multiple connections are handled, specifically how to build a protocol that doesn't
miss block changes, but delays the main plot thread as little as possible.
Also pausing, single-stepping etc. from external commands could be useful in all sorts of other
debugging and peripheral scenarios.
I also have a (somewhat) working prototype, but it's very bad as this is my first time using Rust.
https://github.com/max1220/MCHPRS-RSC
I'll try to come up with a better implementation, but this would be a great feature "upstream", and I'm really out of my depth as a first-time Rust user with all this multi-threaded Rust code.
The text was updated successfully, but these errors were encountered: