Skip to content

feat(workshop): Simplify resource crafting #125

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 26, 2023
Merged

Conversation

oliversalzburg
Copy link
Member

There was some edge case handling to balance production between plates and steel, which seems entirely redundant, given the balancing behavior of limited crafting.

The trigger applied to some hardcoded material, only a single one, and only for some crafts. This could cause unintuitive crafting behavior.

Even if the trigger wasn't hit, a resource could still be crafted under certain conditions.

The behavior of limited crafting was inconsistent.

The way resource crafting behaves now, should be far more intuitive and consistent. Additionally, it has now been documented.

@oliversalzburg oliversalzburg added type:feature Completely new behavior prio:accepted Tickets under active consideration for implementation needs:testing Work has been done. Someone needs to test it status:inprogress Someone is actively working on this labels Jan 26, 2023
@oliversalzburg oliversalzburg added this to the v2.0-rc milestone Jan 26, 2023
@oliversalzburg oliversalzburg self-assigned this Jan 26, 2023
@oliversalzburg oliversalzburg force-pushed the feat/workshop branch 3 times, most recently from 18bdd66 to 71377f0 Compare January 26, 2023 19:38
@oliversalzburg oliversalzburg force-pushed the main branch 2 times, most recently from 91dfd47 to 6c11005 Compare January 26, 2023 19:42
There was some edge case handling to balance production between plates
and steel, which seems entirely redundant, given the balancing behavior
of limited crafting.

The trigger applied to some hardcoded material, only a single one, and
only for some crafts. This could cause unintuitive crafting behavior.

Even if the trigger wasn't hit, a resource could still be crafted under
certain conditions.

The behavior of limited crafting was inconsistent.

The way resource crafting behaves now, should be far more intuitive and
consistent. Additionally, it has now been documented.
@oliversalzburg oliversalzburg merged commit c9a19a2 into main Jan 26, 2023
@oliversalzburg oliversalzburg deleted the feat/workshop branch January 26, 2023 19:45
@oliversalzburg oliversalzburg added status:completed This needs no further attention and removed needs:testing Work has been done. Someone needs to test it status:inprogress Someone is actively working on this labels Jan 26, 2023
@oliversalzburg oliversalzburg removed the prio:accepted Tickets under active consideration for implementation label Apr 27, 2025
@github-actions github-actions bot added needs:triage A developer needs to look at this policy-0 Applied Issue Policy Version labels May 9, 2025
@oliversalzburg oliversalzburg removed the needs:triage A developer needs to look at this label May 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
policy-0 Applied Issue Policy Version status:completed This needs no further attention type:feature Completely new behavior
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

1 participant