Exclude copper golems from entity-activation-range limitations
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 12.7k
- Forks
- 3.5k
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 11
Description
Is your feature request related to a problem?
This is a vanilla parity thing.
In vanilla, copper golems works normally even if the distance to player is >32 blocs. (as indicated in the wiki : https://minecraft.wiki/w/Copper_Golem in the "Behavior" section)
In paper, this does not seem to be the case. (copper golems works ~6x slower when the player is away due to periodic wakeup of the entities every few ticks built-in the entity-activation-range feature)
Describe the solution you'd like.
Possible solution could be : excluding/separating copper golem from the entity-activation-range to mimic vanilla's way.
Describe alternatives you've considered.
I don't see any alternative to restore vanilla parity but will happily be corrected.
Other
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing Paper's entity-activation-range feature and the copper golem's entity behavior, then compare its distant-player behavior with vanilla using the linked wiki reference. Done means copper golems are no longer slowed by the relevant activation-range limitation while other entities retain their existing behavior; no file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100