Skip to content

Conversation

@JR1811
Copy link

@JR1811 JR1811 commented Aug 1, 2025

CCA has been used here to reduce boilerplate for block entity syncing (e.g., chunk saving, ...) and to fix ghosting issues when the pedestal is used by multiple players on a server.

Another PR attempted a fix for the same issue a while ago, but added custom networking, which might be unfit for new modders who are trying to get started with the topic.
This PR removes any custom networking for this issue, besides the single sync() call in the component class itself.

CCA has many other features which might be interesting to look at for other features in the tutorial series, too. The CCA wiki is written in a way where it's easy to get started in roughly less than 30 min with complete custom Components for BlockEntities, Entities, Chunks, Persistent World Data and so on, all including automatic network syncing and client / server / common ticking.

This is also mostly just an example. If it's not needed, the PR can be closed again 👍🏻

@JR1811
Copy link
Author

JR1811 commented Aug 1, 2025

While adding CCA, I have noticed that the issue of players desyncing when interacting with the pedestal seems to only appear when players, who are not Operators, interact with the pedestal block in spawn-protection chunks.

@JR1811 JR1811 changed the title Added Cardinal Components API Fixing BlockEntityRenderer desync and boilerplate with Cardinal Components API Aug 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant