[RELEASE] Akira VN / Story Engine Template

Hey everyone

This is a Visual Novel / Story Engine template for Roblox that lets you drop story content into your game without building all the plumbing yourself.


:warning: Disclaimer: This is a paid resource.

Pricing

  • Base price: $14.99 USD
  • Launch promo: $9.99 USD (33% off – available now)
  • promo Code: 489358-Launch (can use now at checkout)

If you feel the pricing isn’t fair or have feedback, I’m happy to hear it.

Resource Link: https://builtbybit.com/resources/akira-vn-story-engine-template.84432/


It comes with:

  • A dialogue engine (chapters, choices, flags, history)
  • Clean VN-style UI
  • A cutscene sequencer (camera tweens, zoom, over-the-shoulder, camera shake)
  • Animation-driven rigs (idle, walk, run, jump, custom)
  • Optional SlotCore integration for saving flags/endings per player

Perfect for:

  • Story games
  • VN-style episodes/routes in existing games
  • In-game intros, tutorials, and cinematic moments

Showcase


Features

Dialogue Engine (VNEngine)

  • Chapters are just Lua tables (e.g. Prologue.lua)
  • Node types:
    • line - speaker, portrait, text, next
    • choice - prompt with options, supports setFlags
    • command - for things like PLAY_CUTSCENE, END_SCENE, JUMP_SCENE, etc.
  • Built-in:
    • Flags - setFlags on lines/choices for branching routes
    • Seen tracking - mark nodes as seen for future logic
    • History log - used by the log UI panel

VN UI

  • DialogueRoot with:
    • Speaker name
    • Portrait image
    • Main text
    • Choice buttons
    • Continue hint (Click / Space)
  • LogPanel to scroll through previous lines
  • Buttons:
    • Log
    • Skip
    • Auto (toggle auto-advance)
  • All UI is standard Roblox GUI, easy to reskin.

Cutscenes (VNCutscene + SequenceEditor)

Define cutscenes with a fluent sequence builder:

local S = require(EngineFolder.SequenceEditor)

local rigWalkDemo = S.new("rig_walk_demo")
    :fadeIn(0.4)
    :focus("Rig", 0.6)
    :idle("Rig", 1.4)
    :walk("Rig", 5, 2, 1.5)
    :run("Rig", 6, 3, 1.2)
    :jump("Rig", 0.9, 5)
    :anim("Rig", "Wave", 2)
    :zoom("Rig", 45, 0.8)
    :shake(0.5, 0.9, "Explosion")
    :wait(0.3)

Helpers available:

  • :fadeIn(duration?), :fadeOut(duration?)
  • :wait(duration?)
  • :focus(target, duration?)
  • :pan(fromTarget, toTarget, duration?)
  • :overShoulder(fromTarget, toTarget, duration?, options?)
  • :zoom(target, fov, duration?)
  • :shake(duration?, magnitude?, preset?) – uses RbxCameraShaker
  • :idle(rigName, duration?)
  • :walk(rigName, steps?, stepLength?, duration?, options?)
  • :run(rigName, steps?, stepLength?, duration?, options?)
  • :jump(rigName, duration?, height?, options?)
  • :anim(rigName, actionName, duration?, options?)
  • Lower-level: :rigWalk(config), :marker(name)

Target can be a string (e.g. "Rig", "VN_Focus1") or an Instance.

Animation Config (Idle / Walk / Run / Jump / Custom)

All animation IDs are managed in one place: VN.Config.Animations.

Example:

local Animations = {
    Characters = {
        Rig = {
            idle = "rbxassetid://...",
            walk = "rbxassetid://...",
            run  = "rbxassetid://...",
            jump = "rbxassetid://...",

            custom = {
                Wave = "rbxassetid://...",
                Point = "rbxassetid://...",
            },
        },
    },

    Default = {
        idle = "rbxassetid://...",
        walk = "rbxassetid://...",
        run  = "rbxassetid://...",
        jump = "rbxassetid://...",

        custom = {
            -- fallback custom actions
        },
    },
}

return Animations

The cutscene engine resolves animation IDs like this:

  1. Step-specific animId if set
  2. Characters[rigName][action] (e.g. Rig.walk)
  3. Characters[rigName].custom[action] (e.g. Rig.custom.Wave)
  4. Default[action] / Default.custom[action]
  5. Roblox fallback IDs

So to use a custom anim, you just put it in the config and call:

:anim("Rig", "Wave", 2)

Checkpoints / Reusable Scenes

VN.Config.Scenes lets you define reusable entry points:

local Scenes = {
    Scene01_Intro = {
        chapter = "Prologue",
        entryNode = "start",
    },

    Scene02_RigDemo = {
        chapter = "Prologue",
        entryNode = "rig_demo_intro",
    },
}

return Scenes

From a chapter node:

{
    type = "command",
    command = "JUMP_SCENE",
    args = { id = "Scene02_RigDemo" },
    next = "fallback_node_if_missing",
}

Good for:

  • Debugging specific scenes
  • Replaying cutscenes
  • Triggering story beats from the game world

Player Movement Lock

While VN + cutscenes are active:

  • Disables default PlayerModule controls
  • Sets WalkSpeed = 0, JumpPower = 0, AutoRotate = false
  • Unequips tools

When END_SCENE runs, everything is restored automatically.

SlotCore Integration (Optional, Included)

This template includes optional SlotCore integration to persist VN progress.

  • Store: VN created via SlotCoreServer.CreateStore("VN", ...)
  • Data structure contains:
vn = {
    flags = {},          -- current VN flags
    endings = {},        -- map[endingId] = true
    lastEnding = nil,
    lastPlayedAt = 0,
}

Server-side:

  • RequestStartStory:
    • Loads a SlotCore slot (default "1")
    • Passes vn.flags into the VN engine so flags persist between sessions
  • EndingReached:
    • Writes back flags, marks endings[endingId] = true
    • Saves the slot

You can expand this to:

  • Unlock titles/outfits based on endings
  • Track which routes the player has cleared, etc.

Folder Layout

ReplicatedStorage

ReplicatedStorage
├─Packages -- SlotCore Needs this folder
└─ VN
   ├─ Engine
   │  ├─ VNEngine        -- Core state machine
   │  ├─ VNCutscene      -- Camera + rig actions + CameraShaker
   │  └─ SequenceEditor  -- Fluent cutscene builder
   │
   ├─ Scripts
   │  └─ Prologue        -- Example chapter
   │
   ├─ Config
   │  ├─ Settings        -- Portraits & general settings
   │  ├─ Cutscenes       -- All cutscene sequences
   │  ├─ Animations      -- Animation IDs
   │  └─ Scenes          -- Checkpoints / scene entry definitions
   │
   └─ Frameworks
      ├─ CameraShaker    -- RbxCameraShaker
      └─ SlotCore        -- SlotCore framework (server/client)

ReplicatedStorage/VNRemotes

  • RequestStartStory : RemoteFunction
  • EndingReached : RemoteEvent

StarterGui

  • VNScreen (ScreenGui) with:
    • DialogueRoot (main VN UI)
    • LogPanel
    • (FadeLayer is created automatically at runtime)

StarterPlayerScripts

  • VNClient (LocalScript)

ServerScriptService

  • VNServer (ServerScript) - handles SlotCore + VN start/end decisions

Quick Start

  1. Import the VN folder + frameworks (CameraShaker, SlotCore) into ReplicatedStorage.VN.
  2. Put VNRemotes (with RequestStartStory, EndingReached) in ReplicatedStorage.
  3. Put VNScreen in StarterGui.
  4. Put VNClient in StarterPlayerScripts.
  5. Put VNServer in ServerScriptService.
  6. Edit:
  • VN.Scripts.Prologue → your story content
  • VN.Config.Animations → your animation IDs
  • VN.Config.Cutscenes → your custom sequences
  • VN.Config.Scenes → your reusable scene entry points

Press Play:
Prologue will run on join, lock movement, play the demo cutscenes, then hand control back to the player.


Example Chapter Flow

Prologue shows a full chain:

rig_demo_cutscene = {
    type = "command",
    command = "PLAY_CUTSCENE",
    args = { id = "rig_walk_demo" },
    next = "rig_os_cutscene",
},

rig_os_cutscene = {
    type = "command",
    command = "PLAY_CUTSCENE",
    args = { id = "rig_over_shoulder_demo" },
    next = "rig_outro_cutscene",
},

rig_outro_cutscene = {
    type = "command",
    command = "PLAY_CUTSCENE",
    args = { id = "rig_outro_demo" },
    next = "end_scene",
},

end_scene = {
    type = "command",
    command = "END_SCENE",
    args = { endingId = "prologue_clear" },
},

So you can chain multiple cutscenes in a row, then cleanly end the VN.


FAQ

Q: Can I use this without SlotCore?
Yes. SlotCore is optional. You can comment out or replace the SlotCore bits in VNServer and plug in your own datastore solution.

Q: Can I use my own UI?
Yes. The VNClient just needs references to the main objects (DialogueRoot, labels, containers). You can completely reskin it or rebuild the layout.

Q: Does it support multiple chapters?
Yes. Just add more modules in VN.Scripts and call engine:Start("Chapter2", "start", flags) or JUMP_SCENE into them.

Q: Does it support voice acting / sound?
Not built-in, but it’s easy to add a command node type like PLAY_SOUND and handle it in VNClient next to PLAY_CUTSCENE.


Where to Get It

BuiltByBit:
Akira VN / Story Engine Template - Link)

Includes:

  • Full VN engine + cutscene system
  • Example Prologue + 3 demo cutscenes
  • CameraShaker, SlotCore integration
  • README Script
4 Likes

Good project, but im poor😭

3 Likes