Content generated with AI — it may contain mistakes.

ExyliaKillEffect/GuidesUpdated in v1.9.1

Create effects with AI

Describe the kill effect you want, copy the prompt, and paste the answer into effects.yml.

Page 9 of 224 min read

Describe a kill effect in your own words and an AI writes it for you, ready to paste. Writing one by hand means knowing dozens of shapes, forty parameters and what ease:in does to a falling sword. You do not have to. The prompt below carries all of it — the step language, the limits, the three rules that save an afternoon, and two shipped effects in full — so the only thing left for you is the idea.

Write the idea first#

The prompt is only as good as what you put in it. "Something cool" produces something generic; a paragraph produces the effect you pictured. Say:

What it is made of

Real blocks and items, named. NETHERITE_SWORD, AMETHYST_CLUSTER, CRYING_OBSIDIAN. This is what gives an effect its silhouette — particles are only the light around it.

What moves, and where

Falls from above, closes on the centre, throws itself outwards, rises and hangs. Give it a direction and a distance: "twelve blades fall from ten blocks up".

How long it lasts

A kill effect is a scene of a second and a half to three seconds. Say whether you want a single slam or three beats one after another.

What happens to the body

Every shipped effect choreographs the victim with a [RAGDOLL] line, frame by frame: the body dances, is slapped, spins or is spelled into a word, then bursts, collapses or dissolves. Say what it does — and whether a copy of the killer walks in to act it out, or the players watching join in. Or ask for no body at all.

The mood and the sound

Heavy and grinding, or bright and clean. Name a sound if you have one in mind; otherwise let the model choose and change it afterwards.

A worked example of an idea

"A funeral. The victim kneels, then falls forward. Eight DEEPSLATE_TILES pillars rise out of the ground around them in a circle of three blocks, slowly, over a second. A SOUL_LANTERN hangs above the body and glows. Muffled bell at the end. Cold, quiet, no fire."

Copy the prompt#

AI

Write your idea

The prompt around it is already written — the step language, the limits, and effects that ship. Copy it, paste it into your AI, and paste the answer into effects.yml.

Write your idea to build the prompt

Write the idea in the box, copy the prompt with your idea already inside it, paste it into whichever AI you use, and send it.

Then#

Paste the answer into effects.yml

Open plugins/ExyliaKillEffect/lang/<code>/effects.yml (or the web editor, which checks it before saving) and paste the block under kill_effects:, at the same indentation as the effects already there. Make sure its category is one that exists.

Reload

/killeffectsadmin reload, not needed from the web editor. Every player picking that effect is re-checked against the new catalogue, so an effect that stops existing is dropped from whoever had it.

Read the console

A step that cannot be read is dropped and printed with the line that caused it. That is your proofreader: if nothing appears, every line was understood.

Watch it, then tune it

Test it on yourself. Numbers are the easy part to change — radius, life, size, the [DELAY] between beats. The prompt asks the model to explain what each step does so you know which number to move.

The model can still be wrong

It writes a material that does not exist, or a parameter a shape does not understand, and the console says so. It cannot break the plugin — a bad line is dropped, the rest of the effect still plays — but it can waste an afternoon if you do not read the console. Give the error back to the AI and it usually fixes it in one turn.

It is a permission too

The key you paste becomes exyliakilleffect.effect.<key>, so nobody sees the new effect until they are granted it. See Permissions.

Everything the prompt knows is documented here too, if you would rather write the effect yourself: Sequences is the full step language, and Effects and categories is the file around it.

Check that it works#

Run /killeffect preview <id> with the preview stage set (see first steps): the scene plays and the console printed no line starting effects.yml kill_effects.<id>.

Something missing on this page? Tell us on Discord