Presets

World presets

Keep inventory preset workflow

Keep inventory preset workflow is now a complete Gamerule workflow instead of a templated command note. Use this preset when deaths should not destroy test items, keys, boss rewards, or progression tools. It is especially useful while iterating on adventure maps because a failed combat test should not force the creator to rebuild the inventory state. The article keeps the setup fields, output review, Project placement, and result capture together so the command is easy to audit before it becomes part of a map setup, event trigger, or reusable command pack. The workflow keeps the exact `keepInventory` rule and `true` value visible before the command is saved. That sounds small, but it prevents the common confusion between a playtest convenience and a release rule that should be documented for players.

Read inENRUDEESPT中文日本語VIFR한국어IDPLTR

Preset result

`/gamerule keepInventory true` is saved as a reusable setup line for testing and adventure maps.

Output

Keep inventory gamerule command

/gamerule keepInventory true

Preset screenshot

Start with the Gamerule controls that define the preset state.
The second shot highlights the setting or companion command that changes player-facing behavior.
The output shot keeps the final command or command pair visible before it enters Project.
`/gamerule keepInventory true` is saved as a reusable setup line for testing and adventure maps.

Build the preset

  1. Open the Gamerule workbench.
  2. Set Rule to `keepInventory`.
  3. Set Value to `true` for testing or player-friendly map rules.
  4. Review the `/gamerule keepInventory true` output.
  5. Save the command to Project with a name that explains whether it is debug-only or release-ready.
  6. Run it before inventory-heavy tests and confirm the rule is part of the setup pack.

Why this Gamerule preset belongs in Project

Use this preset when deaths should not destroy test items, keys, boss rewards, or progression tools. It is especially useful while iterating on adventure maps because a failed combat test should not force the creator to rebuild the inventory state.

The workflow keeps the exact `keepInventory` rule and `true` value visible before the command is saved. That sounds small, but it prevents the common confusion between a playtest convenience and a release rule that should be documented for players. A copied command is only useful when the surrounding assumptions are visible: selector scope, world state, order inside the pack, and the exact output that will be pasted into Minecraft. Treat this preset as a checkpoint where those details can be reviewed before the command leaves NBTForge.

The gallery is structured around that review. The first shot shows the workbench state, the second shot calls out the field or companion module that changes player-facing behavior, and the output shot keeps the command or command pair visible. When the preset has a visible result, the in-game capture confirms the same idea in a restored test world rather than relying on a generic overlay.

Testing and scope checks

Keep inventory can hide real survival balance problems. Use it during iteration, then decide whether the final map should keep it enabled or move the rule into a debug-only setup function.

Run the first smoke test with a narrow selector and a clean world state. Environment, utility, routing, and feedback commands can look harmless, but they often affect every player or the whole world. Confirm the command changes only the intended state, then save the exact output beside the setup or follow-up lines that explain why it exists.

If the command becomes part of a function file or command-block chain, test the copied artifact, not only the live workbench state. That catches stale selectors, wrong command order, missing setup lines, and effects that only appeared to work because a previous test left state behind.

  • Keep selectors narrow until the full pack is reviewed.
  • Place world setup before encounter-specific overrides.
  • Save feedback commands next to the state change that triggers them.

Where to go next

Pair this with reward item presets and cleanup commands so repeated tests start from a known inventory state.

For adjacent setup, compare the gamerule adventure map preset, adventure map key item preset, and kill cleanup preset.

FAQ

Can I paste this Gamerule command into chat?

Usually yes for a one-command smoke test if the selector is safe and the line is short. For repeatable map behavior, save it to Project and copy the ordered pack or function-style output.

Why include a result capture for a utility-style preset?

The result capture proves the command changed visible world, HUD, routing, or feedback state in Minecraft instead of only looking correct in the output panel.

What should I check before sharing this preset?

Check selector scope, command order, target version, and whether the command belongs in setup, encounter logic, feedback, or cleanup. Those categories decide where it should sit in a Project pack.

Open this workflow

Start from the related Gamerule workbench, then adjust the preset fields for your world.