Behavior Tick Rates aren't operating as designed
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 12.7k
- Forks
- 3.5k
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 11
Description
Expected behavior
The behaviours tick rates configured to the configurable tick rate in the Paper World Config.
(Recorded using Paper-1.19 Latest with same configuration from 1.20.2)
Observed/Actual behavior
The behaviours tick rates aren't configuring to the configurable tick rate set in the Paper World Config.
Steps/models to reproduce
- Set configuration with the following settings in
paper-world-defaults-yml
tick-rates:
behavior:
villager:
validatenearbypoi: 300
aquirepoi: 300
- Start up server and make a similar build to build shown in the videos.
- Villager is changing POI as soon as lever is pressed rather than 300 ticks after.
Plugin and Datapack List
- Essentials
- LuckPerms
- PlugManX
- ViaBackwards
- ViaVersion
Paper version
This server is running Paper version git-Paper-280 (MC: 1.20.2) (Implementing API version 1.20.2-R0.1-SNAPSHOT) (Git: 4675152)
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 reproducing the villager behavior using the paper-world-defaults-yml settings under tick-rates.behavior.villager, with validatenearbypoi and aquirepoi set to 300. Compare the configured rate with the observed POI change timing; the issue is resolved when the villager waits for the configured interval.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100