Crossbow reload: which bolt stack the auto-reload takes (lowest slot vs smallest stack)

Open
#3,566 0 comments 0 reactions 0 assignees View on GitHub

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

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

area: server bug priority: low

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from opensro-dev/opensro

All issues in opensro-dev/opensro

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.