Expose lastKnownSpeed, lastKnownPosition and getKnownSpeed() in Entity
Open
Nobody has claimed this yet.
status: needs triage
- 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?
for a long time, if you want to get a player's speed, you have to do calcs like what in nms(location subtractions), after exposing these, you can get rid of scheduler speed calculation since nms already provided that
Describe the solution you'd like.
Expose these
Describe alternatives you've considered.
No
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 locating the Entity API and the NMS-provided lastKnownSpeed and lastKnownPosition values mentioned in the issue. Determine how getKnownSpeed() and those values should be exposed, then verify that callers can use them without scheduler-based speed calculations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100