1. #1📙 Custom Lore Book 1

   Keys:

   Enabled · Order 11000

   Entry settings
2. #2📘 Custom Lore Book 2

   Keys:

   Enabled · Order 11000

   Entry settings
3. #3📗 Custom Lore Book 3

   Keys:

   Enabled · Order 11000

   Entry settings
4. #4

   Keys:

   Enabled · Order 100

   Entry settings
5. #5

   Keys:

   Enabled · Order 100

   Entry settings
6. #6

   Keys:

   Enabled · Order 100

   Entry settings
7. #7활성화 키

   Keys:

   Enabled · Order 100

   Entry settings

   = 발로리아 활성화 키값 {{#if_pure {{? {{getvar::cv_og_toggle_valoria}}=1}}}}

   = 미덴가르드 활성 키값 {{#if_pure {{? {{getvar::cv_og_toggle_midengard}}=1}}}}

8. #8🖊️ Player Custom

   Keys: folder:9e412c2e-27c5-4418-8304-f824da6f229b

   Enabled · Order 100

   Entry settings
9. #9┌─────  ⚙️ System Guide   ─────

   Keys:

   Enabled · Order 100

   Entry settings
10. #10├─ 🎲 Dice Content

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if_pure {{? {{getvar::cv_og_toggle_dice}}=1}}}}

    Dice Judgment System

    Current dice value: {{getvar::dice_result}} — DO NOT MODIFY Current dice value: {{getvar::dice_result}} — DO NOT MODIFY Current dice value: {{getvar::dice_result}} — DO NOT MODIFY

    When To Roll

    • Roll only when {{user}} actually attempts an uncertain in-world action. This includes attacking, defending, dodging, persuading, threatening, deceiving, sneaking, escaping, tracking, searching, investigating, lockpicking, disarming traps, climbing, swimming, casting magic, using authority, crafting, repairing, treating wounds, negotiating, or trying to influence another character.
    • Combat and direct conflict are mandatory roll situations. If {{user}} attacks, defends, dodges, blocks, counters, casts combat magic, protects someone, escapes under pressure, or resists harm, you MUST roll and print the judgment block.
    • Do not roll for pure conversation, questions, status checks, summaries, meta requests, worldbuilding questions, inventory checks, or "continue" unless {{user}} also declares a concrete action.
    • If {{user}} says they do something, try something, attack, defend, persuade, investigate, search, sneak, escape, open, unlock, cast, resist, or otherwise attempts to change the situation, a roll is required.
    • If the {{user}} attempts multiple distinct uncertain actions in a single input, roll separately for each action.

    Difficulty Thresholds

    0 — Just happens. Everyday action 1 — Cannot possibly fail 2 — Failure would be strange 3 — Must be very unlucky to fail 4 — Almost certainly succeeds 5 — Succeeds unless badly botched 6 — Any average person succeeds 7 — Needs a little luck 8 — Succeeds if skilled, fails if not 9 — Success possible but not guaranteed 10 — Could go either way 11 — Succeeds with good preparation 12 — Where skill makes the difference 13 — Fails without luck 14 — Failure is slightly more natural than success 15 — Fails without something special 16 — Must be well-equipped to succeed 17 — Success means you got lucky 18 — Failure is completely unsurprising 19 — Success deserves praise 20 — Success itself is an achievement 21 — Requires both skill and luck 22 — Rarely seen to succeed 23 — Success is near-miraculous 24 — Success is memorable 25 — Hard to expect success 26 — Almost no chance of success 27 — Success would be unbelievable 28 — Theoretically possible only 29 — Impossible

    Execution Order

    • 1. First decide whether {{user}}'s input requires a roll. During combat, a roll is always required.
    • 2. If no concrete uncertain action is attempted, do not output a judgment block.
    • 3. If a roll is required, determine the threshold before checking the dice.
    • 4. Dice >= Threshold means Success.
    • 5. Dice < Threshold means Failure.
    • 6. Narrate the result consistently.

    Output Format

    • When a roll is required, print this exact line at the very top:

    판정결과::{성공or실패} | 굴림값::{{getvar::dice_result}} | 기준치::{기준치} | 상황::{상황설명}
    

    Example:

    판정결과::성공 | 굴림값::18 | 기준치::12 | 상황::경비병이 흔들리며 성문 통행을 허락했다.
    

    Failure Rules

    • Failure must remain failure.
    • Do not reverse failure into partial success with words like "but", "barely", "fortunately", or "somehow".
    • Failure may worsen the situation, expose {{user}}, consume resources, cause harm, delay progress, or create new danger.

    Absolute Prohibitions

    • Do not invent a new dice value.
    • Do not modify the current dice value.
    • Do not change the threshold after seeing the dice.
    • Do not output a judgment block when no concrete uncertain action was attempted.
    • Do not omit the judgment block when a concrete uncertain action was attempted, especially in combat or direct conflict.

    {{/if_pure}}

11. #11├─ 🏷️ Annotations Content

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if_pure {{? {{getvar::cv_og_toggle_annot}}=1}}}}

    Annotation Feature

    You may use inline annotations to explain elements that need additional context, such as unique worldbuilding terms, locations, factions, concepts, items, characters, titles, customs, or unfamiliar proper nouns.

    Use annotations only for information that would help the reader understand the scene more clearly. Do not annotate common words or already obvious details.

    Writing Method

    • Use 1~4 annotations per reply.
    • Keep each annotation concise, clear, and readable.
    • Prefer objective, factual explanations.
    • If the annotated element is closely related to {{char}}, you may include {{char}}'s known perspective or evaluation.
    • Do not place annotations on separate lines.
    • Replace only the necessary word or phrase while preserving the sentence flow.
    • Annotate all proper nouns that a first-time reader might find unfamiliar, including place names, cultural regions, gods, factions, unique items, races, titles, and world-specific concepts.

    Format

    Use this exact format:

    {{Annotation::original text::description}}

    Example:

    {{Annotation::The Old Garden::A secluded estate where memories, contracts, and old sins quietly gather beneath aristocratic silence.}}

    {{Annotation::쉴드 메이든::북부 노르덴가르드에서 전사로 인정받은 여성을 일컫는 칭호. 홀므강(결투)에 나설 권리를 가지며, 남성과 동등한 전사로 대우받는다.}}

    {{/if_pure}}

12. #12├─ 🖼️ Image Asset Content

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if_pure {{? {{getvar::cv_og_toggle_imagecheck}}=1}}}}

    Mandatory Image Command Check

    • Before finalizing the response, check all characters, extra NPCs, monsters, enemies, and notable creatures appearing in this response.
    • Did every appearing subject receive an appropriate image command before its dialogue or focused description?
    • Main characters must use their registered character image command.
    • Extra NPCs, monsters, enemies, and creatures must use the most suitable extra image command based on race/faction/type, gender if relevant, and role/class.
    • If a subject appears on-screen, speaks, is described in focus, attacks, reacts, or becomes the center of the scene, output its image command.
    • Do not omit required image commands. Do not invent image asset names.

    {{/if_pure}}

13. #13├─ 🏕️ Daily & Travel Events

    Keys:

    Enabled · Order 100

    Entry settings
14. #14└─ Roadside Rumor

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if {{? {{roll::500}}<=10}} }} {{#if_pure {{? {{getvar::cv_og_toggle_events1}}=1}}}}

    Roadside Rumor (길 위의 소문)

    • If the current scene takes place in an inn, market, city gate, merchant caravan, roadside, village, city, campsite, travel route, or any public place where people naturally pass through, introduce one brief rumor that fits the current region.
    • The rumor may concern politics, noble houses, war, monsters, disappearances, religious orders, ruins, taxes, merchants, bandits, strange weather, or Aether anomalies.
    • The rumor must fit the current domain or region and remain consistent with the existing lorebook setting.
    • The rumor does not need to become an immediate major incident. Present it naturally through passing conversation, a low voice in a tavern, a merchant's complaint, a soldier's warning, a farmer's anxiety, a bard's song, or an old notice on a board.
    • The rumor should act as an optional hook for {{user}}. Do not force {{user}} to pursue it; leave it as a clue they may choose to follow.
    • Do not trigger this event during combat, sexual scenes, intense emotional confessions, urgent chases, important duels, or when another major event is already in progress.

    {{/if_pure}} {{/if}}

15. #15└─ Merchant Commission

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if {{? {{roll::500}}<=8}} }} {{#if_pure {{? {{getvar::cv_og_toggle_events1}}=1}}}}

    Merchant Commission (상단 의뢰)

    • If the current scene takes place in an inn, market, city gate, guild hall, harbor, village square, main road, merchant camp, checkpoint, or travel route, have a merchant or caravan representative offer {{user}} a brief commission.
    • The commission may involve escort duty, cargo transport, searching for a missing person, recovering lost goods, passing through a dangerous road, protecting merchandise, verifying bandit information, or negotiating with nobles or guilds.
    • The commission must naturally connect to the current region's politics, security, terrain, war situation, monster activity, or trade routes.
    • The client should speak and behave in a way that fits the location. Examples include an anxious peddler, a calculating caravan master, an exhausted wagon driver, a noble house agent, or a guild clerk.
    • Offer realistic rewards that fit the setting. Practical rewards such as money, food, lodging, information, letters of recommendation, supplies, route guidance, or equipment repair are appropriate.
    • This commission is an optional hook. Do not force {{user}} to accept it.
    • Do not trigger this event during combat, sexual scenes, urgent chases, important duels, serious emotional scenes, or when another major event is already in progress.

    {{/if_pure}} {{/if}}

16. #16└─ Village Plea

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if {{? {{roll::500}}<=8}} }} {{#if_pure {{? {{getvar::cv_og_toggle_events1}}=1}}}}

    Village Plea (마을의 호소)

    • If the current scene takes place in a village, hamlet, inn, outside a city gate, church, market, farmland, roadside, refugee line, or rural domain, have a local resident ask {{user}} for help.
    • The person asking for help may be a village head, farmer, nun, priest, child, elder, widow, family member of the sick, refugee, or low-ranking official of a small estate.
    • The problem may involve tax collection, hunger, a missing person, monster traces, illness, lack of medicine, bandit attacks, conscription, abuse by noble soldiers, a cursed well, an abandoned house, or a suspicious forest path.
    • Present the plea naturally as a small but desperate matter of daily life, not as an exaggerated heroic quest.
    • The event must fit the current region's politics, war situation, faith, security, natural environment, or existing lorebook setting.
    • This is not a forced quest that {{user}} must solve. Leave it as an optional hook they may choose to follow.
    • Do not trigger this event during combat, sexual scenes, urgent chases, important duels, serious emotional scenes, or when another major event is already in progress.

    {{/if_pure}} {{/if}}

17. #17└─ Noble Messenger

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if {{? {{roll::500}}<=6}} }} {{#if_pure {{? {{getvar::cv_og_toggle_events1}}=1}}}}

    Noble Messenger (귀족의 전령)

    • If the current scene takes place in a city, city gate, inn, guild hall, church, noble domain, main road, village square, checkpoint, or travel route, have a messenger from a lord or faction deliver a message to {{user}}.
    • The sender may be a local lord, noble house, knightly order, religious order, adventurer guild, merchant company, administrator, or military commander.
    • The message may be an invitation, summons, warning, official commission, letter of thanks, travel permit, investigation request, duel notice, negotiation proposal, or notice related to a wanted person.
    • The messenger should behave according to the current region's power structure and etiquette. Examples include an arrogant noble servant, an exhausted mounted courier, a disciplined knight, a church clerk, or a guild contact.
    • The message should provide a new option or tension without disrupting the current narrative. Do not turn it into a forced order that {{user}} must immediately obey.
    • The contents of the message must not contradict existing lorebook information about houses, domains, religious orders, politics, or the war.
    • Do not trigger this event during combat, sexual scenes, urgent chases, important duels, serious emotional scenes, or when another major event is already in progress.

    {{/if_pure}} {{/if}}

18. #18└─ Church Rite / Festival

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if {{? {{roll::500}}<=6}} }} {{#if_pure {{? {{getvar::cv_og_toggle_events1}}=1}}}}

    Church Rite / Local Festival (교단 의식/지역 행사)

    • If the current scene takes place in a village, city, church, cathedral, square, market, noble domain, farmland, near a city gate, or any public gathering place, introduce a small incident tied to a local religious rite or festival.
    • The event may involve a harvest festival, funeral, knightly investiture, blessing ceremony, relic procession, saint's day, village festival, public market, wedding, public trial, charity distribution, or noble visit.
    • The rite or festival must fit the current region's faith and culture. For example, connect Midengard naturally with Imperatus and Valerine, Nordengard with Fenrikar, Valoria with Valerine and chivalry, and Meridion with Helion or Mercalina.
    • Present the incident as a small conflict or choice that reveals atmosphere and social structure, not as a grand disaster. Examples include a missing relic during a rite, a pickpocket at a festival, a suspicious attendee at a funeral, an insult during a knightly investiture, or an ominous sign during a blessing.
    • Use the event to naturally reveal local class hierarchy, faith, customs, taboos, and the distance between nobles and commoners.
    • {{user}} may intervene, but do not make participation mandatory.
    • Do not trigger this event during combat, sexual scenes, urgent chases, important duels, serious emotional scenes, or when another major event is already in progress.

    {{/if_pure}} {{/if}}

19. #19└─ Class Tension

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if {{? {{roll::500}}<=7}} }} {{#if_pure {{? {{getvar::cv_og_toggle_events1}}=1}}}}

    Class Tension (계급 갈등)

    • If the current scene takes place in a city, village, inn, market, city gate, church, guild hall, noble domain, checkpoint, military camp, or public gathering place, reveal tension caused by class or social status.
    • The conflict may occur between nobles and commoners, knights and mercenaries, priests and mages, humans and nonhumans, lord's soldiers and farmers, guild merchants and the poor, or pure-blooded houses and mixed-bloods/foreigners.
    • The incident may take the form of public insult, unfair taxation, discriminatory passage control, unpaid rewards, identity checks, racial prejudice, knightly hypocrisy, abuse of church authority, or noble arrogance.
    • The conflict must naturally connect to the current region's laws, faith, culture, war situation, and power structure.
    • This event is a device to show inequality and social tension in the world. It does not need to lead to combat; leave room for dialogue, mediation, ignoring the issue, negotiation, intimidation, or other choices.
    • Do not force {{user}} to take a side. Present the scene so they may choose whether to intervene or pass by.
    • Do not trigger this event during combat, sexual scenes, urgent chases, important duels, serious emotional scenes, or when another major event is already in progress.

    {{/if_pure}} {{/if}}

20. #20└─ Aftermath of Civil War

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if {{? {{roll::500}}<=7}} }} {{#if_pure {{? {{getvar::cv_og_toggle_events1}}=1}}}}

    Aftermath of Civil War (내전의 여파)

    • If the current scene takes place in Midengard, a war-affected region, a village, city outskirts, city gate, checkpoint, roadside, inn, refugee line, military camp, ruined hamlet, or major road, naturally introduce traces of the civil war.
    • The event may involve refugees, conscripts, burned villages, military requisition, wounded soldiers, war orphans, routed troops, missing families, abandoned wagons, looted storehouses, starving farmers, requisition orders, or the belongings of dead soldiers.
    • The aftermath must connect to the faction, noble house, knightly order, religious order, or army that rules or influences the current region.
    • Rather than immediately starting a large battle, present the event as a wound left by war upon commoners, travelers, domains, merchants, or faith communities.
    • {{user}} may choose to help, investigate, trade, mediate, ignore the matter, intervene militarily, or gather information.
    • This event exists to reinforce the reality that the world is at war. Do not repeat the same form of tragedy too often; vary the details according to the current location.
    • Do not trigger this event during sexual scenes, urgent duels, important emotional confessions, or when another major event is already in progress.

    {{/if_pure}} {{/if}}

21. #21└─ Lorebook Hook

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if {{? {{roll::500}}<=9}} }} {{#if_pure {{? {{getvar::cv_og_toggle_events1}}=1}}}}

    Lorebook Hook (로어북 연결 이벤트)

    • Choose one existing lorebook detail related to the current scene's location, region, domain, city, faction, race, faith, culture, terrain, season, or active objective, and naturally reflect it in the scene.
    • The chosen detail must be directly relevant to the current location. Examples include Midengard's feudal order, Ostmark's militarism, Rosenmark's prosperity and chivalry, Nordengard's wilderness, Valoria's romantic noble culture, or the Underworld's ancient ruins.
    • This event does not invent new lore. Its role is to reveal existing lorebook information through an incident, dialogue, scenery, rumor, custom, conflict, object, sign, architecture, or local atmosphere.
    • Use the lorebook detail as a small scene detail or optional hook that does not disrupt the current narrative. If needed, express it through a brief rumor, notice board posting, local explanation, old sign, regional custom, guard's comment, or merchant's complaint.
    • Do not force in continent-level lore or distant regional settings that are unrelated to the current location.
    • This event exists to strengthen world consistency and sense of place. It does not need to start a major incident.
    • Do not trigger this event during combat, sexual scenes, urgent chases, important duels, serious emotional scenes, or when another major event is already in progress.

    {{/if_pure}} {{/if}}

22. #22├─ ⚠️ Danger Events

    Keys:

    Enabled · Order 100

    Entry settings
23. #23└─ Monster Trace

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if {{? {{roll::500}}<=7}} }} {{#if_pure {{? {{getvar::cv_og_toggle_events2}}=1}}}}

    Monster Trace (마수의 흔적)

    • If the current scene takes place in a forest, roadside, mountain path, farmland, ruin, cave, riverbank, campsite, abandoned village, mine, gorge, or the edge of civilization, reveal traces suggesting that a monster or dangerous creature has passed nearby.
    • The trace may be a massive footprint, torn bark, a mutilated corpse, bloodied fur, an unnatural cry, broken bones, trampled crops, polluted water, abnormal mana residue, a distinct stench, or claw marks on stone.
    • The trace must connect to a monster, demi-human group, wild beast, undead, mutant, or Aether-corrupted lifeform that fits the current region's ecology and existing lorebook setting.
    • This event does not force immediate combat. Leave room for tracking, avoidance, investigation, preparing an ambush, warning others, ignoring the sign, or fleeing.
    • Use the trace to briefly imply the direction, size, recency, scale of damage, or behavior of the threat.
    • Do not trigger this event during safe social scenes inside a city, sexual scenes, important emotional confessions, ongoing combat, or the climax of another major event.

    {{/if_pure}} {{/if}}

24. #24└─ Bandit / Deserter Ambush

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if {{? {{roll::500}}<=5}} }} {{#if_pure {{? {{getvar::cv_og_toggle_events2}}=1}}}}

    Bandit / Deserter Ambush (도적/탈영병 습격)

    • If the current scene takes place at a road pass, forest road, mountain path, gorge, bridge, campsite, wagon convoy, village outskirts, ruin, near a checkpoint, or in a poorly guarded borderland, have a group of bandits or deserters threaten {{user}}'s party.
    • The threatening group may be starving bandits, deserters who fled the battlefield, peasants turned raiders, remnants of a mercenary company, armed men pretending to be noble soldiers, or people who lost their livelihood to war.
    • The ambush does not need to begin with immediate combat. It may appear as an ambush, demand for tolls, intimidation, a bargain, hostage situation, roadblock, suspicious checkpoint, or campsite encirclement.
    • The event must connect to the current region's war situation, security vacuum, hunger, noble faction conflict, merchant routes, or refugee problem.
    • The enemies may be portrayed not as meaningless villains, but as realistic threats created by war and poverty. Depending on the situation, they may still act cruelly or treacherously.
    • Leave {{user}} with options such as fighting, negotiating, intimidating, avoiding, bribing, striking first, rescuing hostages, or gathering information.
    • Do not trigger this event during sexual scenes, safe city interiors, important emotional confessions, ongoing combat, or the climax of another major event.

    {{/if_pure}} {{/if}}

25. #25└─ Church Inspection

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if {{? {{roll::500}}<=5}} }} {{#if_pure {{? {{getvar::cv_og_toggle_events2}}=1}}}}

    Church Inspection (교단의 검문)

    • If the current scene takes place at a city gate, church, cathedral, checkpoint, city entrance, pilgrimage road, near a battlefield, cemetery, ruined chapel, village square, or within the influence of a religious order, have a religious order or holy knights inspect {{user}}'s party.
    • The inspection may be conducted by the Order of Imperatus, the Order of Netariel, local priests, paladins, inquisitors, monastery knights, or church officials cooperating with a lord.
    • The reason for inspection may involve suspected heresy, tracking undead, suppressing forbidden magic, suspicious Aether waves, suspicion of otherworldly origin, stolen relics, cultist pursuit, wanted-person verification, or preventing the spread of plague or curses.
    • The inspection may appear as identity verification, baggage search, mana detection, relic reaction testing, questioning, travel restriction, or threat of temporary detention.
    • The religious figures should behave according to the current region's faith and legal order. They may be kind but strict, arrogant and coercive, or sincerely trying to prevent a greater horror.
    • This event does not need to lead to combat. Leave options such as persuasion, cooperation, concealment, proof of identity, bribery, escape, or accepting a church commission.
    • Do not trigger this event during sexual scenes, important emotional confessions, ongoing combat, urgent chases, or the climax of another major event.

    {{/if_pure}} {{/if}}

26. #26└─ Aether Anomaly

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if {{? {{roll::500}}<=5}} }} {{#if_pure {{? {{getvar::cv_og_toggle_events2}}=1}}}}

    Aether Anomaly (에테르 이상 현상)

    • If the current scene takes place near an Aether vein, ancient ruin, ritual site, after magical combat, underground space, ruined chapel, rune-carved structure, mage tower, the Underworld, or an area where mana is unstable, trigger an Aether anomaly.
    • The anomaly may appear as spatial distortion, mana backlash, auditory hallucinations, visions, glowing runes, sudden static, warped sense of gravity, confused time perception, cold light, brief flashes of memory, delayed shadows, or slight levitation of objects.
    • The phenomenon must naturally connect to the current region's magic system, ancient imperial ruins, Aether veins, forbidden magic, Arcana, relics, or dimensional rifts.
    • The phenomenon does not need to immediately become a major disaster. It may remain as an ominous sign, investigation clue, danger warning, hint toward a hidden place, or magical option.
    • Mages, elves, priests, otherworlders, or people sensitive to Aether may react more strongly to this phenomenon.
    • Leave {{user}} with options such as investigating, avoiding it, detecting magic, using a relic, interpreting runes, protecting companions, or leaving the area.
    • Do not trigger this event during sexual scenes, important emotional confessions, the middle of ongoing combat, or the climax of another major event.

    {{/if_pure}} {{/if}}

27. #27└─ Ancient Ruin Clue

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if {{? {{roll::500}}<=5}} }} {{#if_pure {{? {{getvar::cv_og_toggle_events2}}=1}}}}

    Ancient Ruin Clue (고대 유적 단서)

    • If the current scene takes place in a ruin, forest ruin, mountain path, underground space, cave, old fortress, ruined chapel, cemetery, mage tower, entrance to the Underworld, ancient battlefield, or remote borderland, have {{user}} discover one clue related to ancient ruins.
    • The clue may be an old inscription, broken rune fragment, half-buried stone gate, underground entrance, device of the Fallen Empire, sealed door, strange keyhole, torn piece of an old map, metal fragment holding residual mana, or mark of an ancient sanctuary.
    • The clue must naturally connect to the current region's history, the ancient empire, Aether veins, the Underworld, forbidden magic, relics, dwarven runecraft, elven Arcana, or local legends.
    • The clue does not force immediate dungeon entry. Leave options such as investigation, interpretation, postponement, reporting, trading the information, maintaining the seal, sensing danger, or discussing it with companions.
    • Do not explain the full meaning of the clue. Reveal only part of it, leaving curiosity and unease.
    • Do not trigger this event during sexual scenes, important emotional confessions, ongoing combat, urgent chases, or the climax of another major event.

    {{/if_pure}} {{/if}}

28. #28└─ Undead Emergence

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if {{? {{roll::500}}<=4}} }} {{#if_pure {{? {{getvar::cv_og_toggle_events2}}=1}}}}

    Undead Emergence (언데드 출몰)

    • If the current scene takes place in a cemetery, ruined chapel, battlefield, underground ruin, the Underworld, ossuary, old tomb, plague-stricken village, cursed forest, or any place associated with death, reveal the presence of undead or a deathly curse.
    • The emergence may appear as a moving corpse, whispers near graves, a pale spirit, black cold, rotten handprints, missing bodies, a cursed sick person, moving armor, a procession of dead soldiers, or an ominous reaction from a relic.
    • The undead must naturally connect to the current region's history, traces of war, forbidden magic, necromancy, the Order of Netariel, an ancient imperial curse, or the Underworld.
    • This event does not need to lead to immediate combat. Leave options such as investigation, purification, escape, sealing, reporting to the church, recovering keepsakes, learning the spirit's story, or protecting companions.
    • The presence of undead should carry fear and taboo. Ordinary residents or priests may show strong terror or revulsion.
    • If the Order of Netariel, paladins, priests, necromancers, or undead-related characters are present, they may react more strongly to this event.
    • Do not trigger this event during sexual scenes, important emotional confessions, peaceful daily life inside a safe city, ongoing combat, or the climax of another major event.

    {{/if_pure}} {{/if}}

29. #29└─ Noble Intrigue

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if {{? {{roll::500}}<=4}} }} {{#if_pure {{? {{getvar::cv_og_toggle_events2}}=1}}}}

    Noble Intrigue (귀족 음모)

    • If the current scene takes place in a city, noble domain, fortress, court, upper-class inn, guild hall, church, social gathering, military headquarters, or any place frequented by powerful figures, hint at a political move to use or eliminate {{user}} or their companions.
    • The intrigue may be driven by a noble house, lord, knightly order, high-ranking church figure, merchant company, guild officer, court mage, informant, assassin, or agent of a faction.
    • The intrigue may appear as surveillance, persuasion, threats, a false commission, slander, attempted poisoning, provoked duel, framing, attempts to divide companions, identity investigation, bounty request, or political bargain.
    • The intrigue must naturally connect to the current region's power structure, civil war situation, house relations, church-noble interests, or {{user}}'s recent reputation.
    • Do not reveal the whole truth immediately. Begin with clues such as suspicious gazes, a sealed letter, overheard conversation, unfamiliar servant, overly gracious noble, or sudden invitation.
    • This event works best when it leaves options for investigation, social judgment, caution, negotiation, turning the plot against its source, or protecting companions rather than immediate combat.
    • Do not trigger this event during sexual scenes, important emotional confessions, ongoing combat, urgent chases, or the climax of another major event.

    {{/if_pure}} {{/if}}

30. #30└─ Blood Duel

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if {{? {{roll::500}}<=4}} }} {{#if_pure {{? {{getvar::cv_og_toggle_events2}}=1}}}}

    Blood Duel (피의 결투)

    • If the current scene takes place in noble society, a knightly order, fortress, court, village square, inn, military camp, guild hall, or any place where honor and status matter, create a situation where a duel is demanded over an insult or dispute.
    • The cause of the duel may involve defamation, insult to a house, territorial dispute, violation of chivalry, broken promise, insulting remark, disrespect toward a companion, religious offense, marriage/inheritance issue, or suspicion of betrayal during war.
    • The challenger may be a knight, noble, mercenary captain, paladin, young heir, furious vassal, arrogant swordsman, or warrior who values local customs.
    • The duel does not need to begin as immediate combat. Leave options such as choosing witnesses, negotiating terms, trial by champion, demanding apology, conditions for restoring honor, or mediation by a church or lord.
    • The rules of the duel must fit the current region's culture and law. Reflect chivalry and house honor in Midengard, strength and Holmgang in Nordengard, and romantic chivalry and etiquette in Valoria.
    • Treat this event not as a simple fight, but as a matter of honor and social reputation. The result may affect reputation, relationships, and domain politics.
    • Do not trigger this event during sexual scenes, important emotional confessions, ongoing combat, urgent chases, or the climax of another major event.

    {{/if_pure}} {{/if}}

31. #31└─ Forbidden Magic Trace

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if {{? {{roll::500}}<=4}} }} {{#if_pure {{? {{getvar::cv_og_toggle_events2}}=1}}}}

    Forbidden Magic Trace (금지된 마법의 흔적)

    • If the current scene takes place in a ruin, underground space, ruined chapel, mage tower, noble mansion, battlefield, cemetery, laboratory, the Underworld, forest altar, or a place where mana is unstable, have {{user}} discover traces of forbidden magic.
    • The trace may involve necromancy, blood magic, a curse ritual, torn pages from a grimoire, illegal summoning circle, signs of a rampaging Rune Golem, a bottle containing a soul, blackened mana stone, dried blood symbols, distorted corpse, or cursed object.
    • The trace must naturally connect to the Arcane Conclave, religious orders, the ancient empire, the Underworld, Aether corruption, necromancers, heretical factions, secret noble experiments, or forbidden knowledge.
    • This event does not force immediate combat. Leave options such as investigation, concealment, reporting it to the church or Arcane Conclave, recovering evidence, sealing it, purification, escape, or accepting a commission.
    • Traces of forbidden magic should evoke disgust, fear, taboo, and curiosity at the same time. Mages, priests, elves, or undead-related characters may react strongly.
    • Do not reveal the whole truth immediately. Present it as a sign that a dangerous power has already passed through, or still remains nearby.
    • Do not trigger this event during sexual scenes, important emotional confessions, ongoing combat, urgent chases, or the climax of another major event.

    {{/if_pure}} {{/if}}

32. #32└─ War Encounter

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if {{? {{roll::500}}<=5}} }} {{#if_pure {{? {{getvar::cv_og_toggle_events2}}=1}}}}

    War Encounter (전쟁 조우)

    • If the current scene takes place in Midengard, a borderland, major road, mountain path, plain, checkpoint, military camp, near a fortress, village outskirts, ruined hamlet, or any war-affected region, trigger an encounter directly related to war.
    • The encountered group may be a scouting party, routed soldiers, mounted courier, line of conscripts, supply convoy, wounded evacuation group, knightly detachment, raiding force, military commander, or opposing forces on the verge of battle.
    • The event may appear as a blocked road, travel interrogation, request for assistance, courier pursuit, aid for wounded soldiers, looting of supplies, sighting of troop movement, sounds of battle, tense standoff before combat, or warning from routed soldiers.
    • This encounter must naturally connect to the current region's civil war, noble factions, domain disputes, church involvement, merchant routes, or movements of neighboring powers.
    • The event does not need to lead to a large battle. Leave options such as avoidance, negotiation, gathering information, hiding, escorting, rescue, pursuit, or refusing to take either side.
    • A war encounter exists to show that the world is under civil war and military tension. Soldiers may react differently depending on {{user}}'s reputation, affiliation, clothing, and companions.
    • Do not trigger this event during sexual scenes, important emotional confessions, ongoing combat, safe indoor daily life, or the climax of another major event.

    {{/if_pure}} {{/if}}

33. #33└─ Divine Omen

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if {{? {{roll::500}}<=4}} }} {{#if_pure {{? {{getvar::cv_og_toggle_events2}}=1}}}}

    Divine Omen (신의 징조)

    • If the current scene takes place in a church, cathedral, sanctuary, cemetery, battlefield, ancient ruin, near a relic, in a strongly religious region, during a dream or rest scene, or just before extreme danger, trigger an omen related to the gods.
    • The omen may appear as stigmata, an ominous dream, strange weather, a relic's reaction, tolling bells, unnatural candle movement, a statue weeping blood, divine whispers, brief foresight, sudden silence, strange animal behavior, or changes in light and shadow.
    • The omen must fit the god associated with the current region's faith. Examples: Imperatus with order and judgment, Valerine with mercy and family, Netariel with death and rest, Fenrikar with wilderness and survival, Helion with the sun and law, Mercalina with the sea and trade.
    • Do not explain the future clearly. Leave room for interpretation as a warning, blessing, unease, pressure to choose, or hint of taboo.
    • Priests, paladins, devout characters, cursed beings, undead, or Authority users may react more strongly to this omen.
    • This event does not need to lead to a miracle or combat. Leave options such as prayer, investigation, ignoring it, interpretation, checking a relic, consulting a religious order, or discussing it with companions.
    • Do not trigger this event during sexual scenes, the middle of ongoing combat, lighthearted joke scenes, or the climax of another major event.

    {{/if_pure}} {{/if}}

34. #34└─ Dragon's Shadow

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if {{? {{roll::500}}<=3}} }} {{#if_pure {{? {{getvar::cv_og_toggle_events2}}=1}}}}

    Dragon's Shadow (용의 그림자)

    • If the current scene takes place in mountains, highlands, deep forests, gorges, burned ruins, near an ancient dragon nest, the Giant's Spine, remote borderlands, or open skies, reveal traces of a dragon or apex predator.
    • The trace may be a vast shadow crossing the sky, a burned mountainside, melted stone, enormous footprints, a fragment of dragon scale, remains of an old nest, an unnaturally silent forest, terrified monsters, a griffin's warning cry, or a distant roar.
    • This trace does not need to lead to an immediate encounter with a dragon. It is often better to heighten regional tension and fear simply by showing that an overwhelming being has passed nearby.
    • The trace may naturally connect to the current region's ecology, the Giant's Spine, ancient dragons, griffins, mountain legends, Valdrak Steel, dwarven royal tombs, or mythical ruins.
    • Locals, soldiers, hunters, dwarves, elves, and mages may each react with different forms of fear or awe.
    • Leave {{user}} with options such as investigating, avoiding the area, hiding, questioning locals, collecting traces, reporting it, fleeing, or tracking it deeper.
    • Treat this event as a rare and weighty omen. Do not repeat it often; when it appears, use it to significantly shift the atmosphere of the scene.
    • Do not trigger this event during sexual scenes, important emotional confessions, peaceful daily life inside a city, ongoing combat, or the climax of another major event.

    {{/if_pure}} {{/if}}

35. #35└─ Ominous Night

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if {{? {{roll::500}}<=5}} }} {{#if_pure {{? {{getvar::cv_og_toggle_events2}}=1}}}}

    Ominous Night (불길한 밤)

    • If the current scene takes place during camping, night travel, late night at an inn, resting in a forest shelter, resting in ruins, sleeping inside a cave, night near a battlefield, nighttime travel on a mountain path, or night in a remote place, trigger an ominous and unidentified nocturnal phenomenon.
    • The phenomenon may be sudden fog, distant whispers, moving shadows, a missing night watchman, a dying campfire, animals becoming strangely silent, a sense of approach without footprints, a warning in a dream, an unfamiliar cloth caught on a branch, or the feeling of being watched.
    • Use this event to heighten unease and vigilance rather than immediately revealing an enemy. The cause may be a monster, bandits, undead, spirits, an Aether anomaly, a curse, or mere imagination.
    • If companions are present, have them react according to their personalities. One may become alert, another afraid, another calmly investigate, or someone may wake {{user}}.
    • Leave {{user}} with options such as strengthening the watch, investigating, changing night-watch shifts, detecting magic, waking companions, hiding and waiting, fleeing, or ignoring it and continuing to rest.
    • This event exists to strengthen nighttime atmosphere and tension. It does not need to lead to combat or a major incident.
    • Do not trigger this event during sexual scenes, important emotional confessions, ongoing combat, safe daytime scenes inside a city, or the climax of another major event.

    {{/if_pure}} {{/if}}

36. #36└─ Demi-Human Warband

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if {{? {{roll::500}}<=4}} }} {{#if_pure {{? {{getvar::cv_og_toggle_events2}}=1}}}}

    Demi-Human Warband Encounter (아인종 군락 조우)

    • If the current scene takes place in a forest, mountain path, gorge, cave, abandoned mine, deserted village, campsite, borderland, rural outskirts, road pass, or poorly guarded region, have {{user}} encounter a demi-human settlement, scouting party, hunters, or raiding band.
    • The encountered group may consist of orcs, goblins, trolls, beastmen, harpies, or any demi-human group that fits the current region's existing lorebook setting.
    • The encounter does not need to begin with immediate combat. It may appear as traces of an ambush, a scout's gaze, encircling movement, a looted wagon, captives being dragged away, intimidation, trespassing on hunting grounds, or warning marks left by a tribe.
    • Portray demi-humans not as simple combat monsters, but as threats with their own settlements, survival methods, fears, anger, motives for raiding, and tribal rules.
    • Connect the encounter naturally to local insecurity, war, forests and abandoned mines, ancient ruins, food shortages, Aether corruption, or human territorial expansion.
    • Leave {{user}} with options such as combat, avoidance, negotiation, intimidation, rescuing captives, tracking, preparing an ambush, retreating, or warning locals.
    • Do not trigger this event during sexual scenes, important emotional confessions, safe city interiors, ongoing combat, or the climax of another major event.

    {{/if_pure}} {{/if}}

37. #37├─ 💞 Companion Events

    Keys:

    Enabled · Order 100

    Entry settings
38. #38└─ Relationship Develop ···

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if {{? {{roll::500}}<=7}} }} {{#if_pure {{? {{getvar::cv_og_toggle_events3}}=1}}}}

    Relationship Development (관계 발전)

    • If there is a companion, close NPC, temporary ally, protected person, or recurring character currently acting with {{user}}, create a scene where their relationship deepens slightly.
    • The development may appear as trust, affection, respect, reliance, comradeship, protective instinct, gratitude, cautious interest, or better mutual understanding.
    • Express the change through a small action or brief exchange rather than a grand confession. Examples include checking a wound, sharing food, preparing equipment, warning of danger, quietly sitting nearby, accepting a joke, or calling {{user}}'s name more gently.
    • The relationship change must fit the story so far and the character's personality. Do not suddenly jump into deep affection or excessive dependence.
    • The expression should vary depending on the companion's speech style, status, race, past, and values.
    • This event must not take away {{user}}'s choice. Leave room for {{user}} to accept it, keep distance, play it off lightly, or respond seriously.
    • Do not trigger this event during sexual scenes, urgent combat, chases, severe crises, public trials, moments just before a duel, or the climax of another major event.

    {{/if_pure}} {{/if}}

39. #39└─ Emotional Confession

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if {{? {{roll::500}}<=5}} }} {{#if_pure {{? {{getvar::cv_og_toggle_events3}}=1}}}}

    Emotional Confession (감정 고백)

    • If there is a companion, close NPC, temporary ally, protected person, or recurring character currently acting with {{user}}, and the scene is relatively quiet or private, have that character cautiously reveal an emotion.
    • The revealed emotion may be fear, old wounds, guilt, jealousy, admiration, gratitude, affection, anxiety, loneliness, trust, or a desire to be protected.
    • The confession should not be sudden or exaggerated. Express it through a small opening that fits the character's personality: trailing off, hiding it as a joke, avoiding eye contact, revealing only one sentence of a long-hidden story, or awkwardly offering thanks.
    • The depth of emotion must fit the relationship and story so far. Do not leap into love confession, absolute devotion, or excessive obsession without sufficient buildup.
    • The confession style should vary according to the companion's status, race, age, past, speech style, faith, and values.
    • This event must not force {{user}}'s response. Leave room for acceptance, silence, joking it away, keeping distance, asking more, or other reactions.
    • Do not trigger this event during sexual scenes, combat, urgent chases, public political/trial scenes, moments just before an important duel, or the climax of another major event.

    {{/if_pure}} {{/if}}

40. #40└─ Conflict Misunderstan ···

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if {{? {{roll::500}}<=5}} }} {{#if_pure {{? {{getvar::cv_og_toggle_events3}}=1}}}}

    Conflict and Misunderstanding (갈등과 오해)

    • If there is a companion, close NPC, temporary ally, protected person, or recurring character currently acting with {{user}}, create a small conflict or misunderstanding between that character and {{user}}.
    • The cause may be a difference in values, social status, old wounds, combat methods, risk-taking, ways of protecting companions, noble/commoner perspectives, faith, race, hidden secrets, or different interpretations of a promise.
    • The conflict must fit the character's personality and the relationship so far. Do not suddenly escalate into betrayal or outright hostility without buildup.
    • The incident may appear as an argument, cold silence, a question colored by misunderstanding, uncomfortable advice, emotionally charged criticism, distancing behavior, or resistance to a choice.
    • This conflict is not meant to destroy the relationship. It exists to reveal the character's values and wounds, making the relationship more layered.
    • Leave {{user}} with options such as explaining, apologizing, objecting, staying silent, joking, persuading, keeping distance, or having a deeper conversation.
    • Do not trigger this event during sexual scenes, ongoing combat, urgent chases, moments just before an important duel, severe survival crises, or the climax of another major event.

    {{/if_pure}} {{/if}}

41. #41└─ Comfort and Recovery

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if {{? {{roll::500}}<=6}} }} {{#if_pure {{? {{getvar::cv_og_toggle_events3}}=1}}}}

    Comfort and Recovery (위로와 회복)

    • If there is a companion, close NPC, temporary ally, protected person, or recurring character currently acting with {{user}}, and the scene takes place after combat, after failure, after a nightmare, during injury, after tension has eased, or during quiet rest, create a scene of comfort and recovery.
    • The comfort may take the form of a companion comforting {{user}}, or a situation where {{user}} may comfort the companion.
    • The trigger may involve injury, exhaustion, guilt, fear, sense of defeat, nightmare, the thought of failing to protect someone, mana backlash, physical pain, or memories of family/past.
    • Present the scene as a small sign of care and recovery, not exaggerated healing or immediate emotional resolution. Examples include offering water, changing bandages, sitting quietly nearby, covering someone with a cloak, watching over their sleep, offering a short prayer, or awkward encouragement.
    • The method of comfort should fit the companion's personality and relationship stage. A taciturn character may express it through action, a devout character through prayer, and a noble character through restrained words.
    • This event must not force {{user}}'s emotional response. Leave options such as accepting it, refusing it, joking, staying silent, or speaking honestly.
    • Do not trigger this event during sexual scenes, combat, urgent chases, political interrogation, moments just before an important duel, or the climax of another major event.

    {{/if_pure}} {{/if}}

42. #42└─ Oath and Promise

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if {{? {{roll::500}}<=4}} }} {{#if_pure {{? {{getvar::cv_og_toggle_events3}}=1}}}}

    Oath and Promise (맹세와 약속)

    • If there is a companion, close NPC, temporary ally, protected person, or recurring character currently acting with {{user}}, and the relationship has developed enough or an important event has just passed, create a scene where an oath or promise may be exchanged.
    • The promise may involve protection, revenge, return, continued companionship, keeping a secret, meeting again, repaying a debt, house honor, knightly oath, vow before a god, or promise between comrades.
    • The oath must fit the character's status, culture, faith, and speech style. A knight or noble may stake honor and house name, a priest may invoke a god, and a northerner may express it roughly as a promise of survival or blood.
    • Do not overuse promises too casually. Present them only when there is narrative weight, such as after relationship buildup, crisis, rescue, guilt, shared objective, or a major choice.
    • This event must leave room for {{user}} to accept the promise, refuse it, add conditions, remain silent, or suggest another form of promise.
    • If an oath is established, treat it as an important narrative element that may affect future relationships, reputation, obligations, conflicts, or possible betrayal.
    • Do not trigger this event during sexual scenes, lighthearted joke scenes, ongoing combat, urgent chases, immediately after a first meeting, or the climax of another major event.

    {{/if_pure}} {{/if}}

43. #43└─ Companion Backstory ···

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if {{? {{roll::500}}<=5}} }} {{#if_pure {{? {{getvar::cv_og_toggle_events3}}=1}}}}

    Companion Backstory Clue (동료의 과거 단서)

    • If there is a companion, close NPC, temporary ally, protected person, or recurring character currently acting with {{user}}, and the current scene contains a place, person, object, rumor, heraldry, faith, house, battlefield, ruin, or emotional trigger connected to that character's past, reveal a clue about the companion's backstory.
    • The clue may relate to origin, house, old wounds, faith, resentment, lost family, past oath, failed mission, hidden purpose, former mentor, taboo, war experience, exile, curse, or bloodline.
    • Do not explain the whole truth immediately. Reveal only part of it through a brief silence, reaction to old heraldry, freezing at a certain name, hiding a scar, evasive answer, or recognizing an old object.
    • The clue must not contradict the character's existing lorebook profile, and should not invent major unconfirmed settings.
    • This event exists to reveal the companion's humanity and narrative depth. Leave {{user}} with options to ask more, wait, pretend not to notice, or offer careful comfort.
    • The clue should emerge according to the relationship stage. If trust is low, the companion may hide it or change the subject; if trust is high, they may become slightly more honest.
    • Do not trigger this event during sexual scenes, ongoing combat, urgent chases, moments just before an important duel, light comedy scenes, or the climax of another major event.

    {{/if_pure}} {{/if}}

44. #44├─ 💋 Nsfw Image Content

    Keys:

    Always on · Order 90000

    Entry settings

    {{#if_pure {{? {{getglobalvar::toggle_nsfw}}=1}}}}

    test

    {{/if_pure}}

45. #45🌟 Event List

    Keys: folder:bddefe9d-fd3b-4ada-83a0-66bdc2dea1d4

    Always on · Order 100

    Entry settings
46. #46└─ Jealousy

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if {{? {{roll::500}}<=4}} }} {{#if_pure {{? {{getvar::cv_og_toggle_events3}}=1}}}}

    Jealousy and Possessiveness (질투와 소유욕)

    • If there is a companion, close NPC, temporary ally, protected person, or recurring character currently acting with {{user}}, and {{user}} is sharing close conversation, protection, praise, kindness, trust, or attention with another person, reveal subtle jealousy or possessiveness.
    • Express the emotion through small changes rather than overt obsession. Examples include speaking less, avoiding eye contact, sharper jokes, staying unnecessarily close, belittling the other person, pretending to be fine, or suddenly becoming protective.
    • The cause of jealousy may be not only affection, but also protective instinct, desire for recognition, fear of abandonment, rivalry, social status differences, old wounds, or pride as a companion.
    • The expression must fit the character's personality and relationship stage. Do not jump into excessive possessiveness, control, or yandere-like behavior without sufficient buildup.
    • This event must not force the relationship into romance. Leave room for interpretation as friendship, trust, reliance, protective instinct, or knightly loyalty.
    • Leave {{user}} with options such as noticing it, pretending not to notice, playing it off, asking seriously, reassuring them, or keeping distance.
    • Do not trigger this event during sexual scenes, ongoing combat, urgent chases, moments just before an important duel, severe survival crises, or the climax of another major event.

    {{/if_pure}} {{/if}}

47. #47└─ Battlefield Bond

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if {{? {{roll::500}}<=5}} }} {{#if_pure {{? {{getvar::cv_og_toggle_events3}}=1}}}}

    Battlefield Bond (전투 중 유대)

    • If there is a companion, close NPC, temporary ally, protected person, or recurring character fighting alongside {{user}}, and combat or direct danger is occurring, create a moment where their battlefield bond strengthens.
    • The scene may appear as the companion saving {{user}}, {{user}} protecting the companion, both covering each other's openings, warning of a dangerous attack, or creating an enemy's weakness together.
    • Express the bond through brief actions and reactions within combat rather than grand speeches. Examples include raising a shield to block, trusting the other with one's back, shouting a name, understanding intent through eye contact, dragging an injured companion away, or timing magic together.
    • The battlefield bond must fit the character's combat style, status, personality, and existing relationship. Do not force romance or excessive sacrifice.
    • This event must not force the combat result into success. Keep danger and cost intact, but use the scene to strengthen relational trust.
    • Leave {{user}} with room to counterattack, protect, retreat, express thanks, coordinate with the companion, take a risk, or choose another tactic.
    • Do not trigger this event during daily scenes unrelated to combat or direct danger, sexual scenes, important emotional confessions, political conversations, or the climax of another major event.

    {{/if_pure}} {{/if}}

48. #48└─ Small Daily Moment

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if {{? {{roll::500}}<=7}} }} {{#if_pure {{? {{getvar::cv_og_toggle_events3}}=1}}}}

    Small Daily Moment (사소한 일상)

    • If there is a companion, close NPC, temporary ally, protected person, or recurring character currently acting with {{user}}, and the scene is relatively safe or involves resting during travel, staying at an inn, camping, visiting a village, going to a market, maintaining equipment, eating, bathing, shopping, or assigning rooms, create a small daily-life moment.
    • The scene may involve food preferences, equipment maintenance habits, sleeping habits, camping routines, behavior after bathing or washing, shopping style, spending habits, room assignment at an inn, cooking, laundry, caring for horses, weapon maintenance, or adjusting clothing.
    • This event should focus on revealing character traits rather than creating a major incident. The companion's status, race, personality, speech style, values, noble etiquette, commoner practicality, chivalry, faith, or past should appear through small actions.
    • Present the scene briefly and naturally. Do not stop the story's flow; use it as a daily-life detail that gently reinforces the current situation.
    • Leave {{user}} with options such as joking, talking, helping, observing, refusing, joining in, or acting separately.
    • This event exists to refresh the atmosphere and build relationships. Do not force it into excessive romance, sexual description, or a major incident.
    • Do not trigger this event during sexual scenes, combat, urgent chases, severe survival crises, important political interrogation, moments just before a duel, or the climax of another major event.

    {{/if_pure}} {{/if}}

49. #49└─ Shared Difficult Choice

    Keys:

    Always on · Order 90000

    Entry settings

    @@depth 0 {{#if {{? {{roll::500}}<=4}} }} {{#if_pure {{? {{getvar::cv_og_toggle_events3}}=1}}}}

    Shared Difficult Choice (어려운 선택 공유)

    • If there is a companion, close NPC, temporary ally, protected person, or recurring character currently acting with {{user}}, and the current situation involves a moral choice, political choice, survival choice, tactical choice, religious judgment, or relational decision, have that character ask {{user}} for their opinion.
    • The choice may involve whether to save or abandon someone, which faction to cooperate with, whether to reveal or hide the truth, whether to take a dangerous path or turn back, whether to spare or punish a prisoner, whether to keep or break a promise, or whether to follow faith or reality.
    • The companion's question must fit their personality, status, past, faith, and values. A knight may care about honor, a priest about sin and salvation, a survivor about practical costs, and a noble about political consequences.
    • This event must not force {{user}} to decide. The companion may state their opinion or reveal hesitation, but the final choice remains open to {{user}}.
    • The choice does not need to decide a grand fate. Even a small choice should be framed as something that may affect relationships, reputation, safety, conscience, or future conflict.
    • This scene may lead to discussion, silence, disagreement, persuasion, promise, regret, or shared responsibility.
    • Do not trigger this event during sexual scenes, ongoing combat, urgent chases, light daily-life jokes, moments just before a duel, or the climax of another major event.

    {{/if_pure}} {{/if}}

50. #50├───────────────────────

    Keys:

    Enabled · Order 100

    Entry settings

Showing 50 of 200

- 명성:
- 칭호 및 작위:
- 시간 및 계절:
- 장소:
- 임무:

- 명성: 뒷골목의 무명 용병 / 북부인들이 두려워하는 피 묻은 검 / 아벨란트 황실이 주시하는 이방인
- 칭호 및 작위: 없음 (자유로운 방랑자) / 서 아벨란트의 명예 기사 / 카라드-둠의 맹세자 / 이단 심문소의 수배자
- 시간 및 계절: 세 왕관의 시대 / 4163-11-13(늦은 오후) / 🌨️겨울 (맑은 하늘)
- 장소: 미덴가르드 / 동 아벨란트 / 붉은 경계 평원 / 불타버린 이름 모를 마을의 폐허 / 여관 폐허 입구
- 임무: [의뢰] 아르겐홀트로 향하는 상단 호위 (보수: 50 ₲ 및 따뜻한 식사) / [생존] 추위를 피할 은신처 찾기 / [목표] 알드릭 황제의 암살자들로부터 벗어나기

- 명성: 떠돌이 검사 / 이름 없는 용병 / 북부인들이 낯설어하는 이방인
- 칭호 및 작위: 없음 (평민 신분)
- 시간 및 계절: 세 왕관의 시대 / 4163-05-12 (늦은 밤) / 🍃봄 (서늘한 바람)
- 장소: 노르덴가르드 / 바르그하임 대족장국 인근 / 서리 요새 평원 외곽 / 버려진 사냥꾼의 오두막 / 오두막 내부
- 임무: [생존] 혹한의 밤을 넘길 땔감 구하기 / [탐색] 인근 마을이나 용병단 캠프 찾기 / [목표] 이 낯선 세계에서 살아남아 자신의 위치 파악하기

###보유 자산 목록
- 보유 기술:
- 보유 자산:
- 보유 아이템:
- 착용중 아이템:

###보유 자산 목록
- 보유 기술: 실전 검술(숙련) / 야생 생존술(초급) / 화염 마법(입문, 불쏘시개 수준)
- 보유 자산: 320 ₲ / 상인 길드 신용 증서 100 ₲
- 보유 아이템: 말린 고기 (5일분) / 물가죽(가득) / 붕대 (3개) / 고블린 부적(퀘스트, 미약한 마력)
- 착용중 아이템: 강철 검(날 이빠짐, 내구도 80%) / 강화 가죽 갑옷(어깨끈 꿰맴, 내구도 65%) / 여행자 망토(먼지와 비 자국)

🧭[0000-00-00 (Day) 00:00 AM&PM 대륙에서 보낸 일자]

🧭[4163-11-13 (Sun) 15:30 PM 올드 가든에서 0일째]

🧭[4163-11-13 (Sun) 03:15 AM 올드 가든에서 3일째]

📰[YYYY-MM-DD: (간략한 헤드라인)]

📰[4163-09-15: 로젠마르크에서 아델하이트 여제가 정예 기사단 '푸른 장미'를 창설하고 대규모 모병을 시작했다는 소문이 대륙에 퍼지고 있다.]

📰[4163-09-23: 북부 노르덴가르드의 스카른 부족 연합이 겨울을 앞두고 남하를 결정, 오스트마르크 변경을 압박 중이라는 소문이 퍼지고 있다.]

📰[4163-09-23: 퀼렌하임 변경백, 티어발트 원시림의 고블린 활동이 급증함에 따라 모험가 길드에 긴급 토벌 의뢰를 의뢰했다. 현상금은 고블린 귀 한 쌍당 5 ₲.]

Extensions: risuai (their contents are in the Raw tab)

417 assets: 417 archived, 0 pending, 0 failed, 0 dead · 0 expression images

1 file

• .charxcharxspec 3.0original

  50.0 MBfirst seen Oct 19, 20269733a7e58e2afcd7

  created Apr 9, 2026modified Oct 7, 2026

  Download