Skip to content

Partial reloads 13: Keep a chambered round through a MilSO reload - #2299

Closed
sunzenshen wants to merge 1 commit into
stack/reload-zr68c/80-kylafrom
stack/reload-zr68c/90-milso
Closed

sunzenshen wants to merge 1 commit into
stack/reload-zr68c/80-kylafrom
stack/reload-zr68c/90-milso

Conversation

@sunzenshen

@sunzenshen sunzenshen commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Description

Depends on NeotokyoRebuild/neoAssets#185 (layer 13: the MilSO chamber phases file).

Partial reloads 13: add a chambered round to the MilSO. This PR builds on layer 12 (#2298, the Kyla) and pairs with
neoAssets layer 13. Next: #2300 (14, AA13).

As for the Tachi (layer 11, #2297), the generic chamber code of layer 08 (#2294) does the work: this PR adds the three
script lines and has no code changes.

  • MilSO: #base "weapon_milso_reload_phases.txt", "ReloadPhases" {}, "ChamberedRound" "1", as the Tachi has
    them. The phases file has one 3_cycle row each for reload and reloadempty, at the ammo credit (1.667 s).
    The MilSO keeps its shipped reload clips and sounds whole: a tactical reload gives 12+1, a dry reload 11+1.
  • No resume: the MilSO phases have no unload or load step, so a switch before the credit cancels the reload as on
    master; a switch after the credit keeps the rounds and the chambered round.
  • The flag sv_neo_reload_experimental defaults to 1 while the partial-reload stack is reviewed (Partial reloads 06: Resume a ZR68C reload after the magazine is unloaded #2293); the
    last PR of the stack sets it back to 0. With the flag at 0 the MilSO behaves as on master.

How to review

  1. weapon_milso.txt: the three lines, as weapon_tachi.txt has them (Partial reloads 11: Keep a chambered round through a Tachi reload #2297).
  2. The neoAssets layer 13 phases file.
  3. Test in game: "How to test".

How to test

  1. Load a map (the flag is 1 by default) as Recon and take the MilSO: 11 rounds in the HUD row, the round icon lit
    (11+1).
  2. Fire a few rounds and reload: the row fills to 12, the icon stays lit (12+1).
  3. Fire it empty: the slide locks (fireempty, idle01empty). Reload: the icon is dim until the slide release, then
    lit with 11 in the row.
  4. Reload empty and switch to the primary just after the slide release, then back: a plain draw, 11+1 kept.
  5. Repeat with sv_neo_reload_experimental 0 (set before the map loads): master, 12 rounds, no +1.

Results

Layer 13 build (this PR + neoAssets layer 13), Linux Debug, ntre_engage_ctg, owner MilSO plus a bot_mimic bot:

case flag 1 flag 0 (master)
tactical from 9 (8+1) reload: 13 (12+1) at +1.64 s, reserve 36 -> 24 reload: 12 at +1.64 s, reserve 36 -> 24
dry from 0 reloadempty: 12 with the chamber filled at the credit (+1.64 s; one tick 12 with the chamber empty, then 11+1) 12
dry, switch after the credit (+1.86 s), back plain draw, 11+1 kept, no second reload; fires plain draw, 12 kept
dry, switch before the credit (+1.25 s), back drawempty, clip 0, a fresh reloadempty to 11+1 the same, 12
last round fired, switch away and back fireempty, drawempty, idle01empty, then the auto reloadempty to 11+1 the same sequences, 12
HUD (frame crops) tactical: icon lit throughout, row 8 -> 12; dry: icon dim and row 0, then icon lit with row 11
headless TDM, 12 Recon bots (MilSO secondary), flag 1, 1 round PASS, match_end=True, 0 asserts; bots switched to the MilSO 18 times

Toolchain

  • Linux GCC Distro Native (Linux Mint 22.3, GCC 13.3.0)

Linked Issues

The MilSO script gets the reload phases from neoAssets and a chamber
slot: #base "weapon_milso_reload_phases.txt", "ReloadPhases" {} and
"ChamberedRound" "1", as the Tachi has them. The generic chamber code
then gives 12+1 after a tactical reload and 11+1 after a dry one, with
the chamber filled at the ammo credit. No code changes.
@sunzenshen

Copy link
Copy Markdown
Contributor Author

Closing to clear the board in favor of the PR stack of sunzenshen#34

@sunzenshen sunzenshen closed this Nov 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Animations Animation stuff. Including the syncronizing of animations between client and server based on state.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants