Your registry account is separate from player accounts.
CONTENT OPERATIONS
Case library
Independent registry
Sandbox by default · No connection to game accounts, balances or the
engineers’ deployment. Integration stays with the engineering team.
CASE BUILD WORKFLOW
Turn a portfolio gap into a measured caseEach draft should carry the decision record from strategy
through launch.
1 · Find the gapGame, audience, role and price band
2 · Set the promisePlayer reason to choose the case
3 · Review evidenceComparable demand and compositions
4 · Build the payoutSupport, anchor and chase skins
5 · Review riskRTP, typical result and fulfilment
6 · MeasureChoice, repeat use and contribution
Find a Wayger caseNarrow the portfolio by its strategic role, theme and
economics.
DECISION SUPPORT
Use observed demand to choose what Wayger should test
This page ranks cases
within one competitor and one captured measure.
Use it to find recurring concepts, price points, names and skin
combinations that deserve a Wayger test. It does not estimate
unique players, future revenue or the probability that a Wayger
case will succeed.
1 · Find a signalSelect a game, measure and source snapshot.
2 · Read the contextCheck creator, price, theme and captured skins.
3 · Form a hypothesisExplain what may be driving the observed activity.
4 · Test at WaygerBuild a draft and measure exposure, choice and repeat
play.
Do: compare cases measured by the same source
counter. Do not: compare raw opening counts
between sites or treat visits × rank as player count.
Research findings about each source and case type. Unknown scope
remains unknown. These reviews supplement the original snapshots;
they do not change captured values or qualify a player ranking.
Gathering priorities and coverage
Traffic determines research priority only. It never scales a case
score into estimated players. Status describes inspected evidence,
not the absence of a feature on the entire site.
New draft
Case details
Research informing this design
References point to immutable observations. Add a reference
from Case analytics and explain the design hypothesis;
source popularity does not validate Wayger odds or returns.
New draft target: 84%–87.5%, initially 85.4%. Payout variance
does not change RTP. Price is calculated from the table.
Rounded effective RTP must remain at least 84% to release.
How rare skins, odds and RTP fit together
RTP is the sum of each item’s probability multiplied by its
value, divided by case cost. A rarer, more valuable prize
can increase payout variance while the average return stays
the same.
Illustration: at a cost of 10, a 90% chance of 5 and 10%
chance of 40 returns 8.5 on average. A 99% chance of 5 and
1% chance of 355 also returns 8.5. Both have 85% RTP, with
very different payout experiences.
Choose the target RTP, then the items and probability rule.
This tool calculates cost from that table; it does not
silently change odds to meet a desired price. If you change
the table, recalculate. Chase labels identify items for
review and do not change their odds. Chase and other-item
contributions add up to effective RTP.
Names cannot claim profit, rarity, return rate or official
endorsement.
MARKETING
Marketing & launch brief
Turn the case concept into a clear customer promise and a
simple learning plan. Odds and price remain controlled by
the economics section.
1 · PositionWho is it for and why would they choose it?
2 · MeasureWhat customer and business result signals success?
3 · LearnWhat fair comparison will tell us what worked?
STARTING POINT
Find a starting collection
Generate a catalogue shortlist inside this draft, then
review and adjust every skin before calculating.
The assistant reads current USD catalogue quotes and item
types from this database. It marks the highest-value skin as
the visual hero and groups supporting skins by kind or value.
After calculation, the drop table also shows each skin’s win
chance. Recommendations never invent odds, RTP or the final
case price.
Drop table
Selected skins, roles and probabilities
Case economics
Price and player-value indicators calculated from the selected
skins and probabilities.
Sandbox values use USD listing quotes as demonstration display
units. This is not an approved cash-to-Chip conversion.
Payout shape and design review
Uploaded artwork
No card artwork
Build the case from catalogue skins
Pick the CS2 or Rust skins first. Their images, exact market
names and current catalogue quotes will be connected to the
drop table automatically.
Up to 8 MB. Art is supplied by your art team.
Release review
Review the current candidate against the last release. A release
permanently freezes its values, weights, rule and uploaded art.
RESEARCH ONLY · Competitor valuations and currencies are preserved.
These records are never released to the game.
Find comparable competitor casesStart with the game and source, then narrow by evidence
quality, composition and price.
Popularity ranks are within each source, not a cross-site league
table. Traffic-weighted rank combines within-source position with
estimated monthly site visits for research prioritization; it is
not a player count. Unmeasured cases remain unranked.
Identity reconciliation
Record an evidenced link to a canonical item. Original research
rows remain unchanged.
Add a registry user
Engineer read-only token
Access to exports and released versions only. Expires in 30 days.
Released definitions
Read-only exports for the engineering team. Import and activation
remain with JP and Jose.