Update to 24w14potato #293
Conversation
|
Thanks! Note that the |
EnderKill98
force-pushed
the
silly/24w14potato
branch
from
1379260
to
bed277a
Compare
|
Yeah I just noticed that. I thought some weird transparency issue was the cause for the black boxes, but the texture pointed to something like Then the offsets were all wrong though, which is when I double checked and noticed the issue. I force-pushed the branch, which is now based on Edit:
Yeah, the check for F3 and one mixin signature were already fixed. The custom payload stuff did change a lot though. I used one of minecrafts own Payloads as a guide. Fingers crossed, it just works 🤞 . |
|
Fun fact: You can't eat him, but he is still nutritious 🤣
|
Turns out that the payloads need to be registered server-side now for the server to be able to encode the packet. Some other changes made: - Made the Identifier for the exhaustion/saturation payloads match the latest Neoforge version - `class` -> `record` - A few style changes
|
Great work on this! It turns out that the packets need to be registered server-side to avoid packet encoding failure when sending a sync packet from the server to the client, but other than that everything looks good. Thanks! |
Since I was porting some mods I can't live without, I thought it would be cool to have this as well.
The mod is not free of errors. I noticed this render artifact:
The hunerbar has also some transparency issue when indicating newly added food when holding an item and not fully fed:
Also, while I updated the CustomPayload to the new architecture, it could not test it yet (thought it starts which is already a good indicator).
This might be a useful stepping stone. Just verify that the server plugin integration works, fix the 2 render artifacts, and it should probably be 90% done for 1.20.5 as fabric calls the version "1.20.5-alpha.24.12.potato" in the
fabric.mod.json.I didn't test or try to port Forge. Only Fabric.