guild crest: every upload is refused on our shard (no crest store: SRO_AGENT_MARKS_DIR unset)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 半天
- 新手友好度
- 25/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- go
调研方向
Start in cmd/services/sro-gameworld/wiring_authority.go, where the crest store opens only when SRO_AGENT_MARKS_DIR is set, and at crestregister.go:165 where uploads are refused. The fix lives in the deployment config: server-ops/nomad/jobs/gameworld.nomad.hcl in the opensro-ops repo, which needs a persistent directory owned by the GameWorld user. Confirm the live process environment first. Done means a valid 16×16 crest upload is accepted and shown over a guild member, and this is blocked until #3451 is merged.
由索引模型根据 Issue 内容生成。
描述
Player report (bug-reports forum, 2026-11-12): the guild crest dialog lets the player pick a .bmp file, but the game does not accept it.
Cause (from the deployment source)
- The crest register lane needs a crest store.
cmd/services/sro-gameworld/wiring_authority.goopens one only whenSRO_AGENT_MARKS_DIRis set. Without it,crestregister.go:165refuses every upload ("crest register: no crest store wired"). - Nothing in the production deployment sets it: neither the GameWorld Nomad job (opensro-ops
server-ops/nomad/jobs/gameworld.nomad.hcl) norapps/server/config/shard-settings.json. So on our shard every crest upload is refused, whatever the file. - Even with the store wired, a registered crest never shows over characters until #3451 lands: the client fetches
/marks/without the/apibase.
Not yet confirmed against the live process environment: the deployment source is the only input that sets it.
Done when
- The GameWorld job sets
SRO_AGENT_MARKS_DIRto a persistent directory owned by the GameWorld's user that survives releases. - #3451 is merged.
- On the live server, a valid 16×16 crest upload is accepted and shows over a guild member.
- 主要语言
- 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 天内回复