Crossbow reload: which bolt stack the auto-reload takes (lowest slot vs smallest stack)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 24/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- go, reverse-engineering
- Domain
- game-dev, reverse-engineering
Research direction
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.
Written by the indexing model from the issue text.
Description
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).
- Dominant language
- Go
- Stars
- 97
- Forks
- 61
- Avg merge
- 4h 14m
- Merged PRs (30d)
- 913
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from opensro-dev/opensro
-
area: client enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
opensro-dev/opensro#3681 ·
Maintainers usually reply within 1 day
-
area: client bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
opensro-dev/opensro#3228 · 1 comment ·
Maintainers usually reply within 1 day
-
Format one minified client file with dprint (ongoing: one file per PR)Possibly taken A pull request linked to this issue is open or already merged. Openarea: client enhancement good first issue priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
opensro-dev/opensro#1 · 1 comment ·
Maintainers usually reply within 1 day
-
area: server bug priority: medium
Difficulty 3/5 Half a day Newbie friendliness 55/100
opensro-dev/opensro#3687 ·
Maintainers usually reply within 1 day
-
area: ops bug priority: high
Difficulty 4/5 3-5 days Newbie friendliness 32/100
opensro-dev/opensro#3685 ·
Maintainers usually reply within 1 day
All issues in opensro-dev/opensro
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
unbound-force/gaze#353 ·
Maintainers usually reply within 1 day
-
bug cross-seed ready-for-human
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
OneBusAway/maglev#2102 ·
Maintainers usually reply within 2 days
-
affects-8.5 component/session severity/moderate sig/transaction type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Waiting start: the fixed 503 body says another instance holds the lease when that may not be soOpen
Difficulty 1/5 Under an hour Newbie friendliness 70/100
Judgment-Pack/judgment-pack-gateway#474 ·
Maintainers usually reply within 1 day