Black Magik Studios Documentation

Custom LoRAs

Custom LoRAs Overview

Start here to choose the right LoRA pack for the asset you are building.

Custom LoRAs Overview

Black Magik’s Custom LoRAs are pack-specific tools for repeatable RPG asset production. Each pack is trained for a particular subject type, canvas shape, and cleanup workflow, so the fastest way to get reliable results is to choose the guide that matches the asset you are building.

The workflow is designed for consistency: load the right LoRA, keep its trigger token intact, start at the recommended canvas size, generate a clean source image, then finish the result in Aseprite with the same cleanup tools you use for the rest of your game art.

Main Areas

Area Purpose
Characters Use Portrait and Walk packs for readable character faces, dialogue art, and movement-sheet bases.
Terrain Use Wang Tileset, Single Tile, Wall, and Cliff packs for repeatable ground, elevation, and environment surfaces.
Structures Use Building and Border packs for roof-driven buildings, presentation frames, and decorative map or UI elements.
Items and Props Use Small Items, Medium Items, and Large Items packs for pickups, furniture, obstacles, and scene-defining objects.

First Session Checklist

  1. Open the guide for the asset type you want to create.
  2. Load that specific LoRA before prompting. These packs are not meant to be treated as interchangeable presets.
  3. Keep the documented trigger token exactly as written, then build the subject description around it.
  4. Start at the recommended generation size for that pack.
  5. Use the published model strength range first, then adjust only when the pack is clearly underfiring or overfitting.
  6. Generate a clean source image, then finish masking, slicing, palette cleanup, or tile conversion in Aseprite.

What Each Guide Includes

  • Recommended baseline settings.
  • The exact trigger prompt for that pack.
  • A proven example prompt you can branch from.
  • A current reference image that shows the intended output style.
  • Short prompting notes so you know which details matter most at the target asset scale.

Good Habits

  • Treat each pack as its own recipe instead of forcing one shared prompt formula across the whole lineup.
  • Leave simple background or white background in place when a guide uses it. Those constraints make masking, cleanup, and slicing easier.
  • Keep prompts focused on the asset itself rather than a full scene unless the guide calls for scene context.
  • Save prompts and settings that produce clean outputs so you can reuse them across related assets.
  • Do final production cleanup in Aseprite: palette control, edges, transparency, slicing, and tile validation still matter.

System Requirements

Requirement Details
Runtime Custom LoRAs are used through Grimoire’s local generation workflow, so the Grimoire system requirements apply.
Models Use a compatible local checkpoint and the specific LoRA pack named in each guide.
Storage Keep additional disk space available for LoRA files, checkpoints, generated images, and cleaned production assets.
Editor Aseprite is recommended for final masking, transparency, palette cleanup, slicing, and tile validation.