Duck Blocks

Put a trigger on a block, a stand button, or a click hitbox and use it to drive commands, sounds, particles, displays, motion, or travel.

That covers the small stuff like panels and doors, but it also covers the bigger stuff like station pieces, ride systems, and moving props.

On first enable, Duck Blocks creates config.yml, animations.yml, effects.yml, duckblocks.yml, and duckblocks-state.yml.

Open /duckblock gui, create one trigger, add one visible action, save, and retest. If you are already looking at a trigger, the same command jumps straight into that trigger editor. If you plan to use add-from-file, the commands/ folder is created the first time that command is used.

/duckblock gui
/duckblock help
/duckblock add-from-file station_open.txt console

commands:
  - "db:message &aGenerator online"
  - "db:sound BLOCK_NOTE_BLOCK_PLING 1 1"
  - "db:particle ELECTRIC_SPARK 8 0.2 0.2 0.2 0.01"

config.yml handles server-wide defaults. duckblocks.yml stores the trigger library. animations.yml and effects.yml hold reusable presets.

That structure is why the plugin scales well for map teams. Builders can work in game, while admins still keep files they can review, copy, and maintain.

Duck Blocks supports per-player redstone, nearby and timed activation, timelines, particle shapes, display actions, and optional ModelEngine binding from the same runtime.

Travel is the standout lane: walkable platforms, mountable movers, SMART carry, collider shulkers, and waypoint-based movement that feels much closer to a ride system than a normal trigger plugin.

db:particlefx ring ELECTRIC_SPARK 1.4 96 0.0 0.0

Redstone is event-driven. Animations only tick triggers that actually have animations. Nearby checks are throttled. Timeline loops are chunk-safe. Travel persistence does not force chunk loading. State autosave runs asynchronously.

Admins also get useful controls for save cadence, clickbox defaults, animation cadence, permissions, redstone behavior, batch tools, reloads, cleanup, and carry debugging.

redstoneEnabled: true
redstoneEdge: ON
redstoneDebounceMs: 250
redstonePerPlayer: true
redstoneRange: 12.0
redstoneMaxTargets: 16
redstoneSkipIfEmpty: true
requirePlayerPlaceholder: true

The plugin targets Paper 1.21.x on Java 21. ModelEngine is the clearly implemented optional bridge for owned or attached models and runtime actions.

ProtocolLib and PacketEvents are also declared as softdepends in plugin.yml, but the cleanest buyer-facing message is that ModelEngine is the main real integration surface.

Triggers can dispatch console or player commands after resolving placeholders such as {player}, {uuid}, {world}, {x}, {y}, and {z}. Waypoint actions also add {trigger}.

That makes Duck Blocks a practical front-end for quests, permissions, warps, scoreboards, cutscenes, and other plugin-driven systems.

Per trigger, you can tune delay, cooldowns, one-time behavior, redstone edge handling, display content, interpolation, offsets, rotations, animations, timelines, travel, ModelEngine settings, hidden state, and hitboxes.

The admin side adds batch tools, copy and paste and clone flows, nearby mass edits, file and book command authoring, display editing, travel path tools, and ModelEngine-specific GUI surfaces.

execDelayMs: 250
cooldownMs: 1500
cooldownScope: PER_PLAYER
oneTime: false
displayText: "<green>Platform Ready"
displayScale: 1.0
hidden: false

Use a few short examples to show the command surface, the db action language, and the travel depth.

/duckblock gui

/duckblock add-from-file station_open.txt console

db:particlefx ring ELECTRIC_SPARK 1.4 96 0.0 0.0

travel:
  enabled: true
  trigger: CLICK
  mode: LOOP
  speedBlocksPerSecond: 1.5
  smooth: true
  walkable: true
  walkPlatformType: COLLIDER_SHULKERS
  carryMode: SMART
  walkLevitationAssist: true
  mountable: true
  mountSneakToMount: true