Use and steps
A visible path from input to trade-off.
- 01
Set mode and goals
Choose the context and weight only the goals that matter to you.
- 02
Enter owned Charms
Copy names and Notches from your current UI, record when you checked them, select the modes you confirmed there, then add your own goal-fit and drawback-risk ratings.
- 03
Check each Pair
Mark what you personally confirmed; anything missing remains Unknown.
- 04
Inspect trade-offs
Read separate Confirmed, Conditional and Rejected sections without a combined score.
Worked example
One known Pair, one unknown Pair.
Enter three owned Charms under a three-Notch budget. If one two-Charm Pair is confirmed compatible, another is confirmed conflict and a third is not checked, the results separate those outcomes instead of treating missing knowledge as compatibility.
Confirmed
Fresh inputs and every included Pair checked compatible
Conditional
Unknown Pair or a confirmation older than 30 days
Rejected
Budget, selected mode or confirmed Pair conflict failed
Method
Keep confirmed and uncertain choices separate
The planner checks every non-empty combination up to three slots. Confirmed and Conditional choices are compared separately. A choice is marked as a weaker fit only when another is at least as good on every active goal, risk and Notch cost, and better on at least one.
Limitations
No hidden gameplay layer
The planner does not load verified effects, health formulas, merge outcomes, clan exceptions, or an automatic tie-break. Player ratings are subjective inputs. A large result set is grouped by identical visible values and kept intact.
Evidence boundary
Why some Charm answers stay conditional
This planner keeps unverified Notch and Pair details out of its results. Confirm those details in your current game UI before treating a combination as ready.
Privacy
This page forgets the session.
Charm names, Notches, ratings, modes, dates, Pair states and results stay only on this open page. Clear Session or refresh removes them. Site-level measurement or advertising scripts may load under the site's consent settings, but these player inputs are never passed to them.
What is not collected
No player inputs sent to analytics or advertising
The planner does not send Charm inputs or results to a server or third party.
FAQ
Questions the comparator must answer honestly.
Why did a Pair become Conditional?
At least one included Pair is Unknown, or one of its UI confirmation dates is more than 30 days old.
Why is there no single winner?
Different goals, risk and Notch cost create real trade-offs. The planner keeps every still-competitive choice visible and does not invent a combined score.
What happens above 25 comparable choices?
The true count stays visible. Choices with identical values are grouped, every member remains inspectable, and the page asks you to narrow inventory or goals.
Can these entries become site data?
No. Your entries and calculated combinations never become site-provided Charm data.
Next step
Verify Conditional Pairs in your current game UI.
Then update the Pair state or observation date and compare again.