Add client side entities page #267
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
olijeffers0n
requested changes
Nov 18, 2023
There was a problem hiding this comment.
Thanks for your addition. The naming is slightly misleading because these are server-side entities, not client-side. There is also a lot of room for improvement on the implementation side. Maybe if you note that this is a fairly quick and dirty way of doing this it would be better
|
Superseded, thank you for your work! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A lot of times people appear in #paper-dev trying to get some packet magic working for basic client side entities, so I figured it would be nice to have some documentation around the already existing API.
The only problem with this is that
Entity.setVisibleByDefaultandPlayer.showEntityare still marked as experimental.