Back to mods
CollectionMaster project artwork

CurseForge · Minecraft mod

CollectionMaster

Turn gathered resources into rewards through configurable item collections and milestones.

Choose a version Pick your version below, then grab the matching file.

Quick answer

Which CollectionMaster release should I use?

Updated yesterday
Latest stable file collectionmaster_1.0.1_mc26.2_neoforge.jar
Game version 26.2
Loader NeoForge

collectionmaster_1.0.1_mc26.2_neoforge.jar targets 26.2 with NeoForge. The project page does not say whether this file belongs on the client, dedicated server, or both. 1 required mod needs a matching file.

Where it goes

Is CollectionMaster required on the client, server, or both?

The project page does not say whether this file belongs on the client, dedicated server, or both.

Client Source doesn’t say
Dedicated server Source doesn’t say
Loader for this release NeoForge
Required install it here Optional supported, not mandatory Not supported do not install here Source doesn’t say do not assume

The source does not explicitly classify this release as client-only or server-only.

What else does collectionmaster_1.0.1_mc26.2_neoforge.jar need?

collectionmaster_1.0.1_mc26.2_neoforge.jar. Change the file and its required mods may change too.

1 required mod needs a matching file

Install Fabric API first, but 1 required mod has no matching file for this setup. Do not mix loader builds to force a match.

Fabric API Needed by collectionmaster_1.0.1_mc26.2_neoforge.jar
required
No matching file

We only count dependency files that match this setup. A file for another loader does not fill the gap.

Before you install it

Add CollectionMaster without breaking your instance.

Built for collectionmaster_1.0.1_mc26.2_neoforge.jar. Pick another file and the loader, install side or required mods may change.

  1. 01

    Stick to this file

    Use collectionmaster_1.0.1_mc26.2_neoforge.jar. It targets 26.2 with NeoForge; another release may have different loader, side or dependency requirements.

  2. 02

    Bring the mods it needs

    Install Fabric API first, but 1 required mod has no matching file for this setup. Do not mix loader builds to force a match.

  3. 03

    Put it on the correct side

    The project page does not say whether this file belongs on the client, dedicated server, or both.

  4. 04

    Pick the file you checked

    Use the “Get this file” button beside collectionmaster_1.0.1_mc26.2_neoforge.jar. It opens that exact file at the source.

About this project

What does CollectionMaster add?

CollectionMaster

CollectionMaster adds collectible item collections to Minecraft. Discover a collection by finding its target item, contribute items to complete progressively larger milestones, and claim item rewards as you advance.

✅ Features

  • Ready-to-play collections for common vanilla items. (Work in progress, more collections will be added)
  • Twenty-three default milestones, from 10 items up to 500,000, with configurable shared fallback rewards.
  • The included collections have their own themed reward tables. Custom collections can inherit the global milestones and rewards or define their own.
  • Progress and pending rewards are stored per player in the world save and validated by the server.

📖 Opening the catalog

Open the catalog with K by default. The key can be changed in Minecraft's Controls settings. You can also use either command:

  • /collectionmaster
  • /cmaster

In multiplayer, install the mod on both the server and each connecting client.

The catalog groups discovered collections by category. It shows each collection's target item, current progress, milestone requirements, and rewards. Undiscovered collections are not listed individually; the catalog can show an aggregate count of how many remain. Use the mouse wheel over the milestone area to browse milestones.

Choose 1, Stack, or All to deliver items from your inventory. A delivery is limited to the amount needed by the remaining milestones. Completed milestone rewards appear on their cards and can be claimed there. If the inventory cannot fit a reward, it remains pending.

⚙️ Collection definitions

Collection definitions are JSON files in:

config/collectionmaster/collections/

The directory is scanned recursively, so you can organize definitions in subfolders. On first launch, the mod installs ten example collection files. Existing files are preserved.

A minimal custom collection can omit both milestone fields and inherit the global milestone amounts and rewards:

{
  "id": "collectionmaster:amethyst",
  "name": "Amethyst",
  "category": "Ores",
  "target_item_ids": ["minecraft:amethyst_shard"],
  "enabled": true
}

Every definition requires a unique collection id, a name, a category, and exactly one target item in target_item_ids. Item IDs use Minecraft's namespace:path format. The enabled field is optional and defaults to true.

Using the global defaults

The global options file is config/collectionmaster.json. It contains:

  • default_milestone_amounts: 23 positive, strictly increasing item requirements. The built-in sequence is 10, 20, 50, 100, 250, 500, 1000, 2500, 5000, 10000, 20000, 30000, 40000, 50000, 60000, 70000, 80000, 90000, 100000, 200000, 300000, 400000, 500000.
  • default_milestone_rewards: 23 reward groups, one for each default milestone. Each reward has an item_id and a positive count. A group may contain more than one reward.
  • show_locked_collections: controls whether the catalog displays the aggregate count of undiscovered collections; defaults to true.

The global reward table is shared by collections that do not provide their own reward definition. Edit the options file to change the defaults for newly defined collections that inherit them.

Overriding rewards for a collection

Use milestone_rewards when a collection should keep the global milestone amounts but use a different reward table. It replaces the entire global reward table and must contain exactly 23 reward groups, in milestone order:

"milestone_rewards": [
  [{"item_id": "minecraft:amethyst_block", "count": 2}],
  [{"item_id": "minecraft:experience_bottle", "count": 4}]
]

The snippet shows the shape only: a complete collection definition must provide all 23 groups. Each group is a list so a milestone can grant multiple item types.

Defining custom milestones

Use milestones to define a collection's milestone numbers, requirements, and rewards directly:

"milestones": [
  {
    "number": 1,
    "required_amount": 32,
    "rewards": [{"item_id": "minecraft:amethyst_block", "count": 2}]
  },
  {
    "number": 2,
    "required_amount": 128,
    "rewards": [
      {"item_id": "minecraft:amethyst_block", "count": 4},
      {"item_id": "minecraft:experience_bottle", "count": 8}
    ]
  }
]

Milestone numbers must start at 1 and be consecutive; requirements must be positive and increase from one milestone to the next. Each milestone needs at least one reward. Use either milestones or milestone_rewards in a collection file, not both.

Bisect Pedrijoe

Project description from CurseForge.

Pick your setup

CollectionMaster by Minecraft version and loader

Choose the version and loader you play, then open the matching release.

6 available setups

Check the dependencies, then try the file in a copied instance before changing a world you care about.

Recent files

CollectionMaster versions and loaders

12 of 12 releases match

Looking for an older file? The official CurseForge project page is in Resources.