Use the Blueprint Manager Plugin on Rust

Blueprint Manager decides which blueprints players already know, so they skip the research grind. You can hand out whole groups of blueprints through permissions, set a starter list that everyone gets, hold chosen blueprints back until some time after a wipe, and reset or unlock a player's blueprints from a command. This guide covers installing it, the permissions, the admin commands and the advanced mode.

Checked against Blueprint Manager 2.1.5 by Whispers88 on uMod (released 2 July 2026), October 2026.

Install it

1. Open the Plugins tab, search the Store for BlueprintManager and press Install. How to install Oxide/uMod plugins on your Rust server has the steps, including adding Oxide to a plain server.
2. A plugin installed onto a running Oxide server stays unloaded until you Restart the server or type oxide.load BlueprintManager in the Console. On Carbon it loads by itself, and c.load BlueprintManager or c.reload BlueprintManager in the Console loads or reloads it by hand.
3. Its permissions exist only once it has loaded. Its config file, oxide/config/BlueprintManager.json (carbon/configs on Carbon), appears after the first load.

Permissions

The plugin builds most of its permissions from the game's own blueprint list when it starts:

Grant them from the Console with oxide.grant on Oxide, or c.grant on Carbon. For example, to give the default group every blueprint and an admin group the admin commands:

oxide.grant group default blueprintmanager.all
oxide.grant group admin blueprintmanager.admin

On Carbon, the same lines start with c.grant instead:

c.grant group default blueprintmanager.all
c.grant group admin blueprintmanager.admin

A player gets the blueprints when they connect, and again when a permission or group changes, as long as Update players on permission change (automatically updates a players BPs when their permissions change) is on (it is by default).

Admin commands

These need blueprintmanager.admin. Without it the player is told "You don't have permission to use this command." They work as a chat command with a slash, or in the Console, and the target player must be online. You can give a name or a SteamID64.

Items are given by shortname or item ID, such as rock.

The config

Open Installed on the Plugins tab, press Config on Blueprint Manager, edit, press Save, then Reload plugin. The main settings are:

• Simple Mode (disables advance blueprint management options): true.
• Wipe BPs with Map Wipe: false. Turn it on to clear every player's blueprints when a new map is created.
• Blacklist (items from being automatically learnt): a list of item shortnames the plugin never hands out.
• DefaultBPs (Blueprints to be automatically learnt): a list everyone learns on connecting.
• Assign custom BP unlocks to various perms (permission, BP List: your own permission names, each with a list of items. Start from the two examples.

Advanced mode

Set Simple Mode to false and reload. The plugin then writes an entry for every blueprint under Advanced Blueprint Management Options, named by item shortname, with these fields:

• defaultBP: everyone learns it automatically.
• canResearch: whether it can be unlocked in the tech tree. When it can't, the player is told the blueprint is locked, with the time left or "forever".
• scrapRequired: the blueprint's scrap requirement, which the plugin sets on it.
• unlockMinutesAfterWipe: minutes after the map was created before it can be researched. -1 means no timer. The timer applies only when this is above 0 and canResearch is false.
• autoUnlockMinutesAfterWipe: when the timer ends, add it to the blueprints everyone learns.

The file gets long because every blueprint is listed, so search it rather than scrolling.

Common problems

1. "Cannot find player by the ... identifier". The player is offline or the name doesn't match. Use their SteamID64.
2. "Cannot find a blueprint for ... Use the item shortname or ID". Check the item's shortname.
3. The permission doesn't exist. The plugin is still unloaded. Restart, or run oxide.load BlueprintManager (Oxide) or c.load BlueprintManager (Carbon).
4. A config entry is ignored. The Console prints a "Cannot find a blueprint" line at load for any shortname in the blacklist, default or custom lists that doesn't match an item.