Fix Captain weapon demand #20

Open
beasty wants to merge 1 commit from fix-captain-weapon-demand into main
Owner

Summary

  • select one non-repeating smithy_weapon order when an appointed Captain sees an exact unequipped warrior and no usable or in-flight supply
  • preserve player-authored Smithy queues and suppress duplicate orders while the finite Weapon is in production or transit
  • cover Ore-to-Smelter-to-Smithy production and the same exact Weapon identity through storage and automatic issue

Validation

  • cargo nextest run -p cat-sim --test source_cargo_campaign captain (3 passed)
  • cargo nextest run --workspace --profile smoke (74 passed)
  • cargo clippy -p cat-sim --all-targets -- -D warnings
  • cargo fmt --all -- --check
  • git diff --check
## Summary - select one non-repeating smithy_weapon order when an appointed Captain sees an exact unequipped warrior and no usable or in-flight supply - preserve player-authored Smithy queues and suppress duplicate orders while the finite Weapon is in production or transit - cover Ore-to-Smelter-to-Smithy production and the same exact Weapon identity through storage and automatic issue ## Validation - cargo nextest run -p cat-sim --test source_cargo_campaign captain (3 passed) - cargo nextest run --workspace --profile smoke (74 passed) - cargo clippy -p cat-sim --all-targets -- -D warnings - cargo fmt --all -- --check - git diff --check
Fix Captain weapon demand
Some checks failed
Rust and WASM quality gates / Rust format and Clippy (pull_request) Successful in 1m2s
Rust and WASM quality gates / Build test archive once (pull_request) Failing after 26m12s
Rust and WASM quality gates / Rust tests (shard 1/4) (pull_request) Has been skipped
Rust and WASM quality gates / Rust tests (shard 2/4) (pull_request) Has been skipped
Rust and WASM quality gates / Rust tests (shard 3/4) (pull_request) Has been skipped
Rust and WASM quality gates / Rust tests (shard 4/4) (pull_request) Has been skipped
Rust and WASM quality gates / Build browser client (pull_request) Has been skipped
a36dbba767
Select one non-repeating Smithy weapon order when an appointed Captain observes an exact work-capable warrior without usable or in-flight supply. Cover the complete Ore-to-Smithy finite identity journey through storage and automatic issue to that warrior.

Powered by human calories and mass GPU cycles.
Some checks failed
Rust and WASM quality gates / Rust format and Clippy (pull_request) Successful in 1m2s
Rust and WASM quality gates / Build test archive once (pull_request) Failing after 26m12s
Rust and WASM quality gates / Rust tests (shard 1/4) (pull_request) Has been skipped
Rust and WASM quality gates / Rust tests (shard 2/4) (pull_request) Has been skipped
Rust and WASM quality gates / Rust tests (shard 3/4) (pull_request) Has been skipped
Rust and WASM quality gates / Rust tests (shard 4/4) (pull_request) Has been skipped
Rust and WASM quality gates / Build browser client (pull_request) Has been skipped
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin fix-captain-weapon-demand:fix-captain-weapon-demand
git switch fix-captain-weapon-demand

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff fix-captain-weapon-demand
git switch fix-captain-weapon-demand
git rebase main
git switch main
git merge --ff-only fix-captain-weapon-demand
git switch fix-captain-weapon-demand
git rebase main
git switch main
git merge --no-ff fix-captain-weapon-demand
git switch main
git merge --squash fix-captain-weapon-demand
git switch main
git merge --ff-only fix-captain-weapon-demand
git switch main
git merge fix-captain-weapon-demand
git push origin main
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
beasty/cat_idler!20
No description provided.