✨ Bring your Minecraft world to life.

RuneFX Engine lets you place, animate, combine, move, and trigger environmental VFX directly inside Minecraft through a visual in-world editor. Build stationary ambience, send effects along custom paths, stack complete compositions, and preview every change live without writing effect configuration by hand.

⚠️ Important: RuneFX Engine is built for official RuneFist Effects content. It loads compatible, signed RuneFist .rfxpack products and does not import or guarantee support for third-party VFX, loose Blockbench files, custom spritesheets, MythicMobs effects, or packs made by other creators. The built-in Vanilla Particle Workshop remains available for supported native Minecraft particles.

🎨 Visual editing, directly in your world

GUI-first workflow: browse, place, edit, duplicate, preview, save, and remove VFX through clear menus.
Live editor stick: select anchors, grab points, adjust depth, snap to surfaces, and move effects in real time.
Private audiences & quest effects: target complete VFX/SFX setups to Everyone, Activator Only, Scoreboard Tag, or Permission—without adding a quest-plugin dependency.
Stationary and multi-point paths: use Linear, centripetal Catmull-Rom, Bezier, or B-Spline curves.
Path control: forward, reverse, and ping-pong traversal with easing and follow-path orientation.
Layered compositions: combine up to 16 installed RuneFist VFX under one lifecycle, activation setup, and path.
Per-layer controls: offset, rotate, scale, delay, change playback speed, hide, duplicate, or reorder layers.
Complete lifecycle: every authored effect can use smooth spawn, looping idle, and death behavior.
Native activation: always active, fixed/random intervals, player proximity, enter/leave, block interaction, redstone, and command triggers.
Persistent placements: saved VFX return after restarts and product updates use safe validation and rollback.

🧩 Four visual systems in one workflow

Complete animated 3D ModelEngine VFX
Animated 3D model-particle emitters
Custom 2D billboard sprites and per-particle sprite-sheet animation
Supported native Minecraft Java particles

RuneFX exposes only the controls that are safe for each effect. Depending on the selected VFX, these may include scale, rotation, playback speed, brightness/glow, emission, lifetime, shape, spread, velocity, gravity, drag, spin, simulation space, and activation behavior.

🔊 Sound that belongs in the world

Use SFX independently: place positional sound effects or non-musical regional ambience without needing a visual effect.
Bring compositions to life: layer SFX with VFX so sound follows the same placement, path, lifecycle, and triggers.
Built for responsive scenes: official sound packs can use separate spawn, idle, moving, and death cues.
Fine-tune every placement: adjust volume, pitch, natural pitch variation, audible range, and loop spacing directly through the visual editor.

Sounds can react to proximity, interaction, intervals, redstone, commands, and other RuneFX triggers while distance-aware playback keeps them grounded in the world.

✨ Vanilla Particle Workshop

Create and edit placements from supported Minecraft Java particles without importing custom files. Choose a particle visually, preview it immediately, then adjust only the settings that apply to it. Workshop particles can also be stacked beside installed RuneFist VFX.

📦 Included with RuneFX Engine

RuneFX Engine 1.2.0 for Paper
The complete visual editor, editor stick, menus, paths, compositions, activation system, and placement manager
The Vanilla Particle Workshop
Starter Dust - native Minecraft particle example
Included 3D VFX - complete animated ModelEngine example
Included Animated Swirl - custom animated 2D sprite example
Included 3D Particle - independently animated 3D particle example
A concise installation, validation, troubleshooting, and rollback guide

The rest of the Effects catalog is not included. Additional official RuneFist Effects are separate products designed to appear automatically in RuneFX after their untouched .rfxpack is placed in plugins/RuneFX/packs.

🛠️ Requirements

Minecraft / Paper: 1.21.11
Java: 21 or newer
ModelEngine: 4.1.x required; R4.1.0 tested
Client resource pack: every player must accept the current server pack
Nexo: optional
Folia: not supported

Other server forks or newer game/dependency versions may work, but they are not supported unless they are explicitly listed. Support may request reproduction on the supported Paper build.

MythicMobs, ItemsAdder, MMOItems, MMOCore, WorldGuard, Citizens, PlaceholderAPI, and Nexo are not required for RuneFX's placement, path, composition, or activation systems. ModelEngine is the required dependency and is not included with this purchase.

🚀 Installation

Stop and back up the server.
Install ModelEngine 4.1.x.
Extract the download and place RuneFX-Engine-1.2.0.jar in plugins/.
Complete one resource-pack flow: Nexo or standalone.
Start the server, join as an operator, and accept the refreshed resource pack.
Run /rfx status and /rfx validate, then open the editor with /rfx.

With Nexo

RuneFX publishes one managed external pack and asks Nexo to regenerate and upload the combined pack. Reconnect after the refreshed pack is available.

Without Nexo

RuneFX generates plugins/RuneFX/generated/RuneFX-ResourcePack.zip. The server owner must host or merge that ZIP into the resource pack delivered to players. RuneFX does not host the standalone ZIP by itself.

Installing a purchased Effects product

Place the untouched .rfxpack directly in plugins/RuneFX/packs. Do not extract it, rename internal files, edit it, or manually copy models into ModelEngine. Open Effects > Installed Products to see signature, compatibility, dependency, activation, and resource-pack status.

🔐 Official content and protected assets

RuneFX recognizes only compatible packs signed by RuneFist Studios. Buying the Engine does not unlock third-party VFX import, and support does not cover effects, models, sprites, or modified packs from another creator.

Current RuneFist Effects products use signed protected runtime packs. Editable source projects, private authoring configuration, signing tools, and original Blockbench project files are NOT included unless a listing explicitly says otherwise. Protected model and effect data is handled automatically by RuneFX. Do not extract, modify, repackage, redistribute, or resell product contents.

Players must still receive client resource-pack assets to render custom visuals. Protection keeps editable authored source and internal configuration out of the normal customer workflow, detects modifications, and discourages redistribution; it is not advertised as unbreakable DRM.

Performance and visual expectations

RuneFX applies per-effect and global safety limits to protect server and client performance. Dense emitters may be capped, delayed, or skip new particles when a shared display budget is full. Actual capacity depends on the server, player count, simultaneous placements, view distance, effect type, and client hardware. Start with the authored defaults and test changes before production use.

Brightness level 15 means Minecraft fullbright behavior; it does not automatically create shader bloom. Shader packs, client mods, accessibility settings, and resource-pack order can change how an effect appears.

💡 Frequently asked questions

Can I import my own VFX or another creator's VFX?

No. RuneFX loads compatible official RuneFist .rfxpack products. It does not import arbitrary models, spritesheets, YAML, Snowstorm files, MythicMobs effects, or third-party packs. You can create placements from supported native particles in the Vanilla Particle Workshop.

Does buying RuneFX include every Effects product?

No. This purchase includes the Engine and the four demonstrations listed above. Commercial Effects products are sold separately.

Does RuneFX replace ModelEngine?

No. ModelEngine 4.1.x is required and is not included.

Do I need Nexo?

No. Nexo is optional. Without it, you must deliver RuneFX's generated standalone resource pack through your normal server resource-pack setup.

Are original Blockbench projects included?

No, unless a specific product listing explicitly states otherwise.

Can I use a plugin reloader?

No. Stop the server before replacing RuneFX or required dependency JARs. RuneFX's own reload is for product/config rescans, not live plugin replacement.

💬 Support

Support covers installation on the listed environment, untouched official RuneFist products, reproducible RuneFX defects, and behavior promised on this page. It does not automatically cover third-party/custom/repacked VFX, unsupported forks or versions, plugin reloaders, manual resource-pack conflicts, bespoke effect creation, or unrelated plugins installed beside RuneFX.

For the fastest diagnosis, include the exact versions, affected product, full startup/reproduction log from mclo.gs, output from /rfx status and /rfx validate, and clear reproduction steps.

Translations

Translations Guide Coming Soon