Cobbleverse

Cobbleverse Guides

Back to home

Player guide

Cobbleverse Economy and Department Stores

A version-specific guide to CobbleDollars, merchant categories, generated shop search, randomized inventories, progression purchases, and a reproducible budgeting method.

By
Cobbleverse Guides team
Last verified
Version
1.7.42
Checked with
In-game testing, Bundled data, External sources
Sources (6)
  1. Official COBBLEVERSE 1.7.42 releasecurrent release identity
  2. Bundled datadata-parser/data/config/cobbledollars/common.json — enabled NPC and wild-battle income categories
  3. Bundled datafrontend/public/department_stores.json — generated store families, merchants, randomization flags, offers, prices, and counts
  4. Bundled datadata-parser/extract_stores.py and frontend/src/app/battle-shops — generation and live filtering behavior
  5. Bundled datasite-content/items — maintained progression-material acquisition records
  6. Bundled datasite-content/guides/economy/images — verified in-game merchant and privacy-safe local Shop Browser captures
Report a correction

Know What the Economy Covers

CobbleDollars are an account balance shown in merchant interfaces, not an inventory stack. The verified 1.7.42 first-session screen began at zero, and the bundled cobbledollars/common.json enables earnings from NPC battles and wild-Pokémon battles. The data does not justify promising a fixed payout for every opponent, so plan from the bank value actually shown in game.

Know What the Economy Covers - TM Archivist interface showing the CobbleDollar bank balance along the bottom and priced TM offers
TM Archivist interface showing the CobbleDollar bank balance along the bottom and priced TM offers

This guide explains purchase decisions. The Shop Browser remains the authority for current generated prices and merchant placement.

Distinguish Merchant and Store Categories

The generated department-store file groups offers by store family and merchant. The current families include Farmers Market, regular Store Workers, randomized Store Workers, Relic Store Workers, and randomized Relic Store Workers. Each merchant record carries its display name, offer categories, item IDs, prices, counts, source file, and whether it is randomized.

Examples include apricorn/seed sellers, Master of Stones, TM Archivist, battle-item sellers, held-item sellers, vitamins, food, technology, and other specialist inventories. A category name is not proof that every settlement has the same worker.

Search the Live Shop Data

Open Battle & Shops, select Shops, and search by item or merchant. The results table displays Item, Price, Merchant, and Store from frontend/public/department_stores.json. Search before traveling so you know which worker name and store family to inspect.

Search the Live Shop Data - Shop Browser filtered to Gem with generated item, price, merchant, and store columns
Shop Browser filtered to Gem with generated item, price, merchant, and store columns

The Type Gems item page links the stable acquisition guidance to the same live browser. For moves and abilities, use the dedicated Move Shops and Ability Shops views.

Prioritize Early Mid and Late Purchases

Use criteria rather than a fixed shopping list:

Early progression: protect the starting supply. Buy only what directly restores your next attempt, enables a documented locator recipe, or replaces an exhausted capture resource.
Mid progression: spend on repeatable team infrastructure—needed TMs, held items, evolution/form requirements, or recipe materials—after checking that the chosen Pokémon can use them.
Late progression: reserve costly specialist materials for a confirmed legendary, form, or region objective. Follow the exact guide before purchasing multiple components.

The Progression Overview identifies the active checkpoint; Practical Team Building helps decide whether a move or item solves that matchup. A purchase is progression-critical only when the authoritative trainer, legendary, location, or item guide names it.

Treat Randomized Inventories as Randomized

Store families whose generated ID ends in _random contain merchants marked isRandomized: true. Their presence in the data means the offer belongs to a randomized pool; it does not promise that one permanent worker always carries it. Search results may show the same item in fixed and random store families.

For a reliable plan, prefer a fixed store_workers or relic_store_workers result when one exists. If only a randomized result exists, visit another appropriate store or wait for the server's documented refresh behavior. This repository does not currently verify a universal refresh interval.

Reproduce a Current Budget Example

At the 2026-07-30 snapshot, filtering the generated Shop Browser for Gem shows the Master of Stones listing type gems at 25,000 CobbleDollars each. A plan to buy one Water Gem, one Grass Gem, and one Fighting Gem therefore requires:

```text

25,000 + 25,000 + 25,000 = 75,000 CobbleDollars

`

This is a dated example, not a permanent promise. Reopen the live Gem search, copy the three displayed prices, and recalculate before buying. If the bank is below the total, rank the gems by the next verified recipe or matchup and purchase only the first required one. The linked table, not this dated arithmetic, is authoritative after data regeneration.

Troubleshoot a Missing Merchant or Item

No search result: check spelling and try the item namespace-free display name. Then inspect its item/guide page for loot or crafting alternatives.
Merchant name exists but worker is absent: verify the store family and whether the result is randomized. Search another generated merchant source rather than assuming every department store is identical.
Price differs in game: record the installed Cobbleverse version, server rules, merchant name, and displayed offer. A server may run changed data.
Balance does not increase: confirm the battle type and the account bank display. The current config enables NPC and wild-battle earnings but does not establish one payout amount.
Ingredient purchased but recipe fails: compare item identity, quantity, and version with the exact progression or legendary guide.
Unresolved discrepancy: attach a privacy-safe screenshot and source route to the correction form, omitting server addresses and account details.