Repository navigation
feat: draw output aspects from a random pool - #12
Draft
XxFran10xX wants to merge 1 commit into
Draft
XxFran10xX wants to merge 1 commit into
XxFran10xX wants to merge 1 commit into
Conversation
Outputs can list an aspect_pool with a pick count. Each new project draws that many distinct aspects from the pool and adds them to the output's fixed aspects, so the same research needs different aspects each time. Draws are saved with the station; on load, draws that left the pool are replaced from it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Shaymin's request: runestone research should not need the same aspects every time. An output can now list an
aspect_pooland apickcount. Each new project draws that many distinct aspects from the pool, at random, and adds them to the output's fixedaspects(which stay optional).pool_aspects), so they survive restarts. Pool aspects that were not drawn count as off-recipe and are rejected like any other wrong aspect.pickmust be between 1 and the pool size. A pool aspect must exist, need more than 0 points, and not also be a fixed aspect. Fixed aspects pluspickmust fit the 6 GUI rows.aspect_poolbehave exactly as before./research reload, a running station keeps its current draws until the next restart. Fixed aspects already behave the same way.Tests
mvn verify: 240 tests pass and the 100% line-coverage gate is met. New tests cover loading and validation, draws and reconciliation, persistence, and the manager flow. LocallyResearchPersistenceTest#completedProjectsAreDeletedAndFailedDeletionIsLoggedwas excluded: it fails on Windows onmaintoo because the file is still open when the test deletes it. Linux CI runs it.zz_pool_testoutput: pick 3 of earth/nature/fire/ice/water/air):[air, ice, earth]and reshuffled rows (warnings logged), opened, and could be scrapped.Codex stub ... completed output zz_pool_test).Docs:
TF-Minecraft/Docsprojects/Research/overview.md(outputs config row) should get theaspect_poolkeys once this is merged.🤖 Generated with Claude Code