Custom Progression · Format Guide

1 · How to use it

1. Open the game and click Custom Progression in the top bar (visible in both the Dots and Bloops modes).
2. Click Reset editor to default template. The editor fills with the game's current default numbers as JSON — this is the exact schema the loader expects, so it's the best starting point.
3. Edit any values you like. You can also delete everything you're not changing — anything you omit keeps its default (see §3).
4. Make sure the toggle is set to Custom, then click Apply Custom Progression.
5. The page reloads and the whole game rebuilds from your numbers. Your save is kept — only the rules change, not your progress.

To go back, open the menu, switch the toggle to Default, and click Use Default Progression. Your custom JSON stays saved in the editor for next time.

2 · What you can and can't change

Everything in the progression is tunable — not just the costs, but the actual effect of every upgrade. Each tree/shop node and each core Dots upgrade carries an effect descriptor (see §5), so you can make "Spark" give ×10 Bloops instead of ×2, turn a flat bonus into a per-level one, retune rover speed, the prestige multiplier, the XP curve, the generator-tier multiplier — all of it.

The only things you can't do: change the wiring between nodes (prereqs), or add brand-new upgrades — an id that doesn't already exist has nothing behind it, so it's rejected with a note. Everything else is fair game.

3 · The shape of the JSON

The top level is a single JSON object. Every key is optional — include only what you want to change. There are three kinds of keys:

• Upgrade categories (arrays) — merged by id. List only the upgrades you're editing, and within each only the fields you're editing.
• Perk lists (levelPerks, bloopPerks) — merged by lvl.
• Global constants — plain numbers (or number arrays) that replace the default.

So this minimal example only makes Dot Value cheaper and slows the XP curve — everything else stays default:

{
  "basic": [ { "id": "dotValue", "baseCost": 3 } ],
  "xpGrowth": 1.5
}

4 · Upgrade categories

Each is an array of objects identified by id. The table lists which fields you may set; any other field is ignored.

Cost model

• Capped upgrades (basic, prestige, funUpg, sparkleShop): the price of the next level is ceil(baseCost × growth^level), stopping at max levels.
• Generators (funGens): same curve, uncapped. Each unit owned produces rate Bloops/sec (before tier and global multipliers).
• Tree nodes (tree, rtree, btree): single purchase by default. A node with levels > 1 charges cost × costScale^(levelsOwned) per level. tier = its row, col = its column in the diagram.

Dots half

Bloops half

The ids in each category are fixed. Use Reset editor to default template to see them all — e.g. generators are cursor, granny, farm, factory, mine, portal, temple, bank, rocket, galaxy, rift, cosmos.

Effects — what each upgrade does

The effect field controls an upgrade's bonus. For the three basic upgrades it's simply a number (per-level strength):

• dotValue.effect — value multiplier per level (default 2 = doubles = +100%; use 1.5 for +50%, 3 to triple).
• capacity.effect — extra dots on the field per level (default 1).
• dotRate.effect — spawn-interval multiplier per level (default 0.8 = 20% faster each level; lower is faster).

For every tree and shop node, effect is a small descriptor object (or an array of them for a node that does two things). Shape:

{ "stat": "dotMul", "op": "mul", "base": 2, "per": "once" }

• stat — which bonus it feeds (table below). Required.
• op — "mul" (multiply, default) or "add" (add).
• base — the number applied.
• per — "once" (full effect if owned, default) or "level" (scales with levels owned: base^level for mul, base×level for add).

Examples: {"stat":"dotMul","base":2} = ×2 Dots when owned · {"stat":"dotMul","base":1.5,"per":"level"} = ×1.5 Dots per level · {"stat":"capAdd","op":"add","base":3,"per":"level"} = +3 capacity per level.

A few special effects: magnet (any value owned turns it on), {"stat":"vastReach","table":[0,0.1,...]} (a per-level lookup table), and dotPerNode (Scale Dots: ×Dots grows with how many tree nodes you own).

{ "btree": [ { "id": "b1", "name": "Mega Spark", "desc": "×10 Bloops",
                "effect": { "stat": "bloopMul", "base": 10 } } ] }

A node's desc/name is display text only — update it too when you change an effect so the card matches (the prestige and shop cards regenerate their numbers automatically; tree-node text does not). An unknown stat is ignored.

5 · Level perks

Both halves share one level. Milestone perks fire at a level and are permanent. Merge these by lvl; you can change a perk's strength (v), type or desc.

{
  "levelPerks": [
    { "lvl": 5,  "type": "dot", "v": 3,  "desc": "×3 Dots" },
    { "lvl": 3,  "type": "cap", "v": 2,  "desc": "+2 base Dot Capacity" }
  ]
}

Editing a perk's lvl isn't supported (the level it fires at is its identity) — change v/desc instead. Set v to 1 to neutralise a multiplier perk.

6 · Global constants & economy

These are plain top-level numbers (a couple are number arrays). Replace any of them:

7 · Generator tier upgrades

Each Bloops generator has 7 Cookie-Clicker-style tier upgrades, each multiplying that generator's output by genTierMult (default ×2). You control the multiplier, when they unlock, and what they cost:

• Own funGenTierThresholds[t] of a generator to unlock tier t.
• That tier costs generator.baseCost × funGenTierCostMults[t].
• genTierMult (a global constant, §6) sets the per-tier output multiplier.
• funGenTierNames sets the display names — an object keyed by generator id, each value an array of 7 strings.

{
  "funGenTierThresholds": [1, 10, 25, 50, 100, 200, 300],
  "funGenTierNames": {
    "cursor": ["Faster", "Quicker", "Snappy", "Rapid", "Blazing", "Hyper", "Instant"]
  }
}

8 · Worked examples

A · "Speedrun" — everything cheaper, faster levels

{
  "basic": [
    { "id": "dotValue", "baseCost": 3, "growth": 1.6, "max": 50 },
    { "id": "capacity", "baseCost": 5, "growth": 1.7 }
  ],
  "xpGrowth": 1.25,
  "treeUnlockDots": 50,
  "resetUnlockDots": 50000,
  "resetMinDots": 50000
}

B · "Idle empire" — beefier Bloops generators

{
  "funGens": [
    { "id": "cursor", "rate": 1,  "baseCost": 10 },
    { "id": "granny", "rate": 8,  "growth": 1.13 },
    { "id": "farm",   "rate": 50 }
  ],
  "funSparkleDiv": 100000,
  "sparkleShop": [
    { "id": "sGain", "baseCost": 2, "max": 25 }
  ]
}

C · "Hard mode" — steeper everything

{
  "basic": [ { "id": "dotValue", "growth": 2.8 } ],
  "tree":  [ { "id": "p1", "cost": 200 }, { "id": "p3", "cost": 1500 } ],
  "xpGrowth": 1.6,
  "prestigeMinRP": 2000
}

9 · Notes & FAQ

Does it affect both Dots and Bloops? Yes — one JSON object covers both halves. The Dots keys (basic, tree, rtree, prestige, levelPerks, the dots thresholds) and the Bloops keys (funUpg, funGens, btree, sparkleShop, bloopPerks, the tier arrays) live side by side.

Will applying reset my progress? No. Your save (dots, bloops, levels, owned upgrades) is untouched — only the rules change. The page reloads so everything rebuilds cleanly.

What if I set a cost below what I've already paid? Totally fine — you simply keep what you own; future purchases use the new prices.

Can I change what an upgrade does, not just its cost? Yes — that's the effect field (§5). Every tree/shop node and the core Dots upgrades expose it, so you can rescale any multiplier, flip flat bonuses to per-level, and so on.

Can I add a brand-new upgrade or generator? No. Effects are wired to known ids, so an unknown id has nothing behind it — it's skipped with a note. Retune the existing ones instead.

What happens to fields I leave out? They keep their default value. Omitting a key, an array entry, or a single field all mean "leave it as shipped."

It says "Applied with N notes" — is that bad? No. Notes flag fields that were skipped (a typo'd id, a wrong type). Everything valid still applied. Fix the flagged lines if you meant them to take effect.