Recipe for purple does not match #5384
Labels
No Label
1. kind/balancing
1. kind/breaking
1. kind/bug
1. kind/construction
1. kind/documentation
1. kind/enhancement
1. kind/griefing
1. kind/invalid
1. kind/meme
1. kind/node limit
1. kind/other
1. kind/protocol
2. prio/controversial
2. prio/critical
2. prio/elevated
2. prio/good first issue
2. prio/interesting
2. prio/low
3. source/art
3. source/client
3. source/engine
3. source/ingame
3. source/integration
3. source/lag
3. source/license
3. source/mod upstream
3. source/unknown
3. source/website
4. step/approved
4. step/at work
4. step/blocked
4. step/discussion
4. step/help wanted
4. step/needs confirmation
4. step/partially fixed
4. step/question
4. step/ready to deploy
4. step/ready to QA test
4. step/want approval
5. result/cannot reproduce
5. result/duplicate
5. result/fixed
5. result/maybe
5. result/wontfix
ugh/petz
ugh/QA main
ugh/QA NOK
ugh/QA OK
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#5384
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When I seach the crafting guide how to craft violet, one of the recipes tells me, I could use red an blue.
Clicking on "All" my red an blue dye are transfered from the Inventory to the crafting table, but won't produce violet but magenta.. See screenshots.
i wish there was a way to see where specific recipes were defined...
from MTG's dye:
from unifieddyes:
upstream issue: https://github.com/mt-mods/unifieddyes/issues/14, which i expect will be ignored.
in the meantime, i'll integration the recipes
642156f45a
QA
What's the "correct" combo? On testserver, both blue and red AND blue and magenta make two violet dye?
Maybe we should simply leave the recipe combinations to unified dyes and invalidate all others?
the problem here was that there was a recipe conflict - the same recipe was registered w/ two different outputs. many dyes have multiple different combination recipes. i'm not sure it's worth removing all the recipes from mtg dyes. it'd be good to clean up all the duplicate recipes from both mods, but imo a very low priority.
The recipe conflict is resolved. Let's postpone cleaning up all the recipes to another issue: #5605.
this is live