Do you have any sort of plans or roadmaps for logic based suggestions or advice for schine?
Some sort of logic block, that activates adjacent activation modules or buttons(on the same entity), if it recieves a signal through a C-V link. Why? So using copy&paste to generate repetitive logic structures(such as memory for a counter) does not need to be followed up by linking all the storage cells together, which can become quite some work. With the possible addition of cross entity activation, if next to a rail with something docked on it, and an activator/button next to the rail-docker.
The purpose of the latter if we already have the wireless block? The wireless block is too specific. It will only transmit to a specific entity, and that entity will be the same under any circumstances, until the block is linked to a different one. The adjacency mechanic e.g. allows automatic trains to know when to open their automatic doors, even if multiple ones are on the exact same railtrack, so wireless logic can't be used, as it is unknowable which train is at a stop.
Same as above, but for modding?
One of the two until beta: (
IMPORTANT: this is not what schine may be planning, it was what I wish they would plan)
- Fix what little of an API there already is, or expand it.(as some event listeners don't fire currently)
- Deobfuscate more of what is unneccessarily obfuscated.(so that an API is not needed)
Same as above, but for server management tools? (especially live & offline database connections/management and entity/player management?)
A way to use own code for saving and loading a universe(not blueprints), so that people can make formats, that suit their server better at their own risk?
And always: integration of own commands using the command prefix (/), and more commands for just retrieving data about the status quo.
Apart from that, I think much will depend on the needs of the server in question.
