Create: Unlock Schematics

This mod is very simple and has a very specific use: it allows modpack makers to hide schematics from the Schematic Table.

Locked schematics should be placed in locked folder inside the schematics folder. The path would look like this: <instance>/schematics/locked/<schematic name>.nbt.

Then, to unlock the schematic you would use the command this mod adds:

/schematic unlock <schematic name>[.nbt]

• Schematic name can be with .nbt extensions or without.
• If schematic with same name already exists in the schematics folder, it will not be replaced. Player will receive a message that schematic is already unlocked.
• Due to the reason above - your locked schematics should have somewhat unique name, to avoid conflicts with user-created schematics.
• Command requires elevated permission level: cheats enabled, op, server owner, etc...

Knowledgeable folks may have already guessed how this works. Yes, it just copies the file from one folder to another.

Command can be used as a quest reward directly in FTB Quests config ui - '/execute as @p run schematic unlock pillar' or using KubeJS events:  

Unlock schematic on quest completion: 

Create is not required as a dependency. But, obviously, mod is pointless without it. 

Feel free to suggest a feature, if you need it for your modpack. 

•

•

Check out my other mods: 

Enjoying the mod? Your support would be greatly appreciated! 

This mod is very simple and has a very specific use: it allows modpack makers to hide schematics from the Schematic Table.

Locked schematics should be placed in locked folder inside the schematics folder. The path would look like this: <instance>/schematics/locked/<schematic name>.nbt.

Then, to unlock the schematic you would use the command this mod adds:

/schematic unlock [.nbt]

• Schematic name can be with .nbt extensions or without.
• If schematic with same name already exists in the schematics folder, it will not be replaced. Player will receive a message that schematic is already unlocked.
• Due to the reason above - your locked schematics should have somewhat unique name, to avoid conflicts with user-created schematics.
• Command requires elevated permission level: cheats enabled, op, server owner, etc...

Knowledgeable folks may have already guessed how this works. Yes, it just copies the file from one folder to another.

Example:

Unlocks the schematic on quest completion:

onEvent('ftbquests.completed', event => {
    event.server.runCommandSilent(`execute at ${event.player.id} as ${event.player.id} run schematic unlock pillar`)
})

Create is not required as a dependency. But, obviously, mod is pointless without it.

Feel free to suggest a feature, if you need it for your modpack.

Enjoying the mod? Your support would be greatly appreciated!