Presets

Entity presets

Minecraft Effect Command Generator

Effect command searches often ask for infinite or custom effects, but most real maps need controlled duration, correct amplifier, and a safe target selector. This page keeps those choices visible before copy.

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

Preset result

A readable /effect command that is easy to reuse for kits, boss phases, map rewards, and test worlds.

Output

Effect command output

/effect give @p minecraft:speed 120 1 true

Preset screenshot

The NBTForge workbench state used for the minecraft effect command generator article, including the visible controls and generated output.

Build the preset

  1. Open Effects and select the target selector that should receive the effect.
  2. Choose the effect id, duration, amplifier, and whether particles should show.
  3. Use a long duration only when the effect is meant to behave like a persistent state.
  4. Copy the command and test that it targets only the intended player or entity group.

Amplifier is zero-based

Minecraft effect amplifiers are easy to misread. Amplifier 0 is level I, amplifier 1 is level II, and so on. Label the intended level in your preset notes when the command will be reused.

The sample speed command gives Speed II for 120 seconds with hidden particles, which fits kit or map movement feedback.

Infinite effects versus command logic

Very long effects are useful for NPCs, hidden helpers, and persistent arena states. For player buffs, shorter durations are easier to balance and easier to clear.

If an effect belongs to a phase system, keep the matching clear or replacement command in Project.

  • Use hideParticles for clean UI effects.
  • Use tags for mob effect targeting.
  • Use clear commands for reset flows.

Fit the preset into a real project

Treat Minecraft Effect Command Generator as a tested starting point, not just a copied string. After the output works once, save it with a clear Project name, note the target Minecraft version, and keep the preset near related setup commands such as scoreboard, bossbar, loot, or reset lines.

Before publishing the preset to a map, server, or command pack, run it from the copied artifact rather than only from the live workbench. That catches missing dependencies, stale selectors, wrong edition choices, and commands that only worked because local test state already existed.

  • Keep the selected Edition and Version with the shared command.
  • Test selectors against a harmless command before using damage, kill, clear, or teleport.
  • Move long commands into Project or a function-style workflow instead of pasting them into chat.
  • Recheck warnings after changing entities, item components, passengers, or datapack resources.

FAQ

How do I make an infinite effect command?

Use a very long duration or the version-supported infinite duration form when available. For maps, also keep a matching clear command.

Why is my level off by one?

The amplifier value is zero-based. A visible level II effect uses amplifier 1.

When should this preset become part of a command pack?

Use it as a command pack entry when the output depends on setup lines, reset commands, loot resources, scoreboard state, or repeated testing. Single safe commands can still be copied directly from Output.

Open this workflow

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