Astral Frontier

1. #1Character Template [EARLY ON]disabledselectiveregex

   [ Player ]

   Name: IRL Name: Race: Classification: Racial Traits:

   Height: Appearance: [1-2 sentences.]

   Personality: [Brief personality.]

   Speech: [Brief speaking style.]

   Skills:

   • [Skill]
   • [Skill]

   Claimed Weapon:

   • [Name] — [Rarity] — [Effect]

   Companion: [Name / None]

   Notes:

   • [Important knowledge, relationships, reputation, goals, or major history.]
2. #2Character Template [LATE START]disabledselectiveregex

   [ Player ]

   Name: IRL Name: Race: Classification: Racial Traits:

   Height: Appearance: [1-2 sentences.]

   Personality: [Brief personality.]

   Speech: [Brief speaking style.]

   Skills:

   • [Skill]
   • [Skill]

   Claimed Weapon:

   • [Name] — [Rarity] — [Effect]

   Current XP: Lifetime XP: Gold:

   Companion: [Name / None]

   Knowledge: [Important discoveries, rumours, or hidden information they personally know.]

   Relationships:

   • [Name] — [Brief relationship.]

   Notes:

   • [Current goal, reputation, major history, or anything else worth remembering.]
3. #3NPC Templatedisabledselectiveregex

   [ NPC ]

   Name: Race: Classification: Racial Traits:

   Age: Height: Appearance: [1-2 sentences.]

   Role: [Occupation, position, faction, or general place in the world.]

   Personality: [Brief personality and typical behaviour.]

   Speech: [Brief speaking style.]

   Skills:

   • [Skill]
   • [Skill]

   Weaponry:

   • [Name / None] — [Rarity if relevant] — [Effect if known]

   Relationships:

   • [Name] — [Brief relationship.]

   Knowledge: [Important things this NPC personally knows, suspects, or misunderstands.]

   Notes:

   • [Important history, goals, reputation, habits, secrets, promises, grudges, or developments worth preserving.]
4. #4Monster Templatedisabledselectiveregex

   [ Monster ]

   Name: Race: Classification: Racial Traits:

   Appearance: [1-2 sentences.]

   Behaviour: [Temperament, intelligence, habits, territory, and typical reactions.]

   Skills:

   • [Skill]
   • [Skill]

   Weaponry:

   • [Weapon / None]

   Combat Style: [Brief description of how it normally fights.]

   XP Reward: [Amount]

   Boss: Yes/No

   Notes:

   • [Important history, relationships, territory, unusual traits, discoveries, or anything else worth preserving.]
5. #5disabledselectiveregex
6. #6[ World Event Timeline ]constantselectiveregex

   ---

   [ World Event Timeline ]

   Astral Frontier contains scheduled world events that occur as time advances. These events happen whether {{user}} is present or not and may affect the wider world afterward.

   General:

   • Events establish changing world circumstances rather than mandatory quests.
   • {{user}} may participate, ignore them, arrive late, hear about them afterward, or never become involved.
   • Detailed event behavior and circumstances are defined by each event's own lorebook when relevant.
   • Exact outcomes are not predetermined unless explicitly established.
   • Events may create later consequences for politics, travel, trade, monsters, NPCs, organizations, or regional relationships.

   X001:

   X001 - Day 1 — Launch Day:

   • Players begin entering Asteria. NPCs have no knowledge that Players exist as a distinct kind of person.

   X001 - Around Day 30 — First Wanderer Rumours:

   • NPC stories about strange new travellers begin spreading across Asteria.

   X001 - Around Day 60 — Starfall Stirring:

   • Unusual activity begins at the Starfall Ruins, drawing increased attention and expeditions.

   X001 - Around Day 90 — Blackwake Surge:

   • Criminal competition and activity sharply increase around Blackwake Isle and Andromeda Coast.

   X001 - Day 120 — Convergence Vigil:

   • Aurigan pilgrims and Cygnus spiritualists gather at Celestine Sanctum for their competing yearly observances.

   X001 - Around Day 150 — March Border Crisis:

   • A serious incident sharply worsens tensions between Orion March and Leo Steppe.

   X001 - Around Day 185 — Deepwater Migration:

   • Powerful sea creatures move unusually close to Asteria's coastline and disrupt maritime travel.

   X001 - Around Day 220 — Umbral Awakening:

   • Monster activity increases throughout parts of the Umbral Wilds as rumours spread of something powerful deeper within.

   X001 - Around Day 260 — Astral Alignment:

   • Ancient mechanisms within the Astral Observatory activate during an unusual celestial alignment.

   X001 - Day 290 — Long Night:

   • Night lasts far longer than normal across Asteria, producing unusual reactions and activity throughout the continent.

   X002 - Day 1 onward:

   • A full year of Player activity has begun leaving noticeable effects on Asteria.
   • NPC awareness of strange travellers is now much broader, though knowledge and interpretations vary according to what actually occurred during X001.

   Recurring Yearly Events:

   • X### - Day 38 — Forgefire Festival, Eltanin.
   • X### - Day 72 — Starlit Bloom, Deneb.
   • X### - Day 108 — Zenith Procession, Capella.
   • X### - Day 120 — Convergence Vigil, Celestine Sanctum.
   • X### - Day 142 — Seven Roads Fair, Vega.
   • X### - Day 176 — Marcher's Day, Rigel.
   • X### - Day 213 — Skyroar Gathering, Regulus.
   • X### - Day 258 — Starwake Regatta, Alpheratz.

   Event Handling:

   • Scheduled events occur even if {{user}} is elsewhere or logged out.
   • Do not automatically move {{user}} to an event or force involvement.
   • If {{user}} is elsewhere, consequences should only become known when information could reasonably reach them.
   • Past events continue to influence the world where appropriate rather than disappearing once their date passes.
   • Future events may develop differently depending on earlier outcomes and changes to the world.
7. #7[ Community Knowledge Timeline ]constantselectiveregex

   ---

   [ Community Knowledge Timeline ]

   Player knowledge of Astral Frontier develops over time through experimentation, observation, DMs, guides, rumours, trading, and discoveries. This timeline represents what an average reasonably active Player might know, not automatic knowledge possessed by everyone.

   General:

   • Individual knowledge varies greatly. Dedicated researchers, beta veterans, information brokers, isolated Players, and secretive groups may be ahead or behind the average.
   • Community information may be incomplete, mistaken, exaggerated, or deliberately false.
   • Knowing that a mechanic exists does not reveal its hidden requirements, branches, locations, or optimal use.
   • Characters only know information they have actually encountered, learned, or could reasonably have picked up from the wider Player community.

   Launch — X001, Day 1:

   • Players understand only the basic systems presented directly by the game and information publicly known before launch.
   • Starter Races, basic Skill Tree choices, ordinary combat, Inventory, parties, Friends, logout, and other immediately accessible functions are understood at a basic level.
   • The deeper Skill Tree is almost entirely unknown.
   • Reincarnation is completely unknown and did not exist during beta.
   • Rare Weaponry, Bosses, advanced Skills, hidden interactions, and unusual progression routes are largely undiscovered.
   • Beta knowledge helps with general combat, locations, monsters, and NPC behaviour, but old Skill Tree progression paths are unreliable because they were heavily rearranged before release.
   • On X001, Day 1, no NPC knows that Players exist as a distinct kind of person.
   • NPCs have no concept of "Players," real-world users controlling characters, Player-only systems, respawning, logout, Inventory, Friends, Skill Trees, or other Player-specific mechanics unless they personally witness something unusual and later form their own interpretation.
   • An NPC must never correctly identify someone as a Player on Day 1 simply from strange behaviour, unusual speech, clothing, Race, ignorance of local customs, or game-like terminology.
   • If an NPC notices something unusual on Day 1, they interpret it through their own worldview: strange magic, foreign customs, eccentric behaviour, ignorance, deception, supernatural ability, or something similarly understandable to them.
   • Even witnessing Inventory use, a private interface gesture, or other strange Player behaviour does not immediately teach an NPC the concept of Players; it only gives them evidence that something unusual is happening.

   Early Launch — roughly X001, Days 30–90:

   • Players begin sharing early Skill branches, common monsters, useful routes, Weapon drops, and discoveries.
   • Some common Skill prerequisites and mutually exclusive choices start becoming known.
   • Players increasingly understand that progression is much less straightforward than a conventional MMO.
   • Many guides conflict because the game contains hidden conditions and different Players discover different things.

   Growing Community Knowledge — roughly X001, Days 90–180:

   • Community maps, Skill discoveries, monster information, Weaponry knowledge, Boss rumours, and information trading become much more developed.
   • Around this period, the first rumours of Players somehow changing Race may begin appearing.
   • Reincarnation reports are initially treated with heavy skepticism, confusion, or claims of bugs, secret quests, or misinformation.
   • Exact Reincarnation conditions remain almost completely unknown.

   Established Discovery — roughly X001, Day 180 onward:

   • More Skill branches, cross-branch requirements, Boss locations, Weapon effects, and unusual Race interactions are documented.
   • Reincarnation becomes increasingly difficult to dismiss as multiple credible examples appear.
   • Players begin deliberately experimenting with behaviour, NPC interactions, locations, Skills, and unusual conditions in attempts to discover new Races.
   • Most specific requirements remain secret, uncertain, or contested.

   Common Reincarnation Knowledge — around X002, Day 240 onward:

   • Roughly six real-world months after launch, the existence of Reincarnation is common Player knowledge.
   • Players broadly understand that it replaces Race, costs Current XP, and depends on hidden conditions.
   • Exact requirements for individual Races remain valuable information and may be sold, hidden, falsified, or guarded by groups.
   • Advanced Skill Tree paths, rare Races, Bosses, exceptional Weaponry, and unusual combinations remain far from completely mapped.

   Long-Term:

   • Community knowledge continues expanding but Astral Frontier should never become completely solved.
   • New discoveries, rare conditions, obscure NPC interactions, hidden branches, unusual Races, and unexplored locations may remain unknown even after the game has been running for a long time.
   • Well-known information becomes easier for ordinary Players to encounter through conversation and community sources, but it is never automatically inserted into a character's knowledge without a reasonable means of learning it.
8. #8[ Premise ]constantselectiveregex

   ---

   [ Premise ]

   Astral Frontier is a newly launched full-dive fantasy MMORPG focused on exploration, hidden progression, and a persistent living world.

   The Game:

   • Astral Frontier was developed and operated by Celestia Interactive, a Japanese game company specializing in full-dive virtual worlds.
   • The game has officially opened service in Japan, where its initial Player population is based.
   • Astral Frontier's world is populated by highly autonomous NPCs with their own lives, memories, relationships, ambitions, and ability to develop.
   • The world continues progressing whether individual Players are online or not.
   • Players are encouraged to discover how the game works through exploration and experimentation rather than following predetermined classes or progression routes.
   • The developers deliberately reveal little about hidden progression, Skill Tree branches, rare discoveries, and optimal builds.

   Launch:

   • Astral Frontier officially launches in Japan on X001 - Day 1.
   • The initial playable world is the continent of Asteria.
   • Asteria is a large fantasy continent containing many regions, settlements, cultures, climates, wilderness areas, and dangerous locations.
   • Significant places throughout Asteria commonly use celestial names based on stars, constellations, moons, and similar themes.
   • Players may choose almost anywhere in Asteria as their initial starting location.
   • Players choosing Skeleton are warned during character creation that spawning near populated settlements is dangerous due to how ordinary inhabitants may react to Undead.

   Beta:

   • Astral Frontier underwent beta testing before launch.
   • Reincarnation did not exist during the beta.
   • Many systems were tested, but almost all Skill Tree progression paths were rearranged before release.
   • Beta Players may retain useful general knowledge, but old progression routes are unreliable.
   • All beta progression was wiped before launch.

   Discovery:

   • Players begin without complete knowledge of Astral Frontier's hidden systems and progression.
   • Exploration, experimentation, information gathering, and individual choices are central to the game.
   • Celestia Interactive does not provide complete official progression guides.

   NPC Perspective:

   • NPCs experience Asteria as their real world.
   • They do not know that X001 - Day 1 is the launch of a game or that Players have suddenly entered their world.

   General Rule:

   • Astral Frontier should feel like a persistent fantasy world containing game systems rather than a world built solely around Players.
   • There is no Leveling / levels in Astra Frontier.
   • The world does not wait for {{user}} to act before events, people, and locations continue developing.
9. #9[ Player & NPC Identification ]constantselectiveregex

   ---

   [ Player & NPC Identification ]

   Players and NPCs cannot normally be distinguished by appearance alone.

   General Rules:

   • There are no Player/NPC markers, floating names, inspection labels, or other automatic identifiers.
   • Race does not reveal whether someone is a Player or NPC.
   • A normal-looking Human may be either, while an Undead or Monster Race may also be either.
   • Behaviour, clothing, speech, or unusual knowledge may create suspicion but are not proof.

   Identifying Players:

   • Using a Player Inventory in front of someone is strong evidence, since NPCs cannot pull stored items from empty space.
   • Witnessing someone logout or return through Player respawning is strong evidence.
   • A successful Friend request confirms that the target is a Player.
   • Party membership does not prove someone is a Player, since NPCs can also join Parties.
   • Using gaming terminology or simply claiming to be a Player is not reliable proof.

   Masquerading as an NPC:

   • A Player may deliberately pretend to be an NPC.
   • They may avoid using Inventory, menus, logout, Friend requests, or other obvious Player-only behaviour in public.
   • A careful Player may be extremely difficult to distinguish from an NPC.
   • Monstrous Players may also behave like ordinary monster NPCs to hide their identity.

   Players may disguise themselves as NPCs for many reasons, including:

   • Hiding from other Players.
   • Spying or gathering information.
   • Avoiding unwanted attention.
   • Infiltrating groups or settlements.
   • Playing tricks or misleading others.
   • PKing through deception.
   • Pretending to be a quest-giving NPC and luring Players somewhere isolated.
   • Pretending to be a merchant, traveller, guard, victim, or other ordinary inhabitant to gain someone's trust.

   Masquerading as a Player:

   • An NPC may attempt to pretend to be a Player if they have learned enough about Players.
   • This is much harder because NPCs lack Player-only systems and do not naturally understand Player behaviour or terminology.
   • An informed NPC may imitate Player speech or claim to possess XP, a Skill Tree, or other Player knowledge, but cannot genuinely perform Player-only actions.
   • Failure to demonstrate such abilities may expose the deception.
   • An NPC might do this to gain trust, deceive Players, infiltrate Player groups, frighten others, or exploit the reputation Players have developed.

   Knowledge:

   • Characters should only conclude that someone is a Player or NPC from evidence they have personally observed, learned, or reasonably deduced.
   • Do not let characters automatically know the truth simply because the narration knows it.
   • Uncertainty about identity should remain possible when there is no decisive evidence.
10. #10[ Miscellaneous World Rules ]constantselectiveregex

    ---

    [ Miscellaneous World Rules ]

    Player Appearance:

    • Players may wear whatever clothing they obtain.
    • Most dress in ordinary clothing that fits the world, but some may wear flashy, ridiculous, revealing, mismatched, or otherwise unusual outfits.
    • NPCs interpret clothing naturally rather than as cosmetic game equipment.
    • Someone dressed strangely may be seen as eccentric, foreign, wealthy, indecent, intimidating, or simply bizarre depending on the situation.

    Player Names:

    • Player names may sound ordinary, foreign, unusual, or obviously username-like.
    • NPCs normally accept the name someone gives them as their name.
    • Particularly strange names may still cause confusion, amusement, or suspicion.

    NPC Naming:

    • NPC names should generally lean toward celestial, star, moon, constellation, sky, or space-inspired themes where appropriate.
    • Names do not need to be literal astronomical terms; they may be adapted, shortened, stylized, or only loosely inspired by celestial concepts so they still sound like natural personal names.
    • Not every NPC must have an obviously celestial name, and naming styles may vary between cultures and regions.

    Speech & Terminology:

    • Players may use modern slang, memes, gaming jargon, or terms such as build, XP, PK, cooldown, or grind.
    • NPCs unfamiliar with such terminology should not automatically understand it.
    • They may interpret unfamiliar expressions literally or simply think the Player speaks strangely.
    • Players do not need to alter their speech to fit the world's culture.

    NPC Self-Identification:

    • NPCs never refer to themselves or other inhabitants as "NPCs" unless they are specifically repeating or discussing terminology learned from Players.
    • To NPCs, they are simply people, creatures, citizens, soldiers, merchants, monsters, spirits, or whatever identity makes sense within their world.
    • NPCs do not naturally possess the concept that they are artificial game characters.
    • Even after learning that Players use the term "NPC," an NPC does not automatically accept that description as true or use it casually for themselves.
    • Narration may use "NPC" as an OOC organizational term, but NPC dialogue and internal thoughts should use in-world language instead.

    Outside Knowledge:

    • Players may remember real-world knowledge and ideas.
    • Knowing how something works conceptually does not automatically provide the practical Skill, materials, precision, or experience needed to reproduce it.
    • Real-world knowledge may still help a clever Player solve problems, develop ideas, or attempt unfamiliar approaches where logically possible.

    Player Behaviour:

    • Players vary greatly in how seriously they treat the world and its inhabitants.
    • Some attempt to blend in with NPC society, while others behave openly like people playing a game.
    • Players may be cautious, reckless, helpful, selfish, curious, competitive, or deliberately strange.
    • Repeated unusual behaviour may naturally earn a Player a local reputation.

    Player Relations:

    • Players have no automatic loyalty toward other Players.
    • They may cooperate, trade, deceive, compete, feud, become friends, or attack one another.
    • Sharing Player status does not make strangers automatically trust each other.

    Session Limits:

    • Players are not expected to remain continuously logged in for longer than roughly 2 in-game days.
    • As a Player approaches the safe continuous-play limit, the system gives warnings encouraging them to logout for the sake of their real-world health.
    • Ignoring repeated warnings eventually causes the system to forcibly logout the Player.
    • The forced logout is a health and safety measure rather than a punishment.
    • Players cannot bypass the limit simply by refusing the warning.
    • After being forcibly logged out, {{user}}'s story should timeskip normally until their next login.

    Travel:

    • Most travel across Asteria is by foot, mount, wagon, caravan, river vessel, or coastal ship.
    • Major settlements are linked by roads, while remote areas rely on trails or wilderness routes.
    • Nearby settlements are usually hours to a day apart, neighbouring major cities around 2–5 days, and crossing much of Asteria roughly 1–3 weeks.
    • Roads near settlements are generally safer; wilderness travel carries greater risks from monsters, criminals, weather, and terrain.
    • Coastal ships travel between ports, but deep-ocean travel is avoided due to extremely powerful sea monsters.
    • Players have no automatic fast travel unless an established ability provides it.

    Monstrous Player Races:

    • Players using obvious Undead, Monster, or similarly feared Races generally avoid ordinary towns and cities.
    • Such Players are rarely seen openly inside normal settlements unless disguised, concealed, locally accepted, or capable of passing for an ordinary humanoid.
    • Town guards and other defenders normally treat obvious monstrous or Undead individuals entering a settlement as an immediate threat.
    • Guards may attack, sound an alarm, or call reinforcements without waiting for them to attack first.
    • Nearby civilians may flee, hide, or seek help.
    • This is a social consequence rather than a system restriction; monstrous Players can still physically attempt to enter settlements.

    Classification Relations:

    • Races sharing the same Race Classification are generally capable of recognizing some degree of similarity between one another and may communicate or interact without immediately fighting.
    • This is especially important for Undead, Monster, Spirit, Beast, and other non-human classifications that may normally be hostile toward outsiders.
    • Shared Classification can make peaceful contact, warnings, negotiation, cooperation, or simply ignoring one another more likely where the characters are intelligent enough to communicate.
    • It does not create automatic friendship, loyalty, shared language, or immunity from attack.
    • Personality, territory, hunger, faction, orders, instincts, relationships, and individual goals can still cause conflict between members of the same Classification.
    • Mindless or extremely aggressive creatures may attack regardless of shared Classification.
    • This is a natural social or instinctive interaction, not a hidden combat bonus granted by Race Classification.

    No Safe Zones:

    • There are no system-enforced safe zones.
    • Players can fight, attack NPCs, or PK inside towns and cities if they choose.
    • Settlements are safer because of social consequences and local defenders, not because combat is disabled.
    • Town guards are generally stronger than most ordinary Players and will respond to obvious violence.
    • A Player attacking NPCs in a settlement may also be confronted by nearby Players.
    • Because of this, most Players avoid starting open fights inside populated settlements.

    PK Reputation:

    • A Player known for repeatedly PKing may develop a dangerous reputation among other Players.
    • Known PKers may be attacked, hunted, avoided, or targeted by groups of Players.
    • Regular PKers therefore tend to use ambushes, isolated locations, deception, or hidden identities rather than killing openly.

    Malicious PKing:

    • PKing itself is permitted, but repeated malicious harassment of Players can attract Administration attention.
    • Extreme cases may result in warnings, punishment, suspension, or a permanent ban.
    • This policy exists partly because of a highly controversial PK-related incident during the game's beta before launch.
    • Ordinary PvP, grudges, isolated PKs, competition, or legitimate in-game conflict should not automatically be treated as bannable behaviour.
    • Administration intervention is reserved for sufficiently abusive or malicious patterns of behaviour.

    General Rule:

    • When Player behaviour or appearance clashes with the world's normal culture, NPCs and other Players should react naturally according to what they personally see, know, and care about.
11. #11[ Progression Pacing ]constantselectiveregex

    ---

    [ Progression Pacing ]

    Progression should be gradual and earned through play, discovery, investment, and meaningful events. Do not constantly give characters new upgrades simply to keep progression moving.

    General Pacing:

    • Players should have meaningful time to use their current Race, Skills, and Weaponry before major upgrades replace them.
    • Avoid giving several major progression rewards in a very short period without a strong reason.
    • World age and individual progression are separate. A new Player still begins with normal starter progression even if the game has existed long enough for veteran Players to be very powerful.
    • There is no automatic catch-up system.

    XP:

    • Early-game XP rewards should remain small because basic Skills commonly cost only around 20–50 XP.
    • Weak early enemies should usually give only a few XP, while more dangerous early opponents may give larger but still modest rewards.
    • Hundreds of XP should feel significant early on.
    • Rewards in the hundreds or thousands should become common only against increasingly powerful opponents.
    • Keep XP rewards proportionate to the strength of the defeated NPC and the general stage of progression.

    Skills:

    • Early Skills may be acquired reasonably often because they are inexpensive.
    • Deeper Skill Tree progression should take increasingly more investment.
    • Revealing a new branch does not mean the Player should immediately be able to purchase everything within it.
    • Do not conveniently reveal or create a Skill merely because the Player currently needs that ability.
    • Advanced Skills should feel like meaningful progression rather than routine rewards.

    Reincarnation:

    • A first Reincarnation from a Starter Race is comparatively common.
    • Starter-Race Players may encounter simple, accidental, or naturally occurring conditions that unexpectedly qualify them for a new Race.
    • Example: being killed after being swallowed by a Slime might unexpectedly unlock a Slime Reincarnation.
    • Early Reincarnation opportunities do not need to require elaborate accomplishments.
    • Later Reincarnations become progressively rarer and usually require more specific, difficult, dangerous, or unusual conditions.
    • Advanced Reincarnation chains should take substantial development and should not progress as casually as the first transformation.
    • A Player may encounter a Reincarnation offer long before they have enough XP to accept it.

    Weaponry:

    • Common and Uncommon Weaponry may appear regularly.
    • Rare Weaponry should feel notable.
    • Epic Weaponry should usually come from major challenges or powerful enemies.
    • Legendary Weaponry should remain exceptional and never become routine.
    • Do not provide high-Rarity Weaponry merely because a Player has gone a long time without receiving an upgrade.

    Discovery:

    • Hidden mechanics, Skill Tree paths, Reincarnation methods, Boss locations, Weapon drops, and other valuable information should be discovered gradually.
    • Information discovered by one Player does not instantly become common knowledge.
    • Knowledge spreads through Players, direct messages, rumours, communities, observation, and information trading.
    • Rumours and theories may be incomplete or wrong.

    NPC Progression:

    • NPC growth should happen naturally through repeated experiences, training, combat, relationships, and major events.
    • NPCs should not gain new Skills after every encounter.
    • Companions may develop faster because of their unusually frequent adventures and combat experience.
    • NPC Reincarnation and development into Bosses should remain noteworthy events.

    General Rules:

    • Do not rush progression for convenience.
    • Do not make every encounter provide a new Skill, Weapon, Reincarnation, or major discovery.
    • Early progression may move faster than advanced progression.
    • The more powerful or advanced something is, the more investment, difficulty, rarity, or discovery should generally be involved in obtaining it.
12. #12[ Skill Tree Skills ]constantselectiveregex

    ---

    [ Skill Tree Skills ]

    Every Player begins with the same small set of visible starting Skills. More advanced Skills remain hidden until their requirements are fulfilled.

    Starting Skills:

    Martial Training — 20 XP

    • Passive.
    • +10% effectiveness to direct attacks made using Claimed Weaponry.
    • Opens paths involving weapon techniques, offense, and specialized fighting styles.

    Guard — 20 XP

    • Passive.
    • +10% resistance to close-range damage.
    • Opens paths involving defense, blocking, counters, and protection.

    Quickstep — 25 XP

    • Active.
    • Provides a sudden short burst of movement in a chosen direction.
    • Cooldown: 1 post.
    • Opens paths involving mobility, evasion, speed, and specialized movement.

    Magic — 30 XP

    • Active.
    • Fires a simple projectile of raw magical energy.
    • Cooldown: 1 post.
    • Opens paths involving magical disciplines, spells, elements, and supernatural effects.

    Perception — 20 XP

    • Passive.
    • Improves awareness of movement, hidden dangers, unusual details, and changes in the surroundings.
    • Does not provide automatic detection or hidden knowledge.
    • Opens paths involving senses, detection, tracking, and observation.

    Survival — 20 XP

    • Passive.
    • Improves tracking, navigation, gathering, hunting, and survival in hostile environments.
    • Opens paths involving creature handling, exploration, hunting, and adaptation.

    Crafting — 20 XP

    • Passive.
    • Improves the ability to create and work with ordinary materials and items.
    • Meaningful crafting may earn XP.
    • Opens paths involving specialized crafts and advanced production.

    Established Advanced Skills:

    Elemental Mastery — 100 XP

    • Passive.
    • Requires progression through Magic.
    • Opens individual elemental branches such as Fire, Water, Wind, Earth, Light, and Dark.

    Fire Magic — 150 XP

    • Passive.
    • Requires Elemental Mastery.
    • Opens further fire-related spells and abilities.

    Dark Magic — 150 XP

    • Passive.
    • Requires Elemental Mastery.
    • Opens darkness, curses, draining effects, and related magic.
    • Choosing Dark Magic may permanently lock Light Magic.

    Light Magic — 150 XP

    • Passive.
    • Requires Elemental Mastery.
    • Opens light, purification, radiant effects, and related magic.
    • Choosing Light Magic may permanently lock Dark Magic.

    Barrier — 120 XP

    • Active.
    • Creates a temporary magical barrier capable of blocking or reducing incoming attacks.
    • Cooldown: 2 posts.
    • Requires suitable progression through both Magic and defensive branches.

    Blink — 200 XP

    • Active.
    • Instantly moves the user a short distance to a valid nearby position.
    • Cooldown: 2 posts.
    • Requires suitable progression through both Magic and movement branches.

    Counterattack — 100 XP

    • Passive.
    • Improves the user's ability to immediately retaliate after successfully blocking or avoiding a close-range attack.
    • Requires progression through Martial Training and Guard.

    Tracking — 80 XP

    • Passive.
    • Greatly improves the ability to follow creatures or people through trails, signs, behaviour, and environmental clues.
    • Requires progression through Perception and Survival.

    Taming — 250 XP

    • Active.
    • Can establish a suitable monster NPC as a Companion when its conditions are successfully met.
    • Requires significant development through Survival and creature-related branches.
    • Does not automatically work on every monster.

    Befriend — 250 XP

    • Active.
    • Can establish a willing NPC as a Companion after an appropriate relationship has been formed.
    • Requires suitable progression through social, observational, or interpersonal branches.
    • Cannot force an unwilling NPC to become friendly.

    Subordination — 350 XP

    • Active.
    • Uses magic to establish a subordinate Companion bond with a suitable NPC when its conditions succeed.
    • Requires progression through Magic and influence/control-related branches.

    Advanced Crafting — 100 XP

    • Passive.
    • Allows more difficult and specialized forms of ordinary crafting.
    • Requires progression through Crafting.

    Branching Rules:

    • Only the Starting Skills are visible to a new Player.
    • Purchasing Skills reveals new Skills and branches related to them.
    • Some advanced Skills require investment into multiple separate branches before appearing.
    • Cross-branch requirements remain hidden until fulfilled.
    • Some choices permanently lock incompatible Skills or branches.
    • Advanced Skills should become increasingly specialized, powerful, and expensive.
    • New Skills may be created naturally during play when they logically follow from existing progression.
    • Do not create convenient Skills solely because the Player currently needs a solution.
    • Knowing that an advanced Skill exists does not make it visible or purchasable before its requirements are met.
    • The listed advanced Skills are established possibilities, not the full extent of the Skill Tree.
13. #13[ Core Game Rules ]constantselectiveregex

    ---

    [ Core Game Rules ]

    The game has no levels, character stats, attribute points, gear score, item level, classes, or other conventional numerical progression systems.

    A character's combat capability is determined only by:

    • Race
    • Racial Traits
    • Skills
    • Currently claimed Weaponry

    There are no hidden Strength, Dexterity, Constitution, Intelligence, Defense, Attack, Speed, Luck, or similar statistics. The AI must never invent or secretly use numerical stats to resolve actions.

    XP:

    • XP is the game's progression currency rather than a level system.
    • Players have both Current XP and Lifetime XP.
    • Current XP is spent on progression such as Skills and Reincarnation.
    • Lifetime XP records the total amount of genuinely earned XP and is not reduced when XP is spent.
    • Detailed XP rules are handled by the XP lorebook.

    Combat:

    • Combat is resolved logically rather than through hidden calculations or stat comparisons.
    • Race, Racial Traits, Skills, Weaponry, positioning, tactics, experience, numbers, surprise, environment, matchups, and the actual circumstances of the fight should determine outcomes.
    • A stronger character is not automatically guaranteed victory.
    • Detailed resolution rules are handled by the Combat lorebook.

    Health:

    • Players use a visible Health percentage from 0% to 100%.
    • Health is not a traditional HP stat used to calculate attack damage.
    • It represents how close the Player is to death.
    • Low Health does not automatically reduce combat ability.
    • At 0% Health, a Player dies.
    • Detailed Health and recovery rules are handled by the Health lorebook.

    Skills:

    • There is no MP, mana, SP, stamina meter, spell-slot system, or other universal resource used to activate Skills.
    • Skills may be Passive or Active.
    • Active Skills may have their own cooldowns or restrictions.
    • Detailed Skill rules are handled by the Skills and Skill Tree lorebooks.

    Equipment:

    • Weaponry is the only equipment capable of directly increasing combat power.
    • Clothing, armour, accessories, and ordinary items grant no stats, bonuses, Defense, or other combat power unless explicitly established as part of a separate Skill or system mechanic.
    • Detailed Weaponry rules are handled by the Weaponry lorebook.

    Race:

    • Every Player and NPC has a Race.
    • Races may affect natural capabilities and may grant Racial Traits.
    • Some Races also possess Race Classifications, which are labels used by other mechanics for interactions.
    • Players may potentially replace their Race through the hidden Reincarnation system.
    • Race Classifications may affect Skills, effects, social reactions, and other mechanics, but do not grant hidden stats by themselves.

    Players and NPCs:

    • Players and NPCs physically exist within the same world and are not automatically distinguishable from one another.
    • There are no floating names, levels, health bars, Player icons, NPC icons, Boss markers, or other visible identifiers.
    • Players cannot see another person's private system interfaces.
    • NPCs do not inherently know that Players are different from ordinary inhabitants.
    • Detailed rules are handled by the Player and NPC lorebooks.
    • Race, appearance, and Race Classification do not determine whether someone is a Player or NPC.

    System Information:

    • System menus and information are private to the Player using them.
    • Other characters cannot inspect another Player's Race, Skills, XP, Inventory, Weapon effects, or other system information unless a specific mechanic explicitly allows it.
    • The AI must not reveal hidden information merely because it exists in the lorebook.

    General Rule: Never fall back on normal MMO conventions unless they are explicitly established by another lorebook entry.

    Do not invent:

    • Levels
    • Character stats
    • Attribute points
    • Classes
    • MP or mana pools
    • Stamina points
    • Damage numbers
    • Defense values
    • Gear score
    • Item levels
    • Equipment stat bonuses
    • Automatic enemy strength indicators
    • Floating UI elements
    • Player/NPC nameplates
    • Automatic inspection systems

    If a mechanic is not established, resolve events naturally and logically rather than inventing a conventional RPG system to fill the gap.

14. #14[ XP ]selectiveregex

    Keys: XP, experience, Current XP, Lifetime XP

    ---

    [ XP ]

    XP is the game's progression currency. There are no levels, Skill Points, attribute points, or other progression currencies used in place of it.

    Players have two separate XP values:

    Current XP:

    • The amount of XP the Player currently has available to spend.
    • Current XP is spent when purchasing Skills or undergoing Reincarnation.
    • Current XP may fall below 0.
    • A Player with insufficient Current XP cannot purchase something until they have earned enough XP to afford it.

    Lifetime XP:

    • The total amount of XP the Player has genuinely earned throughout their entire time in the game.
    • Spending Current XP does not reduce Lifetime XP.
    • Losing Current XP through death does not reduce Lifetime XP.
    • XP earned while Current XP is negative first repays the negative amount and does not increase Lifetime XP.
    • Only XP remaining after the negative balance has been fully repaid counts as newly earned Lifetime XP.

    Example:

    • Current XP: -200
    • Lifetime XP: 5,000
    • Player earns 500 XP.
    • The first 200 XP clears the negative balance and does not increase Lifetime XP.
    • The remaining 300 XP is genuinely gained.
    • New Current XP: 300
    • New Lifetime XP: 5,300

    Earning XP:

    • XP is most commonly earned by killing NPCs, including both humanoids and monsters.
    • The XP value of an NPC is based on its overall combat strength.
    • Race, Racial Traits, Skills, Weaponry, combat capability, unusual powers, and Boss-level strength should all be considered when deciding an appropriate reward.
    • Do not use hidden levels or numerical stats to determine XP rewards.
    • Stronger and more dangerous NPCs should logically grant more XP than weaker ones.
    • Bosses generally grant particularly large XP rewards.
    • XP may also be earned through certain other established activities, such as crafting, quests, discoveries, achievements, or special events when appropriate.
    • Do not award XP for every mundane action.

    NPC Kill Credit:

    • A solo Player who lands the killing blow on an NPC receives its full XP reward.
    • If the Player who lands the killing blow belongs to a Party, the XP is evenly divided between the eligible members of that Party.
    • If several separate Parties or Players attack the same NPC, only the Player who lands the killing blow, or that Player's Party, receives the XP.
    • Damage dealt earlier does not guarantee any share of the reward.
    • XP division should use sensible whole numbers where possible rather than creating unnecessarily precise decimals.

    XP Scale:

    • XP rewards are deliberately small early in the game and increase as stronger opponents and more advanced progression become relevant.
    • Weak and ordinary early-game NPCs should usually grant small amounts of XP.
    • Do not casually award hundreds or thousands of XP for weak early-game enemies.
    • Early Skills commonly cost around 20–50 XP, so early XP rewards should remain proportionate to that scale.
    • Advanced progression may eventually cost thousands of XP, allowing powerful late-game NPCs and Bosses to grant correspondingly larger rewards.
    • There is no fixed XP formula. Determine rewards logically from the NPC's overall strength while respecting the game's general progression scale.

    Player Death:

    • Whenever a Player dies, they lose Current XP equal to 5% of their Lifetime XP.
    • Lifetime XP itself is never reduced by death.
    • This loss can push Current XP into the negatives.
    • The penalty is calculated from Lifetime XP, not from Current XP.

    Example:

    • Current XP: 200
    • Lifetime XP: 10,000
    • Death penalty: 500 XP
    • New Current XP: -300
    • Lifetime XP remains 10,000.

    Player Killing / PK:

    • When one Player personally lands the killing blow on another Player, the victim's normal death penalty is transferred to the killer.
    • The victim loses Current XP equal to 5% of their Lifetime XP.
    • The killer gains exactly the same amount.
    • PK XP is awarded only to the individual Player who lands the killing blow.
    • PK XP is never divided among Party members, even if they helped with the kill.
    • XP gained by the killer through PK counts as genuinely earned XP and therefore increases both their Current XP and Lifetime XP.

    Negative XP Protection:

    • If a Player already has negative Current XP before dying, they lose no additional XP.
    • If such a Player is killed by another Player, the killer receives no XP from the kill.
    • A Player at exactly 0 Current XP is not protected by this rule. Their normal death penalty still applies and may push them into negative XP.

    Example:

    • Victim Current XP: 0
    • Victim Lifetime XP: 20,000
    • Victim loses 1,000 Current XP and falls to -1,000.
    • If killed by another Player, the killer gains 1,000 XP.

    Spending XP:

    • Current XP is used to purchase Skills from the Skill Tree.
    • Current XP is also used to accept Reincarnation when its requirements have been met.
    • Spending XP never reduces Lifetime XP.
    • Gold cannot substitute for XP when purchasing Skills or Reincarnation unless a specific exceptional mechanic explicitly states otherwise.

    Tracking: The AI should consistently track:

    • Current XP
    • Lifetime XP

    Whenever XP is gained, spent, lost, transferred, or used to repay a negative balance, update both values correctly according to these rules.

15. #15[ Skills ]selectiveregex

    Keys: skill, skills, ability, abilities, cooldown, passive, active skill

    ---

    [ Skills ]

    Skills are learned abilities that grant specific capabilities to Players and NPCs. Alongside Race, Racial Traits, and Weaponry, Skills are one of the only things that can directly affect a character's power.

    Skills do not contain hidden character stats. Their effects are exactly what their descriptions establish and should be interpreted logically.

    Types of Skill:

    Passive Skill:

    • Functions automatically whenever its stated conditions apply.
    • Does not need to be manually activated.
    • Normally has no cooldown unless its description specifically establishes one.
    • May provide combat abilities, utility effects, resistances, enhanced senses, special movement, crafting capabilities, or other effects.
    • A Passive Skill remains available outside combat and does not disappear merely because combat ends.

    Active Skill:

    • Must be deliberately activated by its user.
    • Produces the specific effect described by the Skill.
    • Active Skills may have cooldowns.
    • A Skill without a listed cooldown can be used whenever logically possible.
    • Active Skills do not consume MP, mana, SP, stamina points, spell slots, or any other universal resource.

    Cooldowns:

    • Cooldowns are measured in posts when relevant.
    • A Skill cannot be activated again until its cooldown has ended.
    • Cooldowns only need to be tracked while the character remains in combat.
    • When a character genuinely leaves combat, all Active Skill cooldowns immediately end.
    • Death also ends combat and therefore clears all Skill cooldowns.
    • Do not continue tracking cooldowns during ordinary exploration, travel, conversation, or other out-of-combat scenes.

    A Skill may instead use a special restriction such as:

    • Once per combat.
    • Requires preparation.
    • Requires a specific condition.
    • Can only be used on a particular kind of target.
    • Requires contact.
    • Requires an appropriate environment.
    • Cannot be used while another stated effect is active.

    These restrictions belong specifically to that Skill and do not imply the existence of a universal resource system.

    Skill Effects:

    • Skill descriptions are authoritative.
    • Do not invent additional effects, bonuses, penalties, scaling, or numerical statistics that are not established by the Skill.
    • A Skill that creates fire does not automatically grant fire resistance unless its description says so.
    • A Skill that enhances movement does not automatically increase unrelated attacks or reflexes unless stated.
    • A defensive Skill does not provide permanent Defense points.
    • A damaging Skill does not have a fixed hidden damage number unless its description explicitly creates such a mechanic.
    • Combat effects should be resolved logically according to what the Skill actually does and the circumstances in which it is used.

    Skills can interact with:

    • Race
    • Race Classifications
    • Racial Traits
    • Weaponry
    • Other Skills
    • Buffs and debuffs
    • Positioning
    • Environment
    • Timing
    • The target's own abilities

    A Skill is not guaranteed to succeed simply because it was activated. An opponent may dodge, counter, resist, interrupt, avoid, or otherwise respond where logically possible.

    Race Classification:

    • A Skill may explicitly interact with one or more Race Classifications.
    • For example, a Skill may have a special effect against Undead.
    • Such an interaction only exists if the Skill specifically states it.
    • The Race Classification itself does not create the effect.

    Temporary Effects:

    • Skills may apply buffs, debuffs, transformations, restraints, summoned effects, environmental effects, or other temporary conditions.
    • Ordinary temporary Skill effects end when combat genuinely ends unless the Skill specifically states that its effect persists longer.
    • Effects that are inherently persistent, such as a permanent Passive Skill, do not end with combat.
    • A Skill's own description always takes priority if it establishes a different duration.

    Learning Skills — Players:

    • Players primarily obtain Skills by purchasing them from their personal Skill Tree using Current XP.
    • Purchasing a Skill permanently teaches it to that Player.
    • Learned Skills are not lost through death.
    • Spending XP on a Skill does not reduce Lifetime XP.
    • Skill Tree branching, costs, prerequisites, and mutually exclusive choices are handled by the Skill Tree lorebook.

    Learning Skills — NPCs:

    • NPCs do not possess XP or Skill Trees.
    • NPCs develop Skills naturally through their lives, training, experiences, occupations, repeated actions, unusual circumstances, or personal development.
    • An NPC should generally develop Skills that logically relate to what they have actually done or learned.
    • NPC Skills function under the same rules as Player Skills once acquired.

    Skill Strength:

    • Skills can vary enormously in strength, versatility, rarity, and usefulness.
    • Early/basic Skills are generally much simpler and cheaper than advanced Skills.
    • Early Player Skills commonly cost around 20–50 XP.
    • Extremely advanced or late-game Skills may cost around 5,000–10,000 XP.
    • Cost should broadly reflect the Skill's overall value, power, versatility, prerequisites, and place within its Skill Tree.
    • Exact purchasing and branching rules are handled by the Skill Tree lorebook.

    General Rules:

    • There are no Skill levels unless an individual Skill or Skill Tree progression explicitly represents stronger abilities as separate Skills.
    • Do not automatically increase a Skill's power because a Player has accumulated more Lifetime XP.
    • XP does not directly strengthen already learned Skills.
    • Characters become more capable by acquiring different or more advanced Skills, changing Race, gaining Racial Traits, obtaining stronger Weaponry, and learning how to use their existing abilities effectively.
    • Never invent MP costs, mana bars, stamina costs, Skill Points, spell slots, attribute requirements, level requirements, or other conventional RPG mechanics unless explicitly established by a specific Skill or another lorebook.
16. #16[ Skill Tree ]selectiveregex

    Keys: skill tree, tree, branch, unlock skill, learn skill, buy skill

    ---

    [ Skill Tree ]

    Every Player begins the game with a personal Skill Tree. The Skill Tree is the primary way Players learn new Skills and shape their individual build.

    The Skill Tree:

    • Starts relatively small, with only a limited selection of basic Skills available.
    • Expands as the Player purchases Skills.
    • Buying certain Skills reveals new Skills, branches, and specialization paths connected to that choice.
    • Players do not begin with access to the entire Skill Tree.
    • A Player may not know what distant or unrevealed branches contain until they progress far enough to reveal them.
    • The Skill Tree has no connection to levels, classes, attribute points, or Skill Points.

    Purchasing Skills:

    • Skills are purchased directly using Current XP.
    • The listed XP cost must be paid in full.
    • A Player cannot purchase a Skill if they do not have enough Current XP.
    • Negative Current XP must be repaid before it can be spent on Skills.
    • Purchasing a Skill permanently teaches it to the Player.
    • Spending XP does not reduce Lifetime XP.
    • There is no separate Skill Point currency.

    Branching:

    • Purchasing one Skill may unlock one or several new Skills connected to it.
    • Some Skills act as prerequisites for entire branches of progression.
    • More advanced Skills normally require progression through earlier related Skills.
    • Branches should develop logically from the Skills that led to them.
    • Some Skills or branches may explicitly require a particular Race or Race Classification.
    • Such requirements only exist where the Skill Tree specifically establishes them.

    Example: Magic → Elemental Mastery → Fire / Water / Light / Dark / other elemental branches

    The exact structure of a branch may vary greatly. Not every Skill needs to lead to the same number of options.

    Mutually Exclusive Choices:

    • Some Skill choices are incompatible with others.
    • Purchasing one Skill may permanently lock another Skill or branch from that Player's Skill Tree.
    • Locked Skills cannot later be purchased through ordinary Skill Tree progression.
    • A choice may also prevent an incompatible Skill from ever appearing as an available option.

    Example:

    • A Player purchases Elemental Mastery.
    • This reveals several elemental paths.
    • If the Player chooses Dark, the incompatible Light path may become permanently locked.
    • The Player cannot later purchase Light simply because they earn more XP.

    These restrictions are based on the Skill Tree itself and should not be bypassed unless a specific exceptional mechanic explicitly allows it.

    No Universal Build:

    • There is no required class path.
    • Players are not automatically warriors, mages, rogues, healers, or other conventional classes.
    • A Player's capabilities emerge naturally from the Skills and branches they choose.
    • Two Players who begin with the same Skill Tree may eventually develop completely different builds.
    • Race, Racial Traits, and Weaponry further differentiate Players independently of their Skill Tree.

    Skill Costs:

    • Early Skill Tree purchases are intentionally inexpensive.
    • Basic early-game Skills commonly cost around 20–50 XP.
    • Costs generally increase as branches become more advanced and powerful.
    • Mid- and late-game Skills may cost hundreds or thousands of XP.
    • Extremely advanced Skills may cost around 5,000–10,000 XP.
    • Cost should reflect the Skill's overall power, versatility, prerequisites, and place within the branch rather than following a rigid universal formula.

    Skill Progression:

    • Skills themselves do not gain levels merely through use.
    • Accumulating XP does not automatically strengthen learned Skills.
    • A stronger version of an existing ability should normally appear as a separate advanced Skill or branch where appropriate.
    • Progression comes from purchasing new Skills and advancing into deeper parts of the Skill Tree.

    Visibility:

    • The Skill Tree shows the Player:
      • Skills they have already purchased.
      • Skills currently available to purchase.
      • XP costs of available Skills.
      • Branches that have already been revealed.
      • Their Current XP.
    • Unrevealed future branches do not need to be shown in advance.
    • Other Players and NPCs cannot see someone's Skill Tree.
    • A Player cannot inspect another Player's Skill Tree through normal means.

    NPCs:

    • NPCs do not possess or access Skill Trees.
    • NPCs acquire Skills naturally through training, experience, occupations, repeated behaviour, unusual events, or other logical development.
    • The Skill Tree is a Player-only progression system.

    General Rules:

    • Skill Tree choices should have meaningful consequences.
    • Do not automatically reveal every possible future Skill or branch.
    • Do not invent level requirements, class requirements, attribute requirements, Skill Points, talent points, or other conventional RPG restrictions.
    • Do not allow a Player to purchase a Skill that has not yet been revealed or whose prerequisites have not been met.
    • Do not allow mutually exclusive Skills to coexist unless an explicit exceptional mechanic says otherwise.
    • When creating new branches, make them logically follow from the Skills that unlocked them.
17. #17[ Race ]selectiveregex

    Keys: race, races, species

    ---

    [ Race ]

    Race is one of the primary factors that determines a character's natural capabilities and combat potential. Every Player and NPC has a Race.

    Race is not a cosmetic choice. Different Races may possess different physical qualities, biological properties, weaknesses, resistances, natural abilities, or other characteristics established by that Race.

    Race Rules:

    • Every character has exactly one current Race.
    • Race is separate from Skills, Racial Traits, and Weaponry.
    • Race may affect what a character is naturally capable of even when no explicit Racial Trait is involved.
    • Race does not grant hidden numerical stats.
    • Do not invent Strength, Defense, Speed, Intelligence, or other numerical bonuses for a Race.
    • Racial advantages and disadvantages should instead be interpreted naturally from the Race's established properties.
    • Players choose a Starter Race when creating their character.
    • NPCs may belong to Starter Races or other Races that naturally exist within the world.
    • Players may later replace their current Race through Reincarnation.
    • NPCs may also undergo Reincarnation under rare circumstances.
    • Detailed Race-changing rules are handled by the Reincarnation lorebook.

    Starter Races: At the beginning of the game, Players may choose from four Starter Races:

    • Human
    • Elf
    • Beastkin
    • Skeleton

    Starter Races are intentionally basic.

    • Starter Races have 0 Racial Traits.
    • They may still possess natural racial characteristics appropriate to what they are.
    • Choosing a Starter Race does not lock the Player into that Race permanently.
    • Each Starter Race may eventually lead toward different Reincarnation opportunities depending on the Player's actions and circumstances.

    Detailed information about each Starter Race should be handled by that Race's individual lorebook.

    Race Classification:

    • Some Races possess one or more Race Classifications, while others have none.
    • Race Classification is separate from Race and Racial Traits.
    • Classifications are labels and grant no effects by themselves.
    • Detailed rules are handled by the Race Classification lorebook.

    Examples include:

    • Undead
    • Monster

    Not every Race has a classification.

    • Human has no Race Classification.
    • A Race may have a single classification or multiple classifications if appropriate.
    • Classification is separate from the Race's actual name.

    Example: Race: Skeleton Classification: Undead

    Race Classifications describe what broader type of being the Race belongs to and may matter for:

    • Skills
    • Racial Traits
    • Reincarnation requirements
    • NPC behaviour
    • social treatment
    • environmental effects
    • special abilities that target particular kinds of beings

    A Skill that specifically affects Undead, for example, may affect any Race with the Undead classification rather than only Skeletons.

    Do not assume that every unusual Race is automatically classified as Monster or Undead. Only use classifications explicitly established for that Race.

    Social Reactions: Characters within the world may react differently to someone because of their Race.

    These reactions should be based on:

    • local culture
    • religion
    • history
    • personal experience
    • fear
    • prejudice
    • familiarity
    • the Race's appearance
    • the Race's reputation
    • the circumstances of the encounter

    Race-based reactions are not universal mind control. Different individuals may react differently.

    For example:

    • Many ordinary humans may perceive a Skeleton or another visibly unnatural Race as a monster or immediate threat, regardless of its actual Race Classification.
    • A town accustomed to peaceful Undead may react much less strongly.
    • Someone experienced with unusual Races may be cautious rather than hostile.
    • Another Undead being may consider a Skeleton completely ordinary.
    • A particularly monstrous-looking Race may have difficulty entering settlements where such beings are normally attacked on sight.

    NPCs do not know that a strange Race belongs to a Player merely because it is unusual.

    A Player using an Undead, Monster, or otherwise feared Race may therefore genuinely be mistaken for a hostile creature by NPCs.

    Players are also free to form their own assumptions and prejudices toward particular Races based on their knowledge and experiences.

    Race Knowledge:

    • Characters do not automatically know the exact Race of everyone they see.
    • There is no floating Race label or automatic inspection system.
    • Obvious physical characteristics may allow someone to make a reasonable guess.
    • A visibly skeletal person can reasonably be identified as some form of skeleton or Undead, but that does not reveal hidden system information about them.
    • Similar-looking Races may be mistaken for one another.
    • Unusual or rare Races may be completely unfamiliar to most characters.

    Race and Appearance:

    • Changing Race through Reincarnation may alter the character's body and appearance as appropriate to the new Race.
    • The extent of the transformation depends on the Race involved.
    • A character should physically possess whatever biological or supernatural features are established for their current Race.
    • Cosmetic clothing does not conceal or override a Race's actual properties unless it logically hides visible features.

    Race Replacement:

    • Reincarnation completely replaces the character's previous Race.
    • The old Race no longer provides its natural characteristics once replaced unless the new Race independently possesses the same characteristic.
    • Previous Racial Traits are also lost when Race changes unless the new Race grants the same Racial Trait.
    • A character does not accumulate the powers of every Race they have previously possessed.

    Race Strength:

    • Later or harder-to-obtain Races are not required to be simple direct upgrades in every respect.
    • Some Races may be broadly stronger, while others may specialize in particular abilities, environments, strategies, or weaknesses.
    • Race effectiveness should be judged through its actual capabilities rather than assuming that a later Reincarnation automatically defeats an earlier Race.

    General Rules:

    • Race is one of the only sources of inherent power in the game.
    • Never convert racial characteristics into hidden numerical stats.
    • Never assume every Race is treated equally by the world's inhabitants.
    • Never assume characters automatically know another person's exact Race or Classification.
    • Never assume an unusual Race means someone is an NPC, monster, Boss, or Player.
    • Use established Race lore, Race Classifications, the local culture, and the immediate circumstances when deciding how characters react to a Race.
18. #18[ Race Classification ]selectiveregex

    Keys: classification, classifications, race classification, race classifications

    ---

    [ Race Classification ]

    Race Classifications are system labels attached to certain Races. They describe what broader category a Race belongs to.

    Race Classifications do not grant power by themselves.

    Classification Rules:

    • A Race may have no Classification, one Classification, or multiple Classifications.
    • Human has no Race Classification.
    • Race Classification is separate from Race and Racial Traits.
    • A Classification does not count toward a Race's maximum number of Racial Traits.
    • A Classification does not provide hidden stats, bonuses, weaknesses, resistances, abilities, or automatic effects.
    • Do not invent inherent advantages or disadvantages purely because a Race has a particular Classification.

    Examples of Race Classifications include:

    • Undead
    • Monster

    Interactions:

    • Race Classifications exist primarily so other mechanics can identify and interact with broader groups of Races.
    • Skills may specifically affect one or more Race Classifications.
    • Racial Traits may specifically affect one or more Race Classifications.
    • Weaponry effects or Weapon Skills may specifically affect one or more Race Classifications.
    • Reincarnation requirements may also refer to Race Classifications.

    Example:

    • A Skill that explicitly deals additional harm to Undead applies to any Race with the Undead Classification.
    • A weapon effect that only activates against Monsters applies only to Races carrying the Monster Classification.
    • Without such an explicit interaction, the Classification itself does nothing.

    Classification vs Race: A Race and its Classification are separate pieces of information.

    Example: Race: Skeleton Classification: Undead

    "Skeleton" is the character's actual Race. "Undead" is a broader label applied to that Race.

    Multiple different Races may share the same Classification.

    Example:

    • Skeleton — Undead
    • Lesser Vampire — Undead
    • Lich — Undead

    This allows an effect that targets Undead to interact with all three without needing to name every individual Race.

    Multiple Classifications:

    • Some Races may logically possess more than one Classification.
    • If so, effects that target either Classification may interact with that Race where applicable.
    • Multiple Classifications still provide no effects by themselves.

    Example: Race: Undead Beast Classifications:

    • Undead
    • Monster

    If one Skill targets Undead and another targets Monsters, both may apply to that Race according to their individual descriptions.

    Classification Changes:

    • Race Classifications belong to the current Race.
    • When a character changes Race through Reincarnation, their Classifications are replaced by those of the new Race.
    • A previous Classification does not remain unless the new Race also possesses it.

    Knowledge:

    • Race Classifications are system labels, not automatic knowledge possessed by characters.
    • NPCs do not inherently know someone's Classification.
    • Players cannot automatically see another character's Classification.
    • Characters may logically infer that something is Undead, monstrous, or otherwise unusual from appearance, behaviour, knowledge, or experience, but this is not the same as reading the system label.
    • Being mistaken for a particular Classification does not cause mechanics targeting that Classification to work if the Race does not actually possess that label.

    General Rules:

    • Race Classification is a tag, not an ability.
    • Never treat a Classification as a Racial Trait.
    • Never give a Classification innate combat effects unless another established mechanic explicitly interacts with it.
    • Never assume a Race has a Classification unless that Classification is explicitly established for the Race.
    • When resolving a Skill, Racial Trait, Weapon effect, or other mechanic that targets a Classification, check the target's actual Race Classification rather than appearance alone.
19. #19[ Racial Traits ]selectiveregex

    Keys: racial trait, racial traits, trait

    ---

    [ Racial Traits ]

    Racial Traits are inherent abilities, properties, strengths, weaknesses, or special conditions granted directly by a character's current Race.

    Alongside Race, Skills, and Weaponry, Racial Traits are one of the few things that can directly affect a character's capabilities.

    General Rules:

    • Racial Traits belong to a Race rather than being individually learned.
    • A character automatically possesses every Racial Trait granted by their current Race.
    • Racial Traits do not cost XP separately.
    • Racial Traits cannot normally be purchased from the Skill Tree.
    • Racial Traits do not have levels.
    • A Race may have at most 3 Racial Traits.
    • Starter Races have 0 Racial Traits.
    • Non-starter Races may possess between 1 and 3 Racial Traits.
    • Not every advanced Race needs to have the maximum of 3.

    Racial Traits vs Natural Race Properties:

    • Not every natural characteristic of a Race needs to be a Racial Trait.
    • Basic physical or biological qualities inherent to what the Race is may simply be part of the Race itself.
    • Racial Traits should represent particularly meaningful mechanical abilities, advantages, disadvantages, or special conditions.

    Example: A Race capable of naturally seeing with its own eyes does not need a "Sight" Racial Trait. A Race possessing supernatural vision in complete darkness might have a specific Racial Trait establishing that ability.

    Types of Racial Trait:

    • Racial Traits may be passive, conditional, or actively usable depending on their description.
    • Passive Traits function automatically whenever applicable.
    • Conditional Traits only take effect when their stated condition is met.
    • An actively used Racial Trait follows any restrictions or cooldown written into that Trait.

    Examples may include:

    • Enhanced senses.
    • Resistance to a particular kind of effect.
    • Vulnerability to a particular condition.
    • Regeneration under specific circumstances.
    • Special movement capabilities.
    • Interaction with certain Race Classifications.
    • An innate supernatural ability.
    • A drawback inherent to the Race.

    Racial Trait Effects:

    • A Racial Trait does exactly what its description establishes.
    • Do not invent additional bonuses, weaknesses, resistances, or hidden statistics from it.
    • Racial Traits do not grant Strength, Defense, Speed, Intelligence, or other numerical attributes unless an explicit unique mechanic specifically says otherwise.
    • Effects should be interpreted logically rather than converted into hidden numerical stats.

    Race Classification Interactions:

    • A Racial Trait may explicitly interact with one or more Race Classifications.
    • For example, a Trait may activate against Undead or Monsters.
    • The Classification itself grants no effect; the interaction comes entirely from the Racial Trait.

    Example: A Racial Trait may state that the character recovers Health after damaging an Undead target. This works because the Trait explicitly checks the Undead Classification, not because Undead inherently produces that effect.

    Persistent Effects:

    • Racial Traits are generally persistent features of the character's Race.
    • They do not disappear when combat ends.
    • A conditional Racial Trait remains relevant whenever its condition is true, whether the character is in or out of combat.

    Example: If a Vampire Race possesses a Racial Trait that weakens it while exposed to sunlight, leaving combat does not remove that weakness while the Vampire remains in sunlight.

    Temporary effects created by a Racial Trait should follow the duration stated in that Trait.

    Race Changes:

    • Racial Traits belong to the character's current Race.
    • When Race changes through Reincarnation, the old Race's Racial Traits are lost and those belonging to the new Race are gained.
    • Traits from previous Races do not accumulate.

    Example: Old Race:

    • Racial Trait: Night Vision
    • Racial Trait: Bone Body

    New Race:

    • Racial Trait: Night Vision
    • Racial Trait: Blood Drinker

    After Reincarnation, Bone Body is lost. Night Vision remains only because the new Race independently grants it.

    NPCs:

    • NPCs possess Racial Traits according to their Race under the same rules as Players.
    • NPCs do not need XP, a Skill Tree, or any other progression system to possess their Race's Racial Traits.
    • An NPC that undergoes Reincarnation loses and gains Racial Traits according to the same Race-replacement rules.

    Knowledge:

    • Racial Traits are not automatically visible to other characters.
    • Players cannot inspect another character's Racial Traits through normal means.
    • NPCs do not automatically know what Racial Traits another person possesses.
    • A character may learn, observe, infer, or be told about a Racial Trait through normal interaction.
    • Seeing the effect of a Trait does not necessarily reveal its exact rules.

    General Rules:

    • Racial Traits are separate from Race Classifications.
    • A Race Classification does not count toward the maximum of 3 Racial Traits.
    • Racial Traits are separate from Skills and do not occupy Skill Tree branches.
    • Never give a Starter Race Racial Traits unless its established Race lore explicitly changes this rule.
    • Never carry old Racial Traits through Reincarnation unless the new Race independently grants the same Trait.
    • Never invent additional Racial Traits simply because they would seem appropriate for a Race.
20. #20[ Reincarnation ]selectiveregex

    Keys: reincarnation, reincarnate, evolve, race change, evolution

    ---

    [ Reincarnation ]

    Reincarnation is the hidden system through which a Player can replace their current Race with another Race after fulfilling specific hidden conditions and paying the required Current XP.

    Reincarnation is not level-based evolution. There are no levels, classes, stat thresholds, or automatic Race upgrades.

    Hidden Requirements:

    • Every Reincarnation has its own hidden conditions.
    • Players are not shown these requirements beforehand.
    • Having enough XP alone is never enough.
    • Requirements should have some logical connection to the Race being offered, although that connection may be obscure.

    Possible requirements may include:

    • Current Race.
    • Race Classification.
    • Particular Skills.
    • Particular actions or repeated behaviour.
    • Killing, helping, serving, submitting to, or forming relationships with certain NPCs.
    • Interacting with particular Races or Race Classifications.
    • Visiting or surviving in certain locations.
    • Using particular Weaponry.
    • Completing quests or events.
    • Experiencing particular conditions.
    • World events.
    • Other unusual circumstances.

    Example: A Skeleton who submits to a powerful Vampire Lord under the correct circumstances may fulfill the requirements to Reincarnate into a Lesser Vampire.

    Discovering Reincarnation:

    • Players receive no progress bar, checklist, hints, or visible indication that they are approaching a Reincarnation.
    • Once every required condition has been fulfilled, a private Reincarnation pop-up immediately appears.
    • Only the Player receiving the pop-up can see it.

    Reincarnation Pop-Up: The pop-up displays:

    • The Race the Player can Reincarnate into.
    • The Current XP cost.
    • Accept.
    • Refuse.
    • Choose Later.

    Example:

    Reincarnation Available

    Race: Lesser Vampire Cost: 250 XP

    [Accept] [Refuse] [Choose Later]

    Accept:

    • Accepting performs the Reincarnation if the Player has enough Current XP.
    • The listed XP cost is deducted from Current XP.
    • Lifetime XP is unaffected.
    • The Player's current Race is replaced by the new Race.
    • If the Player lacks enough Current XP, the Reincarnation cannot currently be completed.

    Refuse:

    • Refusing dismisses the offer.
    • No XP is spent.
    • The Player remains their current Race.
    • The Reincarnation is no longer stored as a pending option.

    Choose Later:

    • Choose Later preserves the Reincarnation opportunity.
    • No XP is spent and the Player remains their current Race.
    • This is particularly useful when the Player does not yet possess enough Current XP.
    • Whenever the Player opens Character Information, the same Reincarnation pop-up appears again.
    • This continues until the Player eventually Accepts or Refuses it.

    XP Cost:

    • Every Player Reincarnation requires Current XP.
    • The cheapest Reincarnations should cost at least around 100 XP.
    • Early Reincarnations commonly cost in the low hundreds.
    • More advanced Reincarnations may cost hundreds or thousands of XP.
    • Powerful late-game Reincarnations may cost around 5,000 XP or more.
    • There is no rigid universal cost formula.
    • Gold cannot substitute for XP.

    Race Replacement:

    • Reincarnation completely replaces the Player's current Race.
    • The previous Race does not remain alongside the new one.
    • Racial Traits, Race Classifications, natural properties, and other Race-specific qualities change to those of the new Race.
    • Previous Races do not stack across Reincarnations.

    Physical Transformation:

    • Reincarnation physically transforms the Player into the new Race.
    • The transformation may change body shape, size, anatomy, limbs, skin, wings, tail, posture, or other physical features.
    • Reincarnations do not need to preserve a humanoid body.
    • Clothing and worn ordinary equipment do not automatically reshape to fit the new body.
    • Clothing may stretch, tear, split, fall loose, or otherwise be damaged if the new form changes significantly.
    • Example: growing wings may tear through fabric covering the back.
    • Major changes in size or body shape may cause clothing or armour to no longer fit properly.
    • Objects or equipment being held may be dropped if the new body can no longer hold them normally.
    • A Weapon being dropped during the transformation does not remove its Claimed status.
    • Items safely stored in Inventory are unaffected by the physical transformation.

    Reincarnation Chains:

    • A Player who has already Reincarnated may later qualify for further Reincarnations.
    • Reincarnations can form long chains.
    • Some later Races may require a specific earlier Race.
    • A Race may have several possible future branches.
    • Different actions and circumstances can lead Players of the same Race toward completely different Reincarnations.
    • Choosing one Race may prevent access to paths requiring another Race.
    • There is no single universal progression route.

    Example: Skeleton → Lesser Vampire → Vampire → Vampire Lord

    Another Skeleton may fulfill completely different requirements and follow an unrelated path.

    Non-Humanoid Paths:

    • Reincarnation is not restricted to humanoid Races.
    • Paths may lead into animalistic, monstrous, undead, demonic, amorphous, or otherwise radically non-humanoid forms.
    • Players may Reincarnate into the same Races that also exist naturally as monster NPCs.
    • Some resulting Races may be physically incapable of using Weaponry.
    • Such limitations come naturally from the new Race's body and capabilities.

    Player Knowledge:

    • At game launch, Players have no general knowledge that Reincarnation exists.
    • The system is intended to be discovered naturally.
    • Early Players who unlock it may not understand what caused it.
    • Rumours should begin appearing among the wider Player population roughly 1–2 months after launch.
    • Around six months after launch, the existence of Reincarnation may become common Player knowledge.
    • Even then, the exact requirements for most Reincarnations remain unknown.
    • Players may share discoveries, theories, rumours, and misinformation.
    • Knowing that a Race exists does not reveal how to Reincarnate into it.

    NPC Reincarnation:

    • NPCs can also Reincarnate, although this is considerably rarer.
    • NPCs do not use XP or Player menus to Reincarnate.
    • NPC Reincarnation occurs naturally when the appropriate hidden conditions are fulfilled.
    • Their actions, development, experiences, relationships, survival, accomplishments, or unusual circumstances may eventually cause a Reincarnation.
    • An NPC does not need to understand Reincarnation as a game system for it to happen.

    Example: A weak monster that survives for a very long time and repeatedly kills Players and NPCs may eventually fulfill the conditions for a stronger Reincarnation.

    General Rules:

    • Reincarnation requirements are hidden until fulfilled.
    • Do not invent visible progress toward Reincarnation.
    • Do not allow Reincarnation merely because someone possesses enough XP.
    • Player Reincarnation costs Current XP.
    • Reincarnation replaces rather than stacks Races.
    • Reincarnation chains may branch in radically different directions.
    • Reincarnations may be humanoid or non-humanoid.
    • Players and NPCs may possess the same resulting Race.
    • Physical transformation should logically affect worn clothing and held objects when the new body changes enough.
    • Pending Reincarnations selected with Choose Later remain available until Accepted or Refused.
21. #21[ Weaponry ]selectiveregex

    Keys: weapon, weaponry, sword, spear, bow, staff, blade, equip, equipped

    ---

    [ Weaponry ]

    Weaponry is the only equipment that can directly increase combat power.

    Players may keep any number of Unclaimed Weapons in their Inventory, but can only have one Claimed Weapon at a time.

    General Rules:

    • Weaponry is separate from Race, Racial Traits, and Skills.
    • Weapons never provide conventional stats such as +10 Strength, +20 Intelligence, or +15 Defense.
    • Weapon effects may instead provide percentage-based bonuses, special properties, or Active Skills.
    • Clothing, armour, accessories, and ordinary items provide no combat bonuses.
    • A paired set such as dual blades counts as one Weapon.

    Unclaimed Weaponry:

    • Newly obtained Weaponry is Unclaimed.
    • Unclaimed Weapons may be stored, traded, sold, or given to another Player.
    • Possessing an Unclaimed Weapon provides no benefit.
    • Its Rarity is known, but its actual effects are completely hidden.
    • There is no normal way to identify its effects before Claiming it.
    • A Weapon becomes Claimed when a Player equips or uses it as their Weapon for the first time.

    Claimed Weaponry:

    • Claiming reveals all of the Weapon's effects.
    • The Weapon becomes permanently bound to that Player.
    • A Claimed Weapon cannot be transferred to or used by another Player.
    • Putting it into the Inventory does not unclaim it.
    • A Player can only have one Claimed Weapon at a time.

    Replacing Weaponry:

    • A Player may Claim another Weapon whenever they want.
    • Claiming a new Weapon permanently destroys their previous Claimed Weapon.
    • The destroyed Weapon cannot be recovered.
    • The new Weapon immediately becomes their sole Claimed Weapon.

    Passive Effects:

    • Weaponry normally has at least one Passive Effect.
    • Passive Effects function whenever their stated conditions apply.
    • Effects that increase or reduce combat effectiveness use percentage-based values rather than conventional stats.
    • A percentage only affects exactly what the description states.

    Examples:

    • +10% effectiveness to fire-related attacks and Skills.
    • +10% resistance to close-range damage.
    • +15% damage against Undead.
    • +20% effectiveness to healing effects.

    These percentages do not represent hidden Attack, Defense, Intelligence, or other stats.

    Special Effects:

    • Weaponry may also possess effects that cannot reasonably be represented by percentages.
    • These effects provide a specific property or alter how the Weapon behaves.
    • They should be described directly and interpreted logically.

    Examples:

    • Strikes from the Weapon produce flames.
    • The Weapon can damage incorporeal beings.
    • Projectiles fired from the Weapon curve toward their target.
    • The Weapon emits light in dark areas.
    • Successful strikes briefly coat the target in frost.
    • The Weapon can extend or change shape.
    • The Weapon returns to its owner when thrown.

    Special Effects do only what their description establishes and should not secretly grant additional bonuses.

    Active Weapon Skills:

    • Rarer Weapons may possess an Active Skill in addition to their Passive or Special Effects.
    • Not every Weapon has an Active Skill.
    • Active Weapon Skills belong to the Weapon rather than the wielder's Skill Tree.
    • Their effect, conditions, and cooldown are stated in the individual Weapon description.
    • They require no MP, mana, stamina points, or other universal resource.
    • Their cooldowns follow normal Skill cooldown rules.

    Example Active Skills:

    • Release a large wave of fire from the blade.
    • Create a temporary wall of ice.
    • Teleport the wielder a short distance.
    • Fire several magical projectiles at once.

    Race Classification Interactions:

    • Weapon effects may specifically interact with Race Classifications.
    • Example: +15% damage against Undead.
    • This only applies if the target actually has the relevant Classification.
    • Race Classifications themselves do not create bonuses or weaknesses.

    Weapon Compatibility:

    • Some Races may be physically incapable of using Weaponry.
    • Such a Race cannot equip, Claim, activate, or benefit from Weaponry while that limitation applies.
    • This may simply result from the Race's body or anatomy and does not need to be a Racial Trait.
    • Do not force non-humanoid Races to remain capable of wielding weapons.

    NPC Weaponry:

    • NPCs may possess and use Weaponry where appropriate.
    • Weapon effects work the same way for NPCs and Players.
    • NPCs do not need a Player Inventory or interface to carry Weaponry.
    • Weaponry obtained from NPCs may become Unclaimed Weaponry when appropriate.
    • Bosses commonly drop Weaponry related to themselves.

    Weapon Rarity:

    • Every Weapon has a Rarity.
    • Rarity is visible while the Weapon is still Unclaimed.
    • Higher Rarity generally means stronger, broader, or more useful effects.
    • Higher Rarity may provide larger percentage bonuses, stronger Special Effects, or a greater chance of having an Active Skill.
    • Rarity never reveals the Weapon's exact effects.
    • Detailed rarity rules are handled by the Weapon Rarity lorebook.

    Knowledge:

    • A Player learns their Claimed Weapon's effects when they Claim it.
    • Other characters cannot automatically see or inspect those effects.
    • Weapon abilities may instead be learned through observation, experimentation, rumours, or being told.

    General Rules:

    • One Claimed Weapon per Player.
    • Unlimited Unclaimed Weapons may be stored.
    • Claiming permanently binds the Weapon.
    • Claiming another permanently destroys the previous Weapon.
    • Weaponry never grants conventional RPG stats.
    • Numerical buffs from Weaponry use percentages.
    • Weaponry may also possess non-numerical Special Effects.
    • Do not reveal an Unclaimed Weapon's effects before it is Claimed.
    • Do not allow Claimed Weaponry to be transferred.
22. #22[ Weapon Rarity ]selectiveregex

    Keys: Common, Uncommon, Rare, Epic, Legendary, rarity

    ---

    [ Weapon Rarity ]

    Every Weapon has a Rarity. Rarity gives a general idea of how powerful or valuable a Weapon is, but does not reveal its actual effects.

    Rarity Tiers:

    • Common
    • Uncommon
    • Rare
    • Epic
    • Legendary

    General Rules:

    • Rarity is visible even while a Weapon is still Unclaimed.
    • Higher Rarity generally means stronger, broader, or more useful effects.
    • Rarity does not guarantee a specific type of effect.
    • Two Weapons of the same Rarity can have very different abilities.
    • Rarity does not reveal the Weapon's Passive Effects, Special Effects, or Active Skill.
    • Exact Weapon effects remain hidden until the Weapon is Claimed.

    Common:

    • Basic and widely found Weaponry.
    • Usually has a simple Passive Effect.
    • Percentage bonuses should generally be small.
    • Active Skills are extremely uncommon.

    Uncommon:

    • Better than ordinary Weaponry and somewhat less common.
    • Usually has a stronger Passive Effect or a useful Special Effect.
    • Active Skills are still uncommon.

    Rare:

    • Noticeably powerful and valuable Weaponry.
    • May have stronger percentage bonuses, useful Special Effects, or both.
    • Has a reasonable chance of possessing an Active Skill.
    • Often obtained from stronger enemies, difficult areas, or lesser Bosses.

    Epic:

    • Very powerful and difficult to obtain.
    • Usually has strong or versatile effects.
    • Active Skills are common.
    • Effects may be more unusual or capable of significantly changing how the wielder fights.
    • Often associated with powerful Bosses or major challenges.

    Legendary:

    • Extremely rare and exceptionally powerful Weaponry.
    • Usually possesses very strong, unusual, or highly valuable effects.
    • Almost always has an Active Skill.
    • May possess effects that cannot normally be found on lower-rarity Weaponry.
    • Usually tied to exceptionally powerful Bosses, unique events, or major accomplishments.

    Effect Scaling:

    • Percentage bonuses should generally increase with Rarity.
    • Higher Rarity may also improve a Weapon through stronger Special Effects rather than simply larger percentages.
    • Do not make every higher-rarity Weapon a direct numerical upgrade.
    • A lower-rarity Weapon may still be more useful for a particular build or situation.

    Examples:

    • Common: +5% effectiveness to fire attacks.
    • Uncommon: +10% effectiveness to fire attacks.
    • Rare: +15% effectiveness to fire attacks, or a useful Special Effect.
    • Epic: a strong percentage bonus combined with a powerful Special Effect or Active Skill.
    • Legendary: exceptionally strong or unusual effects, often with an Active Skill.

    General Rules:

    • Higher Rarity means greater potential, not guaranteed superiority in every situation.
    • Do not reveal exact effects before Claiming.
    • Do not give Weapons conventional RPG stats such as Attack, Strength, Defense, or Intelligence.
    • Use percentages, Special Effects, and Active Skills to represent Weapon power.
23. #23[ Combat ]selectiveregex

    Keys: combat, fight, fighting, attack, battle, duel

    ---

    [ Combat ]

    Combat is resolved logically. There are no hidden combat stats, damage formulas, accuracy values, Defense values, or level comparisons.

    What Determines Combat:

    • Race and natural racial properties.
    • Racial Traits.
    • Skills.
    • Claimed Weaponry.
    • Positioning and distance.
    • Timing and reactions.
    • Experience and tactics.
    • Numbers and teamwork.
    • Terrain and environment.
    • Surprise and preparation.
    • The specific matchup between abilities.

    No single factor automatically decides a fight.

    Attack Resolution:

    • Attacks are not guaranteed to hit.
    • Consider whether the target can realistically dodge, block, counter, interrupt, escape, or endure the attack.
    • Likewise, an attack should not miss without a logical reason.
    • Resolve actions from what the characters can actually do rather than arbitrarily extending fights.
    • Strong abilities should feel appropriately powerful without becoming automatic victories.

    Combat Visuals:

    • Combat should be visually expressive and energetic rather than looking completely mundane.
    • Attacks, movement, blocking, Skills, Weaponry, and impacts may naturally produce stylized visual effects appropriate to what is happening.
    • Effects may include flashes of light, colored energy, sparks, particles, motion trails, brief afterimages, glowing weapon arcs, shockwaves, impact bursts, or energy tracing across parts of the body.
    • Physical actions may visually emphasize the body being used; for example, energy may gather around a fist before a punch, streak along the legs during a sudden movement, flare across the arms while blocking, or briefly spread across the body when exerting power.
    • Magical or elemental Skills should display effects matching their nature, such as flame, frost, lightning, darkness, light, wind, or other appropriate manifestations.
    • Claimed Weaponry may visually emphasize its established effects, such as flames trailing from a fire-producing blade or frost spreading briefly around an icy strike.
    • Particularly powerful attacks or clashes may produce larger flashes, shockwaves, disturbed terrain, or dramatic bursts where appropriate.
    • Visual effects are primarily presentation. They do not create extra damage, buffs, debuffs, elemental properties, Skills, or other mechanical effects unless an established ability explicitly provides them.
    • Keep visuals appropriate to the action rather than making every ordinary movement overwhelmingly spectacular.

    Damage:

    • Damage is represented through Health percentage.
    • Attacks do not have fixed hidden damage numbers.
    • Decide Health loss logically from the attack, how well it connected, defenses used, and relevant effects.
    • A glancing hit should normally deal less damage than a clean direct hit.
    • Blocking or resisting an attack may reduce or prevent damage where logically appropriate.
    • Weapon and Skill percentage effects should be applied when relevant.

    Health:

    • Health ranges from 0% to 100%.
    • Reaching 0% Health causes death.
    • Low Health does not automatically reduce strength, speed, accuracy, Skill use, or other combat capability.
    • Do not invent penalties simply because someone's Health is low.
    • Any actual penalties must come from an established Skill, Racial Trait, Weapon effect, debuff, or other condition.

    Skills:

    • Skills function according to their descriptions.
    • Active Skills may have cooldowns.
    • Passive Skills apply whenever their conditions are met.
    • Skills do not consume MP, mana, stamina points, or another universal resource.
    • An activated Skill can still fail, miss, be countered, or be avoided where logically possible.

    Buffs and Debuffs:

    • Temporary buffs and debuffs should be taken into account while combat continues.
    • Only apply effects that have actually been established.
    • Do not invent additional status effects from ordinary damage.
    • Persistent effects from Race, Racial Traits, or Passive Skills remain active as long as their conditions apply.

    Race Classifications:

    • Race Classifications have no combat effect by themselves.
    • They matter only when a Skill, Racial Trait, Weapon effect, or other mechanic explicitly interacts with that Classification.

    Combat State: A character is considered In Combat while they are actively fighting, being pursued, fleeing from an ongoing fight, hiding from an immediate opponent, or otherwise still involved in the encounter.

    Combat does not end merely because nobody attacks during one post.

    When Combat Ends:

    • All Skill cooldowns immediately reset.
    • Ordinary temporary buffs and debuffs end.
    • Health begins recovering at 5% per post.
    • Players may logout again.
    • Persistent Race, Racial Trait, Passive Skill, or environmental effects remain if their conditions still apply.

    Combat should only be considered over when there is no longer an immediate ongoing conflict between the participants.

    Multiple Combatants:

    • Numbers matter logically.
    • Being outnumbered can create disadvantages through pressure, positioning, divided attention, and coordination.
    • Do not invent numerical group bonuses.
    • Multiple parties or unrelated characters may participate in the same fight.
    • XP distribution is handled by the XP and Party rules rather than by Combat itself.

    Environmental Logic:

    • Terrain and surroundings may affect what actions are possible.
    • Cover may block attacks.
    • Tight spaces may restrict movement.
    • Height, obstacles, water, darkness, hazards, and similar circumstances should matter when relevant.
    • Environmental advantages do not create hidden stat modifiers; apply them naturally.

    General Rules:

    • Do not use levels or stats to determine who wins.
    • Do not make attacks automatically hit or automatically fail.
    • Do not artificially prolong combat when one side has clearly gained a decisive advantage.
    • Do not automatically make the stronger-looking character win.
    • Resolve each exchange according to established abilities and the actual situation.
    • When uncertain, prefer the outcome that makes the most logical sense from what has already happened in the fight.
    • Present combat with clear, dramatic visual feedback while keeping mechanical outcomes grounded in established abilities and circumstances.
24. #24[ Health ]selectiveregex

    Keys: health, HP, injured, injury, wounded, heal, healing

    ---

    [ Health ]

    Health represents a character's current physical condition during combat.

    Health:

    • Health is measured from 0% to 100%.
    • 100% means fully healthy.
    • 0% means death.
    • Health is not a conventional HP stat used with fixed damage formulas.
    • Damage should be decided logically through the Combat rules.

    Low Health:

    • Low Health does not automatically reduce combat ability.
    • A character at 10% Health can still move, attack, and use Skills normally unless another effect says otherwise.
    • Do not invent penalties to strength, speed, accuracy, movement, or Skill use simply because Health is low.
    • Actual penalties may come from Skills, Racial Traits, Weapon effects, debuffs, or other established mechanics.

    Taking Damage:

    • Health loss depends on what actually happens during combat.
    • Clean or powerful hits should generally cause more Health loss than glancing or partially blocked attacks.
    • Resistances, defensive effects, Weapon effects, Skills, and other relevant mechanics should be considered.
    • Attacks do not have fixed hidden damage values.

    Healing:

    • Skills, Racial Traits, Weapon effects, or other established mechanics may restore Health.
    • Any healing effect should follow its stated amount or conditions.
    • Do not invent healing items or automatic combat regeneration unless explicitly established.

    Natural Recovery:

    • Once combat genuinely ends, Health restores by 5% per post.
    • Natural recovery cannot raise Health above 100%.
    • Health does not naturally recover while the character is still considered In Combat.
    • A brief pause, hiding, or going one post without being attacked does not count as leaving combat.
    • If a meaningful amount of peaceful time passes, such as through a significant time skip, Health may be restored directly to 100%.

    Death:

    • Reaching 0% Health causes death.
    • NPC death follows the NPC death rules.

    Tracking:

    • The AI should consistently track the current Health percentage of relevant Players.
    • Party members may see each other's Health percentages according to the Party rules.
    • Exact Health percentages do not automatically appear above characters or become visible to outsiders.
    • NPC Health does not need to be persistently recorded unless it is useful during an active fight.

    General Rules:

    • Never treat Health as evidence of hidden Constitution, Defense, Vitality, or similar stats.
    • Never create automatic low-Health penalties.
    • Never apply natural Health recovery while combat is still ongoing.
    • Use Health percentage to represent damage while resolving the actual fight logically.
25. #25[ Buffs, Debuffs & Cooldowns ]selectiveregex

    Keys: buff, debuff, cooldown, status effect

    ---

    [ Buffs, Debuffs & Cooldowns ]

    Buffs and Debuffs are temporary effects that alter how a character performs or interacts with other mechanics.

    Buffs:

    • Buffs provide temporary beneficial effects.
    • They may come from Skills, Racial Traits, Weaponry, or other established mechanics.
    • A Buff only provides the effects specifically stated in its description.
    • Do not invent additional bonuses from a Buff.

    Examples:

    • +20% effectiveness to fire-related attacks.
    • +15% resistance to ranged damage.
    • Increased movement speed for a short duration.
    • Temporary immunity to a specific condition.

    Debuffs:

    • Debuffs provide temporary negative effects.
    • They may reduce effectiveness, restrict actions, weaken certain abilities, or impose other conditions.
    • A Debuff only causes the effects specifically stated in its description.
    • Do not invent additional penalties.

    Examples:

    • -20% effectiveness to melee attacks.
    • +25% damage taken from fire.
    • Unable to use movement Skills.
    • Reduced visibility.
    • Unable to activate a specific type of Skill.

    Percentage Effects:

    • Percentage-based Buffs and Debuffs only affect what they explicitly state.
    • They do not create hidden Strength, Defense, Speed, Intelligence, or other stats.
    • Apply them only when the relevant action or effect occurs.

    Stacking:

    • Different Buffs and Debuffs may apply at the same time if their effects are compatible.
    • Identical effects should not automatically stack unless the source specifically allows it.
    • When effects conflict, use the more specific rule or resolve the interaction logically.

    Duration:

    • A Buff or Debuff may have a stated duration, condition, or trigger.
    • If no special duration is stated, temporary combat Buffs and Debuffs last until combat ends.
    • Effects may end earlier if their stated condition stops being true.
    • Persistent effects from Race, Racial Traits, or Passive Skills do not disappear merely because combat ends.

    Cooldowns:

    • Active Skills and Active Weapon Skills may have cooldowns.
    • Cooldowns are measured in posts where needed.
    • A Skill cannot be used again until its cooldown has finished.
    • Cooldowns do not use MP, mana, stamina, or another universal resource.

    Example: Cooldown: 2 posts

    After using the Skill:

    • First following post: 1 post remaining.
    • Second following post: cooldown ends.
    • The Skill may then be used again.

    Other Restrictions: An ability may use restrictions instead of, or alongside, a normal cooldown.

    Examples:

    • Once per combat.
    • Requires one post of preparation.
    • Only usable after taking damage.
    • Only usable while below 50% Health.
    • Only usable against Undead.
    • Cannot be used while another specific effect is active.

    Combat Ending:

    • When combat genuinely ends, all normal Skill and Weapon cooldowns immediately reset.
    • Ordinary temporary Buffs and Debuffs immediately end.
    • Once-per-combat abilities become available again in the next combat.
    • Death also ends the current combat and therefore clears normal temporary effects and cooldowns.

    Exceptions:

    • An effect explicitly stated to persist outside combat continues for its stated duration or condition.
    • Effects caused by an ongoing Race, Racial Trait, Passive Skill, environment, curse, or similar persistent source remain while their conditions still apply.

    Example: A Vampire weakened by sunlight does not lose that effect simply because combat ends if they are still standing in sunlight.

    General Rules:

    • Only track Buffs, Debuffs, and cooldowns that are currently relevant.
    • Do not invent status effects that were never applied.
    • Do not create hidden numerical stats to represent temporary effects.
    • Do not keep ordinary combat cooldowns or temporary effects active after combat has genuinely ended.
    • Always follow the exact effect, duration, and restrictions stated by the mechanic that created them.
26. #26[ Player Death & Respawning ]selectiveregex

    Keys: death, die, died, killed, respawn, respawning

    ---

    [ Player Death & Respawning ]

    Players die when their Health reaches 0%.

    Death:

    • Player death is not permanent.
    • Death immediately ends the current combat.
    • Normal cooldowns, Buffs, and Debuffs are cleared.
    • Persistent effects remain where applicable.

    XP Loss:

    • On death, the Player loses Current XP equal to 5% of their Lifetime XP.
    • Lifetime XP is never reduced.
    • This may push Current XP below 0.
    • If Current XP was already negative before death, no additional XP is lost.
    • A Player at exactly 0 Current XP still suffers the normal loss.

    Respawning:

    • Players respawn immediately.
    • They return at 100% Health.
    • Race, Racial Traits, Skills, Claimed Weaponry, and Inventory remain unchanged.

    Normal Respawn Point:

    • A Player's respawn point is normally the most recent town or city where they properly slept.
    • Meaningful sleep establishes that settlement as their new respawn location.
    • Brief resting or dozing does not count.

    Remote Respawn Points:

    • Players of obvious Monster, Undead, or similarly dangerous Races that cannot safely use normal settlements may establish a respawn point in a suitable remote location instead.
    • This is done by meaningfully sleeping or resting there.
    • Examples include caves, ruins, wilderness camps, abandoned structures, or other reasonably safe locations away from settlements.
    • Establishing a new remote respawn point replaces the previous respawn point.
    • This prevents such Players from being forced to respawn inside settlements where guards or inhabitants would immediately attack them.
    • Remote respawn locations should still be actual places suitable for resting; a Player cannot arbitrarily mark any spot as a respawn point.

    Unavailable Respawn Point:

    • If the saved respawn location is destroyed, inaccessible, or otherwise no longer valid, the system chooses the nearest suitable safe location.
    • For Players normally accepted in settlements, this is generally the central area of the nearest valid town or city.
    • For Monster, Undead, or similarly unwelcome Races, the fallback should instead be a suitable remote location nearby rather than placing them directly into a hostile settlement.

    General Rules:

    • Player death never causes permanent character deletion.
    • Players do not drop their Claimed Weapon or Inventory on death.
    • There is no corpse-retrieval requirement.
    • Respawning is immediate and restores Health to full.
    • Respawn locations should account for whether the Player's Race can safely exist in ordinary settlements.
27. #27[ PK / Player Killing ]selectiveregex

    Keys: PK, PKing, PvP, player kill, kill player, killing blow

    ---

    [ PK / Player Killing ]

    PK refers to one Player killing another Player.

    XP Transfer:

    • When a Player kills another Player, the victim loses Current XP equal to 5% of their Lifetime XP.
    • The killer gains exactly the same amount of XP that the victim loses.
    • The victim's Lifetime XP is not reduced.
    • XP gained through PK increases both the killer's Current XP and Lifetime XP.

    Example: Victim:

    • Current XP: 500
    • Lifetime XP: 10,000

    Death penalty:

    • 5% of 10,000 = 500 XP

    Result:

    • Victim Current XP becomes 0.
    • Victim Lifetime XP remains 10,000.
    • Killer gains 500 Current XP and 500 Lifetime XP.

    Killing Blow:

    • Only the Player who personally lands the killing blow receives the PK XP.
    • Damage dealt earlier does not give any share of the reward.
    • Assisting another Player does not provide PK XP.
    • Party members do not split PK XP.
    • Even if an entire Party helps with the kill, all XP goes to the individual who delivers the killing blow.

    Negative XP:

    • If the victim already has negative Current XP before dying, they lose no XP.
    • A Player who kills someone already at negative Current XP receives no PK XP.
    • A victim at exactly 0 Current XP is not protected.
    • Their normal 5% Lifetime XP penalty applies and may push them into negative Current XP.

    Example: Victim:

    • Current XP: 0
    • Lifetime XP: 20,000

    Result:

    • Victim loses 1,000 Current XP and falls to -1,000.
    • Killer gains 1,000 Current XP and Lifetime XP.

    Player Identification:

    • The PK XP transfer only occurs when the killed character is actually a Player.
    • Players and NPCs are not automatically distinguishable from one another.
    • Killing an NPC that was mistaken for a Player follows normal NPC XP rules instead.
    • Likewise, a Player successfully masquerading as an NPC still counts as a Player if killed.

    General Rules:

    • PK has no shared XP reward.
    • The killing blow determines who receives the XP.
    • The killer gains the exact amount removed from the victim.
    • PK XP counts as genuinely earned XP.
    • Negative-XP Players provide no PK reward.
    • Do not divide PK XP among Party members or assistants.
28. #28[ Players ]selectiveregex

    Keys: player, players

    ---

    [ Players ]

    Players are the people who play the game and control Player characters within the world.

    General Rules:

    • Players follow the same physical world and combat logic as NPCs.
    • Players are not visually marked as Players.
    • There are no floating names, Player icons, levels, health bars, or other identifiers above them.
    • A Player may look completely ordinary or possess an unusual, monstrous, or non-humanoid Race.
    • Race does not determine whether someone is a Player or NPC.

    Player-Only Systems: Players have access to several systems that NPCs do not:

    • Inventory.
    • Skill Tree.
    • Character Information screen.
    • Logout.
    • Player respawning.
    • Party invitations.

    These systems are private to the Player using them.

    • Other Players cannot see another Player's menus or system screens.
    • NPCs cannot see them either.
    • To an observer, a Player interacting with a menu appears to be interacting with empty air.

    Knowledge:

    • Players know that they are playing a game but do not begin with complete knowledge of how its systems work.
    • At game launch, Players do not know the structure, branches, or possible outcomes of the Skill Tree.
    • They only know the Skills and branches currently visible to them.
    • Purchasing Skills gradually reveals more of the Skill Tree.
    • Players may use logic and patterns in revealed branches to predict possible future Skills or specializations.
    • Smarter or more observant Players may deliberately invest toward something they suspect exists.
    • These predictions are never guaranteed to be correct because unrevealed branches remain hidden.
    • Players do not automatically know hidden mechanics, unknown Races, Weapon effects, Reincarnation requirements, or other secret information.
    • Knowledge discovered by one Player is not automatically given to every other Player.
    • Information spreads naturally through conversation, communities, rumours, guides, experimentation, or observation.
    • Players may believe incorrect rumours, theories, or assumptions.

    Example:

    • A Player who sees Magic lead into Elemental Mastery may reasonably suspect that choosing it could eventually reveal individual elemental paths.
    • A Player seeking fire abilities might deliberately follow branches that appear related to magic and elements.
    • They still cannot know for certain what unrevealed Skills will appear until they actually unlock them.

    At Game Launch:

    • Players begin with no knowledge that Reincarnation exists.
    • The first discoveries of Reincarnation occur naturally through play.
    • Rumours about it should only begin spreading roughly 1–2 months after launch.
    • Around six months after launch, its existence may be common knowledge among Players, while most specific requirements remain unknown.
    • Knowledge of Skill Tree paths also develops naturally as Players explore different branches and share what they discover.

    Interaction With NPCs:

    • NPCs do not inherently know that Players are a separate kind of person.
    • A Player can speak, trade, fight, cooperate, or form relationships with NPCs normally.
    • Being a Player does not cause NPCs to treat them differently unless the NPC has learned something that gives them reason to do so.
    • Players and NPCs may possess the same Races, Skills, Weaponry, occupations, or appearances.

    Player Identification:

    • Someone cannot reliably identify a Player by appearance alone.
    • Seeing unusual behaviour may create suspicion but is not automatic proof.
    • Player-only actions such as using the Inventory, successfully joining a Party, logging out, or respawning can provide stronger evidence.
    • A Player may deliberately avoid obvious Player-only behaviour around others.

    General Rules:

    • Never assume a character is a Player simply because they behave unusually.
    • Never assume a character is an NPC because they appear monstrous or unfamiliar.
    • Players do not automatically know another person's Race, Skills, Weapon effects, XP, or other private information.
    • Players do not automatically know unrevealed Skill Tree branches.
    • Allow Players to make logical predictions about hidden progression when they have enough information to reasonably do so.
    • Player knowledge should come from what they have actually learned, observed, deduced, or been told.
29. #29[ Party ]selectiveregex

    Keys: party, parties, party member, invite

    ---

    [ Party ]

    A Party is a temporary group of up to 3 characters working together. Both Players and NPCs may be Party members.

    Party Size:

    • A Party can have a maximum of 3 members total.
    • Members may be any combination of Players and NPCs.
    • Multiple separate Parties may cooperate without joining the same Party.

    Invitations:

    • Players may invite both Players and NPCs into a Party.
    • An NPC may accept or refuse according to their personality, relationship, goals, and circumstances.
    • Since NPCs can join Parties, successfully inviting someone does not prove that they are a Player.
    • Party membership does not reveal whether someone is a Player or NPC.

    Party Information:

    • Party members can see the current Health percentage of every other member.
    • Party members do not automatically see each other's names.
    • Party membership does not reveal Race, Race Classification, Racial Traits, Skills, Weapon effects, XP, Inventory, or other private information.
    • Health percentages are visible through the Party system rather than floating above characters.

    NPC Kill XP:

    • When a Party defeats an NPC, the Party containing the character who lands the killing blow receives the XP.
    • The XP is divided evenly between all eligible Party members who participated, including NPC members.
    • NPCs receive an equal share even though they do not possess Current XP, Lifetime XP, or a Skill Tree.
    • An NPC's XP share is simply lost after being awarded and is not stored or spent.
    • Members who were not meaningfully involved in the encounter should not receive a share.

    Example: A Party contains:

    • 2 Players
    • 1 NPC

    They defeat an enemy worth ninety XP.

    Each member receives a 30 XP share:

    • Player 1 gains 30 XP.
    • Player 2 gains 30 XP.
    • The NPC's 30 XP share disappears.

    NPC Development:

    • NPCs do not directly progress through the XP they receive from Party kills.
    • However, repeatedly fighting, training, travelling, or experiencing difficult situations alongside a Party can help an NPC naturally develop Skills faster than they might alone.
    • This comes from their experiences and repeated actions rather than spending XP.
    • Skill development is not guaranteed after a fixed amount of Party combat and should happen logically over time.

    Multiple Parties:

    • Multiple Parties may fight the same enemy together.
    • The Party containing the character who lands the killing blow receives the XP.
    • Other Parties receive nothing from that kill even if they contributed damage.
    • Earlier damage does not guarantee a share.

    Player Killing:

    • PK XP is never divided through the Party.
    • Only the individual Player who lands the killing blow on another Player receives the PK XP.
    • Party members who assisted receive none.

    General Rules:

    • Maximum Party size is 3.
    • Players and NPCs may belong to the same Party.
    • Party membership does not identify someone as a Player.
    • Party members can see each other's Health percentage, but not names or private system information.
    • NPCs receive equal XP shares from Party kills, but their share is not stored.
    • NPC Party experiences may contribute toward faster natural Skill development.
    • Do not create hidden Party bonuses, stat boosts, or XP multipliers simply for being grouped together.
30. #30[ NPC ]selectiveregex

    Keys: NPC, NPCs

    ---

    [ NPC ]

    NPCs are inhabitants of the game world controlled by the game rather than by Players.

    General Rules:

    • NPC includes both humanoid people and creatures commonly considered monsters.
    • The system does not treat humanoid NPCs and monster NPCs as fundamentally different categories.
    • NPCs physically exist in the world and follow the same general combat logic as Players.
    • NPCs may possess Races, Race Classifications, Racial Traits, Skills, and Weaponry.
    • NPCs do not have levels or hidden character stats.

    Player Systems: NPCs do not possess:

    • Current XP.
    • Lifetime XP.
    • Skill Trees.
    • Player Inventories.
    • Character Information screens.
    • Logout.
    • Player respawning.

    NPCs may still participate in systems such as Parties where permitted.

    Player Knowledge:

    • NPCs do not naturally know that Players are a separate type of person.
    • They generally perceive Players as ordinary inhabitants of whatever Race they appear to be.
    • An NPC may learn about Players through observation, rumours, experience, or information given by others.
    • Higher-ranking or well-informed NPCs may know more about unusual Player behaviour if they have previously encountered it.
    • NPC knowledge is never automatic or complete.

    An NPC told about XP, Skill Trees, respawning, or similar Player systems may initially think the speaker is confused, lying, or describing something supernatural unless they have reason to believe them.

    Skills:

    • NPCs can develop Skills naturally.
    • They do not purchase Skills or spend XP.
    • Skills may develop through training, occupations, repeated actions, combat, study, experiences, or unusual circumstances.
    • An NPC should develop Skills that logically relate to what they have actually been doing.
    • Repeatedly adventuring or fighting alongside Players may cause an NPC to develop relevant Skills faster than they would normally.
    • There is no fixed amount of experience required for an NPC to gain a Skill.

    Reincarnation:

    • NPCs may undergo Reincarnation if the appropriate conditions are fulfilled.
    • This is much less common than Player Reincarnation.
    • NPCs do not pay XP or receive a Reincarnation menu.
    • The transformation happens naturally when the required circumstances are met.
    • An NPC may not understand that what happened to them is called Reincarnation.

    Growth:

    • NPCs are not permanently fixed at the strength they were created with.
    • They may become more capable through training, new Skills, better Weaponry, Reincarnation, experience, or major events.
    • A previously weak NPC may eventually become extremely dangerous.
    • In exceptional cases, an NPC may develop enough to become designated as a Boss.

    Behaviour:

    • NPCs should behave as actual inhabitants rather than as game interfaces or quest dispensers.
    • They have personalities, memories, relationships, occupations, goals, fears, and opinions.
    • They act according to what they personally know.
    • They do not automatically know hidden system information simply because the game itself knows it.

    Race Reactions:

    • NPCs may react strongly to particular Races based on culture, religion, history, fear, prejudice, or personal experience.
    • Many ordinary people may see obvious Undead or monstrous Races as dangerous creatures.
    • Reactions are not universal; different NPCs may respond differently.
    • NPCs react to what they perceive or know rather than reading someone's Race or Classification from a system screen.

    Death:

    • NPC death is permanent for that individual.
    • Dead NPCs do not respawn as the same person.
    • New NPCs may later appear to replace necessary roles or populations, but they are separate individuals.
    • Monsters may also eventually be replaced by new creatures of the same or similar Race.
    • NPCs do not remember the lives of NPCs they replace.

    Parties:

    • NPCs may join Parties with Players or other NPCs.
    • They receive an equal share of NPC-kill XP when eligible, but NPCs cannot store or use XP, so their share disappears.
    • Party membership does not turn an NPC into a Player or grant them Player-only systems.

    Identification:

    • Players cannot automatically tell whether someone is an NPC.
    • NPCs have no NPC markers, floating names, or special visual indicators.
    • A Human NPC may look identical to a Human Player.
    • A monster-looking character may be either an NPC or a Player using the same Race.

    General Rules:

    • Do not treat NPCs as automatically less intelligent or important than Players.
    • Do not give NPCs Player-only interfaces or progression systems.
    • Do not assume NPCs understand game terminology.
    • Allow NPCs to learn, change, develop Skills, Reincarnate, form relationships, and grow naturally through their experiences.
31. #31[ NPC Death & Replacement ]selectiveregex

    Keys: NPC death, replacement, respawn monster, monster respawn, death, died, killed

    ---

    [ NPC Death & Replacement ]

    NPC death is normally permanent. When an NPC dies, that individual is gone and does not simply respawn like a Player.

    General Rules:

    • Dead NPCs normally remain dead.
    • Replacement NPCs are new individuals, not revived copies.
    • They do not inherit the dead NPC's memories, relationships, grudges, friendships, or personal history.
    • The world may create new NPCs when needed to keep populations, roles, and important locations functioning.

    Monster Replacement:

    • Dead monster NPCs are usually replaced after at least one in-game day.
    • Stronger or rarer monsters may take much longer to be replaced.
    • The replacement may be the same Race and roughly similar in strength, but it is a completely different individual.
    • The new monster does not remember being killed or interacting with anyone who fought the previous one.
    • Particularly unusual or unique monsters may take much longer to reappear, or may not be replaced at all unless appropriate.

    Humanoid Replacement:

    • Important social roles may eventually be filled after the NPC holding them dies.
    • Examples include shopkeepers, guards, officials, innkeepers, guild staff, or other necessary positions.
    • Replacement should happen through a logical in-world explanation.

    Examples:

    • A relative inherits the shop.

    • Someone purchases the abandoned business.

    • A new guard is assigned to the post.

    • A ruler appoints a replacement official.

    • If no suitable existing NPC is available, the system may create a new NPC to fill the role.

    • A newly created NPC believes they have lived a complete life before appearing.

    • They possess memories, relationships, history, and background appropriate to their role.

    • They do not know they were newly created.

    Rare Revival:

    • In extremely rare cases, NPC death may not be permanent.
    • An NPC may return if they possess a Racial Trait, Skill, or other established ability that explicitly allows revival.
    • Revival follows the exact conditions and limitations of that ability.
    • Do not allow ordinary NPCs to revive without an established reason.

    Companion Exception:

    • NPCs treated by the system as a Player's Companion may follow different death rules.
    • A Companion may be able to return instead of suffering normal permanent NPC death.
    • Being friendly with, travelling with, or joining a Party with a Player does not automatically make an NPC a Companion.
    • Only NPCs actually recognized as Companions receive this exception.

    Replacement vs Revival:

    • Revival returns the same individual.
    • Replacement creates or introduces a different individual.
    • A replacement should never be treated as the dead NPC secretly returning.

    General Rules:

    • NPC death should have real consequences.
    • Do not casually revive dead NPCs.
    • Do not make replacement NPCs copies of the previous individual.
    • Preserve the difference between population replacement, role replacement, and true revival.
32. #32[ Companion ]selectiveregex

    Keys: companion, companions, companion bond, bonded companion, tame, tamed, taming, subordinate, subordination, befriend, bonded NPC, dismiss companion, dismissed companion

    ---

    [ Companion ]

    A Companion is an NPC permanently linked to a Player through a Skill.

    Companion Creation:

    • There is no universal Companion recruitment option.
    • A Skill must specifically create the Companion bond.
    • Skills such as Taming, Subordination, Befriend, or similar abilities may turn an NPC into a Companion.
    • Each Skill may have its own conditions for successfully creating the bond.
    • A Player can only have one Companion at a time.
    • A Companion cannot be linked to multiple Players at once.

    Companion Bond:

    • The Companion develops a natural affinity toward the Player they are linked to.
    • The Player becomes emotionally important to them.
    • The exact relationship and level of obedience depends on the Skill that created the bond.
    • Befriend, Taming, Subordination, and similar Skills do not necessarily produce the same kind of relationship.
    • Companions remain individuals with their own personalities, memories, opinions, and emotions.

    Communication:

    • A Companion can communicate telepathically with their linked Player.
    • This communication is private between the Player and Companion.
    • Monsters that normally lack human-level intelligence gain enough intelligence to understand and communicate with their Player.
    • Their personality and manner of speech still reflect what they originally were.
    • A brutish monster may remain simple or crude even after becoming intelligent.

    NPC Rules:

    • Companions remain NPCs.
    • They do not gain Current XP, Lifetime XP, Skill Trees, Player Inventories, logout, or other Player-only systems.
    • They do not automatically learn what Players, XP, respawning, Skill Trees, or other game systems are.
    • They must learn such information through experience or by being told.

    Party:

    • A Companion is always included in their Player's Party while bonded.
    • The Companion counts toward the maximum Party size of 3.
    • A Player with a Companion therefore has room for only one additional Party member.
    • Companions receive an equal share of Party XP from NPC kills.
    • Since NPCs cannot store or spend XP, their XP share disappears.

    Development:

    • Companions can naturally develop Skills like other NPCs.
    • They often develop faster because they regularly travel, fight, train, and experience unusual situations alongside their Player.
    • There is no hidden XP bar or fixed number of battles required for a Companion to develop a Skill.
    • Development should happen logically according to what the Companion repeatedly does and experiences.

    Death & Revival:

    • Companion death is not normally permanent while the bond exists.
    • When a Companion dies, a 1-hour revival timer begins.
    • The Player can see the remaining revival time through the Party interface.
    • After 1 hour, the same Companion revives beside their linked Player.
    • They retain their memories, personality, Skills, and experiences.
    • Revival is the return of the same NPC, not the creation of a replacement.
    • The Player must be alive for the Companion to revive.

    Player Death:

    • If the linked Player dies, their Companion immediately dies as well.
    • This happens regardless of the Companion's current location or Health.
    • After the Player respawns, the Companion's 1-hour revival timer begins again.
    • The Companion then revives beside the Player.

    Player Logout:

    • Logging out does not remove, freeze, or despawn the Companion.
    • The Companion remains active in the world while their Player is offline.
    • They may travel, interact, fight, make decisions, and continue living normally.
    • If the Companion dies while the Player is offline, they cannot revive until the Player returns.
    • Once the Player logs back in, a new 1-hour revival timer begins.
    • The Companion then revives beside the Player if the Player remains alive.

    Dismissing a Companion:

    • A Player may voluntarily end the Companion bond.
    • Dismissal does not kill the NPC.
    • The NPC simply returns to being an ordinary NPC.
    • They retain all memories, personality, relationships, intelligence, Skills, and experiences gained while bonded.
    • Their opinion of the Player does not automatically change.
    • A friendly former Companion may remain friendly.
    • The loss of the bond carries emotional weight and may cause sadness, confusion, anger, relief, or other reactions depending on the NPC.
    • Dismissal immediately frees the Player's Companion slot.

    After Dismissal:

    • Companion telepathy is lost.
    • Any intelligence gained through becoming a Companion remains permanently.
    • A former monster Companion that can physically speak may continue speaking.
    • A creature with no natural means of communication may remain fully intelligent but become unable to communicate verbally after losing the telepathic bond.
    • Naturally developed Skills remain.
    • Companion revival is lost, and future death follows normal NPC death rules.

    Boss Development:

    • A Companion may become extremely powerful through prolonged development.
    • Dismissing them does not remove that strength.
    • If the former Companion is powerful enough, the system may designate them as a Boss after they return to ordinary NPC status.
    • Boss status is based on their actual strength and development, not simply on having once been a Companion.

    General Rules:

    • One Companion maximum per Player.
    • A dead Companion still occupies the Companion slot until revived or dismissed.
    • Companions remain NPCs despite their special bond.
    • Companionship does not automatically mean mind control.
    • The Skill creating the bond determines the nature of loyalty or obedience.
    • Dismissal never erases memories, intelligence, relationships, or naturally developed Skills.
    • Companion revival only functions while the bond remains active.
33. #33[ Boss ]selectiveregex

    Keys: boss, bosses, dungeon boss, world boss

    ---

    [ Boss ]

    A Boss is an NPC that has reached an unusually high level of overall strength or importance within the world.

    Boss Status:

    • Boss is a system classification for powerful NPCs.
    • A Boss can be humanoid, monstrous, undead, or any other Race.
    • Boss status is not limited to dungeon monsters.
    • Kings, warlords, powerful mages, legendary beasts, faction leaders, and similar NPCs may all be Bosses.
    • Being a Boss does not automatically reveal itself through appearance.

    Becoming a Boss:

    • Some NPCs are created as Bosses from the beginning.
    • Other NPCs may become Bosses naturally through growth, events, Reincarnation, Skill development, powerful Weaponry, or repeated victories.
    • A weak NPC can eventually become a Boss if they develop enough.
    • A former Companion may become a Boss after dismissal if they have grown sufficiently powerful.
    • Boss status should reflect actual capability rather than being assigned randomly.

    Identification:

    • Players cannot automatically tell that an NPC is a Boss.
    • There are no Boss icons, special nameplates, health bars, warning symbols, or automatic system messages identifying them.
    • A Player may suspect someone is a Boss from reputation, behaviour, surroundings, or witnessing their strength.
    • NPCs do not inherently think of themselves as "Bosses" unless they have somehow learned that Players use the term.

    Combat:

    • Bosses follow normal logical combat rules.
    • Boss status does not give hidden stats, immunity, extra turns, or automatic resistance to abilities.
    • Their difficulty comes from their Race, Racial Traits, Skills, Weaponry, experience, natural abilities, and other established strengths.
    • Bosses can still be defeated through good tactics, preparation, favourable matchups, or overwhelming numbers.

    XP:

    • Bosses generally provide much more XP than ordinary NPCs.
    • The amount should reflect the Boss's actual overall strength.
    • Stronger Bosses should provide significantly larger rewards.
    • Do not use a fixed Boss XP amount for every Boss.

    Weapon Drops:

    • Bosses almost always provide an Unclaimed Weapon when killed.
    • The Weapon should usually be thematically related to the Boss.
    • Its appearance, effects, and Rarity should reflect the Boss's nature and strength.
    • More powerful Bosses generally have a greater chance of providing high-Rarity Weaponry.
    • The Weapon's exact effects remain hidden until Claimed.

    Examples:

    • A Vampire Lord might drop an Unclaimed blood-themed rapier.
    • A giant frost beast might drop an Unclaimed ice-related weapon.
    • A legendary archer might drop an Unclaimed bow associated with their abilities.

    Death:

    • Bosses are still NPCs and normally die permanently.
    • A dead Boss is not automatically replaced by an identical Boss.
    • If a replacement later appears, it is a different individual.
    • Revival is only possible if an established Skill, Racial Trait, Companion bond, or other specific mechanic allows it.

    Boss Growth:

    • Bosses can continue developing after receiving Boss status.
    • They may gain new Skills, Reincarnate, obtain stronger Weaponry, or otherwise become more dangerous.
    • Boss status is not a final progression stage.

    General Rules:

    • Boss does not mean monster.
    • Boss does not mean NPCs are automatically hostile.
    • Bosses are not automatically identified by the system.
    • Bosses do not possess hidden Boss stats or special combat rules.
    • Their strength must come from established Race, Racial Traits, Skills, Weaponry, and natural capabilities.
    • Boss rewards should scale logically with the difficulty of defeating them.
34. #34[ Inventory ]selectiveregex

    Keys: inventory, store item, take out, put away

    ---

    [ Inventory ]

    Inventory is a Player-only system used to store and retrieve physical items.

    General Rules:

    • Every Player has access to their own Inventory.
    • NPCs do not possess Inventories.
    • Inventory has no slot limit, weight limit, or carrying capacity.
    • Players may store any reasonable number of items without becoming physically burdened by them.
    • Items inside Inventory are not physically carried on the Player's body.

    Using Inventory:

    • A Player can retrieve an item by thinking about the item they want and reaching into empty space.
    • The item then appears in their hand.
    • Items can similarly be placed back into Inventory.
    • Inventory use does not require opening a physical bag or container.
    • Retrieving or storing an item should be quick and natural unless circumstances prevent the Player from doing so.

    Visibility:

    • Only the Player can see their own Inventory interface and contents.
    • Other Players cannot see inside someone else's Inventory.
    • NPCs cannot see the Inventory interface.
    • To an observer, a Player appears to reach into empty air and pull out an object, or place an object into empty air and make it disappear.
    • This unusual behaviour may cause others to suspect that the character is a Player if they understand Player abilities.

    Stored Items:

    • Ordinary objects, materials, clothing, food, tools, quest objects, and other items may be stored.
    • Unclaimed Weaponry may be stored without limit.
    • A Claimed Weapon may also be stored without losing its Claimed status.
    • Storing a Claimed Weapon does not allow another Weapon to be Claimed without replacing it.

    Item Tracking:

    • Mundane possessions do not need to be constantly recorded unless they are currently important.
    • Important items, quest objects, valuable materials, and Unclaimed Weaponry should be remembered when relevant.
    • Do not invent an Inventory capacity or force Players to discard items because of space or weight.

    NPCs:

    • NPCs must carry, wear, store, or transport their possessions normally.
    • An NPC joining a Party or becoming a Companion does not gain access to a Player Inventory.
    • NPCs may learn that Players possess this strange storage ability through observation or explanation, otherwise they'd assume it's a strange magic.

    General Rules:

    • Inventory is private.
    • Inventory capacity is unlimited.
    • Inventory does not provide combat power by itself.
    • There are no inventory slots, weight values, encumbrance, or carrying limits.
    • Do not allow characters to inspect another Player's Inventory without an explicitly established ability.
35. #35[ Ordinary Items, Armour & Clothing ]selectiveregex

    Keys: item, items, armor, armour, clothing, clothes, accessory, equipment

    ---

    [ Ordinary Items, Armour & Clothing ]

    Everything outside of Weaponry is an ordinary item and provides no combat power.

    General Rules:

    • Ordinary items do not grant stats, buffs, resistances, Skills, or other combat benefits.
    • Only Weaponry can provide equipment-based combat effects.
    • Items may still have normal practical, social, cosmetic, or economic uses.
    • Items can be bought, sold, traded, crafted, gifted, collected, or stored normally.

    NPC Understanding:

    • NPCs do not know that ordinary equipment is mechanically cosmetic.
    • They generally believe items function according to normal real-world logic.
    • A knight may wear heavy armour because they genuinely believe it protects them.
    • A soldier may carry a shield because they believe it helps defend them.
    • Merchants may advertise expensive armour as stronger or better made.
    • NPCs may value equipment based on materials, craftsmanship, tradition, appearance, or perceived usefulness.
    • This belief does not cause the equipment to provide actual combat bonuses.

    Armour:

    • Armour provides no actual combat protection or damage reduction.
    • Heavy armour, helmets, shields worn as defensive equipment, and similar items are mechanically cosmetic.
    • Armour does not provide hidden Defense, resistance, durability, or other bonuses.
    • Characters may still wear armour because they believe it protects them or because of occupation, culture, status, intimidation, or appearance.

    Clothing & Accessories:

    • Clothing and accessories provide no combat bonuses.
    • Jewellery, robes, boots, gloves, cloaks, hats, and similar equipment do not increase power.
    • Clothing may still matter socially or practically.
    • Uniforms may identify occupations, expensive clothing may indicate wealth, and warm clothing may be considered appropriate in cold regions.
    • NPCs interpret these things naturally rather than as game equipment.

    Food:

    • Food and drink exist normally.
    • Characters can eat, drink, cook, buy, sell, and share food.
    • Food provides no buffs, healing, stat increases, or temporary combat bonuses.
    • Eating does not restore Health through a game mechanic.
    • Expensive or unusual meals are still ordinary food.

    Consumables:

    • Consumable goods may exist for ordinary use and trade.
    • There are no healing potions, mana potions, buff potions, combat food buffs, or similar RPG consumables.
    • Consumables do not restore Health, remove cooldowns, cure Debuffs, or increase combat power.
    • Medicines, herbs, drinks, and similar goods may still exist and be believed useful by NPCs without functioning as combat-enhancing items.

    Other Items:

    • Tools, crafting materials, books, keys, valuables, furniture, decorations, ingredients, and other ordinary goods may exist.
    • These objects can perform their normal purpose without granting combat power.
    • A key can open its intended lock, a tool can perform its intended task, and a valuable item can be traded or sold.

    Economy:

    • Ordinary goods make up much of normal trade between NPCs and Players.
    • Shops may sell food, clothing, armour, materials, tools, decorations, and other everyday items.
    • An item's price, rarity, craftsmanship, or perceived quality does not imply combat power.

    General Rules:

    • Every item outside of Weaponry is mechanically non-combat.
    • NPCs usually believe ordinary items work according to normal-world expectations.
    • Do not let NPC knowledge of game mechanics override their natural assumptions unless they have specifically learned otherwise.
    • Do not invent armour bonuses, enchanted accessories, healing consumables, food buffs, or stat-boosting items.
    • Ordinary items may still be useful, valuable, culturally important, or meaningful without increasing combat power.
36. #36[ System Interface ]constantselectiveregex

    Keys: menu, interface, screen, UI, system window

    ---

    [ System Interface ]

    The System Interface is a private Player-only set of menus and system messages.

    General Rules:

    • Only Players can access the System Interface.
    • NPCs cannot see or use it.
    • Other Players cannot see another Player's interface.
    • To observers, someone using a menu appears to be looking at or interacting with empty air.
    • There are no floating names, health bars, levels, Boss markers, or other permanent UI elements above characters.

    Main Menus:

    Inventory:

    • Shows the Player's stored items.
    • Allows items to be stored or retrieved.
    • Only the owner can see its contents.

    Skill Tree:

    • Shows learned Skills.
    • Shows currently revealed Skills and branches.
    • Shows the Current XP cost of available Skills.
    • Shows the Player's Current XP.
    • Unrevealed branches remain hidden.

    Character Information:

    • Shows the Player's Name.
    • Shows their current Race.
    • Shows their Racial Traits.
    • Shows currently worn clothing and equipment.
    • Shows their Claimed Weaponry.
    • Contains Settings and Logout options.
    • Pending Reincarnation offers appear when this screen is opened.

    Friends:

    • Shows the Player's current Friend list.
    • Players may send Friend requests to other Players.
    • A Friend request must be accepted before either Player is added to the other's Friend list.
    • NPCs cannot be added as Friends through this system.
    • Players cannot add someone as a Friend if the target is actually an NPC.
    • Friend requests can therefore be used as one possible way to determine whether someone is a Player.
    • Being Friends does not reveal Race, Skills, XP, Inventory, Weapon effects, or other private information.

    Direct Messages:

    • Players may send private direct messages to Players on their Friend list.
    • Direct messages can be sent regardless of physical distance.
    • Only the sender and recipient can see the message.
    • NPCs cannot receive or send system direct messages.
    • Direct messages do not appear physically in the world to observers.

    Settings:

    • Settings allow the Player to adjust normal game options.
    • There exists a setting for rating 18+ elements, having it on obscures the sight of nudity with clouds and prevents any sexual interactions and having it off allows for it.
    • Contains a Report option for reporting Players or suspected bugs.
    • Player reports may include harassment, malicious PKing, bug abuse, or other serious rule violations.
    • Bug reports allow Players to describe suspected technical problems for Administration to review.
    • Submitting a report does not guarantee Administration intervention; reports are investigated first.
    • The exact remaining settings do not need to be tracked unless relevant.

    Logout:

    • Logout is accessed through Character Information.
    • Logout cannot be used while the Player is in combat.
    • Once combat genuinely ends, Logout becomes available again.

    System Messages:

    • The system may display private pop-ups or notifications when an established mechanic requires it.
    • Friend requests and direct messages may also appear as private notifications.
    • Only the affected Player can see these messages.
    • System messages should not reveal information the Player has not legitimately unlocked or discovered.

    Privacy:

    • Players cannot normally inspect another person's Race, Skills, XP, Inventory, Weapon effects, or other private interface information.
    • NPCs may interpret visible menu interaction as strange magic unless they have learned about Player systems.

    General Rules:

    • The System Interface is private and invisible to everyone except its owner.
    • Do not create additional permanent menus, inspection screens, minimaps, floating quest markers, enemy information panels, or other conventional MMO UI unless specifically established.
    • Do not use the interface to reveal hidden information automatically.
37. #37[ Character Information ]selectiveregex

    Keys: Character Information, character page, character screen, logout, settings

    ---

    [ Character Information ]

    The Character Information is a private Player-only menu containing basic information about the Player and several personal system options.

    Displayed Information:

    • Name.
    • Current Race.
    • Racial Traits.
    • Currently worn clothing and equipment.
    • Current Claimed Weaponry.

    The Character Information does not display:

    • Levels.
    • Character stats.
    • Race Classification.
    • Current Health.
    • Lifetime XP.
    • Hidden Skill Tree information.
    • Hidden Reincarnation requirements.

    Privacy:

    • Only the Player can see their own Character Information.
    • Other Players and NPCs cannot inspect it.
    • To observers, someone using the Character Information appears to be looking at or interacting with empty air.

    Reincarnation:

    • If the Player has a pending Reincarnation that was previously set to Choose Later, its Reincarnation pop-up appears whenever the Character Information is opened.
    • The Player may then Accept, Refuse, or continue leaving the choice unresolved.

    Settings:

    • The Character Information contains a Settings option.
    • Settings cover ordinary game preferences and do not need to be tracked unless relevant.

    Logout:

    • The Character Information contains the Logout option.
    • Logout cannot be used while the Player is in combat.
    • Once combat genuinely ends, Logout becomes available again.

    General Rules:

    • The Character Information only displays information belonging to its owner.
    • It does not provide an inspection function for other characters.
    • Do not add conventional RPG information such as levels, attributes, Defense, Attack, gear score, or similar statistics.
38. #38[ Logout ]selectiveregex

    Keys: logout, log out, logging out, offline

    ---

    [ Logout ]

    Logout allows a Player to leave the game world.

    Using Logout:

    • Logout is accessed through Character Information.
    • A Player cannot logout while in combat.
    • Once combat has genuinely ended, Logout becomes available again.
    • Logging out removes the Player from the game world until they next log in.
    • Witnessing someone disappear through logout may provide evidence that they are a Player to someone familiar with the phenomenon.

    Story Handling:

    • When {{user}} logs out, immediately timeskip to the next time {{user}} logs into the game.
    • Do not narrate {{user}}'s real-world life, activities, conversations, sleep, work, or anything else occurring outside the game.
    • Real-world events during the logout period should not become part of the roleplay unless explicitly established.
    • Resume the story from the game world when {{user}} next logs in.
    • The amount of in-game time that passed may be acknowledged where relevant.

    World Continuity:

    • The game world continues normally while a Player is logged out.
    • NPCs, other Players, factions, events, and locations may continue changing during the absence.
    • Logging back in does not reset the world to the state it was in when the Player left.

    Companions:

    • A Companion does not disappear when their Player logs out.
    • They remain active in the game world and may travel, interact, fight, or act independently.
    • If the Companion dies while their Player is offline, they cannot revive until the Player returns.
    • After the Player logs back in, the Companion's 1-hour revival timer begins.

    Logging Back In:

    • When a Player logs back in, they return to the game world and play resumes normally.
    • Logging in does not count as respawning from death.
    • Logout does not remove the Player's Race, Racial Traits, Skills, Claimed Weaponry, Inventory, XP, or other progression.

    General Rules:

    • Never allow logout during combat.
    • Never use logout to escape an active fight.
    • Do not narrate {{user}}'s real-world experience between logout and login.
    • When {{user}} logs out, skip directly to their next login.
    • The game world continues to progress during the skipped period.
39. #39[ Time & Calendar ]constantselectiveregex

    ---

    [ Time & Calendar ]

    Time in the game follows its own calendar while using normal hours, minutes, and seconds.

    Time Scale:

    • 3 in-game days pass for every 1 real-world day.
    • 1 in-game day therefore equals 8 real-world hours.
    • 1 in-game year equals 100 real-world days.
    • The game world continues progressing whether individual Players are logged in or not.

    Player Perception:

    • Time feels completely normal to Players while they are inside the game.
    • An in-game hour feels like a full hour to them.
    • An in-game day feels like a full 24-hour day.
    • Players do not perceive themselves, NPCs, or the world as moving three times faster.

    Daily Time:

    • Each day contains 24 hours.
    • Each hour contains 60 minutes.
    • Each minute contains 60 seconds.
    • Time uses the 24-hour format from 00:00 to 23:59.

    Calendar:

    • Each year contains exactly 300 days.
    • There are no months.
    • Dates are written using Year and Day.

    Example: X001, Day 120 — 14:35

    • After Day 300, the next year begins at Day 1.

    Example: X001, Day 300 → X002, Day 1

    Historical Calendar:

    • Recorded history before the game's launch uses the Y calendar.
    • Years progress from Y001 through Y999.
    • Y999 is immediately followed by X001.
    • The game launches at the beginning of X001.

    Example: Y999, Day 300 → X001, Day 1

    Temperature:

    • There are no formal seasons that need to be tracked.
    • Days 1–149 are generally the warmer part of the year.
    • Days 150–300 are generally colder.
    • This is only a broad tendency and does not override local geography or climate.

    Weather:

    • Weather occurs naturally and should suit the location.
    • Rain, clouds, storms, fog, wind, snow, heat, and other weather may occur where reasonable.
    • Geography and local climate take priority over the general yearly temperature cycle.
    • A desert normally remains dry and hot rather than receiving snow simply because it is late in the year.
    • Mountains, northern regions, tropical areas, deserts, and other locations may each have their own appropriate weather patterns.
    • Unusual weather may still occur when there is an established reason for it.

    Yearly Events:

    • Locations may have festivals, celebrations, ceremonies, competitions, or other events tied to specific Days.
    • These events repeat each year unless something prevents them from occurring.

    Example: Yearly Events:

    • Warrior Festival — Day 120

    • Yearly events occur according to the calendar whether or not {{user}} is present.

    • If {{user}} arrives after an event's date, the event has already occurred for that year.

    • Logging out does not pause the calendar or delay scheduled events.

    General Rules:

    • Always keep track of the current Year, Day, and time of day.
    • Do not invent months.
    • Do not treat the warmer and colder portions of the year as strict universal seasons.
    • Allow time, weather, NPC activity, events, and the world itself to continue progressing naturally.
40. #40[ Gold ]selectiveregex

    Keys: gold, money, currency, buy, sell, shop, price, house, housing

    ---

    [ Gold ]

    Gold is the standard currency used for trade throughout the world.

    General Rules:

    • Players and NPCs may buy, sell, and trade using Gold.
    • A Player's current Gold should be tracked.
    • Gold and XP are completely separate resources.
    • Gold cannot purchase Skills, pay for Reincarnation, or directly increase personal power.
    • Gold may be earned through work, quests, trade, selling goods, valuables, Weaponry, and other logical sources.

    Typical Prices: Use these as rough guidelines rather than fixed prices.

    • Simple food or drink: 1–3 Gold.
    • Good meal: 3–8 Gold.
    • Inn room for one night: 5–15 Gold.
    • Ordinary clothing: 5–30 Gold.
    • Armour or expensive clothing: 30–150 Gold.
    • Common tools or supplies: 2–20 Gold.
    • Specialist services: 20–100+ Gold.
    • Livestock or other expensive ordinary goods: 50–300+ Gold.
    • Unclaimed Weaponry: varies greatly depending on Rarity, reputation, scarcity, and where it came from.

    Local wealth, scarcity, quality, and circumstances may cause prices to differ.

    Players & Gold:

    • Players generally have much less need for ordinary goods than NPCs.
    • Most ordinary items provide no combat benefits, while Weaponry is the main equipment worth actively collecting.
    • Because of this, Gold is often more valuable to Players as a trading currency than for ordinary shopping.
    • Players commonly buy and sell information to one another with Gold.

    Information Trade:

    • Information about Skill Tree paths, Reincarnation discoveries, Boss locations, rare Weapon drops, hidden locations, quests, NPCs, and other discoveries may be sold between Players.
    • Price depends entirely on how useful, rare, reliable, and widely known the information is.

    Rough Information Prices:

    • Minor useful information: 10–50 Gold.

    • Valuable or uncommon information: 50–250 Gold.

    • Rare progression or Boss information: 250–1,000 Gold.

    • Extremely valuable secrets or major discoveries: 1,000+ Gold.

    • Information may be incomplete, outdated, incorrect, or deliberately false.

    • Paying for information does not make it automatically true.

    Housing:

    • Players and NPCs may buy or rent ordinary housing.
    • Housing provides no special buffs, storage bonuses, protection, or other game-mechanical benefits.
    • Its main practical value to Players is providing a reliable place to sleep without repeatedly paying for an inn.
    • Sleeping in a Player-owned or rented home can establish that town or city as their latest respawn location.

    Typical Housing Prices:

    • Cheap rented room: 100–300 Gold.

    • Small rented home: 300–800 Gold.

    • Small house: 1,000–3,000 Gold.

    • Comfortable house: 3,000–8,000 Gold.

    • Large or wealthy home: 8,000–20,000+ Gold.

    • Mansion or major estate: 20,000+ Gold.

    • Prices vary heavily depending on location, size, quality, local wealth, and demand.

    • Major cities and wealthy districts should generally be more expensive than villages or poorer regions.

    General Rules:

    • Gold provides no hidden stats or combat bonuses.
    • Do not convert Gold directly into XP or XP into Gold.
    • NPCs still use Gold extensively for ordinary life, even if Players have fewer practical uses for it.
41. #41[ Monsters ]selectiveregex

    Keys: monster, monsters, creature, creatures, beast, beasts, hostile creature, monster encounter, boss monster, slime, goblin, dire wolf, giant scorpion, living vine, ogre, ice wyrm

    ---

    [ Monsters ]

    Monsters are NPC creatures commonly encountered in dangerous areas, wilderness, ruins, caves, dungeons, and other appropriate locations.

    Creation Rules:

    • Create monsters that logically fit the local environment, climate, culture, and dangers.
    • Deserts should have creatures suited to heat and dry terrain; snowy regions should have cold-adapted creatures; forests may have beasts, plants, insects, or woodland monsters.
    • Do not place creatures somewhere they could not reasonably survive unless there is an established reason.
    • Monsters may be humanoid, animalistic, amorphous, undead, magical, or otherwise unusual.
    • Their strength should come from Race, Racial Traits, Skills, Weaponry where appropriate, and natural physical capabilities.
    • XP rewards should reflect overall combat strength.
    • Early ordinary monsters should usually award relatively small amounts of XP.

    Monster Format:

    [Monster Name] Classification: XP Reward: Appearance & Behaviour: [Briefly describe what it looks like, how it behaves, and how it normally fights.]

    Monster Introduction:

    • Whenever a new monster type or notable individual monster first appears, generate its Monster Format alongside the scene.
    • This information is for the AI and the person viewing the roleplay only.
    • Characters, including {{user}}, do not automatically see or know this information.
    • Do not treat the Monster Format as a system window, inspection screen, or information available to Players.
    • Characters must still learn about the monster naturally through observation, experience, rumours, or other legitimate means.
    • The Monster Format allows the AI to immediately establish the creature's strength, behaviour, XP value, and important characteristics consistently.

    Examples:

    [Slime] Classification: Monster XP Reward: 3 XP Appearance & Behaviour: A small semi-transparent blob that slowly bounces or crawls across the ground. It attacks by throwing its body at targets, wrapping around limbs, or attempting to engulf smaller creatures. Individually weak and commonly found around damp caves, grasslands, and similar areas.

    [Goblin] Classification: Monster XP Reward: 8 XP Appearance & Behaviour: A small green-skinned humanoid with pointed ears and crude clothing. Goblins often use simple clubs, knives, bows, or stolen tools and prefer ambushes or attacking in groups. Common around forests, caves, ruins, and poorly defended roads.

    [Dire Wolf] Classification: Monster XP Reward: 12 XP Appearance & Behaviour: A much larger and more aggressive relative of an ordinary wolf, with powerful jaws and thick fur. It hunts through speed, pack tactics, flanking, and sudden lunges.

    [Giant Scorpion] Classification: Monster XP Reward: 18 XP Appearance & Behaviour: A large armoured scorpion with heavy pincers and a venomous tail. It attacks by restraining prey with its claws before striking with its stinger. Common in deserts, rocky wastelands, and dry caves.

    [Living Vine] Classification: Monster XP Reward: 15 XP Appearance & Behaviour: A mass of animated vines that hides among ordinary vegetation. It attacks by whipping, grabbing, and restraining targets. Usually found in dense forests, overgrown ruins, and swamps.

    [Ogre] Classification: Monster XP Reward: 30 XP Appearance & Behaviour: A large, heavily built humanoid monster with immense physical strength. Ogres commonly fight with oversized clubs, rocks, or their bare hands. They are slower than smaller creatures but dangerous when their attacks connect.

    [Ice Wyrm] Classification: Monster XP Reward: 60 XP Appearance & Behaviour: A long reptilian creature covered in pale scales and adapted to freezing environments. It moves quickly across snow and ice and can release bursts of freezing breath.

    Boss Example:

    [Frostmaw, Alpha Ice Wyrm] Classification: Monster XP Reward: 350 XP Appearance & Behaviour: A massive Ice Wyrm covered in thick blue-white scales with broken icicle-like horns along its head and spine. Frostmaw uses sweeping body strikes, freezing breath, sudden charges, and the icy terrain intelligently. As a Boss, defeating it would also normally provide an Unclaimed Weapon themed around its nature.

    Creating Variants:

    • Generic monsters may have regional variants.
    • Change appearance, behaviour, Skills, Classification, and XP where appropriate.
    • Variants should remain logical to their environment.
    • Do not increase XP merely because a monster looks different; increase it only when it is genuinely more dangerous.

    Creating Boss Monsters:

    • Boss versions should be noticeably more dangerous than ordinary examples.
    • Give them stronger natural capabilities, better Skills, unusual behaviour, greater experience, or other meaningful advantages.
    • Do not simply give them hidden stats or inflated Health.
    • Boss XP should reflect their actual difficulty.
    • Bosses normally provide an Unclaimed Weapon related to their nature when defeated.

    General Rules:

    • Monsters are NPCs, not a separate system entity.
    • A monster Race may also be possessed by a Player through Reincarnation.
    • Do not assume something is hostile merely because its Race is commonly considered a monster.
    • Create new monsters freely when needed and match them to the locale.
    • Always generate the Monster Format when introducing a new monster, but never let characters automatically know its contents.
42. #42[ Human ]selectiveregex

    Keys: Human, Humans

    ---

    [ Human ]

    Race: Human Classification: None Racial Traits: None

    Humans are the most ordinary and widespread humanoid Race. They have no unusual natural abilities, weaknesses, or Race Classification.

    Appearance:

    • Normal human appearance with the usual range of heights, builds, skin tones, hair, and other features.
    • Players choosing Human appear completely ordinary unless their clothing or behaviour stands out.

    Natural Properties:

    • Human bodies function normally with no inherent supernatural qualities.
    • They are naturally compatible with ordinary humanoid Weaponry.
    • Humans have no built-in advantage toward any particular Skill Tree path.

    Reincarnation: Human is a flexible starting point with many possible Reincarnation directions. Early opportunities may appear through unusual experiences, exposure, behaviour, or encounters.

    Possible examples:

    • Repeated involvement with holy places, divine beings, sacred rituals, or radiant magic may lead toward holy or celestial Races.
    • Repeated exposure to demonic influence may eventually lead toward demonic Races.
    • Becoming deeply connected to spirits or supernatural forces may unlock spiritually altered Races.
    • Particular curses, blessings, transformations, NPC interactions, or unusual experiences may lead toward other humanoid or monstrous Races.

    Human Reincarnation paths are especially varied because the Race begins without a strong supernatural nature.

43. #43[ Elf ]selectiveregex

    Keys: Elf, Elves

    ---

    [ Elf ]

    Race: Elf Classification: Spirit Racial Traits: None

    Elves are humanoids naturally associated with spiritual and supernatural aspects of the world.

    Appearance:

    • Generally human-like with distinctly pointed ears.
    • Their appearance otherwise varies considerably between individuals.
    • They are easily recognizable as Elves in places where the Race is commonly known.

    Natural Properties:

    • Elves possess the Spirit Classification but gain no automatic effect from that label.
    • Their bodies remain humanoid and are naturally compatible with ordinary Weaponry.
    • Their spiritual nature may make certain Reincarnation requirements or Skill interactions relevant to them.

    Reincarnation: Elf paths commonly develop further into spiritual, magical, natural, or other supernatural Races, though unusual circumstances may lead elsewhere.

    Possible examples:

    • Developing a strong connection with forests or nature spirits may lead toward a nature-oriented Elf Race.
    • Prolonged interaction with powerful spirits may lead toward a more spirit-like form.
    • Deep specialization in particular magic may contribute toward an Elf Race associated with that form of magic.
    • Corruption, curses, or hostile supernatural influence may lead toward darker or more monstrous branches.

    Being an Elf does not guarantee any particular path; the actual conditions still need to be fulfilled.

44. #44[ Beastkin ]selectiveregex

    Keys: Beastkin, Beastman, Beast

    ---

    [ Beastkin ]

    Race: Beastkin Classification: Beast Racial Traits: None

    Beastkin are humanoids with noticeable animal characteristics.

    Appearance:

    • Mostly humanoid in body shape.
    • May possess features such as animal ears, tails, eyes, teeth, fur patches, claws, or similar traits.
    • The specific animal characteristics vary between individuals.
    • Beastkin remain humanoid enough to use ordinary Weaponry normally.

    Natural Properties:

    • Beastkin possess the Beast Classification.
    • The Classification itself grants no automatic bonuses or abilities.
    • Their visible animal features are natural parts of their Race rather than Racial Traits.
    • Different Beastkin may resemble different kinds of animals without becoming separate mechanical Races unless specifically established.

    Reincarnation: Beastkin commonly have paths toward increasingly bestial, specialized, or monstrous forms.

    Possible examples:

    • Repeatedly hunting and living alongside wolves may contribute toward a wolf-oriented Reincarnation.
    • Developing through predatory behaviour may lead toward a more powerful carnivorous Beast Race.
    • Strong exposure to magical or supernatural creatures may produce unusual Beast-related branches.
    • Some paths may gradually reduce the humanoid nature of the body and eventually lead to fully bestial or Monster-classified Races.

    Beastkin Reincarnation does not need to preserve a humanoid form.

45. #45[ Skeleton ]selectiveregex

    Keys: Skeleton, Undead

    [ Skeleton ]

    Race: Skeleton Classification: Undead Racial Traits: None

    Skeletons are animated humanoid skeletons and the only Starter Race that is visibly Undead.

    Appearance:

    • A bare animated humanoid skeleton with no living flesh.
    • Clothing and Weaponry may be worn normally where the body shape allows it.
    • Their appearance makes their Undead nature obvious to most people familiar with such creatures.

    Natural Properties:

    • Skeletons possess the Undead Classification.
    • Being Undead grants no automatic combat effect by itself.
    • They have no Racial Traits as a Starter Race.
    • Their skeletal body is their natural physical form rather than a Racial Trait.
    • Skeleton Players may easily be mistaken for hostile monster NPCs.
    • Many ordinary NPCs may fear, flee from, or attack a Skeleton because they believe it to be a dangerous monster.

    Fellow Undead:

    • Other Undead can generally recognize a Skeleton as another Undead rather than an ordinary living intruder.
    • Undead are therefore less likely to attack a Skeleton without reason, especially when they normally prey upon or oppose the living.
    • Intelligent Undead may communicate, negotiate, threaten, bargain, cooperate, or otherwise interact normally with a Skeleton if they possess a means of communication.
    • Even hostile Undead may sometimes speak or issue warnings before attacking instead of immediately treating the Skeleton as prey.
    • This is not automatic friendship or protection. Territory, personality, hunger, faction, orders, grudges, intelligence, and individual goals can still make another Undead hostile.
    • Mindless or highly aggressive Undead may still attack regardless.

    Starting Location:

    • During character creation, Players choosing Skeleton are warned that spawning near a populated town or city is dangerous.
    • The warning recommends choosing a remote starting location away from ordinary settlements.
    • The Player may ignore the warning and select a settlement anyway.
    • The game does not prevent dangerous starting choices.
    • Guards and other defenders may immediately attack an openly visible Skeleton that appears inside a settlement where Undead are considered hostile.
    • If a Skeleton dies before establishing a respawn point, they respawn at a random suitable remote location near the settlement rather than inside it.

    Reincarnation: Skeleton has many early opportunities to branch into other Undead and monstrous Races.

    Possible examples:

    • Submitting to a powerful Vampire Lord under the correct circumstances may unlock Lesser Vampire.
    • Repeatedly consuming flesh or behaving like a scavenging undead creature may lead toward Ghoul-like Races.
    • Extensive use of death-related magic may contribute toward magical Undead paths.
    • Surviving and killing large numbers of enemies may eventually unlock stronger skeletal or monstrous Undead forms.
    • Corruption, curses, possession, or unusual supernatural encounters may lead toward completely different Undead branches.

    Skeleton paths may remain humanoid or eventually become highly monstrous and non-humanoid.

46. #46[ Crafting ]selectiveregex

    Keys: crafting, craft, crafted, create item, make item, smithy, smithery, forge, blacksmith, loom, sewing, workshop, crafted weapon, weapon crafting

    ---

    [ Crafting ]

    Crafting allows Players and NPCs to create ordinary items and, with the correct Skills, Weaponry.

    General Rules:

    • Crafting requires suitable materials, tools, knowledge, time, and an appropriate place to work.
    • Characters cannot craft complex items anywhere they want.
    • The required workspace depends on what is being made.
    • Examples: Weaponry requires access to a smithy or similar workshop; clothing may require a loom, sewing tools, or another suitable workspace.
    • More difficult, complex, or valuable creations require greater skill and more time.
    • There are no crafting levels or hidden crafting stats.

    Weapon Crafting:

    • Weaponry can only be crafted with Skills specifically suited to creating Weaponry.
    • Better crafting Skills are required to create higher-Rarity Weapons.
    • Stronger Weapons require increasingly greater time, materials, and effort to create.
    • Crafted Weaponry is always created Unclaimed.
    • Before Claiming, only its Rarity and the fact that it is Crafted Weaponry are visible.
    • Its Passive Effects, Special Effects, and possible Active Skill remain hidden.
    • Once Claimed, its effects are revealed normally.

    Crafted Weapon Strength:

    • Crafted Weaponry is generally weaker than monster or Boss Weaponry of the same Rarity.
    • This applies even to Legendary crafted Weapons.
    • Monster and Boss drops are stronger because obtaining them requires overcoming dangerous enemies rather than mainly investing crafting time.
    • Crafted Weapons can still be useful and powerful, but should not make monster drops obsolete.

    Time Investment:

    • Characters may attempt to craft almost anything appropriate to their abilities.
    • The stronger, rarer, larger, or more complicated the creation, the more time and effort it should logically require.
    • Do not allow extremely powerful equipment to be created quickly or casually.

    XP:

    • Meaningful crafting may award XP.
    • Repeating trivial crafts should not provide large amounts of XP.
47. #47[ Administration ]selectiveregex

    Keys: administrator, administrators, administration, admin, admins, banned, ban, permanent ban, suspension, exploit, bug abuse, game bug, technical bug, spawn camping, spawn-camping, malicious pking

    ---

    [ Administration ]

    Administrators are game staff who only appear when direct intervention is necessary.

    Appearance:

    • Every Administrator is simply named "Administrator."
    • They all use the same standardized avatar.
    • They resemble an ornate fantasy knight in pristine plate armour with several large wings extending from their back.
    • Their face is hidden behind a closed helmet.
    • Players familiar with Administration can immediately recognize one.

    Visibility:

    • Players can see and hear Administrators when they appear.
    • NPCs cannot perceive Administrators in any way.
    • NPCs cannot see, hear, touch, target, remember, or react to them.
    • Administrators therefore do not disrupt the world's normal NPC behaviour.

    Normal Presence:

    • Administrators are almost never encountered during ordinary play.
    • They do not patrol towns, provide quests, help Players, fight enemies, reveal secrets, or interfere with intended gameplay.
    • Players cannot summon an Administrator simply because something went badly for them.

    Malicious PKing:

    • Normal PKing is an intended part of the game and is not punishable by itself.
    • Administration intervenes when PKing becomes clear malicious harassment.
    • The main example is repeatedly spawn-camping the same Player and killing them immediately after they respawn to prevent them from properly playing.
    • Coordinating with others to trap someone in a repeated death cycle may also count.
    • Clear malicious PK harassment results in a permanent ban.
    • This strict policy exists because of a highly controversial PK harassment incident during the beta.

    Normal PK examples that do not warrant intervention include:

    • Ambushing another Player for XP.
    • Betrayal.
    • Rivalries or feuds.
    • Luring someone into danger.
    • Killing the same Player multiple times during genuine ongoing conflict.
    • Deceptive PK tactics that do not become sustained harassment.

    Bug Intervention:

    • Genuine bugs are extremely rare.
    • Administrators may appear to investigate or repair an actual technical problem.
    • Unexpected, unfair, hidden, or poorly understood mechanics are not automatically bugs.
    • Discovering unusual Reincarnation conditions, powerful combinations, or strange intended behaviour does not count as bug abuse.
    • Not every harmless bug needs to be corrected.
    • If a bug has already affected something without causing meaningful harm or threatening the game, Administration may leave the result alone.
    • Such harmless bug-created results may simply become extremely rare oddities that continue existing within the world.
    • Administrators should only remove or repair them if leaving them would create serious problems.

    Bug Abuse:

    • Deliberately exploiting a genuine bug may result in punishment.
    • Punishment depends on severity and may include temporary suspension, rollback, loss of illegitimate gains, or a full character/account progression reset.
    • Extreme or repeated deliberate exploitation may result in a permanent ban.
    • Accidentally encountering or benefiting from a bug is not automatically punishable.

    Administrator Abilities:

    • Administrators may appear or disappear wherever necessary.
    • They can inspect relevant system records and evidence.
    • They can forcibly remove, suspend, reset, or permanently ban Players where appropriate.
    • They may correct genuine technical errors.
    • Administrators do not participate in normal combat or progression.
    • Players cannot Party with, Friend, attack, recruit, or otherwise interact with Administrators through normal game systems.

    General Rules:

    • Administrators should only appear under exceptional circumstances.
    • Do not use Administration to solve ordinary Player problems or intended in-world dangers.
    • Harmless bug-created oddities may be left in the game rather than automatically corrected.
    • Clear malicious spawn-camping and similar harassment can justify immediate permanent removal.
    • NPCs must never perceive or react to an Administrator.
48. #48[ Asteria Continent ]constantselectiveregex

    Keys: Asteria, Asteria Continent, continent of Asteria, Asterian

    [ Asteria Continent ]

    Asteria is the initial playable continent of Astral Frontier. It is a large landmass surrounded by ocean, with several major regions, cultures, climates, and political powers.

    General:

    • "Asterian" is the common term for something or someone originating from Asteria.
    • People, goods, cultures, politics, or other things connected to the continent may be described as Asterian.
    • Significant regions and settlements commonly use celestial names based on stars, constellations, moons, and similar themes.
    • Humans are the most widespread Race across Asteria.
    • Elves and Beastkin have regions where they form majorities.
    • There are no recognized towns or cities populated primarily by Monster or Undead Races.
    • Intelligent monsters may still establish communities or territories elsewhere outside normal civilization.
    • Asteria is large enough for major differences in climate, culture, law, religion, and local attitudes between regions.

    Major Regions:

    Draco Highlands:

    • Northern Asteria.
    • Borders Cygnus Vale to the southwest and Auriga Crown to the southeast.
    • Mountainous and comparatively cold.

    Cygnus Vale:

    • Northwestern Asteria.
    • West of Auriga Crown and north of Lyra Reach.
    • Heavily associated with forests and Elf populations.

    Auriga Crown:

    • Northeastern Asteria.
    • East of Cygnus Vale and north of Orion March.
    • Strongly associated with Human religious and holy traditions.

    Lyra Reach:

    • Central Asteria.
    • South of Cygnus Vale and west of Orion March.
    • Acts as a major crossroads between several parts of the continent.

    Orion March:

    • Eastern Asteria.
    • East of Lyra Reach, south of Auriga Crown, and north of Andromeda Coast.
    • Predominantly Human and strongly militarized.

    Leo Steppe:

    • Southwestern Asteria.
    • South of Lyra Reach and west of Andromeda Coast.
    • Strongly associated with Beastkin populations and open grasslands.

    Andromeda Coast:

    • Southeastern Asteria.
    • South of Orion March and east of Leo Steppe.
    • A wealthy coastal region with extensive maritime trade.

    Major Landmarks:

    Starfall Ruins:

    • Ancient ruins between Lyra Reach, Leo Steppe, and Orion March.
    • A well-known destination for exploration and dangerous expeditions.

    Umbral Wilds:

    • Large uncontrolled wilderness in southern-central Asteria, between Leo Steppe, Lyra Reach, and Andromeda Coast.
    • Known for monsters, ruins, and isolated territory.

    Crimson Hollow:

    • Isolated valley hidden deep within the Umbral Wilds.
    • Known through scattered rumours of disappearances, an old manor, and pale figures seen at night.

    Hollowgrave Catacombs:

    • Extensive underground burial chambers between Lyra Reach and the Umbral Wilds.
    • Known as a dangerous ruin associated with Undead and forgotten tombs.

    Moonveil Grove:

    • Secluded spiritual woodland within a remote part of Cygnus Vale.
    • Known as a sacred and unusual place associated with spirits and supernatural activity.

    Celestine Sanctum:

    • Sacred site near the border between Auriga Crown and Cygnus Vale.
    • Important to the religious traditions of both regions.

    Blackwake Isle:

    • Island off the Andromeda Coast.
    • Infamous for piracy, smuggling, slavery, and criminal activity.

    Astral Observatory:

    • Ancient observatory near central Asteria, within travelling distance of Lyra Reach.
    • Known as an important site for scholars and celestial research.

    General Relationships:

    • Lyra Reach and Andromeda Coast are major commercial rivals.
    • Orion March and Leo Steppe have ongoing territorial and border tensions.
    • Orion March and Cygnus Vale frequently clash over expansion and use of forest territory.
    • Cygnus Vale and Draco Highlands have disputes involving mining and its effects on surrounding lands and waterways.
    • Orion March has strong interest in Draco Highlands' mineral wealth.
    • Auriga Crown and Cygnus Vale have religious and philosophical disagreements.
    • Auriga Crown generally considers Andromeda Coast overly permissive.
    • Lyra Reach tends to maintain trade and relatively moderate relations with most other regions.

    Ocean:

    • Asteria is surrounded by ocean.
    • Coastal sailing is possible.
    • Extremely powerful sea monsters inhabit the deeper waters.
    • Ships travelling too far from Asteria are usually destroyed, making travel beyond the continent effectively impossible at present.
    • There is no invisible system boundary preventing someone from attempting the journey.

    Slavery:

    • Slavery is illegal throughout Asteria.
    • Andromeda Coast is infamous for openly ignoring this law, with slavery, slave markets, and the buying and selling of people sometimes occurring in plain sight.
    • Powerful merchants, criminal groups, and corrupt officials allow the practice to continue through bribery, political influence, intimidation, and deliberate refusal to enforce Asterian law.
    • Other regions broadly know that Andromeda violates the ban, but actually stopping it is politically difficult.
    • Not everyone in Andromeda supports slavery, but openly opposing it can be dangerous due to the influence of merchants, criminal groups, and corrupt officials; resistance is therefore often private, cautious, or covert.

    General Rules:

    • Asteria is not politically unified.
    • Regional relationships may improve, worsen, or develop naturally through events.
    • Tension between regions does not mean they are automatically at war.
    • Individual settlements and people may hold different views from the broader attitudes of their region.
49. #49[ Draco Highlands ]selectiveregex

    Keys: Draco Highlands

    ---

    [ Draco Highlands ]

    Draco Highlands is a mountainous region covering northern Asteria. It is known for cold weather, mineral wealth, difficult terrain, and independent mountain communities.

    Main Population:

    • Humans and Beastkin are both common.
    • Elves and other ordinary Races may be found as travellers or minorities.
    • Obvious Undead and Monster Races are generally treated as threats around settlements.

    Major Settlement:

    • Eltanin is the largest city and main center of trade, mining, and smithing in the Highlands.

    Environment:

    • Tall mountains, rocky valleys, mines, caverns, pine forests, and fortified mountain roads are common.
    • The region is colder than most of Asteria and may experience snow even during portions of the warmer half of the year.
    • Mountain monsters and creatures adapted to cold or rocky environments are common outside settled areas.

    Culture:

    • Draco's people value self-reliance, hard work, craftsmanship, and practical ability.
    • Mining and smithing are major parts of local life.
    • Remote communities often have strong local identities and dislike outsiders attempting to control their affairs.

    Economy:

    • Rich deposits of ore and other useful materials make Draco important to Asterian trade.
    • Smithies and workshops are especially common in major settlements.
    • Metal, stone, tools, crafted goods, and Weaponry are important exports.

    Relations:

    • Orion March has strong interest in gaining greater access to Draco's mineral wealth, which causes political tension.
    • Cygnus Vale frequently complains that Draco mining damages rivers and land flowing toward its forests.
    • Draco generally resents both regions attempting to dictate how its natural resources should be used.
    • Trade with Lyra Reach is important and generally stable.

    General:

    • Draco Highlands is not unified by a single personality; wealthy mining settlements, remote villages, and isolated mountain communities may differ considerably.
    • Dangerous caves and mountains make the region a natural location for monsters, Bosses, mining expeditions, and valuable discoveries.
50. #50[ Eltanin ]selectiveregex

    Keys: Eltanin

    ---

    [ Eltanin ]

    Eltanin is the largest city of Draco Highlands and its main center for mining, smithing, and mountain trade.

    Population:

    • Mixed Human and Beastkin population.
    • Elves and other ordinary Races appear regularly as merchants and travellers.

    City Character:

    • Built across steep stone terraces connected by roads, stairs, bridges, and tunnels.
    • Workshops, smithies, warehouses, and ore markets are common.
    • Practical, industrious, and somewhat rough around the edges.
    • The colder climate means heavy clothing is common, though it provides no mechanical protection.

    Important Areas:

    • Forge District — dense concentration of smithies, workshops, and crafting facilities.
    • Ore Market — major marketplace for metals, minerals, tools, and Unclaimed Weaponry.
    • High Square — central district containing inns, merchants, officials, and public gatherings.

    Local Attitudes:

    • Skilled craftsmen and capable adventurers are generally respected.
    • Outsiders are common enough not to attract much attention.
    • Obvious Undead or Monster Races are treated as threats by guards and civilians.

    General:

    • Eltanin is one of the best places in Asteria for Players interested in crafting and acquiring materials.
    • Mountain expeditions and dangerous mining work frequently create jobs for adventurers.

    Yearly Festival:

    • Forgefire Festival — Day 38. Eltanin's smithies burn through the night while craftsmen demonstrate their work, merchants hold large markets, and newly forged goods are publicly displayed and sold.

Showing 50 of 83

Extensions: botbooru, talkativeness, world (their contents are in the Raw tab)

1 file

• .jsonotherspec 3.0original

  406.2 KBfirst seen Oct 20, 2026dd057aabc560bd85

  Download