PaperMC / PaperMC/Paper

Configurable entity tracking ranges per entity type

Open
#13,377 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

scope: configuration 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 the longest time it's only been possible to configure tracking ranges per arbitrary groups of entity types, while the vanilla game actually has it's own tracking ranges for each different entity type, most commonly 8 or 10 chunks distance by default.

Describe the solution you'd like.

To be closer to vanilla and also prevent having to periodically add new tracking range options, I think it would be best to add a new option in the paper config that allows configuring the tracking range per entity type. The config could also allow using vanilla's entity type tags (prefixed by #) to configure it for multiple entities at once and/or the activation type name as a migration path from the current spigot config.

As for the defaults, ideally we could default everything to vanilla and advise people to only turn it down if entity tracking is really causing strain on their server, but, obviously more input wanted.

Describe alternatives you've considered.

Continue suffering from the dreaded invisible ghast attack.

Other

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by locating Paper's entity-tracking and configuration code, then compare the current group-based ranges with vanilla's per-entity defaults. Done would require an agreed design for per-entity and tag-based settings, migration from the current Spigot configuration, and default values.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.