Problems with villager zombification

未关闭
#14,465 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
java
领域
backend

调研方向

Start by tracing villager profession handling during zombification and curing in Paper’s server code; the issue does not name a file or test. Compare the profession and locked trades before zombification, on the zombie villager, and after curing, then look for an existing test that covers this conversion. Done means the profession and original trades are preserved through both steps, with the expected discount.

由索引模型根据 Issue 内容生成。

描述

status: needs triage version: 26.3
Expected behavior

When a librarian villager with locked trades (traded with at least once) is zombified, the zombie villager should still be a librarian. After curing, it should be a librarian with its original trades and a discount on them.

Observed/Actual behavior

In about 50 zombifications, two librarians with locked trades (two different villagers) changed their profession to toolsmith during the zombification itself. The resulting zombie villager changed to a toolsmith, and it stayed a toolsmith after curing.

Steps/models to reproduce

Trade with a librarian villager at least once to lock its trades.
Let a zombie convert it into a zombie villager (normal zombification, no smithing tables or other job blocks nearby).
Check the zombie villager's profession: in rare cases (2 of ~50) it is a toolsmith instead of a librarian.
Cure it: it stays a toolsmith.

Plugin and Datapack List

No Plugins or Datapacks installed

Paper version

This server is running Paper version 26.3-240-main@6b68358 (2026-11-04T04:04:15Z) (Implementing API version 26.3.build.240-stable)
You are 2 version(s) behind
Download the new version at: https://papermc.io/downloads/paper
Previous version: 26.3-227-7f9c797 (MC: 26.3)

Other

No response

主要语言
Java
星标
12.8k
派生
3.6k
平均合并
2 天 21 小时
30 天内合并 PR
33

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

PaperMC/Paper 的其他 Issue

查看 PaperMC/Paper 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。