Skip to content

    Free generator · no sign-up

    LitRPG System Notification Generator

    A System notification generator formats the messages a LitRPG System shows its characters: level ups, new skills, titles, quests and loot. Good System messages are short, use the same words every time and put the change first, like [Skill acquired: Ember Step (Rare)]. Fill in the details, then copy it as text or as a box for Royal Road.

    Message

    Style

    [Skill acquired: Ember Step (Rare)]
    [Cost: 20 MP]
    [Cooldown: 8 seconds]

    Copy for Royal Road pastes a bordered System box into Royal Road's chapter editor, whichever style you pick here.

    Need ideas? Ten random System messages

    Level ups, loot, kills and warnings, built from the other generators' word lists.

    Messages

    Style

    • [You have slain Sewerblob (Lv. 33). +460 XP.]
    • [You have slain Silent Watcher (Lv. 27). +440 XP.]
    • [Boss encountered: Mormael, the Last Warden]
    • [New quest: Clear the Red Cinderworks]
    • [Class evolution available: Hexstrider]
    • [Class evolution available: Iron Hierophant]
    • [Skill acquired: Curse Tolerance (Common)]
    • [Achievement unlocked: Last One Standing]
    • [Title earned: Golem Bane]
    • [Skill acquired: Sweep of a Thousand Cuts (Legendary)]

    Made in your browser from word lists. No AI, nothing saved, free.

    What makes a good LitRPG System message?

    A good System message is short, uses the same words every time, and puts the important part first. Readers scan notifications rather than read them, because they want to find the change fast: what was gained, what went up, what it cost.

    Consistency matters more than style. Pick a format, brackets or a box, and use it for the whole story. If level ups read “[Level up! You have reached level 21.]” in chapter 5, they should look the same in chapter 205. Readers learn the shape and start skimming for it, which is exactly what you want.

    How should you format System messages?

    Square brackets are the safest format, and boxed System windows (the “blue boxes” readers talk about) are common too. Whichever you pick:

    • One idea per line. [Skill acquired: Ember Step (Rare)] and then [Cost: 20 MP] reads better than one long line.
    • The same verbs every time: acquired, reached, earned, obtained. Don't alternate between gained, learned and unlocked unless they mean different things in your System.
    • Numbers readers can check. If the MC gets 5 free points at every level, say so, and make sure the totals add up later.
    • Long descriptions only the first time. The second time a skill levels up, one line is enough.

    How do you get a System box onto Royal Road?

    Paste it as a table. Royal Road's chapter editor keeps tables and inline styles when you paste, and drops style sheets and classes. Box-drawing characters only line up in a monospace font, and most readers see your chapter in a proportional one, so a drawn box can come out ragged. “Copy for Royal Road” on this page copies the message as a bordered single-cell table in a monospace look, the same way PlotWrite's Copy for Royal Road does for a whole chapter, so it pastes in as one clean box. Check the preview on a phone before you publish.

    What are the common System message mistakes?

    • Walls of notifications. Ten boxes in a row stop the scene. Group small gains into one message, or sum them up at the end of the chapter.
    • Numbers that drift. If the box says level 21 and the next chapter's status screen says 20, readers notice.
    • Changing the format mid-story without a reason. If the System changes, make it a plot point.

    PlotWrite's Story brain remembers every level, skill and reward your System hands out, by chapter.

    PlotWrite reads the chapters you've written, keeps each fact with the chapter it became true, and checks a new chapter against them before you post.

    • No card needed
    • Cancel anytime
    • PlotWrite never charges for AI

    Questions

    System notifications: common questions

    What does a LitRPG level up message look like?
    Usually a bracketed line with the new level, then one for any free points: [Level up! You have reached level 21.] and [5 free attribute points available.] Keep the wording identical every time, so readers can skim straight to the number.
    What is a blue box in LitRPG?
    It's readers' nickname for a System window: a status screen or notification set apart from the prose, often as a box. Some readers love them and some skim them, so keep each one short and in the same format.
    Brackets or a box: which is better?
    Brackets are the safest: they survive any editor, any font and any screen. Box-drawing characters look great where text is monospace, like Discord code blocks, but drift out of line elsewhere. For Royal Road, use brackets and Copy for Royal Road.
    Does this generator use AI?
    No. It builds System messages from hand-picked word lists and naming patterns, right in your browser. Nothing you choose is sent anywhere, it's free, and every click gives you a fresh batch.
    Can I add descriptions, costs and cooldowns?
    Yes. Put anything extra in the extra lines box, one per line. Each line becomes its own line of the message, in the same style.