Crossbow reload: which bolt stack the auto-reload takes (lowest slot vs smallest stack)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 24/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- go, reverse-engineering
调研方向
Start with reloadMagazine in apps/server/internal/game/action/ammunition.go, which picks the bag stack by lowest slot from slot 13. The real work is in the v1.150 server disassembly: confirm whether native auto-reload takes the first matching slot or the smallest stack, and cite the address in a code comment. Done when the Go reload order matches that address and the owner has answered the thread.
由索引模型根据 Issue 内容生成。
描述
Player report from Discord (2026-11-13): with a crossbow equipped, the reload does not take the smallest bolt stack. It takes what looks like a random one, which splits the player's stacks. The player asks that it always use the lowest stack.
What the port does: reloadMagazine (apps/server/internal/game/action/ammunition.go) moves the bag stack of the spent type that has the lowest slot number. Its comment says the reference server searches the bag from slot 13. So the stack chosen depends on bag order, not on stack size.
To find out
- Check that native claim against the server disassembly: does the auto-reload take the first matching slot from 13, or the smallest stack?
- What the v1.150 client does when it requests a reload itself, if it ever does.
Done when: the reload order matches the disassembly, with the address cited at reloadMagazine. If native takes the first slot, the thread gets that answer (the owner words the reply).
- 主要语言
- Go
- 星标
- 97
- 派生
- 61
- 平均合并
- 4 小时 14 分钟
- 30 天内合并 PR
- 913
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
opensro-dev/opensro 的其他 Issue
-
area: client enhancement priority: low
难度 2/5 1-3 小时 新手友好度 75/100
opensro-dev/opensro#3681 ·
维护者通常 1 天内回复
-
area: client bug priority: low
难度 2/5 1-3 小时 新手友好度 78/100
opensro-dev/opensro#3228 · 1 条评论 ·
维护者通常 1 天内回复
-
Format one minified client file with dprint (ongoing: one file per PR)可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭area: client enhancement good first issue priority: low
难度 2/5 1-3 小时 新手友好度 75/100
opensro-dev/opensro#1 · 1 条评论 ·
维护者通常 1 天内回复
-
area: server bug priority: medium
难度 3/5 半天 新手友好度 55/100
opensro-dev/opensro#3687 ·
维护者通常 1 天内回复
-
area: ops bug priority: high
难度 4/5 3-5 天 新手友好度 32/100
opensro-dev/opensro#3685 ·
维护者通常 1 天内回复
查看 opensro-dev/opensro 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 66/100
unbound-force/gaze#353 ·
维护者通常 1 天内回复
-
bug cross-seed ready-for-human
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 64/100
OneBusAway/maglev#2102 ·
维护者通常 2 天内回复
-
affects-8.5 component/session severity/moderate sig/transaction type/bug
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 70/100
Judgment-Pack/judgment-pack-gateway#474 ·
维护者通常 1 天内回复