Spells in
a playable scene.

Watch the effects at gameplay distance.

Look at the whole action: where the cast starts, what moves toward the target, when the impact lands and how long the aftermath remains. Watch at the size you expect players to use, not only in a close-up preview.

What the package handles.

Arcane Foundry supplies 150 spell designs across ten domains, 30 ground sigils, complete sequence prefabs, phase-entry prefabs, editable C#/URP shaders and JSON appearance presets. Related designs share composition families and rendering modules.

The 600 phase-entry prefabs are four entry points for each of the same 150 designs, not 600 additional spells. Use them when your animation or gameplay system owns the timing.

The verified package baseline is Unity 6.3 LTS and newer (tested 6000.3.27f1 and 6000.6.7f1), URP 17.3+ (tested 17.3.0 and 17.6.0), Windows x64 / Direct3D 12. Built-in, HDRP, other versions and other platforms are unverified. Consult the supplied compatibility notes before importing.

Play through the pool.

Assign a scene VfxPool, a supplied SpellDefinition and a target transform. Pass world-space ground positions; the effect adds its visual height. If your gameplay code uses its own assembly definition, add a reference to ArcaneFoundry.Runtime.

using ArcaneFoundry;
using UnityEngine;

public sealed class SpellPreview : MonoBehaviour
{
    [SerializeField] VfxPool pool;
    [SerializeField] SpellDefinition spell;
    [SerializeField] Transform target;

    public void Cast()
    {
        if (!pool || !spell || !target) return;
        pool.Spawn(spell, transform.position, target.position);
    }
}

Call Cast() from your own ability code or animation event. Completed sequences return to the pool. Prewarm an appropriate number during loading with the coroutine pool.Prewarm(spell, count: 8, perFrame: 2); eight is an example, not a universal budget.

Pooling reduces creation/reuse work. It does not eliminate active rendering, transparent overdraw or lighting cost. Profile the simultaneous casts your actual encounters use.

Compose for the encounter.

1. Establish scale. Compare an effect's footprint with a character and its intended target area. The visual radius does not automatically define a gameplay collider.
2. Keep the sigil subordinate. Choose None, Light, Medium or Detailed, then tune sigil opacity and brightness. A large impact need not compete with a detailed ground circle.
3. Check interruptions. Integrate your cancellation and phase timing, then confirm a stopped ability does not leave unintended visuals or extra gameplay lights behind.
4. Check terrain and camera. Atmospheric bodies use camera-facing textured layers. Ground feathering assumes a locally horizontal plane at the target height; it does not conform to arbitrary terrain or soften every intersection with actors and walls.
5. Check pale terrain. Follow the bright-background guide before making glow stronger.

If you also own Isometric Lighting, its generic transient-light API can be driven by your ability events. Arcane Foundry and Lighting are separate products; neither requires the other, and the complete private demo adapter is not included.

Try the supplied tools.

Use the package's supplied showcase scenes and examples to inspect individual designs and presets. For schema details, runtime copies and offscreen recording order, read the integration notes. For a controlled dark/pale-ground comparison, use the readability guide.

Explore Arcane Foundry →