Clean Your Keycaps Systems

Clean Your Keycaps has several later systems exposed through Roblox’s official commerce catalogs: Common, Rare, and Legendary Crates; Luck and server Luck; Shiny Chance; and Instant Weather. These names are enough to confirm that the developer recognizes the concepts. They are not enough to publish Crate pools, probabilities, pity, Shiny effects, Weather types, schedules, or rewards.

This hub gives each system one canonical guide and a shared evidence rule. Use the current in-game panel for operating details, distinguish permanent gamepasses from repeatable developer products, and record one variable at a time.

Evidence status: Catalog names are Official. All random rates, pools, triggers, durations, stacking, and rewards remain Needs in-game testing. No complete index is claimed.

Choose a systems guide

Use Crates to compare the three officially named Crate products and document a live pool safely. It explains why product tier names cannot prove reward rarity or odds.

Use Luck & Shiny to separate the 2x Luck and 2x Shiny Chance gamepasses from one-use Luck Roll and server Luck developer products. It avoids treating several multiplier names as one stat.

Use Weather to verify a live Weather state, trigger, duration, affected mechanic, and Instant Weather product without inventing a schedule.

Crates: names are not drop tables

The official developer-product catalog contains Common Crate, Rare Crate, and Legendary Crate entries created August 1, 2026. The names establish three product tiers. They do not reveal contents, reward weights, guaranteed rarity, duplicate handling, normal acquisition, or whether the products remain visible in every server.

Before opening a Crate, capture the current pool and probability panel if the game provides one. Record source, cost type, and any server Luck or personal Luck state. Then record the actual result.

Do not build an odds table from a few openings. A complete current pool needs every entry and the displayed or well-supported rate source. If no pool is shown, publish only observed results with sample size and date.

Luck: personal, server, and one-use concepts

Roblox lists a permanent gamepass named 2x Luck. Developer products include 5x Luck Roll [1 USE] and server Luck multipliers from 2x through 64x. These are distinct catalog entries and may have different scopes or durations.

Do not combine their labels by arithmetic unless the current game displays the result. A one-use roll may apply to one event, while server Luck may affect everyone in the current server for an unknown period. The catalog does not say.

Before testing, record every visible multiplier and the target system. Use a sufficiently large sample for random outcomes and avoid changing more than one effect.

Shiny Chance is a separate pass

The official gamepass catalog lists 2x Shiny Chance separately from 2x Luck. That confirms a Shiny chance concept and suggests the two labels are distinct purchases, but it does not define their relationship.

Identify what can become Shiny in the live game. Capture the base chance if shown, the effect of a Shiny outcome, and which action rolls it. Do not infer that a Shiny cap is more valuable, faster, rarer by a particular amount, or purely cosmetic.

One surprising result is not evidence of the base rate. Keep sample size and active effects visible.

Weather: existence without a schedule

Instant Weather is an official developer-product name created August 1. It confirms a Weather concept but no public type list, natural schedule, duration, boost, reward, or trigger.

When Weather appears, record the exact on-screen name, start and end time, visual indicator, and any tooltip. Compare the same action before, during, and after while keeping tools and passes stable.

Do not state that Weather affects Luck, money, Shiny chance, cleaning, Workers, or Crates unless the live game says so or a controlled observation supports it.

Permanent pass versus developer product

The distinction matters for all these systems:

• 2x Luck and 2x Shiny Chance are in the gamepass catalog.
• 5x Luck Roll [1 USE] is a developer product.
• 2x through 64x Server Luck are developer products.
• Instant Weather and all three Crates are developer products.

Read current price, description, duration, target, and repeatability on the Roblox prompt. Public prices and blank descriptions can change, so this hub does not freeze them.

A safe random-system test

1. Confirm the exact official experience and current server.
2. Record Rebirth, tools, Workers, personal Luck, server Luck, Shiny pass, and Weather.
3. Capture the pool or effect description before spending.
4. Change one variable.
5. Record every outcome, including common results and duplicates.
6. Keep sample size visible.
7. Stop at a predetermined budget.
8. Label the result as observed rather than universal.

This protects players from two errors: presenting a tiny lucky streak as a rate and presenting a product label as a mechanic.

Systems mistakes

• Publishing Crate contents copied from another game.
• Treating Common/Rare/Legendary product names as a full reward hierarchy.
• Multiplying Luck labels together without a displayed stat.
• Assuming Luck includes Shiny Chance despite separate passes.
• Calling Instant Weather permanent or naming Weather types without evidence.
• Building odds from a few openings.
• Ignoring server-wide effects when comparing personal passes.

Systems FAQ

Are Crates confirmed?

Yes. Common, Rare, and Legendary Crate developer products exist. Their pools and odds are not publicly documented.

What does Luck affect?

The official catalog verifies Luck products but not the target system. Read the current live tooltip.

What is Shiny?

2x Shiny Chance confirms a random Shiny concept. Eligible outcomes and effects need in-game verification.

What Weather events exist?

No complete type list or schedule was verified. Record exact live Weather names when they appear.

Do these systems require Robux?

The reviewed evidence covers Roblox products and passes. Normal free acquisition or triggers must be checked separately and should not be assumed absent.