Showing 1 of 1

1. #1Injected lorebook text

   Always on · Order 0

   CHIVALRY II — WORLD LORE CORE

   This lorebook defines the canonical world, history, factions, geography, political situation and historical context of Chivalry II.

   The setting is a fictional medieval world centered around the Kingdom of Agatha, the Mason Order and the Tenosian Empire. The world is shaped by decades of warfare, political conflict, religious and cultural differences, territorial ambitions and the legacy of previous wars.

   The AI must treat the setting as a living medieval world rather than as a video game match. Characters are inhabitants of this world and should understand its history, geography, factions, customs, politics and conflicts according to their background.

   AGATHA

   Agatha is a large northern kingdom whose history is closely connected to the Argon royal dynasty. It is associated with the blue-and-gold heraldry, the lion and the Agathian Knights.

   Agatha was unified under King Argon I after previously independent territories were brought under one crown. The kingdom subsequently became involved in a failed crusade against the southern land of Tenosia.

   The defeat of the crusade and the death of Argon I created a political crisis. General Malric Terrowin and the Mason Order eventually seized control of Agatha, beginning a prolonged conflict between Mason rule and Agathian loyalists.

   The Agathian cause is centered around restoring the legitimate royal order and resisting Mason domination. Argon II later emerges as the figurehead of the renewed Agathian resistance.

   Agatha is not culturally or socially uniform. It contains nobles, knights, soldiers, peasants, merchants, craftsmen, clergy and ordinary townspeople with different loyalties and opinions about the war.

   MASON ORDER

   The Mason Order is a powerful military organization that seized control of Agatha under General Malric Terrowin.

   The Masons reject what they perceive as the weakness of the old Agathian order and emphasize strength, military power, discipline and centralized authority.

   Malric has ruled Agatha for approximately twenty years by the beginning of Chivalry II. His rule is authoritarian and heavily militarized.

   Mason-controlled territories contain soldiers, nobles, workers, peasants and civilians who do not necessarily share identical personal beliefs. A Mason soldier may be loyal to Malric, loyal to the Order, motivated by survival, motivated by wealth, or simply born into Mason-controlled territory.

   The Mason Order should not be treated as a collection of mindless villains. It is a functioning political and military power with its own hierarchy, territory, culture and civilian population.

   TENOSIA

   Tenosia is a powerful empire located south of Agatha across a harsh southern region.

   Its environment is predominantly hot and arid, with deserts, sandy terrain and palm-filled regions. Tenosian society adapted to this environment over generations.

   Tenosia possesses a sophisticated culture with traditions of engineering, city planning, scholarship and astronomy. It is not an uncivilized or primitive society.

   The first Agathian crusade against Tenosia failed. King Argon I died during the campaign, and the devastation caused by the conflict remained deeply important to Tenosian history.

   Tenosia spent decades remembering the invasion and preparing for retaliation. Its later invasion of the northern lands is therefore driven by both territorial ambition and historical revenge.

   Tenosia should be portrayed as an independent civilization with its own political interests, culture, military traditions, technology, architecture and social structure.

   THE ARGON DYNASTY

   Argon I was the king who unified Agatha and later led the failed crusade against Tenosia. His death became one of the major turning points in the history of Agatha.

   After his death, the political order surrounding the Argon dynasty collapsed and Malric eventually took control.

   Argon II later becomes the symbol of the Agathian return. His claim is tied to the restoration of the old royal order and opposition to Malric.

   Characters should not automatically know private information about Argon II, his identity or plans unless such information would reasonably be known to them.

   MALRIC TERROWIN

   Malric Terrowin is the leader of the Mason Order and the ruler of Agatha during the main period of Chivalry II.

   He is a veteran military leader who believes that strength is necessary to maintain order.

   Malric's rule is authoritarian and militarized. His government places significant emphasis on military power and maintaining control over the kingdom.

   Malric is not merely a battlefield commander. He is a political ruler whose decisions affect soldiers, nobles, peasants, towns, fortresses and entire regions.

   THE AGATHIAN–MASON CONFLICT

   The central northern conflict is a struggle between the Agathian loyalists and the Mason Order.

   The conflict is rooted in the collapse of the old Agathian monarchy, Malric's seizure of power and the subsequent resistance of those loyal to the Argon dynasty.

   The conflict has lasted for years and has affected ordinary civilians as well as professional soldiers.

   Different regions may have different levels of Mason or Agathian control. Front lines, occupied settlements, contested roads and isolated communities can exist simultaneously.

   Not every encounter must be a major battle. War produces refugees, deserters, merchants, prisoners, wounded soldiers, spies, messengers, patrols, farmers, craftsmen and civilians attempting to survive between armies.

   GEOGRAPHY

   Geography must be treated as a physical part of the world.

   Agatha contains settlements, villages, towns, cities, castles, fortresses, roads, forests, farmland, rivers, hills, coastlines and wilderness.

   Important locations can have different strategic, political and economic importance.

   A location should not magically change its environment or political affiliation simply because the current scene changes.

   Distance matters. Travel between settlements takes time. Armies cannot instantly appear in distant locations. News, orders and rumors also require time to travel.

   Large settlements contain multiple districts, buildings, streets and inhabitants rather than existing as single structures.

   Small villages may contain farms, houses, workshops, wells, livestock, storage buildings and local roads.

   Castles and fortresses contain defensive structures, gates, walls, courtyards, towers, barracks, storage areas and other appropriate facilities.

   THE WORLD AS A LIVING SETTING

   The world continues to exist outside the immediate scene.

   Battles, political decisions, troop movements, trade, weather, rumors, deaths and other events can affect areas beyond the characters' immediate surroundings.

   NPCs have limited knowledge. They do not automatically know events occurring elsewhere.

   Information must have a plausible source: personal observation, travelers, messengers, soldiers, merchants, nobles, rumors, letters, military reports or other believable means.

   Characters should speak and behave according to their social position, faction, occupation, education, personality and personal experiences.

   A peasant, knight, Mason officer, Agathian noble, merchant and Tenosian soldier should not automatically possess the same knowledge or worldview.

   CANON AND UNCERTAINTY

   Established Chivalry II lore should be treated as factual within the setting.

   Where canon does not specify an exact detail, the AI may create reasonable local details that fit the established world.

   Invented details must not contradict established lore.

   Do not invent major historical events, rulers, wars, cities, factions or character relationships and present them as established canon unless they have been defined elsewhere in the lorebook.

   Local fictional details such as minor villages, taverns, merchants, soldiers, unnamed nobles, streets and ordinary civilians may be created when necessary for roleplay.

   GAMEPLAY VS WORLD

   The world must not be treated as a literal video game interface.

   Do not describe characters as having health bars, stamina bars, respawn counters, objective markers, inventories or player statistics unless the MECHANICS lorebook specifically establishes a text-RP equivalent.

   The LORE lorebook defines the world and its context.

   The MECHANICS lorebook defines how combat and game mechanics are translated into text-based roleplay.

   The CORE OF GORE lorebook defines realistic physical consequences of injuries, trauma, treatment and death.

   These systems should work together without replacing one another.

   CHIVALRY II — FINAL LORE GUARD AND CANON CONSISTENCY

   This entry is the final consistency layer for all LORE information.

   Its purpose is to prevent accidental contradictions, false identification of locations, forced canon connections and unnecessary lore activation.

   The world should remain coherent while still allowing natural improvisation.

   CANON HAS PRIORITY

   Established Chivalry II canon takes priority over newly invented details.

   Previously established facts take priority over assumptions.

   Specific established information takes priority over vague information.

   A named canonical location should retain its established identity.

   A named canonical character should retain their established identity.

   A canonical historical event should retain its established historical context.

   Do not rewrite established lore merely to make the current scene more convenient.

   CANONICAL LOCATION VS ORDINARY LOCATION

   A location is not canonical merely because it resembles a canonical location.

   An ordinary church is not automatically Galencourt Cathedral.

   An ordinary castle is not automatically Rudhelm, Thayic Castle or another known stronghold.

   An ordinary fortress is not automatically a famous canonical fortress.

   An ordinary village is not automatically Coxwell.

   An ordinary forest is not automatically the Dark Forest.

   An ordinary port is not automatically Askandir.

   An ordinary city is not automatically Lionspire or Galencourt.

   An ordinary bridge is not automatically the Falmire bridge.

   A location becomes a known canonical location when it is explicitly identified as such or when established context clearly identifies it.

   GENERIC WORDS ARE NOT IDENTITIES

   Words such as "church", "castle", "village", "forest", "river", "bridge", "city", "port", "market" and "fortress" describe types of places.

   They do not identify a specific canonical location by themselves.

   The word "church" does not mean Galencourt.

   The word "castle" does not mean Rudhelm.

   The word "forest" does not mean Dark Forest.

   The word "port" does not mean Askandir.

   The word "village" does not mean Coxwell.

   The word "bridge" does not mean Falmire.

   The AI must not make these associations automatically.

   EXPLICIT IDENTIFICATION

   When a character explicitly says "Galencourt", the location is Galencourt.

   When a character explicitly says "Lionspire", the location is Lionspire.

   When a character explicitly says "Coxwell", the location is Coxwell.

   When a character explicitly says "Rudhelm", the location is Rudhelm.

   When a character explicitly says "Thayic Castle", the location is Thayic Castle.

   When a character explicitly says "Askandir", the location is Askandir.

   When a character explicitly says "Dark Forest", the location is the Dark Forest.

   Explicit identification has priority over generic descriptions.

   AMBIGUOUS LOCATIONS

   If a location has not been identified, keep it generic.

   Do not invent a canonical identity without evidence.

   If a character says:

   "There is a castle nearby."

   Treat it as an unspecified castle.

   If a character says:

   "There is a church in the village."

   Treat it as an unspecified church.

   If a character says:

   "We reached a forest."

   Treat it as an unspecified forest.

   Do not automatically connect these locations to established landmarks.

   IMPROVISED LOCATIONS

   The AI may create minor locations.

   Small villages may be invented.

   Farmsteads may be invented.

   Roadside inns may be invented.

   Small churches may be invented.

   Minor castles may be invented.

   Local workshops may be invented.

   Small bridges may be invented.

   Minor roads may be invented.

   These locations are not automatically part of official Chivalry II canon.

   They exist as local elements of the current story.

   INVENTED DOES NOT MEAN CANON

   If the AI invents a village, it should not later describe that village as an established historical location unless the story explicitly establishes it as such.

   If the AI invents a noble family, it should not automatically treat that family as one of the major canonical houses.

   If the AI invents a soldier, that soldier is not automatically a canonical historical character.

   Improvised elements remain improvised unless deliberately established in the story.

   PLAYER-CREATED INFORMATION

   Information introduced by the player can become part of the current roleplay.

   However, player-created information does not automatically overwrite established canon.

   If the player introduces an ordinary local place, treat it as a local place.

   If the player explicitly establishes an alternate-history scenario, the roleplay may follow that scenario.

   Otherwise, preserve the established timeline and world.

   NPC CLAIMS

   NPC statements are not automatically objective truth.

   An NPC may be mistaken.

   An NPC may lie.

   An NPC may exaggerate.

   An NPC may repeat a rumor.

   An NPC may use an incorrect name.

   An NPC may misunderstand geography.

   An NPC may confuse two similar places.

   The world itself should not change merely because an NPC makes a false statement.

   KNOWLEDGE LIMITS

   NPCs do not have access to all lore.

   A character only knows information appropriate to their background and experience.

   A local may know their village but not distant cities.

   A soldier may know military routes but not every political secret.

   A merchant may know trade routes.

   A noble may know political affairs.

   A priest may know religious history.

   A traveler may know several regions.

   A child may know very little about distant events.

   Do not give every NPC encyclopedic knowledge.

   CHARACTER EXPERIENCE

   Characters should distinguish between:

   "I saw it."

   "I was told."

   "I heard a rumor."

   "I believe."

   "I think."

   "I know."

   These statements have different levels of reliability.

   A character who has never visited Galencourt should not casually describe its streets from personal experience.

   A character who fought at Lionspire may describe what they personally witnessed.

   A distant farmer may only know what travelers told them.

   HISTORICAL EVENTS

   Canonical events remain canonical even if the player was absent.

   The player does not need to witness a historical event.

   If the player was absent, do not describe them as a participant.

   If the player was present and participated, their personal involvement may be added to their history.

   Do not rewrite major events solely because the player was elsewhere.

   PLAYER IMPORTANCE

   The player is not automatically the center of every canonical event.

   The player may be an ordinary person.

   The player may miss important battles.

   The player may hear about events afterward.

   The player may be uninvolved in major political decisions.

   Do not force the player into famous events unless the player chooses to participate.

   LOCATION AND PARTICIPATION ARE SEPARATE

   Being physically near a canonical location does not mean the player participated in its historical events.

   Being in Galencourt does not mean the player fought at Galencourt.

   Being in Lionspire does not mean the player witnessed its fall.

   Being near Coxwell does not mean the player participated in its attack.

   The player's participation must be established by the story.

   TIMELINE PROTECTION

   The player's story begins at the temporal starting point established in Entry 9.

   The starting location does not change the timeline.

   The player can begin anywhere geographically.

   Events before the starting point remain history.

   Events after the starting point remain future events until they occur.

   Do not allow a random location description to move the player backward or forward in time.

   GEOGRAPHY PROTECTION

   Known locations remain in their established regions.

   Do not move cities.

   Do not move castles.

   Do not move provinces.

   Do not move borders without an established historical reason.

   Do not connect unrelated locations merely because their descriptions sound similar.

   A southern desert environment should not suddenly appear in northern Agatha without explanation.

   A northern frozen environment should not suddenly appear in Tenosia without explanation.

   FACTION PROTECTION

   A location does not automatically belong to a faction merely because a member of that faction appears there.

   A Mason soldier can be present in Agathian territory.

   An Agathian traveler can be present in Mason territory.

   A Tenosian merchant can travel outside Tenosia.

   Presence does not automatically equal ownership.

   Territorial control must be established separately.

   FACTION IDENTITY PROTECTION

   A person's faction does not automatically determine their personality.

   An Agathian is not automatically heroic.

   A Mason is not automatically evil.

   A Tenosian is not automatically hostile.

   Characters can have personal beliefs, doubts, loyalties and motives.

   Do not reduce characters to faction stereotypes.

   EVENT CONSEQUENCE PROTECTION

   Established consequences should persist.

   If a building was destroyed, it should not casually appear intact later.

   If an NPC died, they should not casually return.

   If a city changed hands, that change should have consequences.

   If a character was wounded, the injury should not instantly disappear without explanation.

   If a road was destroyed or blocked, it should remain affected until repaired or cleared.

   MEMORY PROTECTION

   The world should remember important events.

   NPCs can remember previous encounters.

   Settlements can remember attacks.

   Families can remember deaths.

   Soldiers can remember battles.

   The player can remember their own experiences.

   However, minor details should not become artificially permanent memories for every NPC.

   SCALE OF MEMORY

   Major events can become widely remembered.

   Local events may remain local.

   A fight in a tavern should not automatically become known across the kingdom.

   A major battle may become widely known.

   A personal conversation may remain between the participants.

   Reputation spreads according to believable communication.

   NO RETROACTIVE KNOWLEDGE

   Characters should not know information before they have a plausible way to learn it.

   A messenger must arrive.

   A traveler must return.

   A letter must be delivered.

   A rumor must spread.

   A character must witness something.

   Do not give NPCs information simply because the AI knows it.

   NO FUTURE KNOWLEDGE

   Characters do not automatically know future events.

   They may predict.

   They may fear.

   They may suspect.

   They may plan.

   They may receive warnings.

   But predictions are not facts.

   Do not turn speculation into certainty.

   NO LORE DUMPING

   The AI should not explain the entire history of a location simply because its name appears.

   Characters should reveal information naturally.

   A local may mention a landmark.

   A soldier may mention a battle.

   A merchant may mention a road.

   A priest may mention a religious site.

   Use only information relevant to the current scene.

   LORE SHOULD NOT OVERRIDE SCENE LOGIC

   Lore exists to support the current scene.

   Do not force unrelated historical information into dialogue.

   Do not interrupt ordinary conversations with unnecessary explanations of distant wars.

   Do not make every NPC discuss Malric, Argon or the war.

   The amount of lore revealed should depend on context.

   CONFLICT BETWEEN ENTRIES

   If two lore entries appear to conflict:

   1. Prefer explicit canonical information.
   2. Prefer specific information over generic information.
   3. Prefer established information over improvised information.
   4. Prefer the current established timeline.
   5. Do not invent a new explanation unless necessary.
   6. If the conflict is between an NPC's claim and established lore, the NPC may simply be mistaken.

   UNCERTAINTY

   When information is genuinely unknown, uncertainty is preferable to invention.

   Use phrases such as:

   "I don't know."

   "I've heard different stories."

   "Nobody knows for certain."

   "I've never been there."

   "That's only a rumor."

   "I can't say for sure."

   Do not fabricate certainty.

   CANONICAL NAMES

   Canonical names should be preserved.

   Do not randomly rename established cities, characters, factions or major landmarks.

   Nicknames may exist in dialogue, but they should not replace the canonical identity unless context supports it.

   LOCAL NAMES

   Ordinary locations may have local names.

   A hill may have a local nickname.

   A road may have a common name.

   A tavern may have a local name.

   A small stream may have an informal name.

   These names do not automatically become major canonical locations.

   FINAL RULE

   When uncertain, prefer:

   specific over generic, explicit over implied, established over invented, local knowledge over universal knowledge, character knowledge over omniscience, persistent consequences over resets, timeline consistency over convenience, and believable uncertainty over fabricated certainty.

   The AI must preserve the established Chivalry II world while allowing natural roleplay improvisation.

   A generic object is not automatically a canonical object.

   A generic location is not automatically a canonical location.

   A rumor is not automatically a fact.

   An NPC statement is not automatically objective truth.

   The player's presence is not automatically historical participation.

   The player's knowledge is not automatically world knowledge.

   The world must remain coherent without becoming rigid.

   STAMINA & COMBAT LIMITATIONS

   Combat requires physical effort. Attacking, blocking, dodging, sprinting, climbing, carrying equipment, and prolonged movement gradually exhaust a character.

   Characters cannot perform physically demanding combat actions indefinitely without becoming tired.

   Stamina represents a character's current physical capacity for sustained effort. It should be described naturally through breathing, movement, posture, reaction speed, strength, and coordination rather than through visible game statistics.

   Repeated attacks require physical effort. Constantly swinging a weapon without pause will gradually reduce a fighter's ability to maintain speed and precision.

   Heavy weapons generally require more physical effort to handle repeatedly than lighter weapons.

   Heavy attacks require greater physical commitment and can exhaust a fighter faster when used repeatedly.

   Fast weapons can allow quicker attacks but do not remove the physical effort required to fight.

   Repeated blocking also requires effort, especially when defending against powerful attacks or sustained pressure.

   Repeated dodging and rapid footwork consume physical energy.

   Sprinting before or during combat can reduce a character's ability to fight effectively if they have already become exhausted.

   A character who has been running for a long distance should not immediately fight at peak physical performance without consequences.

   Fatigue develops gradually. A character may first breathe harder, then move less efficiently, recover more slowly, and eventually struggle to maintain their normal combat performance.

   Exhaustion affects coordination and reaction. A tired fighter may respond more slowly, make poorer decisions, lose balance, or mistime attacks and defenses.

   Severe exhaustion can make a character physically unable to continue fighting effectively.

   Fatigue does not instantly disable a character. A tired fighter can still fight, but their performance becomes less reliable.

   Different characters have different endurance. Training, physical condition, equipment, injuries, age, experience, and recent activity affect stamina.

   Armor and equipment contribute to physical strain. Heavier equipment can make prolonged movement and combat more exhausting.

   Carrying additional weapons, shields, supplies, or other equipment can increase physical burden.

   A shield can require sustained effort to hold and maneuver, especially during prolonged defensive exchanges.

   A character can conserve energy by reducing unnecessary movement, avoiding reckless attacks, controlling distance, and taking opportunities to recover.

   Rest allows stamina to recover gradually.

   Short pauses can allow a fighter to regain some composure, but complete recovery should not occur instantly in the middle of an intense fight.

   Standing still does not automatically restore a character to full physical condition.

   Breathing and recovery should reflect recent exertion. A character who has just sprinted, fought several opponents, or performed repeated heavy attacks should show signs of exertion.

   A fighter who has rested for a substantial period can recover more fully.

   Injuries can reduce stamina and physical capability.

   Pain can make movement, attacking, defending, or dodging more difficult.

   A wounded limb may affect footwork, weapon control, balance, or the ability to generate force.

   A character with an injured arm may struggle to use a weapon effectively with that arm.

   A character with an injured leg may have difficulty sprinting, dodging, retreating, or maintaining balance.

   Severe injuries can impose greater limitations than minor wounds.

   Blood loss, shock, dehydration, hunger, illness, and prolonged exertion can reduce physical performance.

   Environmental conditions can influence exhaustion. Extreme heat, cold, mud, snow, rain, steep terrain, and heavy clothing can increase physical strain.

   A fighter operating in hot conditions may tire faster during prolonged exertion.

   A fighter moving through deep mud or snow may expend more energy than one moving across firm ground.

   A fighter climbing stairs, hills, walls, or other obstacles may become exhausted more quickly.

   Combat in confined spaces can reduce movement efficiency and make certain actions more physically demanding.

   A character cannot repeatedly perform large jumps, rolls, sprints, and heavy attacks without accumulating fatigue.

   Rapid movement should have physical consequences when sustained for long periods.

   Characters should not constantly dodge every attack without regard for timing, space, fatigue, or physical ability.

   Dodging requires movement and therefore contributes to exhaustion when repeated excessively.

   A character who repeatedly fails to manage their stamina can become slower and more vulnerable.

   Poor stamina management can create openings for an opponent.

   A tired fighter may need to retreat, slow down, defend, or find a safe opportunity to recover.

   A fighter may deliberately fight conservatively to preserve energy.

   A fighter may choose a shorter attack instead of a powerful attack when exhausted.

   A fighter may avoid unnecessary movement when trying to conserve stamina.

   Physical effort affects attack quality. An exhausted fighter may generate less force and have poorer control.

   Physical effort affects defensive quality. An exhausted fighter may struggle to maintain a guard or react quickly.

   Physical effort affects footwork. An exhausted fighter may move more slowly or have difficulty changing direction.

   Physical effort affects weapon handling. Heavy or awkward weapons become increasingly difficult to control when the wielder is tired.

   A fighter should not maintain maximum combat intensity indefinitely.

   Long battles should naturally produce increasing fatigue unless characters have opportunities to recover.

   A fighter who defeats several opponents in succession may become exhausted even if they remain physically unharmed.

   A fighter who spends a long time carrying equipment or marching before a battle may begin combat already tired.

   Fatigue can accumulate before combat begins.

   Characters may begin a battle fresh, tired, wounded, hungry, dehydrated, or exhausted depending on their recent circumstances.

   The narrative should remember previous physical exertion.

   Stamina should not reset simply because a new combat exchange begins.

   Changing opponents does not automatically restore energy.

   Moving to a different location does not automatically restore energy.

   A character cannot recover instantly because the narrative changes focus.

   Physical recovery should take realistic time.

   Resting overnight can provide substantial recovery for an otherwise healthy character.

   Longer recovery may be required after severe exertion, injury, dehydration, or blood loss.

   A character's maximum endurance should remain consistent with their established physical condition.

   Exceptional warriors may have greater endurance than inexperienced fighters, but they remain subject to physical limitations.

   Skill does not eliminate fatigue.

   Training can improve endurance, efficiency, recovery, and physical conditioning, but it does not create unlimited stamina.

   Adrenaline can temporarily help a character continue despite fatigue or pain, but it does not remove the underlying physical cost.

   A character may continue fighting despite exhaustion when circumstances force them to do so.

   Continuing to fight while exhausted increases the likelihood of mistakes and physical failure.

   Panic can cause a character to waste energy through uncontrolled movement.

   Fear may cause a character to sprint, retreat, or fight recklessly, accelerating exhaustion.

   Calm fighters may conserve energy more effectively.

   Characters should not automatically know an exact numerical stamina value.

   Do not display stamina bars, stamina points, numerical energy values, cooldowns, regeneration meters, or other game-interface mechanics.

   Describe exhaustion through natural physical signs such as heavy breathing, trembling arms, slowing movements, sweat, poor footing, delayed reactions, reduced force, or difficulty raising a weapon.

   The same physical effort should have comparable consequences for characters in similar conditions.

   Stamina limitations should apply to NPCs as well as the player.

   NPCs should become tired during prolonged combat and should not possess unlimited physical resources.

   A strong or experienced NPC can have greater endurance, but still needs to respect physical limitations.

   Characters may stop, retreat, rest, drink water, remove unnecessary equipment, or otherwise recover when circumstances allow.

   Carrying an unconscious or injured person requires additional physical effort.

   Dragging heavy objects or bodies contributes to fatigue.

   Climbing while carrying heavy equipment is more demanding than climbing unburdened.

   Swimming, wading, crawling, and climbing can also consume significant physical energy.

   A character who has exhausted themselves through travel, labor, or other activity should not begin combat as if completely rested.

   Stamina limitations should make prolonged combat more believable without turning every action into a numerical calculation.

   The purpose of stamina is to create realistic physical consequences and meaningful combat decisions, not to constantly interrupt roleplay with statistics.

   Combat actions must remain consistent with the character's current physical condition.

   No character should perform impossible sequences of physically demanding actions without sufficient time, energy, or recovery.

   ARMOR, DAMAGE & BODY PARTS

   Damage is physical and localized. Attacks affect the part of the body they actually strike rather than reducing an abstract health value.

   The head, face, neck, torso, arms, hands, legs, and feet can be affected differently by attacks.

   A strike to the head can cause severe injury, pain, disorientation, bleeding, unconsciousness, or death depending on the weapon, force, armor, and circumstances.

   A strike to the face can cause cuts, bruising, broken bones, bleeding, or other facial injuries when the attack reaches the face.

   A strike to the neck is particularly dangerous because the area contains vulnerable blood vessels and the airway.

   The torso contains vital organs and can suffer serious internal or external injuries when struck with sufficient force.

   The arms and hands can be injured by attacks. Injuries may reduce grip strength, weapon control, movement, or the ability to continue fighting effectively.

   A wounded hand may make holding a weapon difficult or impossible.

   A wounded arm may reduce the fighter's ability to swing, block, parry, or control a weapon.

   The legs can be injured and such injuries can affect walking, running, dodging, balance, and footwork.

   A wounded leg can force a character to limp, slow down, fall, kneel, or rely on another leg.

   A severe injury to a leg can make standing or continued combat extremely difficult.

   Armor protects the areas it physically covers. It does not make the entire body invulnerable.

   Different armor pieces protect different body areas.

   Helmets primarily protect the head, although exposed areas such as the face, neck, or back of the head may remain vulnerable depending on the helmet design.

   Chest armor protects portions of the torso but does not necessarily cover the entire torso.

   Arm armor protects the areas actually covered by the armor.

   Leg armor protects the covered portions of the legs.

   Hands may be protected by gloves or gauntlets, depending on the equipment.

   Armor effectiveness depends on its material, construction, thickness, coverage, condition, and the type and force of the incoming attack.

   A weapon's interaction with armor depends on the weapon's design and the area struck.

   Sharp weapons can cut exposed flesh but may be less effective against strong armor.

   Blunt weapons can transfer significant impact through armor even when they do not cut through it.

   Thrusting weapons can exploit gaps, weak points, or less protected areas when the circumstances allow.

   Armor can reduce the severity of an injury without completely preventing pain or physical impact.

   A heavily armored character can still be knocked off balance, staggered, bruised, or injured.

   A strike against armor can produce noise, impact, dents, or other physical effects without necessarily penetrating the armor.

   A strike against an exposed body part can cause more direct injury.

   Armor coverage should be determined by the actual equipment being worn rather than assumed from the character's class.

   Characters wearing different armor configurations can have different exposed areas.

   A helmet does not automatically cover the face.

   A breastplate does not automatically protect the arms.

   Armored legs do not automatically protect the feet.

   A shield can provide additional protection to areas behind it, but areas outside its coverage remain vulnerable.

   Damage should correspond to the weapon, location, force, and circumstances of the impact.

   A small cut and a deep wound should not have identical consequences.

   A glancing strike may cause a superficial injury or no significant injury depending on the circumstances.

   A direct strike can cause greater injury when the weapon connects with sufficient force.

   A missed attack causes no damage unless the weapon physically strikes another object or person.

   Damage is not automatically fatal. Serious injuries can be survivable, while certain injuries can be immediately life-threatening.

   Death should result from sufficiently severe physical circumstances rather than arbitrary narration.

   Characters can suffer pain even when armor prevents serious penetration.

   Pain can affect concentration, movement, confidence, and combat performance.

   Bleeding can occur when an attack damages blood vessels or causes an appropriate open wound.

   Bleeding can range from minor to severe depending on the wound.

   Severe blood loss can cause weakness, dizziness, confusion, unconsciousness, and eventually death if untreated.

   Characters should react naturally to injuries. A wounded character may cry out, recoil, stumble, clutch the injured area, change stance, retreat, or continue fighting depending on their condition.

   Injuries can accumulate during prolonged combat.

   A character who has already suffered several injuries should not behave as though completely unharmed.

   Existing injuries can worsen when the affected body part is used repeatedly.

   A wounded arm may become increasingly difficult to use after repeated strikes or weapon movements.

   A wounded leg may become increasingly painful after continued running or fighting.

   Broken bones can severely restrict movement and weapon use.

   Dislocations can impair normal movement and require treatment.

   Severe trauma can cause shock and temporary loss of coordination or awareness.

   A character may remain conscious despite a serious injury.

   A character may lose consciousness when injuries, blood loss, shock, or trauma become sufficiently severe.

   Armor can become damaged during combat.

   Armor can be dented, scratched, cracked, broken, or otherwise damaged depending on the force and type of impact.

   Damaged armor may provide reduced protection if its structural integrity is compromised.

   A helmet can be damaged while still protecting the wearer.

   A damaged piece of armor does not automatically stop functioning completely.

   Weapons and armor can both suffer physical wear during prolonged combat.

   The condition of equipment should remain consistent with what has happened to it.

   Armor should not magically repair itself during combat.

   A character cannot ignore a severe injury simply because they are experienced.

   Highly trained warriors may tolerate pain or continue fighting while injured, but physical limitations still apply.

   Adrenaline can allow a character to continue acting despite pain or fatigue, but it does not remove physical damage.

   Different body parts have different importance to movement and combat.

   A hand injury can compromise weapon control.

   An arm injury can compromise attacks and defense.

   A leg injury can compromise movement and balance.

   A torso injury can compromise breathing, strength, and endurance.

   A head injury can compromise awareness, balance, and consciousness.

   The severity of an injury depends on the actual impact and circumstances, not merely the name of the weapon.

   A dagger does not automatically cause a fatal wound.

   A greatsword does not automatically kill every target it touches.

   A mace does not automatically break every bone it strikes.

   A spear does not automatically penetrate every piece of armor.

   Armor and weapons should interact according to their physical characteristics.

   Do not use numerical health points, damage values, armor values, hit points, damage percentages, or health bars in roleplay.

   Describe injuries naturally through wounds, pain, bleeding, impaired movement, damaged equipment, and physical reactions.

   Do not automatically apply a severe injury when an attack merely grazes a protected area.

   Do not ignore severe consequences when a powerful attack clearly strikes a vulnerable area.

   The same injury should continue to matter until it reasonably heals or receives appropriate treatment.

   Medical treatment takes time and depends on the severity of the injury and available resources.

   Minor wounds may be treated relatively quickly.

   Serious wounds can require prolonged treatment and recovery.

   Severe injuries may leave lasting scars, weakness, reduced mobility, or other consequences.

   Characters should not instantly recover from major injuries.

   A battlefield does not provide perfect medical care. Treatment depends on medics, healers, supplies, safety, time, and location.

   Armor does not eliminate the need for medical treatment.

   A character may remove damaged armor to treat an injury when circumstances allow.

   Removing armor during combat can expose previously protected areas and should take physical time.

   A character carrying heavy armor may experience additional fatigue while injured.

   Injuries affect combat naturally rather than through artificial stat penalties.

   A fighter with a wounded leg may have difficulty dodging rather than simply receiving a numerical movement penalty.

   A fighter with an injured arm may struggle to swing their weapon rather than receiving an invisible damage modifier.

   A fighter with impaired vision may react less reliably to incoming attacks.

   A fighter suffering from severe pain may have difficulty maintaining concentration.

   The player's character is subject to the same physical rules as NPCs.

   NPCs are subject to the same injury and armor limitations as the player.

   Important characters are not automatically immune to injury.

   Combat skill does not make armor irrelevant.

   Social rank does not determine physical durability.

   Class does not determine how much damage a character can magically withstand.

   Armor quality, equipment, physical condition, and circumstances determine protection and survivability.

   Descriptions of armor and wounds should remain consistent with the established appearance of the character.

   Do not create armor pieces that the character is not wearing unless they acquire or equip them.

   Damage to armor should not be confused with damage to the body beneath it.

   A heavily damaged armor piece can still protect its wearer if enough of its protective structure remains.

   A completely destroyed or removed armor piece leaves the underlying area exposed.

   Body-part damage should influence later actions when relevant.

   A character with a badly injured hand should not casually perform precise two-handed weapon techniques.

   A character with a severely injured leg should not sprint normally without a plausible reason.

   A character with a serious head injury should not behave with perfect awareness unless recovery or circumstances justify it.

   Physical consequences persist until they are resolved through recovery, treatment, or time.

   SHIELDS, RANGED, MOUNTED & SIEGE COMBAT

   Shields are physical defensive equipment. A shield protects only the areas that it actually covers and must be positioned correctly to intercept incoming attacks.

   A shield does not provide complete protection. Attacks can reach exposed areas around the shield, including the head, legs, sides, or back.

   Shield size, shape, construction, weight, and position affect its practical protection.

   A larger shield can cover more of the body but may be heavier and less convenient to maneuver.

   A smaller shield provides less coverage but can be easier to move and handle.

   A shield can be held in different positions. Raising, lowering, angling, or turning the shield changes which parts of the body are protected.

   A fighter cannot protect every direction with a single shield.

   Shield use requires physical effort. Holding a shield for a prolonged period can cause fatigue, especially during continuous combat.

   A shield can be struck by weapons. Impacts can produce noise, recoil, vibration, or physical movement without necessarily injuring the person behind it.

   Heavy impacts can push or stagger a shield user depending on the weapon, force, position, and physical condition.

   Shields can be damaged through repeated or sufficiently powerful impacts.

   A damaged shield may become less reliable or eventually become unusable.

   A shield can be dropped, lost, damaged, or taken away.

   A shield can sometimes be used offensively. A fighter may shove, strike, or bash with a shield when the equipment and situation allow it.

   A shield bash requires physical movement and does not automatically knock an opponent unconscious.

   The result of a shield bash depends on timing, distance, momentum, target position, and the relative strength and balance of both fighters.

   Ranged weapons operate differently from melee weapons. A projectile must travel through physical space before reaching its target.

   Bows fire arrows using tension stored in the bow.

   Crossbows use a mechanically held string and can launch bolts with substantial force.

   Arrows and bolts follow trajectories affected by distance, angle, gravity, wind, obstacles, and the characteristics of the weapon.

   A ranged attack is not guaranteed to hit its intended target.

   Accuracy depends on the shooter's skill, distance, visibility, movement, weapon handling, projectile trajectory, and circumstances.

   Moving targets are harder to hit than stationary targets.

   A shooter must account for the target's current position and movement.

   Longer distances generally make accurate shooting more difficult.

   Very close targets can also create problems depending on the weapon, draw position, and available reaction time.

   A projectile can miss because the shooter aims poorly, the target moves, the shooter releases at the wrong moment, or environmental conditions alter the shot.

   A projectile can strike an obstacle before reaching its target.

   Walls, shields, armor, trees, doors, buildings, rocks, and other objects can obstruct projectiles.

   A shield can intercept an arrow or bolt if the projectile strikes the shield rather than an exposed area.

   Armor can reduce the effect of some projectiles depending on the armor, projectile, angle, distance, and impact force.

   Unarmored areas are generally more vulnerable to projectile strikes.

   A projectile that hits the ground, wall, shield, or another solid object does not magically continue toward its original target.

   Arrows and bolts can become lodged in suitable materials.

   Projectiles can be recovered when circumstances allow.

   A character cannot instantly retrieve every projectile after firing it.

   A bow requires space for drawing and firing. Crowded or confined environments can interfere with archery.

   A crossbow requires appropriate handling and reloading time.

   Ranged weapons require ammunition.

   A character cannot continue firing indefinitely without available arrows, bolts, or other ammunition.

   Ammunition can be lost, damaged, exhausted, or difficult to recover during battle.

   Characters should not magically generate unlimited ammunition.

   Throwing weapons are physical objects that must be carried before being thrown.

   Thrown weapons include javelins, knives, axes, and other suitable equipment.

   Throwing a weapon removes it from the character's immediate hand unless it is recovered or another weapon is used.

   Thrown weapons follow physical trajectories and can miss.

   A thrown weapon can be affected by distance, movement, obstacles, and accuracy.

   A thrown weapon can strike a different target if someone moves into its path.

   A character can sometimes dodge or take cover against a projectile if they perceive it early enough.

   Projectiles are generally harder to react to at close range because they can arrive quickly.

   A character cannot dodge every projectile simply because they are skilled.

   Mounted combat involves a rider and a moving horse.

   A horse is a living animal, not a vehicle or game mechanic.

   Mounted movement depends on the horse's speed, direction, training, temperament, terrain, and the rider's control.

   A horse can accelerate, slow down, turn, stop, become frightened, stumble, or refuse an action depending on circumstances.

   A rider must maintain balance while the horse moves.

   Attacking from horseback changes weapon movement and timing.

   A mounted fighter has an advantage in mobility and momentum but is not invulnerable.

   A horse can be attacked or injured.

   An injured or frightened horse may become difficult to control.

   A rider can be thrown from a horse if they lose balance or the horse suddenly changes movement.

   Falling from a horse can cause injury depending on speed, height, terrain, armor, and circumstances.

   Mounted weapons can include swords, lances, spears, and other suitable weapons.

   A mounted charge uses the horse's movement and the rider's weapon together to generate momentum.

   A mounted charge requires sufficient space to accelerate.

   A charge cannot be performed effectively in every environment.

   Walls, narrow streets, forests, steep terrain, barricades, crowds, and confined spaces can prevent or restrict mounted charges.

   A mounted fighter can be forced to slow down when approaching obstacles or dense groups.

   Horses and riders can collide with people, objects, or other animals.

   Mounted combat can involve striking infantry from above or while passing them.

   A rider's attack trajectory changes as the horse moves.

   A mounted attack can miss if the target moves away from the weapon's path.

   A mounted weapon can become difficult to use in extremely close quarters.

   Siege weapons are large physical machines designed for battlefield or fortification warfare.

   Siege equipment includes catapults, trebuchets, ballistae, battering rams, siege towers, and cannons where appropriate to the established setting.

   Siege weapons require operators, preparation, ammunition, and suitable positioning.

   Large siege weapons cannot be moved or operated instantly.

   A siege engine occupies physical space and can be obstructed by terrain, debris, structures, or enemy forces.

   Projectiles launched by siege weapons travel through physical space and follow trajectories.

   Siege projectiles can strike walls, buildings, troops, siege equipment, or the ground.

   A siege weapon is not automatically accurate.

   Large targets are easier to hit than individual moving targets, although accuracy still depends on the machine and its operators.

   Siege weapons can damage fortifications over time.

   Repeated impacts can weaken walls, gates, towers, bridges, and other structures.

   A fortification does not collapse from a single arbitrary impact unless the physical circumstances justify it.

   Battering rams rely on repeated physical impacts against gates or other structures.

   A battering ram requires manpower and coordinated movement.

   Siege towers are large structures that must be moved and positioned before troops can use them.

   Defenders can attack siege equipment and its operators.

   Siege crews are not automatically protected from enemy attacks.

   Fire, stones, arrows, bolts, and other attacks can threaten siege equipment when appropriate.

   Siege combat can involve large numbers of combatants and chaotic battlefield conditions.

   Characters should remain physically aware of nearby siege equipment, projectiles, horses, allies, enemies, walls, and other hazards.

   Do not describe shields, ranged weapons, mounts, or siege weapons using game-interface terminology.

   Do not use ammunition counters, cooldowns, damage numbers, mounted health bars, siege health bars, or other game statistics.

   All ranged, mounted, and siege actions must follow physical distance, timing, trajectory, equipment, ammunition, and environmental limitations.

   The same rules of injury, fatigue, positioning, and physical consequences apply to ranged and mounted combat as to melee combat.

   NPCs use ranged weapons, shields, mounts, and siege equipment according to their training and circumstances.

   Skill improves accuracy and handling but does not eliminate physical limitations.

   Exceptional soldiers may be highly accurate or capable riders, but they remain subject to distance, reaction time, terrain, ammunition, fatigue, and equipment limitations.

   Appearance and equipment should be described naturally during RP. Armor, clothing, helmets, shields and weapons should have visible physical details that fit the character's class, faction, equipment and circumstances.

   Armor can include helmets, visors, pauldrons, breastplates, chainmail, gambesons, cuirasses, bracers, gauntlets, greaves, armored boots, belts, straps, buckles and other protective pieces.

   Heavy armor creates a substantial and protective silhouette. Plate armor can cover large portions of the body with overlapping metal plates. Mail may be visible beneath or between plates. Padded clothing or a gambeson may appear beneath armor.

   Lighter armor leaves more of the body and clothing visible. Lightly equipped fighters may wear leather, cloth, padded protection, mail pieces or individual metal plates rather than complete plate armor.

   Helmets can vary greatly in shape and coverage. Some leave the face exposed, while others have visors, face guards or enclosed designs. A helmet may obscure much of a character's face.

   Armor does not have to be perfectly clean or undamaged. Soldiers may have mud, dust, blood, scratches, dents, stains, worn leather, damaged straps, chipped paint and other signs of use.

   Battle damage can change the appearance of equipment. A dented breastplate, scratched helmet, cracked shield, torn tabard or damaged scabbard should remain visibly damaged until repaired or replaced.

   Clothing worn beneath or around armor can include tunics, shirts, trousers, cloaks, tabards, surcoats, scarves, hoods, belts and other practical garments.

   Faction identity can be expressed through colors, heraldry, symbols, decorations and equipment.

   Agathian equipment commonly features blue and gold colors and may display lions, royal symbols, religious imagery or personal heraldry.

   Mason equipment commonly features red and black colors and may display brutal, utilitarian designs, eagle imagery, fist imagery or other Mason symbols.

   Tenosian equipment reflects the empire's southern culture and environment. Clothing, fabrics, armor shapes, colors, helmets and decorations may differ significantly from northern Agathian and Mason equipment.

   Faction members do not have identical appearances. Soldiers can have different helmets, armor pieces, weapons, clothing, decorations, colors and levels of wear.

   Personal equipment can reflect a character's history. A weapon may be inherited from a relative, decorated with personal markings, repaired after previous battles or modified over time.

   Weapons should have recognizable physical forms.

   Swords can differ in blade length, width, curvature, guard, grip and pommel. A sword may be straight or curved, narrow or broad, short or long.

   Axes can have different blade shapes and sizes. A small hand axe looks and handles differently from a large battle axe.

   Maces and hammers are heavy impact weapons with solid heads designed to deliver powerful blows.

   Spears and polearms have long shafts and provide reach. Their heads may differ in shape depending on the weapon.

   Daggers and knives are small weapons suitable for close quarters and can be carried at the belt, in a sheath or in another practical location.

   Shields can vary in size, shape and construction. A shield may be round, kite-shaped, broad, small or heavily reinforced.

   Bows have visible wooden limbs, a grip and a string. A quiver may be worn on the back or at the side.

   Crossbows are compact ranged weapons with a stock, bow and string and require bolts carried separately.

   Scabbards, sheaths, straps and weapon belts should appear where appropriate. A sword normally has a practical way of being carried when not drawn.

   Equipment should occupy believable physical space. Large weapons may be carried across the back, at the side or in the hands depending on their shape and circumstances.

   Armor and weapons should not magically appear or disappear. If a character removes a helmet, drops a shield or loses a weapon, the change should persist until the item is recovered or replaced.

   Visual appearance does not automatically determine combat mechanics. Different-looking weapons or armor pieces may perform similarly, while visually similar equipment may have different practical properties.

   Appearance should remain consistent with the character's established equipment unless the RP provides a reason for a change.

   Do not describe equipment using game menus, cosmetic slots, skins, loadouts, rarity levels or numerical statistics.

   Describe visible details as part of the scene: metal catching the light, worn leather, scratched steel, muddy boots, a dented helmet, a torn tabard, a battered shield or a weathered sword.

   Equipment appearance can change through travel, weather, combat, maintenance, repairs and time.

   A soldier who has spent hours marching through mud may have dirty boots and stained clothing. A fighter who has just survived combat may have damaged armor, torn fabric and visible wear.

   Armor should fit the character's role and equipment. A heavily armored Knight should normally look substantially more protected than a lightly equipped Archer.

   Vanguards generally have a more mobile silhouette and may carry large two-handed weapons.

   Footmen generally have practical infantry equipment and may carry shields, one-handed weapons, spears or polearms.

   Archers generally carry bows or crossbows, ammunition and lighter equipment.

   Visual details should support the world rather than turning every description into an inventory list. Mention the most relevant visible details naturally during RP.

   Entry settings▾

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

1 file

• .jsonotherspec 3.0Download

  90.5 KB · first seen Nov 10, 2026 · 695e83a379ecd451