Skip to main content
Block Arsenal

Wiki

Duck Blocks wiki

Wiki

Duck Blocks Wiki

In-world machines, trigger systems, moving structures, redstone logic, and the public Duck Blocks authoring workflow.

Getting Started

Start here for first boot, the file split, server-wide defaults, and the real saved trigger shape.

Wiki HomeFirst Boot, Trigger Types, and the File MapConfig YML: Runtime Defaults and Save PolicyDuckBlocks YML: Trigger Layout and Live Examples

In-Game Authoring

Build DuckBlocks live through the admin menu, trigger editor, display editor, and machine-by-machine editor flow.

Main Menu, Create Flow, and the Admin Command SurfaceTrigger Editor, Core Controls, and Machine LayoutCommand Authoring, Books, Command Files, and `db:` Action LinesDisplays, Hitboxes, and ModelEngine

Placeholders and Context

Understand player context, built-in tokens, and how Duck Blocks hands finished commands into the rest of the server.

Placeholders, Player Context, and Command Handoffs

Trigger Logic and Motion

Control how DuckBlocks fire, sequence, move, and carry players through the world.

Activation Sources, Redstone, and Player ProximityRedstone Advanced, Edge Modes, Range, and Player ContextAnimations, Effects, and the Timeline OrchestratorTravel Paths, Walkable Platforms, and Rideable StructuresTravel GUI, Path Builder, Waypoints, and CarryBatch Tools, Presets, and Nearby Mass Edits

YML File Guides

Jump straight into the reusable preset files that make a large Duck Blocks library maintainable.

Animations YML: Motion Presets and When to Use ThemEffects YML: Sounds, ParticleFX, and Combo Presets

Runtime and Troubleshooting

Understand what gets saved, what the carry logs mean, and how to troubleshoot live Duck Blocks cleanly.

Admin Runtime, State, and Live Troubleshooting
What belongs in `effects.yml`The internal action familiesExample sound presetExample particle presetParticleFX shapes worth knowingSound routingCombo presetsBest next pages
YML File Guides

Effects YML: Sounds, ParticleFX, and Combo Presets

Use effects.yml to build reusable sound, particle, and combo stacks for the whole server.

Plugin downloadsDuck Blocks

effects.yml is the reusable spectacle library for Duck Blocks. It is where you store the sounds, particle shapes, and combo stacks that make a machine feel finished.

What belongs in effects.yml

The live preset library already shows the right pattern:

  • simple sound presets
  • particle-shape presets
  • combo presets that stack several lines together

This is the best place for content you want to reuse across many machines.

The internal action families

Duck Blocks' internal line parser supports these major public families:

  • db:message
  • db:actionbar
  • db:title
  • db:particle
  • db:particlefx
  • db:sound
  • db:display
  • db:cmd
  • db:playercmd

Example sound preset

YAML
presets:
  sound_ui_click:
    name: "Sound - UI Click"
    icon: STONE_BUTTON
    lines:
      - "db:sound UI_BUTTON_CLICK vol=1.0 pitch=1.0 audience=player mode=origin range=0"

This is exactly the kind of micro-preset every server ends up using constantly.

Example particle preset

YAML
presets:
  ring_endrod_basic:
    name: "Ring - End Rod"
    icon: END_ROD
    lines:
      - "db:particlefx ring END_ROD 1.5 100 0.0 0.0"

This is the right pattern for reusable decorative or magical geometry.

ParticleFX shapes worth knowing

The public shape family includes patterns such as:

  • ring
  • shockwave
  • spiral
  • helix
  • double helix
  • sphere
  • burst
  • cone
  • beam
  • square
  • triangle
  • cube
  • pyramid
  • cylinder

That is why Duck Blocks can move past ordinary command-block-style feedback and into cinematic machine behavior.

Sound routing

The sound line supports practical routing controls such as:

  • sound id
  • volume
  • pitch
  • range
  • audience
  • origin mode
  • offsets

The big authoring choice is usually:

  • player-only local feedback
  • nearby world feedback
  • origin-based sound
  • around-origin ambience

Combo presets

Combo presets are one of the best ways to keep a large server clean. Use them when one interaction should always come with the same package, such as:

  • a sound plus a ring
  • a title plus a sound sting
  • a particle burst plus a display scale pulse

That keeps you from rewriting the same three or four lines on every single block.

Best next pages

PreviousAnimations YML: Motion Presets and When to Use ThemAdmin Runtime, State, and Live TroubleshootingNext