-
-
Notifications
You must be signed in to change notification settings - Fork 679
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update custom-entities to 1.19.2 #3204
Closed
Konicai
wants to merge
177
commits into
GeyserMC:feature/custom-entities
from
Konicai:custom-entities-1.19.1
Closed
Update custom-entities to 1.19.2 #3204
Konicai
wants to merge
177
commits into
GeyserMC:feature/custom-entities
from
Konicai:custom-entities-1.19.1
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
* Add player skull render distance * Improve updateVisibleSkulls a bit Avoid rechecking visibility on small movements * Periodically despawn unused skull entities * Don't hide skull entity for position/rotation changes Prevents flickering for skulls that are rotating * Update visible skulls when a skull is removed * Only update on removal if an entity is assigned * No need to check for skull in ChunkUtils Update copyright year * Avoid rechecking all skulls when a skull is added/removed * Allow skull render distance and number to be configured Renamed some fields to better match their values * Compare texture property directly from GameProfile * Remove unnecessary blockState field from SkullPlayerEntity * Use binarySearch for insertion Wait for player movement before loading skulls * Allow culling to be disabled by setting max-visible-custom-skulls to -1 * Only remove skulls in inRangeSkulls when culling is enabled * Add suggestions from review * Merge the for loops in updateVisibleSkulls * Fix skulls being leaked on chunk unload
Previously, no indication that the world border exists would show if warning blocks was set to 0.
By placing a locale file in `languages/ll_CC.properties`, any strings in that file will take priority over Geyser's own.
Bumps [gson](https://github.com/google/gson) from 2.8.6 to 2.8.9. - [Release notes](https://github.com/google/gson/releases) - [Changelog](https://github.com/google/gson/blob/master/CHANGELOG.md) - [Commits](google/gson@gson-parent-2.8.6...gson-parent-2.8.9) --- updated-dependencies: - dependency-name: com.google.code.gson:gson dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Prevent max health from being set below 0 * Add more detail to comment
…ure/1.19-bedrock
# Conflicts: # core/pom.xml
Mege master into extensions
* Update to 1.19.20 * Add 1.19.20 mapping * Revert biome changes
# Conflicts: # core/pom.xml
* Fix sending forms with floodgate * Comment about 1.19.20 * Swapped if-else Co-authored-by: Tim203 <mctim203@gmail.com>
# Conflicts: # ap/pom.xml # api/base/pom.xml # api/geyser/pom.xml # api/pom.xml # bootstrap/bungeecord/pom.xml # bootstrap/pom.xml # bootstrap/spigot/pom.xml # bootstrap/sponge/pom.xml # bootstrap/standalone/pom.xml # bootstrap/velocity/pom.xml # common/pom.xml # core/pom.xml # pom.xml
Fix forms and items in extensions
Set baby if armor stand is small for OptionalPack (GeyserMC#3210)
Set baby if armor stand is small for OptionalPack (GeyserMC#3210)
is there a doc for creating the entity ? i wanted to test this |
There is currently no documentation besides the Javadocs already in the code. |
which class is it ? |
…m-entities-1.19.1
Konicai
changed the title
Update custom-entities to 1.19.1
Update custom-entities to 1.19.2
Aug 12, 2022
Question does this have custom model support into this because I saw you merge feature and extensions into this (ik this is stupid but I’m just askin) |
yes |
I’m moving to this branch then lol |
Closed in favour of #3754 |
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.
No description provided.