Open josephcsible opened 6 years ago
This is the cause. Is there a reason for only doing this on the server?
@josephcsible Because only the server knows of these IDs, and stores them.
Not sure if this issue can be easily resolved though, due to how crafting works in 1.12 (completely server-side).
https://github.com/CyclopsMC/CyclopsCore/blob/master-1.12/src/main/java/org/cyclops/cyclopscore/persist/world/GlobalCounters.java#L10 seems to indicate otherwise.
GitHubCyclopsCore - Minecraft coremod for EvilCraft, Integrated Dynamics and others.
Not sure if that description is accurate, I don't remember ever implementing server-client syncing, and I also don't think vanilla does this out-of-the-box for WorldStorage.
This remains a problem in 1.12.2-0.11.17
Issue type:
Only keep the issue types that are applicable.
Short description:
When crafting an omni-directional connector, its group ID isn't immediately synced to the client.
Expected behaviour:
A newly-crafted omni-directional connector should immediately have its group ID visible.
Actual behaviour:
A newly-crafted omni-directional connector does not have its group ID visible until you force the server to tell the client about the item again, such as by moving it around.
Steps to reproduce the problem:
Versions:
Git revision c5ed8ac, with all of the dependencies pulled by gradle for it
Log file:
Nothing relevant