1.21.10/11 Update Tracking
Open
A pull request for this has already been merged.
- #13074 by @jpenilla — merged
- Dominant language
- Java
- Stars
- 12.7k
- Forks
- 3.5k
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 11
Description
Goals
- Rename world config's entity.spawning.despawn-time. The config should not imply that the removal follows all server despawn logic
- Rework brigadier client tree building. Redirects make briagdier commands a graph instead of a tree. DFT is not a suitable algorithm for such data structures.
- Add data converter for invalid team colours, revert https://github.com/PaperMC/Paper/pull/12874
1.21.10 TODOs
- adventure update (paper-api and paper-server build scripts)
- world border migration & check coordinate scale use
- audit spawn position changes
-
add a setSpawnLocation variant w pitch and yawuse pitch and yaw when setting spawn pos with Location - Add API equivalent for SelectableSlotContainer and move common Shelf/ChiseledBookshelf API?
- texture overrides in ResolvableProfile
- Teleport changes #13181
1.21.11 TODOs
- #13351
- 25w43a:
- Connection, ServerConnectionListener - dropped diff for thread pool config (fields gone)
- 25w44a:
- ShulkerBoxBlock: retainUnlootedShulkerBoxLootTableOnNonPlayerBreak patch no longer applies (getDrops override removed)
- #13372
- 25w45a:
- #13369
- 1.21.11-pre2:
- Review BlockLockCheckEvent changes
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 reviewing the remaining unchecked goals and TODO entries in this tracking issue, then inspect the related discussion and merged pull request #13074. Work is complete when the listed configuration, Brigadier, data-converter, API, and 1.21.11 migration items are resolved and their checklist entries can be marked done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100