Cooldowns & Fail Rates

Control pacing, balance rewards, and keep things fun.

Cooldowns and fail rates are the heart of a healthy work command. They decide how often members can earn, how predictable outcomes feel, and how your economy stays balanced over time.

In this section, we’ll break down how to use these settings wisely — using our magical girl /bake job as an example.

⏳ Cooldowns

How often a command can be used.

The cooldown determines how long a member must wait before using the work command again.

In the dashboard, you’ll see two fields:

  • Cooldown – the number

  • Unit – minutes, hours, or days

Example: Daily Magical Baking Job

For .bake, we want this to feel like a once-a-day routine.

Set:

  • Cooldown: 1

  • Unit: Day

This means:

Members can bake magical treats once per day — not endlessly.

🧠 Choosing the Right Cooldown

  • Minutes → Fast-paced servers, testing, mini-games

  • Hours → Casual repeatable jobs

  • Days → Daily routines, roleplay jobs, long-term balance

💡 Tip: Longer cooldowns make rewards feel more meaningful.

🎲 Fail Chance

When magic doesn’t go as planned.

Fail chance controls the probability that a work command fails instead of succeeds. Failure doesn’t have to feel bad — it can be funny, cute, or story-driven.

You can now choose between:

  • Fixed percentages

  • Ranges (new!)

🧮 Fixed Fail Percentage

A simple, predictable option.

Example:

Fail Chance: 30%

This means:

  • 70% success

  • 30% failure

Great for stable, predictable systems.

🎭 Dynamic Fail Ranges (Recommended)

Ranges make outcomes feel less mechanical and more alive.

Example:

Fail Chance: [20–40]

Each time /bake is used, Mochi randomly selects a fail chance between 20% and 40%.

This creates moments like:

“Why did it fail today but not yesterday?”

Perfect for roleplay and immersion.

🪄 Success & Fail Previews

On the right side of the dashboard, you’ll see a live preview of both outcomes:

  • Success preview shows what members see when it works

  • Fail preview shows what they see when it doesn’t

This lets you:

  • Test tone

  • Check formatting

  • Verify variables like {reward} and {cooldown}

Always preview before saving — it helps catch mistakes early.

⚖️ Balancing Tips

To keep work commands enjoyable:

  • Pair longer cooldowns with higher rewards

  • Use fail ranges instead of high fixed failure

  • Keep failures fun, not punishing

  • Avoid stacking high fail rates with long cooldowns

A good rule of thumb:

If something can fail, make it worth retrying tomorrow.

💡 Why This Matters

Cooldowns prevent spam. Fail rates prevent farming.

Together, they:

  • Protect your economy

  • Encourage daily engagement

  • Add tension and surprise

  • Make work commands feel earned

Your magical girl shouldn’t bake endlessly — but when she succeeds, it should feel special ✨

Last updated