Avardon - User contributions [en]

Combat Rulings

2026-07-27T14:26:31Z

Rataj:

This is a collection of various rulings and clarifications regarding combat encounters. It is an extension to the rules with more detailed and in-depth explanations to bring some light into niche situations that might arise.

=== Line of Sight ===
Some abilities such as ranged attacks, or spells that mention "point you can see" or "target you can see" in their description, require sight.

You cannot target character if:
* You don't see at least 50% of their body or the entirety of their head from your first person view.
* Selector (such as with Magic Missile or Eldritch Blast) doesn't let you use it due to missing Line of Sight.
* You are Blinded or have both of your eyes Maimed.
* There is an area effect that restricts vision in between you and the target or at least one of you stands in it without being able to see through with special abilities.
* The target is Invisible and you lack the ability to see invisible creatures.

Additionally, AoE spells that target a point cannot be placed into areas that limit visibility, such as area of Darkness. You may only target the edge of such area, as that's as far as you can see.

==== Crouching ====

Conan mechanical crouch or other animations may not be used to avoid Line of Sight. You can still use animations and poses during combat, just not in a way to restrict LoS or when there's a discussion whether someone has LoS. The visibility rules apply for a standing character. The only exception is being Prone, in which case you should have a suitable animation even for purposes of determining LoS.

=== Observers ===
When a player chooses to observe a fight (having been present for its declaration and using <code>/pvp observe</code>), they are basically communicating to the other players upfront that their character either doesn't want to be involved with either side of the combat, or they are too scared to fight, or for any other reason refuse to fight. Observers are IC, and they chose NOT to fight under any change of circumstance. If they could ever possibly have a reason to join the fight, they have to either join it as an participant at the very beginning of the encounter, or leave the scene entirely. They cannot join into an ongoing fight or participate in the consequence phase or engage in another fight with the winning or losing party after the fight is concluded.

Also keep in mind, that any participant of the fight may void your decision to observe and include you as a target of their intent even and especially if they were the party being subject to a PvP intent, as per rule C.1:
<blockquote>Everyone within the range of a PvP intent is locked into the scene unless they are not targeted by anyone else within the scene lock</blockquote>

=== Doors ===
No player shall interact with doors during combat outside of using the Interact ability in RPR.

It takes an action to lock/unlock a door, a bonus action to open/close it, and an action with DC 15 to breach it, after which it becomes unusable for the duration of combat.

Breaching of a door in combat (and only in combat) is done using Breaching or Lockpicking skill (whichever is higher) or using the Spellcasting modifier in case of casters (if higher than the skills).

=== Hiding ===
Players may [[Hide]] in combat as long as none of their foes have Line of Sight on them - this is checked automatically but good etiquette is expected in case it wouldn't work reliably in all cases.

To reveal a player that is hiding during combat, players may use the Spot free action '''on their turn''', if they see the target.

Players may follow hidden or invisible foes, they still know of their approximate location and it is not considered metagaming.

=== Before Combat ===
As you find yourself in a scene with other players, especially if it may lead to combat, you are expected to act in good faith and let others react to your actions. The contrary would be powergaming.

This includes using any spells, buffs, drinking potions, swapping equipment, interacting with locked doors (or locking them), departing a scene, or entering or leaving a range of 1.5 tiles of another character.

All of these actions have to be emoted first, other players need to be given a chance to react to it. If they want to stop the action, they may also drop PvP intent and you can only proceed with that action on your turn of combat if you still wish to take that action.

Under no circumstances should anyone drink potions, cast buffs, or swap runes, unless others go a full round of emotes without responding to those attempted actions.

Players may also not take a Short Rest or Long Rest during a hostile scene. Refer to the tooltip for acceptable usage.

If a character declares PvP intent in order to halt movement, then the character attempting to move must return to their original position. This can also be used to prevent a character from leaving an active scene, but not to start one.

Drawing any weapons displayed on your character is considered a free action, and is not subject to being contested. The same applies for summoning a Pact Weapon (Pact of the Blade) or a Bonded Weapon (Eldritch Knight). However, switching from a weapon already in hand to another weapon would constitute an action. This only applies before and with PvP Intent, as during fight all of these would be actions.

Disguise Self

2026-07-26T14:26:11Z

Rataj:

{{Infobox Ability
| name = Disguise Self
| image = disguise_self.png
| caption =
| target = Self
| cost = 1 Action
| duration = 6 hours
| damage =
| saves = Investigation (Intelligence)
| level = 1
| school = Illusion
| description =
}}
You make yourself—including your clothing, armor, weapons, and other belongings on your person—look different until the spell ends or until you use your action to dismiss it. You can seem '''1 foot (30cm)''' shorter or taller and can appear thin, fat, or in between.

'''You can only assume a form of a playable race on Avardon and you may not impersonate other existing characters.'''

When using Disguise Self, your depiction of the race that you are disguising as must follow the appearance rules for that particular race. You may not Disguise Self into an elf with a tail. '''You may not Disguise Self to subvert the height rules for any given race''' (see the [[Height Chart]] for more details). If it wouldn't be allowed in whitelisting, it should not be used for Disguise Self. If a height range of the target race doesn't fall within 30cm of your height, you cannot disguise into that race.

The changes wrought by this spell fail to hold up to physical inspection. For example, if you use this spell to add a hat to your outfit, objects pass through the hat, and anyone who touches it would feel nothing or would feel your head and hair. If you use this spell to appear thinner than you are, the hand of someone who reaches out to touch you would bump into you while it was seemingly still in midair.

You can't change your body type, so you must adopt a form that has the same basic arrangement of limbs. Tails are an exception, you can hide it if you have one and the target race doesn't, or you can add it if the target race has one. This does also fail to physical inspection.

Weapons function similarly as described above. You cannot draw a disguised weapon, your own hand would phase through and you'd draw the real one. Otherwise, the extent of the illusion is up to you.

To discern that you are disguised, a creature can use its action to inspect your appearance and must succeed on an Intelligence (Investigation) check against your spell save DC using the Inspect ability.

<small>A failed Inspect roll will apply a global 20 minute cooldown, causing any follow-up attempts at discerning that you are disguised to fail automatically, even from other players.</small>

Disguise Self

2026-07-26T14:23:29Z

Rataj:

{{Infobox Ability
| name = Disguise Self
| image = disguise_self.png
| caption =
| target = Self
| cost = 1 Action
| duration = 6 hours
| damage =
| saves = Investigation (Intelligence)
| level = 1
| school = Illusion
| description =
}}
You make yourself—including your clothing, armor, weapons, and other belongings on your person—look different until the spell ends or until you use your action to dismiss it. You can seem '''1 foot (30cm)''' shorter or taller and can appear thin, fat, or in between.

'''You can only assume a form of a playable race on Avardon and you may not impersonate other existing characters.'''

When using Disguise Self, your depiction of the race that you are disguising as must follow the appearance rules for that particular race. You may not Disguise Self into an elf with a tail. '''You may not Disguise Self to subvert the height rules for any given race''' (see the [[Height Chart]] for more details). If it wouldn't be allowed in whitelisting, it should not be used for Disguise Self. If a height range of the target race doesn't fall within 30cm of your height, you cannot disguise into that race.

You can't change your body type, so you must adopt a form that has the same basic arrangement of limbs.

The changes wrought by this spell fail to hold up to physical inspection. For example, if you use this spell to add a hat to your outfit, objects pass through the hat, and anyone who touches it would feel nothing or would feel your head and hair. If you use this spell to appear thinner than you are, the hand of someone who reaches out to touch you would bump into you while it was seemingly still in midair.

Weapons function similarly as described above. You cannot draw a disguised weapon, your own hand would phase through and you'd draw the real one. Otherwise, the extent of the illusion is up to you.

To discern that you are disguised, a creature can use its action to inspect your appearance and must succeed on an Intelligence (Investigation) check against your spell save DC using the Inspect ability.

<small>A failed Inspect roll will apply a global 20 minute cooldown, causing any follow-up attempts at discerning that you are disguised to fail automatically, even from other players.</small>

Consequences

2026-07-23T23:11:16Z

Rataj:

== Minor Consequences ==
Minor consequences are mechanical consequences that may be applied at any time.

* '''Petty Theft''' - You may rob the target of up to 20 silver coins.
* '''Beating''' - Equivalent of throwing in some additional punches or kicks to the defeated. Dealing 1d4 wounds.

== Major Consequences ==
Major consequences are mechanical consequences that may only be applied if the winning party had at max +1 advantage in numbers (i.e. in 1v1 or 3v2, but not in 3v1 or 5v3), or if the PvP Intent was dropped by the smaller party against overwhelming force.

* '''Theft''' - You may rob the target of up to 50 silver coins.
* '''Battering''' - Equivalent of dealing some heavy blows to the defeated with intention to seriously harm. Dealing 2d8 wounds.
* '''Blood Letting''' - Filling a vial with blood of the defeated. Dealing 2 wounds and Bloodless condition for 8 hours.

== Escalated Consequences ==
Escalated consequences are mechanical consequences that may only be applied if the previous level of escalated consequence was already applied at least once by one of the victors against the defeated or by the defeated on one of the victors in previous fights (and at least one major consequence has to precede even the first escalated one) while also fulfilling the conditions for a major consequence.

Keep in mind that some of these consequences are drastic in nature and shall not be roleplayed in graphical detail without consent of everyone present in the scene. Use ''fade-to-black'' (FTB) when needed.

Escalated consequences are divided into levels, which must occur sequentially between the two parties over multiple instances of combat.

These levels are:
# '''Grievous Harm''' - Very serious beating of the defeated, leaving them severely injured. Dealing 5d6 wounds.
# '''Permanent Injury''' or '''Curse'''
#* '''Maiming''' - Mutilation, or disabling of a limb or an eye. Causing permanent [[Status_Effects#Maims|Maimed status]]. The victim has the right to choose disabling over removal. The victim will also get a Bloody Bundle item, that has to be handed over to the victor if requested. <br><small>[[maims|More information on healing maims]]</small></br>
#* '''Hexing''' - Putting the victim under one of available [[Curses]] (Work in progress, currently unavailable).
# '''Life Threatening Injury''' - Seriously harming the defeated, leaving them to possibly die (they won't, but the victors show intention of leaving them to fate). Dealing 10d6+10 wounds.
# '''Execution''' - ''Character Kill'' (CK), end of story. Only possible with prior staff approval. To get this approval, open a ticket proving escalations from both sides, or proving that the victim repeatedly showed signs of ''No Value of Life'' (NVL) when previous escalated consequences were enacted. Do not use this button unless instructed by staff. <br><small>[[#Character Kill|More information on Character Kills]]</small>

<small>'''''Example:''' To be able to apply Maim (2nd Level) to a character, I must have previously used Grievous Harm (1st Level) on that character in one of our past encounters or my target must have done that to me. Even prior to the first escalated consequence, one of us must have applied a major consequence on the other.''</small>

<small>[[#Flowchart|Flowchart of Consequences]]</small>

== Consented Consequences ==
Consented consequences are non-mechanical consequences that may be applied only if the losing party actively consents to such consequences.

This can be any roleplay consequence as long as the losing party actively consents.
Most common example would be holding the losing party hostage or interrogating them.
Keep in mind that consent can be withdrawn at any time, which ends the scene.

== Free Consequences ==
These consequences may be applied by the winning party and do not prevent another consequence from being applied.

* '''Unmasking''' - Removing an item of clothing, helmet, mask or other similar garment or item that obscures the face of the defeated character.

== Character Kill ==
Also known as CK (some might refer to it as PK - player kill, but please don't kill players), Character Kill is a permanent death of a character, their story ends. To reach this point as a consequence of conflict, all previous escalated consequences have to be documented (see the flowchart below) and have to either come from both sides, or if they are one-sided, the victim has to show signs of ''No Value of Life'' (NVL).

CK always has to be approved by staff ''prior'' to the final conflict in which CK may happen. The button must not be pressed under any other circumstances.

CK as a consequence is however not the only way your character may die. If you wish it yourself to end the life of your character, be it under the blade of another player, maw of a monster, or due to other causes, you may roleplay it, and open a reroll ticket afterwards, retiring your current character.

You cannot however offer a CK or pressure another player into a CK and they cannot just consent to it in the moment. All CKs done as an escalated consequence, including voluntary ones, require approval from staff in advance and have to follow the rules outlined above. But you are always free to reroll your character at the end of a scene without a formal CK.

== Flowchart ==
<gallery>
EscalatedConsFlowchart1.png|Part 1
EscalatedConsFlowchart2.png|Part 2
</gallery>

Consequences

2026-07-18T22:14:50Z

Rataj:

== Minor Consequences ==
Minor consequences are mechanical consequences that may be applied at any time.

* '''Petty Theft''' - You may rob the target of up to 20 silver coins.
* '''Beating''' - Equivalent of throwing in some additional punches or kicks to the defeated. Dealing 1d4 wounds.

== Major Consequences ==
Major consequences are mechanical consequences that may only be applied if the winning party had at max +1 advantage in numbers (i.e. in 1v1 or 3v2, but not in 3v1 or 6v3), or if the PvP Intent was dropped by the smaller party against overwhelming force.

* '''Theft''' - You may rob the target of up to 50 silver coins.
* '''Battering''' - Equivalent of dealing some heavy blows to the defeated with intention to seriously harm. Dealing 2d8 wounds.
* '''Blood Letting''' - Filling a vial with blood of the defeated. Dealing 2 wounds and Bloodless condition for 8 hours.

== Escalated Consequences ==
Escalated consequences are mechanical consequences that may only be applied if the previous level of escalated consequence was already applied at least once by one of the victors against the defeated or by the defeated on one of the victors in previous fights (and at least one major consequence has to precede even the first escalated one) while also fulfilling the conditions for a major consequence.

Keep in mind that some of these consequences are drastic in nature and shall not be roleplayed in graphical detail without consent of everyone present in the scene. Use ''fade-to-black'' (FTB) when needed.

Escalated consequences are divided into levels, which must occur sequentially between the two parties over multiple instances of combat.

These levels are:
# '''Grievous Harm''' - Very serious beating of the defeated, leaving them severely injured. Dealing 5d6 wounds.
# '''Permanent Injury''' or '''Curse'''
#* '''Maiming''' - Mutilation, or disabling of a limb or an eye. Causing permanent [[Status_Effects#Maims|Maimed status]]. The victim has the right to choose disabling over removal. The victim will also get a Bloody Bundle item, that has to be handed over to the victor if requested. <br><small>[[maims|More information on healing maims]]</small></br>
#* '''Hexing''' - Putting the victim under one of available [[Curses]] (Work in progress, currently unavailable).
# '''Life Threatening Injury''' - Seriously harming the defeated, leaving them to possibly die (they won't, but the victors show intention of leaving them to fate). Dealing 10d6+10 wounds.
# '''Execution''' - ''Character Kill'' (CK), end of story. Only possible with prior staff approval. To get this approval, open a ticket proving escalations from both sides, or proving that the victim repeatedly showed signs of ''No Value of Life'' (NVL) when previous escalated consequences were enacted. Do not use this button unless instructed by staff. <br><small>[[#Character Kill|More information on Character Kills]]</small>

<small>'''''Example:''' To be able to apply Maim (2nd Level) to a character, I must have previously used Grievous Harm (1st Level) on that character in one of our past encounters or my target must have done that to me. Even prior to the first escalated consequence, one of us must have applied a major consequence on the other.''</small>

<small>[[#Flowchart|Flowchart of Consequences]]</small>

== Consented Consequences ==
Consented consequences are non-mechanical consequences that may be applied only if the losing party actively consents to such consequences.

This can be any roleplay consequence as long as the losing party actively consents.
Most common example would be holding the losing party hostage or interrogating them.
Keep in mind that consent can be withdrawn at any time, which ends the scene.

== Free Consequences ==
These consequences may be applied by the winning party and do not prevent another consequence from being applied.

* '''Unmasking''' - Removing an item of clothing, helmet, mask or other similar garment or item that obscures the face of the defeated character.

== Character Kill ==
Also known as CK (some might refer to it as PK - player kill, but please don't kill players), Character Kill is a permanent death of a character, their story ends. To reach this point as a consequence of conflict, all previous escalated consequences have to be documented (see the flowchart below) and have to either come from both sides, or if they are one-sided, the victim has to show signs of ''No Value of Life'' (NVL).

CK always has to be approved by staff ''prior'' to the final conflict in which CK may happen. The button must not be pressed under any other circumstances.

CK as a consequence is however not the only way your character may die. If you wish it yourself to end the life of your character, be it under the blade of another player, maw of a monster, or due to other causes, you may roleplay it, and open a reroll ticket afterwards, retiring your current character.

You cannot however offer a CK or pressure another player into a CK and they cannot just consent to it in the moment. All CKs done as an escalated consequence, including voluntary ones, require approval from staff in advance and have to follow the rules outlined above. But you are always free to reroll your character at the end of a scene without a formal CK.

== Flowchart ==
<gallery>
EscalatedConsFlowchart1.png|Part 1
EscalatedConsFlowchart2.png|Part 2
</gallery>

Rules

2026-07-18T21:50:10Z

Rataj:

Hello there! We are glad that you are responsible and will dedicate a few minutes to read our rules.

Please don't just skip through the rules.
We want to keep our server friendly and immersive, prevent any possible attempts to spoil the game, and create a pleasant environment for '''all''' players to enjoy.
If you don't understand something, don't be afraid to ask us on [https://avardon.com/discord Discord] and we'll be more than happy to help you out.

At the same time we try to keep our rules concise and we rely on '''common sense''' of our players. These rules are not supposed to be exhaustive and all-encompassing. We expect our players to avoid any behavior such as ''rule-lawyering'' or acting against good faith and outside of the standards of our community, even if it doesn't break any specific rule outlined on this page.

We also want to make it very clear that no one is exempt from these rules. The rules apply equally to staff and players. In fact, staff members are under higher scrutiny to lead the community by example.

== Community Rules ==
=== M.1 - Server Culture ===
Avardon is an open and welcoming community founded on the expectation, that we treat each other as adults and as if we were all playing at a single table at a friend's house. We expect all players to recognize their peers as partners in collaborative writing and respect them as equals. [[Play-to-Lift]] mentality is expected, not optional.

Harassment, discrimination, or toxicity of any kind is absolutely unacceptable and has no place in our community. We want this community to be a place for you and for us to love coming back to.

=== M.2 - Adults Only ===
This server is only available to those of adult age (18+), who are also mature enough to not make us doubt it.

No representation of child or child-like characters is allowed. All characters must be at least the adult age for their respective species '''and''' also at least 20 years old. Portrayal of pregnancy is also not allowed.

=== M.3 - English Only ===
Avardon is an English speaking community, the sole language to be used in roleplay, tickets, and on any of our official channels is English.

Characters are allowed to use terms from other D&D languages (or suitable real-world languages in the case of regional dialects) as long as it is used sparsely for flavor, and other players whose characters know the language mechanically are helped to understand the phrase you used should they ask. You may not write entire sentences in these flavored languages, nor should you roleplay as knowing and speaking a language that is not included in our server's system. Please also avoid using terms that are too modern, such as internet slang.

=== M.4 - Dispute Resolution ===
If you find yourself in a dispute with another player, try to cooperate and resolve it together. However, do not argue and do not attempt to enforce rules yourself, rather let us know through a ticket. You shall never threaten anyone with a moderation action nor with a ticket.

Do not freeze roleplay to wait for staff involvement, keep the scenes rolling. An exception to this rule is if your consent is violated. In such a case, you may remove yourself from the scene at any time to ensure your personal comfort.

You may not attempt to 'shop' for staff to achieve a desired ruling or outcome of a ticket. Staff are trusted to be impartial. If you feel staff was not impartial in your ticket you may open a staff report.

== Roleplaying Rules ==
=== R.1 - Character Creation ===
All players must follow and complete the whitelisting process before engaging in roleplay on the server. You are expected to follow the guidance provided by staff in your whitelisting ticket.

Characters are expected to follow the server lore in both their behavior and visuals. Please refer to the corresponding [[Races|race]] page for average height and other requirements. Characters should originate either from Toril or the Domains of Dread, including Avardon. Allowable exceptions are the Feywilds (Satyr, Eladrin) and Shadowfell (Shadar-Kai) if appropriate for the character race.

Once your whitelist is approved, you may only make realistic changes to the design of your character, such as changing hair style and warpaints. Your body and face should remain the same.

The depiction of your character should reflect your character sheet and equipment runes. Do not depict or roleplay abilities or equipment your character does not have.

=== R.2 - Roleplay Etiquette ===
When not in the spawn area, you are always considered to be ''In Character'' and should try your best to contribute to the immersive narrative experience with other players. While the concept of good etiquette may be difficult to define exhaustively, we expect you to at the very least:
* Minimize OOC chatter during roleplay scenes.
* React appropriately to the use of social rolls.
* Respect the agency of other players, do not force your actions on them without letting them react (powergaming).
* Do not play omniscient characters. Your character does not have access to an online wiki. Minimise the knowledge of your character to what they reasonably know, and do not 'lore-dump' information on other players.
* Take responsibility in being courteous and understanding towards players even if OOC tension arises. Step away if necessary.
* Respect and value the life of your own character, ensuring that they act in a way that best suits the situation (especially when they are in mortal danger, or at the mercy of another character).

=== R.3 - Metagaming ===
You are not allowed to take ''In Character'' actions based on knowledge you obtained as a player ''Out of Character''. This is known as ''metagaming'' and is strictly forbidden on Avardon.

You should also avoid sharing any information OOC that could influence stories if acted upon IC. Especially if it relates to instances of on-going or very recent combat, details about other characters or their actions. Use common sense, don't ruin stories by enabling others to ''metagame''.

It is important to maintain an immersive atmosphere where players are mostly only aware of what their character would know. Therefore, when in any doubt at all, do not share meta-knowledge with other players.

However, there are exceptions to this rule. You are allowed to share adventures of your own character, and discuss non-actionable things that have happened in the game. You can also look for roleplay and schedule roleplay through OOC means.

=== R.4 - Consent Sheets ===
Players are encouraged to create a consent sheet in their RPR profile to show what themes they are not comfortable with. It is the responsibility of every player to be aware of consent preferences of other players in a scene, as to not violate consent.

When unsure of a particular sensitive theme, the player wanting to initiate this theme is responsible for communicating to all players involved to confirm their approval, as violating preferences due to ignorance will never be excused.

Sensitive themes include, but are not limited to: graphical descriptions of gore, surgeries, torture, mutilation, self harm, and anything of erotic or sexual nature, especially rape (including the mention of).

Be aware that consent sheets cannot be abused to avoid mechanical consequences, and it is the right of any player to request a ''fade-to-black'' (FTB) when wanting to carry out a sensitive topic but not wanting to write out the details of it.

When a player becomes part of a scene which does not conform to their consent sheet and where they are not a main actor, that player is to be given a chance to depart the scene without undue delay.

Players are not allowed to leave feces or any bodily fluids (with exception of blood) in POIs.

=== R.5 - Adult Content ===
While we allow the depiction of adult content (such as nudity and erotic roleplay) on our server, we expect players to do so in responsible manner.

Nudity is not allowed in main hub areas (with exception of player-owned houses). Characters are required to at the very least cover their genitals and breasts.

Scenes depicting sexual themes must take place in a private setting where it may be reasonably assumed that no other players may accidentally stumble upon them.

All scenes of this nature that could be considered non-consensual or dubious in any way require OOC consent that can be withdrawn at any time, allowing players to stop and even void such scene.

Interest in any sexual themes may not be advertised through consent sheets, character profiles, or global chat.

=== R.6 - Act Names ===
Players may use the <code>/act</code> command to change their display name in order to use an alias or conceal their identity, but must not use a name of another character, or one that impersonates them, including names of NPCs.

=== R.7 - LFRP Etiquette ===
When using the Looking for Roleplay functionality on the in-game map, players are expected to follow these guidelines:
* Disable your marker when your scene is locked (PvP intent is dropped).
* Do not approach LFRP marker promoting Solo/Duo/Trio with more than equal number of players if your intention is to take hostile actions.
* Do not use the Solo/Duo/Trio tags in a misleading way. It has to reflect the amount of people present in a scene. These tags also shouldn't be used to deliberately shield yourself against unfair odds when at your base.

Keep in mind the intention of this rule: LFRP etiquette exists to prevent large groups from metagaming information displayed on LFRP markers to secure unfair advantage in combat. LFRP in general serves as a tool to find roleplay, new contacts, new stories and start some narrative.

== Game Rules ==
=== G.1 - Bugs, Cheating, Exploits ===
It may occur that bugs appear in our systems such as the combat or economy related scripts. We expect players to collaborate with the staff team in spotting and mitigating these bugs by reporting them in a timely manner.

We have zero tolerance policy for cheating, exploiting bugs and security vulnerabilities, abusing and misusing systems or enacting DDoS attacks and similar malicious actions.

=== G.2 - Always in a Clan ===
Every player has to be in a clan at all times. Even if they play solo. Any buildings not belonging to a clan will get deleted.

=== G.3 - Showing Equipment ===
Your worn armor and all weapons you intend to use have to be properly shown on your character design (utilizing Tot Custom).

You may not use any weapon in combat that your character isn't visually carrying (exceptions apply, such as pact weapons).

=== G.4 - Climbing ===
You may not climb onto structures, terrain, or other obstacles to enter or leave a clan base without using the Climb or Misty Step ability in RPR. Descending walls or terrain also requires using the Climb ability.

== Building Rules ==
=== B.1 - Building Limits ===
Every clan may only have one base (with exception of '''temporary''' camps).

Do not build beyond boundaries of the map or under terrain.

Main entrance of any build must be accessible without climbing.

Build at least '''50 tiles''' from a base of another clan, 100 tiles from the main hubs, and 50 tiles from any public portal.

Exception to the above are decoration pieces (no buildings) in Durana Gate, as you are allowed to live there, and even if you don't live there, you can put down a mailbox in this town (one per clan).

You may not build inside base game dungeons (caves are allowed, when in doubt ask in a ticket). Special exception is the Wine Cellar dungeon, in which you may build and also the rule of base distances doesn't apply.

Land claim of your build should be proportionate to your clan size, it is not allowed to claim large area with sparsely placed building pieces.

Your build has to reasonably fit the setting and cannot be immersion breaking.

Always stay within the following limits:
{| class="wikitable"
! Players !! Building Pieces !! Decorations
|-
| 1 || 500 || 200
|-
| 2-3 || 800 || 400
|-
| 4-5 || 1500 || 600
|-
| 6-9 || 2500 || 1000
|-
| 10+ || 3500 || 1500
|}
Additionally, no clan should have more thralls/mounts than players.

These limits can be increased with donator building extensions.

=== B.2 - Performance Considerations ===
All clans have to keep server and client performance in mind when building their bases. Do not overuse trees, containers (decorations with inventory) and custom textures, do not put too many light sources close together. Build responsibly.

=== B.3 - Inactivity ===
Players that have been inactive for more than '''30''' days may be removed from their clan by our system. If the inactive player is a clan owner, their build will be transferred to active members or removed.

Builds that violate other rules (such as building limits) while also belonging to an inactive clan may be removed sooner, after 14 days since any member was last online, or 7 days since being brought into a build audit ticket.

=== B.4 - Fair Defense ===
Clans may not stack doors to hide from conflict. Any common area where clan members usually spend time has to be accessible through the maximum of 2 locked doors/gates from outside of the base. Unlocked doors may be reasonably used in addition. Private rooms can be more secured.

== Combat Rules ==
=== C.1 - Scene Lock ===
Once PvP is declared (intent has been dropped using <code>/pvp</code>), the scene is locked and no further players shall join the scene until the consequence phase is over. Everyone within the range of a PvP intent is locked into the scene unless they are not targeted by anyone else within the scene lock, in that case they can either join, leave or observe (declared using <code>/pvp observe</code>). Any player that stumbles upon the scene while it's locked has to leave the area immediately and isn't allowed to watch. Those players cannot roleplay witnessing anything they saw in the locked scene.

Exception from this rule are spars, tournaments, arena fights and friendly brawls, these do not lock the scene and people are free to come and go.

Once a scene is unlocked after the conclusion of consequences, all participants of the scene must be allowed to leave the area without being subject to any subsequent combat encounters.

No size of any group in combat may exceed 5. The total cap for any PvP is always 10 players.

=== C.2 - Combat Etiquette ===
As combat scenes tend to have high tension, it is especially important to be cordial to other players when you fight their characters. While the concept of good etiquette may be difficult to define exhaustively, we expect you to at the very least:
* Act in a friendly and respectful manner in OOC towards your IC foes (they're your fellow storytellers, not your enemies).
* Make sure your conflict has story, roleplay has to precede and follow a combat scene. PvP systems exist as a conflict resolution, to help you progress narrative.
* Emote only outside of your turn, ideally ''after''.
* Try to be swift with your turns, do not prolong combat with micro-optimizations or OOC arguments.
* Help new players and those who don't fight often, answer their questions, and be patient with them.
* Follow the official [[Combat Rulings]] in all niche cases we provided additional clarifications for.

=== C.3 - Consequences ===
The winning party may impose consequences on the losing party after a fight is concluded. While delivering those consequences, players are in a consequence phase.

This phase is only protected for 3 rounds of emotes (each player may write 3 posts), during which the consequences have to be decided and carried out (unless both parties agree on extending the scene lock for up to 1 hour since end of combat). If consequences take longer time than that, the scene is no longer locked and other players may interact with it. Players may move during consequence phase within radius of 20 tiles. Should they move further, the consequence phase and scene lock ends.

We differentiate four categories of consequences:
* Minor consequences are mechanical consequences that may be applied at any time.
* Major consequences are mechanical consequences that may only be applied if the winning party had at max +1 advantage in numbers (i.e. in 1v1 or 3v2, but not in 3v1 or 5v3), or if the PvP Intent was dropped by the smaller party against overwhelming force.
* Escalated consequences are mechanical consequences that may only be applied if the previous level was already applied at least once by one of the victors against the defeated or by the defeated on one of the victors in previous fights (and at least one major consequence has to precede even the first escalated one) while also fulfilling the conditions for a major consequence.
* Consented consequences are non-mechanical consequences that may be applied only if the losing party actively consents to such consequences.

Keep in mind that any thievery consequences may be applied from you on a specific target only once per 24 hours. In other words, you may not rob the same person again after already doing so within the last 24 hours.

Only one consequence shall be applied on a character. Consequence stacking is not allowed.

Unmasking is not considered a consequence and can be done freely on the defeated party after combat.

All possible consequence options are listed in the [[Consequences|guide to consequences]].

=== C.4 - Mugging ===
You may mug someone and it may (or may not) be reasonable for the target character to give up their belongings without a fight. However same rules as with PvP consequences apply. Players can only take what consequences rules would allow them as if a fight was taking a place. If the target complies and PvP takes place anyway, the attackers shall not deliver any further consequences.

=== C.5 - Limits on Hostile Actions ===
While hostile actions are major and important part of our server, there are some limitations to when and where you may perform them.

Hostile actions include but are not limited to: combat, thievery, mugging, attempts to restrict, restrain, or forcefully hold a person, but also threats, harassment, intimidation, provocation, and any other acts that would likely lead to combat.

You may not perform hostile actions when:
* You are in a PvP restricted area (Livarun or Scarabend).
* You are within 20 tile radius of a public waypoint.

Combat Rulings

2026-07-18T19:22:54Z

Rataj: added interaction with locked doors as action

This is a collection of various rulings and clarifications regarding combat encounters. It is an extension to the rules with more detailed and in-depth explanations to bring some light into niche situations that might arise.

=== Line of Sight ===
Some abilities such as ranged attacks, or spells that mention "point you can see" or "target you can see" in their description, require sight.

You cannot target character if:
* You don't see at least 50% of their body or the entirety of their head from your first person view.
* Selector (such as with Magic Missile or Eldritch Blast) doesn't let you use it due to missing Line of Sight.
* You are Blinded or have both of your eyes Maimed.
* There is an area effect that restricts vision in between you and the target or at least one of you stands in it without being able to see through with special abilities.
* The target is Invisible and you lack the ability to see invisible creatures.

Additionally, AoE spells that target a point cannot be placed into areas that limit visibility, such as area of Darkness. You may only target the edge of such area, as that's as far as you can see.

==== Crouching ====

Conan mechanical crouch or other animations may not be used to avoid Line of Sight. You can still use animations and poses during combat, just not in a way to restrict LoS or when there's a discussion whether someone has LoS. The visibility rules apply for a standing character. The only exception is being Prone, in which case you should have a suitable animation even for purposes of determining LoS.

=== Observers ===
When a player chooses to observe a fight (having been present for its declaration and using <code>/pvp observe</code>), they are basically communicating to the other players upfront that their character either doesn't want to be involved with either side of the combat, or they are too scared to fight, or for any other reason refuse to fight. Observers are IC, and they chose NOT to fight under any change of circumstance. If they could ever possibly have a reason to join the fight, they have to either join it as an participant at the very beginning of the encounter, or leave the scene entirely. They cannot join into an ongoing fight or participate in the consequence phase or engage in another fight with the winning or losing party after the fight is concluded.

Also keep in mind, that any participant of the fight may void your decision to observe and include you as a target of their intent even and especially if they were the party being subject to a PvP intent, as per rule C.1:
<blockquote>Everyone within the range of a PvP intent is locked into the scene unless they are not targeted by anyone else within the scene lock</blockquote>

=== Doors ===
No player shall interact with doors during combat outside of using the Interact ability in RPR.

It takes an action to lock/unlock a door, a bonus action to open/close it, and an action with DC 15 to breach it, after which it becomes unusable for the duration of combat.

Breaching of a door in combat (and only in combat) is done using Breaching or Lockpicking skill (whichever is higher) or using the Spellcasting modifier in case of casters (if higher than the skills).

=== Hiding ===
Players may [[Hide]] in combat as long as none of their foes have Line of Sight on them - this is checked automatically but good etiquette is expected in case it wouldn't work reliably in all cases.

To reveal a player that is hiding during combat, players may use the Spot free action '''on their turn''', if they see the target.

Players may follow hidden or invisible foes, they still know of their approximate location and it is not considered metagaming.

=== Before Combat ===
As you find yourself in a scene with other players, especially if it may lead to combat, you are expected to act in good faith and let others react to your actions. The contrary would be powergaming.

This includes using any spells, buffs, drinking potions, swapping equipment, interacting with locked doors (or locking them), departing a scene, or entering or leaving a range of 1.5 tiles of another character.

All of these actions have to be emoted first, other players need to be given a chance to react to it. If they want to stop the action, they may also drop PvP intent and you can only proceed with that action on your turn of combat if you still wish to take that action.

Under no circumstances should anyone drink potions, cast buffs, or swap runes, unless others go a full round of emotes without responding to those attempted actions.

Players may also not take a Short Rest or Long Rest during a hostile scene. Refer to the tooltip for acceptable usage.

If a character declares PvP intent in order to halt movement, then the character attempting to move must return to their original position. This can also be used to prevent a character from leaving an active scene, but not to start one.

Drawing any weapons represented by currently equipped runes that are also displayed on your character is considered a free action, and is not subject to being contested.

Hunting

2026-07-17T04:45:44Z

Rataj:

{{Stub}}

Hunters are able to obtain hides and animal fat by hunting game in any of the hunting grounds. They can also hunt monsters in the [[Infested Ruins]] for more exotic resources.

== Items ==
* [[Hide]]
* [[Animal Fat]] (33% chance from 20+ XP)
===Infested Ruins===
* [[Hook]]
* [[Hyena Ear]]
* [[Giant Finger]]

Consequences

2026-07-16T15:57:17Z

Rataj: added clarifications on CKs

== Minor Consequences ==
Minor consequences are mechanical consequences that may be applied at any time.

* '''Petty Theft''' - You may rob the target of up to 20 silver coins.
* '''Beating''' - Equivalent of throwing in some additional punches or kicks to the defeated. Dealing 1d4 wounds.

== Major Consequences ==
Major consequences are mechanical consequences that may only be applied if the winning party had at max +1 advantage in numbers (i.e. in 1v1 or 3v2, but not in 3v1 or 6v3).

* '''Theft''' - You may rob the target of up to 50 silver coins.
* '''Battering''' - Equivalent of dealing some heavy blows to the defeated with intention to seriously harm. Dealing 2d8 wounds.
* '''Blood Letting''' - Filling a vial with blood of the defeated. Dealing 2 wounds and Bloodless condition for 8 hours.

== Escalated Consequences ==
Escalated consequences are mechanical consequences that may only be applied if the previous level of escalated consequence was already applied at least once by one of the victors against the defeated or by the defeated on one of the victors in previous fights (and at least one major consequence has to precede even the first escalated one) while also fulfilling the conditions for a major consequence.

Keep in mind that some of these consequences are drastic in nature and shall not be roleplayed in graphical detail without consent of everyone present in the scene. Use ''fade-to-black'' (FTB) when needed.

Escalated consequences are divided into levels, which must occur sequentially between the two parties over multiple instances of combat.

These levels are:
# '''Grievous Harm''' - Very serious beating of the defeated, leaving them severely injured. Dealing 5d6 wounds.
# '''Permanent Injury''' or '''Curse'''
#* '''Maiming''' - Mutilation, or disabling of a limb or an eye. Causing permanent [[Status_Effects#Maims|Maimed status]]. The victim has the right to choose disabling over removal. The victim will also get a Bloody Bundle item, that has to be handed over to the victor if requested. <br><small>[[maims|More information on healing maims]]</small></br>
#* '''Hexing''' - Putting the victim under one of available [[Curses]] (Work in progress, currently unavailable).
# '''Life Threatening Injury''' - Seriously harming the defeated, leaving them to possibly die (they won't, but the victors show intention of leaving them to fate). Dealing 10d6+10 wounds.
# '''Execution''' - ''Character Kill'' (CK), end of story. Only possible with prior staff approval. To get this approval, open a ticket proving escalations from both sides, or proving that the victim repeatedly showed signs of ''No Value of Life'' (NVL) when previous escalated consequences were enacted. Do not use this button unless instructed by staff. <br><small>[[#Character Kill|More information on Character Kills]]</small>

<small>'''''Example:''' To be able to apply Maim (2nd Level) to a character, I must have previously used Grievous Harm (1st Level) on that character in one of our past encounters or my target must have done that to me. Even prior to the first escalated consequence, one of us must have applied a major consequence on the other.''</small>

<small>[[#Flowchart|Flowchart of Consequences]]</small>

== Consented Consequences ==
Consented consequences are non-mechanical consequences that may be applied only if the losing party actively consents to such consequences.

This can be any roleplay consequence as long as the losing party actively consents.
Most common example would be holding the losing party hostage or interrogating them.
Keep in mind that consent can be withdrawn at any time, which ends the scene.

== Free Consequences ==
These consequences may be applied by the winning party and do not prevent another consequence from being applied.

* '''Unmasking''' - Removing an item of clothing, helmet, mask or other similar garment or item that obscures the face of the defeated character.

== Character Kill ==
Also known as CK (some might refer to it as PK - player kill, but please don't kill players), Character Kill is a permanent death of a character, their story ends. To reach this point as a consequence of conflict, all previous escalated consequences have to be documented (see the flowchart below) and have to either come from both sides, or if they are one-sided, the victim has to show signs of ''No Value of Life'' (NVL).

CK always has to be approved by staff ''prior'' to the final conflict in which CK may happen. The button must not be pressed under any other circumstances.

CK as a consequence is however not the only way your character may die. If you wish it yourself to end the life of your character, be it under the blade of another player, maw of a monster, or due to other causes, you may roleplay it, and open a reroll ticket afterwards, retiring your current character.

You cannot however offer a CK or pressure another player into a CK and they cannot just consent to it in the moment. All CKs done as an escalated consequence, including voluntary ones, require approval from staff in advance and have to follow the rules outlined above. But you are always free to reroll your character at the end of a scene without a formal CK.

== Flowchart ==
<gallery>
EscalatedConsFlowchart1.png|Part 1
EscalatedConsFlowchart2.png|Part 2
</gallery>

Farkas de Brasov

2026-07-09T20:09:00Z

Rataj:

{{infobox character
| name=Farkas de Brasov
| image=Farkas.jpg
| caption=Count Farkas on his throne
| othernames=The Reckoner
| titles=Count of Avardon
| position=Darklord
| location=[[Castle Valemoor]]
| birth=1365
| birthlocation=[[Livarun]]
| rule=1395 - Present day
| house=[[House de Brasov|de Brasov]]
| family=
| parentage=[[Gabor de Brasov]]
| siblings=[[Istvan de Brasov]]
| spouse=[[Valeria de Brasov]]
| children=[[Ilona de Brasov|Ilona]], [[Katalin de Brasov|Katalin]], [[Reka de Brasov|Reka]]
| gender=Male
}}

'''Farkas de Brasov''' is the current ''Count of Avardon'', and the Darklord of our setting.

He is the first son and only surviving child of [[Gabor de Brasov]].

The Count rules over the entirety of [[Avardon]] from his castle mostly through the [[Comital Court]] that puts his will into motion.

== Early life ==
Farkas was born in [[Livarun]], the capital city of Avardon. His father was distant, raising him with high expectations to prepare the oldest son to eventually take the reins of the county.

== Early career ==
As was a tradition with young future rulers of the family, Farkas was trained in combat and in the strategy of war. Often sent out with a small regiment to settle quarrels between Viscounts and Barons, but even to deal with bandits and raiders.

Once he was approaching adult age, Farkas even led a small army in defense of no longer existing town of [[Coalfort]], and also led diplomatic delegations to the east to strengthen alliances including one with Zhentil Keep where he first met his future wife [[Valeria de Brasov|Valeria]].

=== Anauroch Campaign ===
Together with his father and brother, Farkas was part of the ''Anauroch Campaign'', an effort to push back against Bedine tribes that repeatedly attempted to besiege and claim [[Durana Gate]] and the nearby salt mines.

The campaign was a great success at first, clearing camps and fortifications at the border of Anauroch, even pushing far into the desert.

In the year 1388 DR, [[Gabor de Brasov|Count Gabor]] fell in battle, deep in the Anauroch desert. Farkas and [[Istvan de Brasov|Istvan]] decided not to send a message home and finish the campaign first.

While Farkas' brother gets injured in the subsequent battle and travels back home, rival [[House Steinberg]] has already put a plan in motion, announcing death of the Count to the people of Avardon along with a false report of both sons falling too. Based on records of old claims, [[Malzahin Steinberg]] becomes the new ruler of Avardon, ending the long rule of [[House de Brasov|de Brasov]] family.

Farkas learned of this treachery from a runner sent by Istvan, making him end the campaign and lead the remnants of the army back home only to find out his brother was slain and his own life is in danger as well.

== Hero of the People ==
Rule of Malzahin wasn't popular among the commonfolk, but Steinbergs managed to secure firm control over the army with help of many minor noble houses that were happy to buy more land or positions they were unable to get during Gabor's rule. Support of the new ruler was rising among the rich who saw opportunities in this change.

Farkas knew he had to play it safe, hiding among the people, proving to them that he was not only the rightful heir but also a ruler that would truly care. At first, most didn't care to risk their lives in support of Farkas. After all, they had no idea whether he would be at least half as great of a ruler that his father was.

And so began Farkas' mission of proving himself to the people. He traveled across the land, helping regular people and spreading the word of his mission. Sometimes even risking his own life in heroic deeds for the poor. These acts wouldn't go unnoticed. Nobles and soldiers that served his father joined in support, giving faith to many that joined their rebellion.

In summer of 1395 DR, rabble of unbelievable amount of commoners followed Farkas marching with his soldiers towards [[Castle Valemoor]]. The war that ensued was swift and brutal, but Farkas finally claimed a throne that was rightfully his, and Malzahin was imprisoned.

== Ruler of Avardon ==
People celebrated the victory of Farkas and the beginning of his rule, naming him ''Count Farkas de Brasov the Reckoner''. During months that followed, the new Count didn't act too hastily, he slowly undermined power of Steinbergs while showing benevolence, ruling to true satisfaction of the commonfolk.

Two years of the golden era of Farkas' rule passed, putting minds at ease as the beloved Count was exactly what everyone wished for. Perhaps he was even too good and a little shortsighted, spending so much on present well-being of his subjects with little regard for the future debts. It would be a forgivable mistake if it wasn't for his later acts.

After his second daughter was born in 1397 DR, Farkas was known among the noble circles for his frustration about this 'misfortune' and his desire and obsession with having a son. Avardon historically followed tradition of agnatic primogeniture (male only succession with the oldest son inheriting all titles) and while Farkas could've changed this rule and even did so later in life, at this point in time he was obsessed with keeping the tradition and considering it a great failure and shame if he would fail to do so. Despite being so beloved, this obsession was the hottest rumor among the nobles, and Farkas was commonly mocked for it, especially by Steinbergs who were also strict traditionalists.

In response to this mockery, Farkas went for an unusual punishment, ordering his court wizard to create a disease that would render victims infertile. Secretly spreading this disease among Steinbergs and other prominent houses that could put his rule at risk in the future. This would've not been known until much later, when [[Monvarin]] who created this disease had regrets and revealed the truth. Giving us glimpse into the past, as Farkas' growing paranoia and obsession of securing his rule and legacy led to gruesome acts even before the more widely known terrible deeds.

Farkas could never forgive the treachery of Steinbergs and he was growing paranoid of the possibility of their future attempts at stealing the holdings from his family, he was also impatient to see results of his earlier idea with the disease. A decree was issued, ordering the killing of Steinbergs including their young, an utter destruction of the house and confiscation of their properties. His own court and generals were shocked by the inclusion of children in the decree and some even refused to follow the order to the letter, letting most children escape.

During the following years, Farkas' madness didn't stop and only strengthened just as his rule. Finding out that some Steinbergs survived, he lost trust in the loyalty of his own men and leaned even more into the use of diseases and magic to control his population. Many times was his rule challenged, making him only stricter and more paranoid. From beloved leader became a feared and cruel lord, yet still respected by many just as he is to this day.

== Darklord ==
The terror that the Count caused sometimes backfired, such as when he caught the earliest disease himself, making him infertile and having his pregnant wife be his last chance at having a son.

Once his third daughter, [[Reka de Brasov]] is born, Farkas goes in frenzy and murders his own wife in fit of rage. An act witnessed by his oldest daughter but also by the [[Dark Powers]].

It was at this point that [[Avardon]] became a domain of dread, an eternal purgatory for Farkas to mockingly reflect his evil acts and keep him imprisoned in what he still believes to be his almost ideal land.

With mists on the borders and without trade, the region falls into poverty and famine, and civil wars ensue. But the Count's power is unprecedented and with his rule of iron fist, he easily puts everyone in line. Monsters are created to follow Farkas' orders, one of which is simply to keep people on their toes. Busy fighting the monsters, most don't gather enough power to ever challenge the Count.

Only the daughters are given free reign in regards of gathering power, which they mostly use to fight one another over influence and succession as Farkas seems calm and victorious. Divide and conquer is the chosen tactic now, as it ensures no one can threaten the Count.

Gabor de Brasov

2026-07-09T20:05:09Z

Rataj:

{{infobox character
| name=Gabor de Brasov
| image=
| caption=
| othernames=
| titles=Count of Avardon
| position=
| location=
| birth=1346
| birthlocation=[[Livarun]]
| rule=1367 - 1388
| death=1388
| deathlocation=Anauroch
| age=42
| notablefor=
| house=[[House de Brasov|de Brasov]]
| family=
| parentage=
| siblings=
| spouse=
| children=[[Farkas de Brasov|Farkas]], [[Istvan de Brasov|Istvan]]
| gender=Male
| height=
| hair=
| eyes=
}}

'''Gabor de Brasov''' was never the kind of man who had to shout to command a room. People listened because he spoke with confidence and carried himself with a calm sort of authority. He ruled [[Avardon]] in much the same way. In a place where rival houses were always looking for weakness, that steadiness meant a great deal.

Before he ever became '''Count''', ''Gabor'' learned that survival was about more than strength. It took patience, clear judgment, and knowing when to act and when to wait. By the time he came to power, he was a careful and practical ruler who liked to deal with problems before they had the chance to grow. [[Avardon]] did not become glorious under his rule, but it stayed secure. Trade continued, the borders held, and the people were spared the worst of disorder.

''Gabor'' believed in order and discipline, though he was never needlessly cruel. He upheld the law firmly, but with restraint, and cared more for respect than affection. He did not need to be loved, only to be taken seriously. He believed loyalty should come from trust in a ruler’s consistency, not from fear. For a while, that was enough. His court stayed in line, his generals did their duty, and his rivals thought carefully before making a move. Even so, ''Gabor'' understood how fragile power could be. He watched rival houses closely and never allowed himself to grow too comfortable. He often believed that power was not something a man truly possessed, only something he managed to hold for a time. It was a lesson he passed on to [[Farkas de Brasov|Farkas]], though maybe not in the way he likely intended.

As a father, ''Gabor'' was distant. He was not openly cruel, but warmth did not come easily to him. He raised [[Farkas de Brasov|Farkas]] with high expectations rather than affection. Praise was rare, usually no more than a nod or a few words, while correction came often. In ''Gabor’s'' mind, this was how a ruler was shaped. He taught his son duty, discipline, and the burden of legacy, but he did not teach him how to carry the burdens of such a position. Above all else, ''Gabor'' cared about the future of '''House de Brasov'''. Nearly every decision he made came back to preserving what his family had built and ensuring it would endure after him. He believed that was the true duty of any ruler. It was a burden he accepted without complaint, and one he placed on Farkas long before the boy was truly ready to bear it.

When ''Gabor'' died, [[Avardon]] lost the man who had quietly held much of it together. The order he maintained began to weaken almost at once, and [[House Steinberg]] moved quickly to seize the advantage. It was not that ''Gabor'' had built something frail but it relied heavily upon his strength and personality. What he left behind was a son who learned his lessons, but not his restraint. The caution ''Gabor'' had carried became something harsher in his son, and discipline slowly turned into obsession.

In the end, '''Gabor de Brasov''' was remembered as a good ruler. Not a legendary one, and not the sort of man whose name would live on in songs, but a steady lord who kept his land together in a world always threatening to tear it apart.

Reka de Brasov

2026-07-09T19:58:55Z

Rataj: Created page with "{{infobox character | name=Reka de Brasov | image= | caption= | othernames= | titles= | position=Daughter of the Darklord | location=Unknown | affiliation=The Pale Vigil | birth=1401 | birthlocation= | notablefor= | house=de Brasov | family= | parentage=Farkas de Brasov | siblings=Ilona, Katalin | spouse= | children= | gender=Female | height= | hair= | eyes= }} '''Reka de Brasov''' is the youngest dau..."

{{infobox character
| name=Reka de Brasov
| image=
| caption=
| othernames=
| titles=
| position=Daughter of the Darklord
| location=Unknown
| affiliation=[[The Pale Vigil]]
| birth=1401
| birthlocation=
| notablefor=
| house=[[House de Brasov|de Brasov]]
| family=
| parentage=[[Farkas de Brasov]]
| siblings=[[Ilona de Brasov|Ilona]], [[Katalin de Brasov|Katalin]]
| spouse=
| children=
| gender=Female
| height=
| hair=
| eyes=
}}

'''Reka de Brasov''' is the youngest daughter of [[Count Farkas]].

Katalin de Brasov

2026-07-09T19:57:52Z

Rataj: Created page with "{{infobox character | name=Katalin de Brasov | image= | caption= | othernames= | titles= | position=Daughter of the Darklord | location=Castle Valemoor | affiliation=Gilded Hand | birth=1397 | birthlocation= | notablefor= | house=de Brasov | family= | parentage=Farkas de Brasov | siblings=Ilona, Reka | spouse= | children= | gender=Female | height= | hair= | eyes= }} '''Katalin de Brasov''' is the mid..."

{{infobox character
| name=Katalin de Brasov
| image=
| caption=
| othernames=
| titles=
| position=Daughter of the Darklord
| location=[[Castle Valemoor]]
| affiliation=[[Gilded Hand]]
| birth=1397
| birthlocation=
| notablefor=
| house=[[House de Brasov|de Brasov]]
| family=
| parentage=[[Farkas de Brasov]]
| siblings=[[Ilona de Brasov|Ilona]], [[Reka de Brasov|Reka]]
| spouse=
| children=
| gender=Female
| height=
| hair=
| eyes=
}}

'''Katalin de Brasov''' is the middle daughter of [[Count Farkas]].

Ilona de Brasov

2026-07-09T19:56:59Z

Rataj: Created page with "{{infobox character | name=Ilona de Brasov | image= | caption= | othernames= | titles= | position=Daughter of the Darklord | location=Castle Valemoor | affiliation=The Wardens | birth=1389 | birthlocation= | notablefor= | house=de Brasov | family= | parentage=Farkas de Brasov | siblings=Katalin, Reka | spouse= | children= | gender=Female | height= | hair= | eyes= }} '''Ilona de Brasov''' is the old..."

{{infobox character
| name=Ilona de Brasov
| image=
| caption=
| othernames=
| titles=
| position=Daughter of the Darklord
| location=[[Castle Valemoor]]
| affiliation=[[The Wardens]]
| birth=1389
| birthlocation=
| notablefor=
| house=[[House de Brasov|de Brasov]]
| family=
| parentage=[[Farkas de Brasov]]
| siblings=[[Katalin de Brasov|Katalin]], [[Reka de Brasov|Reka]]
| spouse=
| children=
| gender=Female
| height=
| hair=
| eyes=
}}

'''Ilona de Brasov''' is the oldest daughter of [[Count Farkas]].

Farkas de Brasov

2026-07-09T19:33:22Z

Rataj: typo

{{infobox character
| name=Farkas de Brasov
| image=Farkas.jpg
| caption=Count Farkas on his throne
| othernames=The Reckoner
| titles=Count of Avardon
| position=Darklord
| location=[[Castle Valemoor]]
| birth=1365
| birthlocation=[[Livarun]]
| rule=1395 - Present day
| house=[[House de Brasov|de Brasov]]
| family=
| parentage=[[Gabor de Brasov]]
| siblings=[[Istvan de Brasov]]
| spouse=[[Valeria de Brasov]]
| children=[[Ilona de Brasov|Ilona]], [[Katalin de Brasov|Katalin]], [[Reka de Brasov|Reka]]
| gender=Male
}}

'''Farkas de Brasov''' is the current ''Count of Avardon'', and the Darklord of our setting.

He is the first son and only surviving child of [[Gabor de Brasov]].

== Early life ==
Farkas was born in [[Livarun]], the capital city of Avardon. His father was distant, raising him with high expectations to prepare the oldest son to eventually take the reins of the county.

== Early career ==
As was a tradition with young future rulers of the family, Farkas was trained in combat and in the strategy of war. Often sent out with a small regiment to settle quarrels between Viscounts and Barons, but even to deal with bandits and raiders.

Once he was approaching adult age, Farkas even led a small army in defense of no longer existing town of [[Coalfort]], and also led diplomatic delegations to the east to strengthen alliances including one with Zhentil Keep where he first met his future wife [[Valeria de Brasov|Valeria]].

=== Anauroch Campaign ===
Together with his father and brother, Farkas was part of the ''Anauroch Campaign'', an effort to push back against Bedine tribes that repeatedly attempted to besiege and claim [[Durana Gate]] and the nearby salt mines.

The campaign was a great success at first, clearing camps and fortifications at the border of Anauroch, even pushing far into the desert.

In the year 1388 DR, [[Gabor de Brasov|Count Gabor]] fell in battle, deep in the Anauroch desert. Farkas and [[Istvan de Brasov|Istvan]] decided not to send a message home and finish the campaign first.

While Farkas' brother gets injured in the subsequent battle and travels back home, rival [[House Steinberg]] has already put a plan in motion, announcing death of the Count to the people of Avardon along with a false report of both sons falling too. Based on records of old claims, [[Malzahin Steinberg]] becomes the new ruler of Avardon, ending the long rule of [[House de Brasov|de Brasov]] family.

Farkas learned of this treachery from a runner sent by Istvan, making him end the campaign and lead the remnants of the army back home only to find out his brother was slain and his own life is in danger as well.

== Hero of the People ==
Rule of Malzahin wasn't popular among the commonfolk, but Steinbergs managed to secure firm control over the army with help of many minor noble houses that were happy to buy more land or positions they were unable to get during Gabor's rule. Support of the new ruler was rising among the rich who saw opportunities in this change.

Farkas knew he had to play it safe, hiding among the people, proving to them that he was not only the rightful heir but also a ruler that would truly care. At first, most didn't care to risk their lives in support of Farkas. After all, they had no idea whether he would be at least half as great of a ruler that his father was.

And so began Farkas' mission of proving himself to the people. He traveled across the land, helping regular people and spreading the word of his mission. Sometimes even risking his own life in heroic deeds for the poor. These acts wouldn't go unnoticed. Nobles and soldiers that served his father joined in support, giving faith to many that joined their rebellion.

In summer of 1395 DR, rabble of unbelievable amount of commoners followed Farkas marching with his soldiers towards [[Castle Valemoor]]. The war that ensued was swift and brutal, but Farkas finally claimed a throne that was rightfully his, and Malzahin was imprisoned.

== Ruler of Avardon ==
People celebrated the victory of Farkas and the beginning of his rule, naming him ''Count Farkas de Brasov the Reckoner''. During months that followed, the new Count didn't act too hastily, he slowly undermined power of Steinbergs while showing benevolence, ruling to true satisfaction of the commonfolk.

Two years of the golden era of Farkas' rule passed, putting minds at ease as the beloved Count was exactly what everyone wished for. Perhaps he was even too good and a little shortsighted, spending so much on present well-being of his subjects with little regard for the future debts. It would be a forgivable mistake if it wasn't for his later acts.

After his second daughter was born in 1397 DR, Farkas was known among the noble circles for his frustration about this 'misfortune' and his desire and obsession with having a son. Avardon historically followed tradition of agnatic primogeniture (male only succession with the oldest son inheriting all titles) and while Farkas could've changed this rule and even did so later in life, at this point in time he was obsessed with keeping the tradition and considering it a great failure and shame if he would fail to do so. Despite being so beloved, this obsession was the hottest rumor among the nobles, and Farkas was commonly mocked for it, especially by Steinbergs who were also strict traditionalists.

In response to this mockery, Farkas went for an unusual punishment, ordering his court wizard to create a disease that would render victims infertile. Secretly spreading this disease among Steinbergs and other prominent houses that could put his rule at risk in the future. This would've not been known until much later, when [[Monvarin]] who created this disease had regrets and revealed the truth. Giving us glimpse into the past, as Farkas' growing paranoia and obsession of securing his rule and legacy led to gruesome acts even before the more widely known terrible deeds.

Farkas could never forgive the treachery of Steinbergs and he was growing paranoid of the possibility of their future attempts at stealing the holdings from his family, he was also impatient to see results of his earlier idea with the disease. A decree was issued, ordering the killing of Steinbergs including their young, an utter destruction of the house and confiscation of their properties. His own court and generals were shocked by the inclusion of children in the decree and some even refused to follow the order to the letter, letting most children escape.

During the following years, Farkas' madness didn't stop and only strengthened just as his rule. Finding out that some Steinbergs survived, he lost trust in the loyalty of his own men and leaned even more into the use of diseases and magic to control his population. Many times was his rule challenged, making him only stricter and more paranoid. From beloved leader became a feared and cruel lord, yet still respected by many just as he is to this day.

== Darklord ==
The terror that the Count caused sometimes backfired, such as when he caught the earliest disease himself, making him infertile and having his pregnant wife be his last chance at having a son.

Once his third daughter, [[Reka de Brasov]] is born, Farkas goes in frenzy and murders his own wife in fit of rage. An act witnessed by his oldest daughter but also by the [[Dark Powers]].

It was at this point that [[Avardon]] became a domain of dread, an eternal purgatory for Farkas to mockingly reflect his evil acts and keep him imprisoned in what he still believes to be his almost ideal land.

With mists on the borders and without trade, the region falls into poverty and famine, and civil wars ensue. But the Count's power is unprecedented and with his rule of iron fist, he easily puts everyone in line. Monsters are created to follow Farkas' orders, one of which is simply to keep people on their toes. Busy fighting the monsters, most don't gather enough power to ever challenge the Count.

Only the daughters are given free reign in regards of gathering power, which they mostly use to fight one another over influence and succession as Farkas seems calm and victorious. Divide and conquer is the chosen tactic now, as it ensures no one can threaten the Count.

Farkas de Brasov

2026-07-09T19:33:06Z

Rataj:

{{infobox character
| name=Farkas de Brasov
| image=Farkas.jpg
| caption=Count Farkas on his throne
| othernames=The Reckoner
| titles=Count of Avardon
| position=Darklord
| location=[[Castle Valemoor]]
| birth=1365
| birthlocation=[[Livarun]]
| rule=1395 - Present day
| house=[[House de Brasov|de Brasov]]
| family=
| parentage=[[Gabor de Brasov]]
| siblings=[[Istvan de Brasov]]
| spouse=[[Valeria de Brasov]]
| children=[[Ilona de Brasov|Ilona]], [[Katalin de Brasov|Katalin]], [[Reka de Brasov|Reka]]
| gender=Male
}}

'''Farkas de Brasov''' is the current ''Count of Avardon'', and the Darklord of our setting.

He is the first son and only surviving child of [[Gabor de Brasov]].

== Early life ==
Farkas was born in [[Livarun]], the capital city of Avardon. His father was distant, raising him with high expectations to prepare the oldest son to eventually take the reins of the county.

== Early career ==
As was a tradition with young future rulers of the family, Farkas was trained in combat and in the strategy of war. Often sent out with a small regiment to settle quarrels between Viscounts and Barons, but even to deal with bandits and raiders.

Once he was approaching adult age, Farkas even led a small army in defense of no longer existing town of [[Coalfort]], and also led diplomatic delegations to the east to strengthen alliances including one with Zhentil Keep where he first met his future wife [[Valeria de Brasov|Valeria]].

=== Anauroch Campaign ===
Together with his father and brother, Farkas was part of the ''Anauroch Campaign'', an effort to push back against Bedine tribes that repeatedly attempted to besiege and claim [[Durana Gate]] and the nearby salt mines.

The campaign was a great success at first, clearing camps and fortifications at the border of Anauroch, even pushing far into the desert.

In the year 1388 DR, [[Gabor de Brasov|Count Gabor]] fell in battle, deep in the Anauroch desert. Farkas and [[Istvan de Brasov|Istvan]] decided not to send a message home and finish the campaign first.

While Farkas' brother gets injured in the subsequent battle and travels back home, rival [[House Steinberg]] has already put a plan in motion, announcing death of the Count to the people of Avardon along with a false report of both sons falling too. Based on records of old claims, [[Malzahin Steinberg]] becomes the new ruler of Avardon, ending the long rule of [[House de Brasov|de Brasov]] family.

Farkas learned of this treachery from a runner sent by Istvan, making him end the campaign and lead the remnants of the army back home only to find out his brother was slain and his own life is in danger as well.

== Hero of the People ==
Rule of Malzahin wasn't popular among the commonfolk, but Steinbergs managed to secure firm control over the army with help of many minor noble houses that were happy to buy more land or positions they were unable to get during Gabor's rule. Support of the new ruler was rising among the rich who saw opportunities in this change.

Farkas knew he had to play it safe, hiding among the people, proving to them that he was not only the rightful heir but also a ruler that would truly care. At first, most didn't care to risk their lives in support of Farkas. After all, they had no idea whether he would be at least half as great of a ruler that his father was.

And so began Farkas' mission of proving himself to the people. He traveled across the land, helping regular people and spreading the word of his mission. Sometimes even risking his own life in heroic deeds for the poor. These acts wouldn't go unnoticed. Nobles and soldiers that served his father joined in support, giving faith to many that joined their rebellion.

In summer of 1395 DR, rabble of unbelievable amount of commoners followed Farkas marching with his soldiers towards [[Castle Valemoor]]. The war that ensued was swift and brutal, but Farkas finally claimed a throne that was rightfully his, and Malzahin as imprisoned.

== Ruler of Avardon ==
People celebrated the victory of Farkas and the beginning of his rule, naming him ''Count Farkas de Brasov the Reckoner''. During months that followed, the new Count didn't act too hastily, he slowly undermined power of Steinbergs while showing benevolence, ruling to true satisfaction of the commonfolk.

Two years of the golden era of Farkas' rule passed, putting minds at ease as the beloved Count was exactly what everyone wished for. Perhaps he was even too good and a little shortsighted, spending so much on present well-being of his subjects with little regard for the future debts. It would be a forgivable mistake if it wasn't for his later acts.

After his second daughter was born in 1397 DR, Farkas was known among the noble circles for his frustration about this 'misfortune' and his desire and obsession with having a son. Avardon historically followed tradition of agnatic primogeniture (male only succession with the oldest son inheriting all titles) and while Farkas could've changed this rule and even did so later in life, at this point in time he was obsessed with keeping the tradition and considering it a great failure and shame if he would fail to do so. Despite being so beloved, this obsession was the hottest rumor among the nobles, and Farkas was commonly mocked for it, especially by Steinbergs who were also strict traditionalists.

In response to this mockery, Farkas went for an unusual punishment, ordering his court wizard to create a disease that would render victims infertile. Secretly spreading this disease among Steinbergs and other prominent houses that could put his rule at risk in the future. This would've not been known until much later, when [[Monvarin]] who created this disease had regrets and revealed the truth. Giving us glimpse into the past, as Farkas' growing paranoia and obsession of securing his rule and legacy led to gruesome acts even before the more widely known terrible deeds.

Farkas could never forgive the treachery of Steinbergs and he was growing paranoid of the possibility of their future attempts at stealing the holdings from his family, he was also impatient to see results of his earlier idea with the disease. A decree was issued, ordering the killing of Steinbergs including their young, an utter destruction of the house and confiscation of their properties. His own court and generals were shocked by the inclusion of children in the decree and some even refused to follow the order to the letter, letting most children escape.

During the following years, Farkas' madness didn't stop and only strengthened just as his rule. Finding out that some Steinbergs survived, he lost trust in the loyalty of his own men and leaned even more into the use of diseases and magic to control his population. Many times was his rule challenged, making him only stricter and more paranoid. From beloved leader became a feared and cruel lord, yet still respected by many just as he is to this day.

== Darklord ==
The terror that the Count caused sometimes backfired, such as when he caught the earliest disease himself, making him infertile and having his pregnant wife be his last chance at having a son.

Once his third daughter, [[Reka de Brasov]] is born, Farkas goes in frenzy and murders his own wife in fit of rage. An act witnessed by his oldest daughter but also by the [[Dark Powers]].

It was at this point that [[Avardon]] became a domain of dread, an eternal purgatory for Farkas to mockingly reflect his evil acts and keep him imprisoned in what he still believes to be his almost ideal land.

With mists on the borders and without trade, the region falls into poverty and famine, and civil wars ensue. But the Count's power is unprecedented and with his rule of iron fist, he easily puts everyone in line. Monsters are created to follow Farkas' orders, one of which is simply to keep people on their toes. Busy fighting the monsters, most don't gather enough power to ever challenge the Count.

Only the daughters are given free reign in regards of gathering power, which they mostly use to fight one another over influence and succession as Farkas seems calm and victorious. Divide and conquer is the chosen tactic now, as it ensures no one can threaten the Count.

Farkas de Brasov

2026-07-09T19:29:49Z

Rataj: links

{{infobox character
| name=Farkas de Brasov
| image=Farkas.jpg
| caption=Count Farkas on his throne
| othernames=The Reckoner
| titles=Count of Avardon
| position=Darklord
| location=[[Castle Valemoor]]
| birth=1365
| birthlocation=[[Livarun]]
| rule=1395 - Present day
| house=[[House de Brasov|de Brasov]]
| family=
| parentage=[[Gabor de Brasov]]
| siblings=[[Istvan de Brasov]]
| spouse=[[Valeria de Brasov]]
| children=[[Ilona de Brasov|Ilona]], [[Katalin de Brasov|Katalin]], [[Reka de Brasov|Reka]]
| gender=Male
}}

'''Farkas de Brasov''' is the current ''Count of Avardon'', and the Darklord of our setting.

He is the first son and only surviving child of [[Gabor de Brasov]].

== Early life ==
Farkas was born in [[Livarun]], the capital city of Avardon. His father was distant, raising him with high expectations to prepare the oldest son to eventually take the reins of the county.

== Early career ==
As was a tradition with young future rulers of the family, Farkas was trained in combat and in the strategy of war. Often sent out with a small regiment to settle quarrels between Viscounts and Barons, but even to deal with bandits and raiders.

Once he was approaching adult age, Farkas even led a small army in defense of no longer existing town of [[Coalfort]], and also led diplomatic delegations to the east to strengthen alliances including one with Zhentil Keep where he first met his future wife [[Valeria de Brasov|Valeria]].

=== Anauroch Campaign ===
Together with his father and brother, Farkas was part of the ''Anauroch Campaign'', an effort to push back against Bedine tribes that repeatedly attempted to besiege and claim [[Durana Gate]] and the nearby salt mines.

The campaign was a great success at first, clearing camps and fortifications at the border of Anauroch, even pushing far into the desert.

In the year 1388 DR, [[Gabor de Brasov|Count Gabor]] fell in battle, deep in the Anauroch desert. Farkas and [[Istvan de Brasov|Istvan]] decided not to send a message home and finish the campaign first.

While Farkas' brother gets injured in the subsequent battle and travels back home, rival [[House Steinberg]] has already put a plan in motion, announcing death of the Count to the people of Avardon along with a false report of both sons falling too. Based on records of old claims, [[Malzahin Steinberg]] becomes the new ruler of Avardon, ending the long rule of [[House de Brasov|de Brasov]] family.

Farkas learned of this treachery from a runner sent by Istvan, making him end the campaign and lead the remnants of the army back home only to find out his brother was slain and his own life is in danger as well.

== Hero of the People ==
Rule of Malzahin wasn't popular among the commonfolk, but Steinbergs managed to secure firm control over the army with help of many minor noble houses that were happy to buy more land or positions they were unable to get during Gabor's rule. Support of the new ruler was rising among the rich who saw opportunities in this change.

Farkas knew he had to play it safe, hiding among the people, proving to them that he was not only the rightful heir but also a ruler that would truly care. At first, most didn't care to risk their lives in support of Farkas. After all, they had no idea whether he would be at least half as great of a ruler that his father was.

And so began Farkas' mission of proving himself to the people. He traveled across the land, helping regular people and spreading the word of his mission. Sometimes even risking his own life in heroic deeds for the poor. These acts wouldn't go unnoticed. Nobles and soldiers that served his father joined in support, giving faith to many that joined their rebellion.

In summer of 1395 DR, rabble of unbelievable amount of commoners followed Farkas marching with his soldiers towards [[Castle Valemoor]]. The war that ensued was swift and brutal, but Farkas finally claimed a throne that was rightfully his.

== Ruler of Avardon ==
People celebrated the victory of Farkas and the beginning of his rule, naming him ''Count Farkas de Brasov the Reckoner''. During months that followed, the new Count didn't act too hastily, he slowly undermined power of Steinbergs while showing benevolence, ruling to true satisfaction of the commonfolk.

Two years of the golden era of Farkas' rule passed, putting minds at ease as the beloved Count was exactly what everyone wished for. Perhaps he was even too good and a little shortsighted, spending so much on present well-being of his subjects with little regard for the future debts. It would be a forgivable mistake if it wasn't for his later acts.

After his second daughter was born in 1397 DR, Farkas was known among the noble circles for his frustration about this 'misfortune' and his desire and obsession with having a son. Avardon historically followed tradition of agnatic primogeniture (male only succession with the oldest son inheriting all titles) and while Farkas could've changed this rule and even did so later in life, at this point in time he was obsessed with keeping the tradition and considering it a great failure and shame if he would fail to do so. Despite being so beloved, this obsession was the hottest rumor among the nobles, and Farkas was commonly mocked for it, especially by Steinbergs who were also strict traditionalists.

In response to this mockery, Farkas went for an unusual punishment, ordering his court wizard to create a disease that would render victims infertile. Secretly spreading this disease among Steinbergs and other prominent houses that could put his rule at risk in the future. This would've not been known until much later, when [[Monvarin]] who created this disease had regrets and revealed the truth. Giving us glimpse into the past, as Farkas' growing paranoia and obsession of securing his rule and legacy led to gruesome acts even before the more widely known terrible deeds.

Farkas could never forgive the treachery of Steinbergs and he was growing paranoid of the possibility of their future attempts at stealing the holdings from his family, he was also impatient to see results of his earlier idea with the disease. A decree was issued, ordering the killing of Steinbergs including their young, an utter destruction of the house and confiscation of their properties. His own court and generals were shocked by the inclusion of children in the decree and some even refused to follow the order to the letter, letting most children escape.

During the following years, Farkas' madness didn't stop and only strengthened just as his rule. Finding out that some Steinbergs survived, he lost trust in the loyalty of his own men and leaned even more into the use of diseases and magic to control his population. Many times was his rule challenged, making him only stricter and more paranoid. From beloved leader became a feared and cruel lord, yet still respected by many just as he is to this day.

== Darklord ==
The terror that the Count caused sometimes backfired, such as when he caught the earliest disease himself, making him infertile and having his pregnant wife be his last chance at having a son.

Once his third daughter, [[Reka de Brasov]] is born, Farkas goes in frenzy and murders his own wife in fit of rage. An act witnessed by his oldest daughter but also by the [[Dark Powers]].

It was at this point that [[Avardon]] became a domain of dread, an eternal purgatory for Farkas to mockingly reflect his evil acts and keep him imprisoned in what he still believes to be his almost ideal land.

With mists on the borders and without trade, the region falls into poverty and famine, and civil wars ensue. But the Count's power is unprecedented and with his rule of iron fist, he easily puts everyone in line. Monsters are created to follow Farkas' orders, one of which is simply to keep people on their toes. Busy fighting the monsters, most don't gather enough power to ever challenge the Count.

Only the daughters are given free reign in regards of gathering power, which they mostly use to fight one another over influence and succession as Farkas seems calm and victorious. Divide and conquer is the chosen tactic now, as it ensures no one can threaten the Count.

Farkas de Brasov

2026-07-09T18:57:48Z

Rataj: Farkas story

{{infobox character
| name=Farkas de Brasov
| image=Farkas.jpg
| caption=Count Farkas on his throne
| othernames=The Reckoner
| titles=Count of Avardon
| position=Darklord
| location=[[Castle Valemoor]]
| birth=1365
| birthlocation=Livarun
| rule=1395 - Present day
| house=[[House de Brasov|de Brasov]]
| family=
| parentage=[[Gabor de Brasov]]
| siblings=[[Istvan de Brasov]]
| spouse=[[Valeria de Brasov]]
| children=[[Ilona de Brasov|Ilona]], [[Katalin de Brasov|Katalin]], [[Reka de Brasov|Reka]]
| gender=Male
}}

'''Farkas de Brasov''' is the current ''Count of Avardon'', and the Darklord of our setting.

He is the first son and only surviving child of [[Gabor de Brasov]].

== Early life ==
Farkas was born in Livarun, the capital city of Avardon. His father was distant, raising him with high expectations to prepare the oldest son to eventually take the reins of the county.

== Early career ==
As was a tradition with young future rulers of the family, Farkas was trained in combat and in the strategy of war. Often sent out with a small regiment to settle quarrels between Viscounts and Barons, but even to deal with bandits and raiders.

Once he was approaching adult age, Farkas even led a small army in defense of no longer existing town of [[Coalfort]], and also led diplomatic delegations to the east to strengthen alliances including one with Zhentil Keep where he first met his future wife [[Valeria de Brasov|Valeria]].

=== Anauroch Campaign ===
Together with his father and brother, Farkas was part of the ''Anauroch Campaign'', an effort to push back against Bedine tribes that repeatedly attempted to besiege and claim [[Durana Gate]] and the nearby salt mines.

The campaign was a great success at first, clearing camps and fortifications at the border of Anauroch, even pushing far into the desert.

In the year 1388 DR, [[Gabor de Brasov|Count Gabor]] fell in battle, deep in the Anauroch desert. Farkas and [[Istvan de Brasov|Istvan]] decided not to send a message home and finish the campaign first.

While Farkas' brother gets injured in the subsequent battle and travels back home, rival [[House Steinberg]] has already put a plan in motion, announcing death of the Count to the people of Avardon along with a false report of both sons falling too. Based on records of old claims, [[Malzahin Steinberg]] becomes the new ruler of Avardon, ending the long rule of [[House de Brasov|de Brasov]] family.

Farkas learned of this treachery from a runner sent by Istvan, making him end the campaign and lead the remnants of the army back home only to find out his brother was slain and his own life is in danger as well.

== Hero of the People ==
Rule of Malzahin wasn't popular among the commonfolk, but Steinbergs managed to secure firm control over the army with help of many minor noble houses that were happy to buy more land or positions they were unable to get during Gabor's rule. Support of the new ruler was rising among the rich who saw opportunities in this change.

Farkas knew he had to play it safe, hiding among the people, proving to them that he was not only the rightful heir but also a ruler that would truly care. At first, most didn't care to risk their lives in support of Farkas. After all, they had no idea whether he would be at least half as great of a ruler that his father was.

And so began Farkas' mission of proving himself to the people. He traveled across the land, helping regular people and spreading the word of his mission. Sometimes even risking his own life in heroic deeds for the poor. These acts wouldn't go unnoticed. Nobles and soldiers that served his father joined in support, giving faith to many that joined their rebellion.

In summer of 1395 DR, rabble of unbelievable amount of commoners followed Farkas marching with his soldiers towards [[Castle Valemoor]]. The war that ensued was swift and brutal, but Farkas finally claimed a throne that was rightfully his.

== Ruler of Avardon ==
People celebrated the victory of Farkas and the beginning of his rule, naming him ''Count Farkas de Brasov the Reckoner''. During months that followed, the new Count didn't act too hastily, he slowly undermined power of Steinbergs while showing benevolence, ruling to true satisfaction of the commonfolk.

Two years of the golden era of Farkas' rule passed, putting minds at ease as the beloved Count was exactly what everyone wished for. Perhaps he was even too good and a little shortsighted, spending so much on present well-being of his subjects with little regard for the future debts. It would be a forgivable mistake if it wasn't for his later acts.

After his second daughter was born in 1397 DR, Farkas was known among the noble circles for his frustration about this 'misfortune' and his desire and obsession with having a son. Avardon historically followed tradition of agnatic primogeniture (male only succession with the oldest son inheriting all titles) and while Farkas could've changed this rule and even did so later in life, at this point in time he was obsessed with keeping the tradition and considering it a great failure and shame if he would fail to do so. Despite being so beloved, this obsession was the hottest rumor among the nobles, and Farkas was commonly mocked for it, especially by Steinbergs who were also strict traditionalists.

In response to this mockery, Farkas went for an unusual punishment, ordering his court wizard to create a disease that would render victims infertile. Secretly spreading this disease among Steinbergs and other prominent houses that could put his rule at risk in the future. This would've not been known until much later, when [[Monvarin]] who created this disease had regrets and revealed the truth. Giving us glimpse into the past, as Farkas' growing paranoia and obsession of securing his rule and legacy led to gruesome acts even before the more widely known terrible deeds.

Farkas could never forgive the treachery of Steinbergs and he was growing paranoid of the possibility of their future attempts at stealing the holdings from his family, he was also impatient to see results of his earlier idea with the disease. A decree was issued, ordering the killing of Steinbergs including their young, an utter destruction of the house and confiscation of their properties. His own court and generals were shocked by the inclusion of children in the decree and some even refused to follow the order to the letter, letting most children escape.

During the following years, Farkas' madness didn't stop and only strengthened just as his rule. Finding out that some Steinbergs survived, he lost trust in the loyalty of his own men and leaned even more into the use of diseases and magic to control his population. Many times was his rule challenged, making him only stricter and more paranoid. From beloved leader became a feared and cruel lord, yet still respected by many just as he is to this day.

== Darklord ==
The terror that the Count caused sometimes backfired, such as when he caught the earliest disease himself, making him infertile and having his pregnant wife be his last chance at having a son.

Once his third daughter, [[Reka de Brasov]] is born, Farkas goes in frenzy and murders his own wife in fit of rage. An act witnessed by his oldest daughter but also by the [[Dark Powers]].

It was at this point that [[Avardon]] became a domain of dread, an eternal purgatory for Farkas to mockingly reflect his evil acts and keep him imprisoned in what he still believes to be his almost ideal land.

With mists on the borders and without trade, the region falls into poverty and famine, and civil wars ensue. But the Count's power is unprecedented and with his rule of iron fist, he easily puts everyone in line. Monsters are created to follow Farkas' orders, one of which is simply to keep people on their toes. Busy fighting the monsters, most don't gather enough power to ever challenge the Count.

Only the daughters are given free reign in regards of gathering power, which they mostly use to fight one another over influence and succession as Farkas seems calm and victorious. Divide and conquer is the chosen tactic now, as it ensures no one can threaten the Count.

Lore Introduction

2026-07-09T17:36:54Z

Rataj: small correction

The winding mountain passages and hungering mists of [[Avardon]] welcome you, stranger, be you adventurer, scholar, fortune-seeker, or wayward soul. It seems this [[Ravenloft|Domain of Dread]] draws people in, be it their intention to come here or elsewhere. A weathered people clings to the decaying remnants of what was once a prosperous domain, living in the shadow of old stories and eerie unease. Around fireplaces and tavern tables the common folk speak of fog-bound forests, twisting roads that lead one astray, wretched beasts in the mists, and the ancient bloodline of the noble house that holds dominion in these lands.

It was not always this way. For many generations the lands flourished under the guiding hand of [[House de Brasov]], whose rule brought stability and prosperity to Avardon and its peoples. Under their control trade flourished along the mountain roads and scattered villages grew into thriving communities. That prosperity began to crumble after the death of [[Gabor de Brasov]], a capable lord whose leadership had long kept nearby powers at bay. The network of informants of a longtime rival of the de Brasov family, [[House Steinberg]], delivered news of the aged patriarch passing during one of those border skirmishes. The House Steinberg was quick to spread word that Gabor’s sons had died alongside him, leaving a power vacuum that they quickly seized the chance to fill.

The younger son, [[Istvan de Brasov|Istvan]], was injured in a subsequent battle and returned to a nearby village to recover when he heard the news. Immediately furious, he dispatched a runner to report this treachery to his elder brother, [[Farkas de Brasov|Farkas]]. Unable to temper his wrath, Istvan took a contingent of his men and rode out towards Livarun. In an outrage he rode to the doors of the manor Steinberg and in the ensuing uproar demanded a duel with one of the sons. The Steinbergs were quick to claim he lost his challenge and his men attempted to slay his opponent. The truth, spoken of in hushed voices, was that his challenge had been received by one of the Steinbergs’ treacherous man-at-arms' spears being thrust into his side, and his men cut down in short order.

These rumors reached Farkas before he made it into the city proper, fortunately for him. With his family shattered and their lands stolen and rightfully fearing further betrayal from the Steinbergs he retreated from the outskirts. Though known to those he met, word of him was spread under an assumed identity, affording him a chance to stir up the people’s support. Eventually those supporters included many of the nobles in the region, most of the warriors that had served his father, and a significant portion of the commoners. What all was done during those months remains the subject of rumor with most assuming feats of heroism and some whispering of darker deeds. Either way, he found the support he needed and his rebellion was able to rear its head and issue its own challenge. House Steinberg would face a reckoning for its treachery.

The war that ensued was swift and brutal. Most of the people were eager to see their exiled lord return to power and one by one Steinberg allies fell until the gates of [[Castle Valemoor]] were opened to Farkas once again. His victory ended with him at last named Count Farkas de Brasov the Reckoner, a popular hero, yet in but a two years a decree cast a bloody stain on his newly minted legacy. He ordered the complete and utter destruction of House Steinberg for their perfidious misdeeds. Every member, no matter their age, would be put to death and all their holdings confiscated. Whether every member of the house truly perished remains uncertain, but within three days their name was washed from the land of Avardon.

Not long after Count Farkas secured his rule, misfortune seemed to grow in this war-torn land. Fertile fields yielded scant harvests, disease began to spread among the population as famine ravaged them, and the wilderness seemed to grow restless. Strange figures were glimpsed in the forests and travelers vanished within the fog-choked passes that wind from village to village. Communities that had stood for generations fell silent, abandoned or destroyed, as monsters, illness, and hunger drove people toward [[Livarun]]. Amidst it all tragedy struck the Count’s growing family when the beloved Countess [[Valeria de Brasov]] passed in the delivery of their third daughter, at least so was publicly claimed. Rumors, which were met with harsh response and rebuke, said that it was not the harsh reality of childbirth that took the Countess’ life but that of her husband, angered that she had for a third time failed to deliver him a son to be his heir.

Over time the once-thriving domain collapsed inward until nearly all who remained alive clustered around the city beneath Castle Valemoor. The mists descended across the valleys and in those days the borders of Avardon seemed to grow uncertain and unpredictable. It’s hard to say when exactly the lands seemed to sever themselves from their place upon Toril, but before long trade from outside lands ran dry as caravan drivers and merchants seemed unable to find their way. Though it is not utterly cut off from the outside world, those who come here often find it difficult to leave again. Those that come intentionally seem to find greater odds of successful departure than those who got lost in the mists across Faerun and stumbled into these cursed lands.

Through these grim years the rule of Count Farkas de Brasov has remained the single constant the people of the realm could depend on, though given the iron grasp he kept on the withering lands some mutter discontent at this notion. Though rarely seen beyond the walls of his ancestral hold, his firm authority has preserved what fragile order has remained while the rest of the land crumbled around it. Some claim he is at last succumbing to the curse that haunts this land, some that he is part of it, but none can question his rule. The survivors from Livarun scavenged and took what they could from the ruins of the lost villages, leaving only the barest of ruins behind as they did what they could to attempt to maintain their own sense of normalcy rather than foolishly focusing on the greater fates of the land.

Only recently has Avardon begun to show signs of recovery. The outskirts of Livarun are no longer pushed back by the wilderness, even seeing some measure of rebuilding. Cautiously the people have begun to try and reclaim the farmland on the outskirts of the recovering town, and now people even speak of attempts to start pushing back into the dangerous wilderness to establish other communities so that the realm can begin to recover properly. An influx of outsiders seems to have coincided with this push, perhaps a boon from the lands themselves to combat its troubles.

Much of this fragile renewal is guided by the eldest two daughters of Count Farkas, though they are said to disagree extensively about the form their shared vision of a restored land should take. The oldest, [[Ilona de Brasov]], seems to wish to gather soldiers and those who believe people must grow strong through hardship and vigilance, that they must cow the curse upon these lands into submission through might. Her middle sister, [[Katalin de Brasov]], seems more inclined towards restoring the political and economic foundations that once made these lands so very prosperous. Their younger sister, [[Reka de Brasov]], said to be sickly and rather enigmatic, is similar to her father in that she is almost never seen in the courts of the capital. Some claim her naively obsessed with old legends and the origins of the maladies that infect this land. Regardless of their differences, most locals seem to think the Count’s daughters are rising influences in the lands, perhaps even the cause of the slow reversal of fortunes that seems to be taking place.

Beyond Livarun’s fragile safety remains great danger. Ruined villages still lie scattered across the wilderness, beasts and monsters roam the forests, and the mists continue to drift unpredictably through the mountains. Avardon offers outsiders danger and opportunity in equal measure, be it that they came here by intent or misfortune. Brave adventurers find monsters in the wilds, scholars search for answers to forgotten questions, and ambitious fortune-seekers do their best to carve out their own slice of prosperity amongst the toil of regrowth.

The mists and the [[Dark powers|Dark Powers]] that dwell in them bring people here for reasons none truly understand, but the land has a way of remembering those who walk its roads. In a realm shaped by curses, bloodlines, tragedies, and superstition even the smallest action may become the beginning of a new legend. Every traveler in Avardon carves their own story, eventually becoming part of this land's tale.

What will you write upon this land, stranger?

Lore Introduction

2026-07-09T16:35:56Z

Rataj: added some links

The winding mountain passages and hungering mists of [[Avardon]] welcome you, stranger, be you adventurer, scholar, fortune-seeker, or wayward soul. It seems this [[Ravenloft|Domain of Dread]] draws people in, be it their intention to come here or elsewhere. A weathered people clings to the decaying remnants of what was once a prosperous domain, living in the shadow of old stories and eerie unease. Around fireplaces and tavern tables the common folk speak of fog-bound forests, twisting roads that lead one astray, wretched beasts in the mists, and the ancient bloodline of the noble house that holds dominion in these lands.

It was not always this way. For many generations the lands flourished under the guiding hand of [[House de Brasov]], whose rule brought stability and prosperity to Avardon and its peoples. Under their control trade flourished along the mountain roads and scattered villages grew into thriving communities. That prosperity began to crumble after the death of [[Gabor de Brasov]], a capable lord whose leadership had long kept nearby powers at bay. The network of informants of a longtime rival of the de Brasov family, [[House Steinberg]], delivered news of the aged patriarch passing during one of those border skirmishes. The House Steinberg was quick to spread word that Gabor’s sons had died alongside him, leaving a power vacuum that they quickly seized the chance to fill.

The younger son, [[Istvan de Brasov|Istvan]], was injured in a subsequent battle and returned to a nearby village to recover when he heard the news. Immediately furious, he dispatched a runner to report this treachery to his elder brother, [[Farkas de Brasov|Farkas]]. Unable to temper his wrath, Istvan took a contingent of his men and rode out towards Livarun. In an outrage he rode to the doors of the manor Steinberg and in the ensuing uproar demanded a duel with one of the sons. The Steinbergs were quick to claim he lost his challenge and his men attempted to slay his opponent. The truth, spoken of in hushed voices, was that his challenge had been received by one of the Steinbergs’ treacherous man-at-arms' spears being thrust into his side, and his men cut down in short order.

These rumors reached Farkas before he made it into the city proper, fortunately for him. With his family shattered and their lands stolen and rightfully fearing further betrayal from the Steinbergs he retreated from the outskirts. Though known to those he met, word of him was spread under an assumed identity, affording him a chance to stir up the people’s support. Eventually those supporters included many of the nobles in the region, most of the warriors that had served his father, and a significant portion of the commoners. What all was done during those months remains the subject of rumor with most assuming feats of heroism and some whispering of darker deeds. Either way, he found the support he needed and his rebellion was able to rear its head and issue its own challenge. House Steinberg would face a reckoning for its treachery.

The war that ensued was swift and brutal. Most of the people were eager to see their exiled lord return to power and one by one Steinberg allies fell until the gates of [[Castle Valemoor]] were opened to Farkas once again. His victory ended with him at last named Count Farkas de Brasov the Reckoner, a popular hero, yet his first decree cast a bloody stain on his newly minted legacy. He ordered the complete and utter destruction of House Steinberg for their perfidious misdeeds. Every member, no matter their age, would be put to death and all their holdings confiscated. Whether every member of the house truly perished remains uncertain, but within three days their name was washed from the land of Avardon.

Not long after Count Farkas secured his rule, misfortune seemed to grow in this war-torn land. Fertile fields yielded scant harvests, disease began to spread among the population as famine ravaged them, and the wilderness seemed to grow restless. Strange figures were glimpsed in the forests and travelers vanished within the fog-choked passes that wind from village to village. Communities that had stood for generations fell silent, abandoned or destroyed, as monsters, illness, and hunger drove people toward [[Livarun]]. Amidst it all tragedy struck the Count’s growing family when the beloved Countess [[Valeria de Brasov]] passed in the delivery of their third daughter, at least so was publicly claimed. Rumors, which were met with harsh response and rebuke, said that it was not the harsh reality of childbirth that took the Countess’ life but that of her husband, angered that she had for a third time failed to deliver him a son to be his heir.

Over time the once-thriving domain collapsed inward until nearly all who remained alive clustered around the city beneath Castle Valemoor. The mists descended across the valleys and in those days the borders of Avardon seemed to grow uncertain and unpredictable. It’s hard to say when exactly the lands seemed to sever themselves from their place upon Toril, but before long trade from outside lands ran dry as caravan drivers and merchants seemed unable to find their way. Though it is not utterly cut off from the outside world, those who come here often find it difficult to leave again. Those that come intentionally seem to find greater odds of successful departure than those who got lost in the mists across Faerun and stumbled into these cursed lands.

Through these grim years the rule of Count Farkas de Brasov has remained the single constant the people of the realm could depend on, though given the iron grasp he kept on the withering lands some mutter discontent at this notion. Though rarely seen beyond the walls of his ancestral hold, his firm authority has preserved what fragile order has remained while the rest of the land crumbled around it. Some claim he is at last succumbing to the curse that haunts this land, some that he is part of it, but none can question his rule. The survivors from Livarun scavenged and took what they could from the ruins of the lost villages, leaving only the barest of ruins behind as they did what they could to attempt to maintain their own sense of normalcy rather than foolishly focusing on the greater fates of the land.

Only recently has Avardon begun to show signs of recovery. The outskirts of Livarun are no longer pushed back by the wilderness, even seeing some measure of rebuilding. Cautiously the people have begun to try and reclaim the farmland on the outskirts of the recovering town, and now people even speak of attempts to start pushing back into the dangerous wilderness to establish other communities so that the realm can begin to recover properly. An influx of outsiders seems to have coincided with this push, perhaps a boon from the lands themselves to combat its troubles.

Much of this fragile renewal is guided by the eldest two daughters of Count Farkas, though they are said to disagree extensively about the form their shared vision of a restored land should take. The oldest, [[Ilona de Brasov]], seems to wish to gather soldiers and those who believe people must grow strong through hardship and vigilance, that they must cow the curse upon these lands into submission through might. Her middle sister, [[Katalin de Brasov]], seems more inclined towards restoring the political and economic foundations that once made these lands so very prosperous. Their younger sister, [[Reka de Brasov]], said to be sickly and rather enigmatic, is similar to her father in that she is almost never seen in the courts of the capital. Some claim her naively obsessed with old legends and the origins of the maladies that infect this land. Regardless of their differences, most locals seem to think the Count’s daughters are rising influences in the lands, perhaps even the cause of the slow reversal of fortunes that seems to be taking place.

Beyond Livarun’s fragile safety remains great danger. Ruined villages still lie scattered across the wilderness, beasts and monsters roam the forests, and the mists continue to drift unpredictably through the mountains. Avardon offers outsiders danger and opportunity in equal measure, be it that they came here by intent or misfortune. Brave adventurers find monsters in the wilds, scholars search for answers to forgotten questions, and ambitious fortune-seekers do their best to carve out their own slice of prosperity amongst the toil of regrowth.

The mists and the [[Dark powers|Dark Powers]] that dwell in them bring people here for reasons none truly understand, but the land has a way of remembering those who walk its roads. In a realm shaped by curses, bloodlines, tragedies, and superstition even the smallest action may become the beginning of a new legend. Every traveler in Avardon carves their own story, eventually becoming part of this land's tale.

What will you write upon this land, stranger?

House de Brasov

2026-07-09T16:26:18Z

Rataj:

Notable members:
* [[Farkas de Brasov]]
* [[Gabor de Brasov]]
* [[Valeria de Brasov]]
* [[Istvan de Brasov]]
* [[Ilona de Brasov]]
* [[Katalin de Brasov]]
* [[Reka de Brasov]]

File:Farkas.jpg

2026-07-09T16:19:09Z

Rataj:

== Licensing ==
{{license self|}}

Monvarin

2026-07-09T02:19:39Z

Rataj: Created page with "{{infobox character | name=Monvarin | image=Monvarin.jpg | othernames=Father of the End | position=Master of the Arcane | location=Castle Valemoor | affiliation=Comital Court | notablefor=Creating diseases | gender=Male | hair=Grey | eyes=Silver }} '''Monvarin''' is the ''Master of the Arcane'' of the Comital Court, serving under Count Farkas. He is also known as the ''Court Wizard'' or ''Father of the End''. Being the one responsible for spread of dise..."

{{infobox character
| name=Monvarin
| image=Monvarin.jpg
| othernames=Father of the End
| position=Master of the Arcane
| location=[[Castle Valemoor]]
| affiliation=[[Comital Court]]
| notablefor=Creating diseases
| gender=Male
| hair=Grey
| eyes=Silver
}}

'''Monvarin''' is the ''Master of the Arcane'' of the [[Comital Court]], serving under [[Count Farkas]]. He is also known as the ''Court Wizard'' or ''Father of the End''.

Being the one responsible for spread of diseases, curses, and creation of some of the monsters in [[Avardon]], it comes as no surprise that '''Monvarin''' is one of the most hated figures in the realm, perhaps even more hated than [[Farkas de Brasov|Farkas]] himself.

Rare rumor among locals speaks of regret over his actions later in life, which is stated as a reason why the Count killed him in the year '''1414'''. Yet, the Court Wizard was resurrected about 50 years later and is now back in service.

File:Monvarin.jpg

2026-07-09T01:54:26Z

Rataj:

== Licensing ==
{{license self|}}

Comital Court

2026-07-09T01:53:09Z

Rataj: Created page with "The '''Comital Court''', often called simply a '''court''', is an extended household of the Count including all high ranking officials residing in Castle Valemoor. The court is under the direct authority of Count Farkas and in extension House de Brasov. == Members == * Baron Nikolai Karakas - Constable * Monvarin - Master of the Arcane"

The '''Comital Court''', often called simply a '''court''', is an extended household of the Count including all high ranking officials residing in [[Castle Valemoor]]. The court is under the direct authority of [[Count Farkas]] and in extension [[House de Brasov]].

== Members ==
* [[Nikolai Karakas|Baron Nikolai Karakas]] - Constable
* [[Monvarin]] - Master of the Arcane

Livarun

2026-07-09T01:16:47Z

Rataj:

[[File:Livarun.png|thumb|An overview picture of the settlement of Livarun.]]
At one time, '''Livarun''' was the capital of '''[[Avardon]]''' and stretched the full valley that it resides in to this day; even connecting to the food of the mountain that [[Farkas de Brasov|'''Count Farkas'''<nowiki/>']] castle, now called [[Castle Valemoor]], sits upon. In more modern times, it is a small settlement built upon the ruins of a single district of the old city — a shadow of its former self, yet those clinging to the hope of better days use it as a hub. There is very little business conducted in Avardon that doesn't find its way past the front gate of '''Livarun'''.

PvP is mechanically blocked there just like in [[Scarabend]], conflict is not welcome.

Profession quests in Livarun are instant and reward you 4 silver coins and 1 profession experience.

Nikolai Karakas

2026-07-09T01:16:25Z

Rataj:

{{infobox character
| name=Nikolai Karakas
| image=Nikolai_Karakas.jpg
| titles=Baron
| position=Constable
| location=[[Castle Valemoor]]
| affiliation=[[Comital Court]]
| notablefor=Enforcing law in [[Avardon]]
| house=[[House Karakas|Karakas]]
| gender=Male
| hair=Black
| eyes=Red
}}

Baron '''Nikolai Karakas''' is a ''Constable'' of the [[Comital Court]], enforcing the will of [[Count Farkas]].

Nikolai Karakas

2026-07-09T01:12:12Z

Rataj: Created page with "{{infobox character | name=Nikolai Karakas | image=Nikolai_Karakas.jpg | titles=Baron | position=Constable | location=Castle Valemoor | affiliation=Comital Court | notablefor=Enforcing law in Avardon | house=Karakas | gender=Male | hair=Black | eyes=Red }} Baron '''Nikolai Karakas''' is a ''Constable'' of the Comital Court, enforcing the will of Count Farkas."

{{infobox character
| name=Nikolai Karakas
| image=Nikolai_Karakas.jpg
| titles=Baron
| position=Constable
| location=Castle Valemoor
| affiliation=[[Comital Court]]
| notablefor=Enforcing law in [[Avardon]]
| house=[[House Karakas|Karakas]]
| gender=Male
| hair=Black
| eyes=Red
}}

Baron '''Nikolai Karakas''' is a ''Constable'' of the [[Comital Court]], enforcing the will of [[Count Farkas]].

File:Nikolai Karakas.jpg

2026-07-09T00:23:50Z

Rataj:

== Licensing ==
{{license self|}}

Combat Rulings

2026-07-02T20:49:20Z

Rataj: added ruling on buffs and movement before combat

This is a collection of various rulings and clarifications regarding combat encounters. It is an extension to the rules with more detailed and in-depth explanations to bring some light into niche situations that might arise.

=== Line of Sight ===
Some abilities such as ranged attacks, or spells that mention "point you can see" or "target you can see" in their description, require sight.

You cannot target character if:
* You don't see at least 50% of their body or the entirety of their head from your first person view.
* Selector (such as with Magic Missile or Eldritch Blast) doesn't let you use it due to missing Line of Sight.
* You are Blinded or have both of your eyes Maimed.
* There is an area effect that restricts vision in between you and the target or at least one of you stands in it without being able to see through with special abilities.
* The target is Invisible and you lack the ability to see invisible creatures.

Additionally, AoE spells that target a point cannot be placed into areas that limit visibility, such as area of Darkness. You may only target the edge of such area, as that's as far as you can see.

==== Crouching ====

Conan mechanical crouch or other animations may not be used to avoid Line of Sight. You can still use animations and poses during combat, just not in a way to restrict LoS or when there's a discussion whether someone has LoS. The visibility rules apply for a standing character. The only exception is being Prone, in which case you should have a suitable animation even for purposes of determining LoS.

=== Observers ===
When a player chooses to observe a fight (having been present for its declaration and using <code>/pvp observe</code>), they are basically communicating to the other players upfront that their character either doesn't want to be involved with either side of the combat, or they are too scared to fight, or for any other reason refuse to fight. Observers are IC, and they chose NOT to fight under any change of circumstance. If they could ever possibly have a reason to join the fight, they have to either join it as an participant at the very beginning of the encounter, or leave the scene entirely. They cannot join into an ongoing fight or participate in the consequence phase or engage in another fight with the winning or losing party after the fight is concluded.

Also keep in mind, that any participant of the fight may void your decision to observe and include you as a target of their intent even and especially if they were the party being subject to a PvP intent, as per rule C.1:
<blockquote>Everyone within the range of a PvP intent is locked into the scene unless they are not targeted by anyone else within the scene lock</blockquote>

=== Doors ===
No player shall interact with doors during combat outside of using the Interact ability in RPR.

It takes an action to lock/unlock a door, a bonus action to open/close it, and an action with DC 15 to breach it, after which it becomes unusable for the duration of combat.

Breaching of a door in combat (and only in combat) is done using Breaching or Lockpicking skill (whichever is higher) or using the Spellcasting modifier in case of casters (if higher than the skills).

=== Hiding ===
Players may [[Hide]] in combat as long as none of their foes have Line of Sight on them - this is checked automatically but good etiquette is expected in case it wouldn't work reliably in all cases.

To reveal a player that is hiding during combat, players may use the Spot free action '''on their turn''', if they see the target.

Players may follow hidden or invisible foes, they still know of their approximate location and it is not considered metagaming.

=== Before Combat ===
As you find yourself in a scene with other players, especially if it may lead to combat, you are expected to act in good faith and let others react to your actions. The contrary would be powergaming.

This includes using any spells, buffs, drinking potions, swapping equipment, departing a scene, or entering or leaving a range of 1.5 tiles of another character.

All of these actions have to be emoted first, other players need to be given a chance to react to it. If they want to stop the action, they may also drop PvP intent and you can only proceed with that action on your turn of combat if you still wish to take that action.

Under no circumstances should anyone drink potions, cast buffs, or swap runes, unless others go a full round of emotes without responding to those attempted actions.

Players may also not take a Short Rest or Long Rest during a hostile scene. Refer to the tooltip for acceptable usage.

If a character declares PvP intent in order to halt movement, then the character attempting to move must return to their original position. This can also be used to prevent a character from leaving an active scene, but not to start one.

Drawing any weapons represented by currently equipped runes that are also displayed on your character is considered a free action, and is not subject to being contested.

Rules

2026-06-22T20:57:00Z

Rataj:

Hello there! We are glad that you are responsible and will dedicate a few minutes to read our rules.

Please don't just skip through the rules.
We want to keep our server friendly and immersive, prevent any possible attempts to spoil the game, and create a pleasant environment for '''all''' players to enjoy.
If you don't understand something, don't be afraid to ask us on [https://avardon.com/discord Discord] and we'll be more than happy to help you out.

At the same time we try to keep our rules concise and we rely on '''common sense''' of our players. These rules are not supposed to be exhaustive and all-encompassing. We expect our players to avoid any behavior such as ''rule-lawyering'' or acting against good faith and outside of the standards of our community, even if it doesn't break any specific rule outlined on this page.

We also want to make it very clear that no one is exempt from these rules. The rules apply equally to staff and players. In fact, staff members are under higher scrutiny to lead the community by example.

== Community Rules ==
=== M.1 - Server Culture ===
Avardon is an open and welcoming community founded on the expectation, that we treat each other as adults and as if we were all playing at a single table at a friend's house. We expect all players to recognize their peers as partners in collaborative writing and respect them as equals. [[Play-to-Lift]] mentality is expected, not optional.

Harassment, discrimination, or toxicity of any kind is absolutely unacceptable and has no place in our community. We want this community to be a place for you and for us to love coming back to.

=== M.2 - Adults Only ===
This server is only available to those of adult age (18+), who are also mature enough to not make us doubt it.

No representation of child or child-like characters is allowed. All characters must be at least the adult age for their respective species '''and''' also at least 20 years old. Portrayal of pregnancy is also not allowed.

=== M.3 - English Only ===
Avardon is an English speaking community, the sole language to be used in roleplay, tickets, and on any of our official channels is English.

Characters are allowed to use terms from other D&D languages (or suitable real-world languages in the case of regional dialects) as long as it is used sparsely for flavor, and other players whose characters know the language mechanically are helped to understand the phrase you used should they ask. You may not write entire sentences in these flavored languages, nor should you roleplay as knowing and speaking a language that is not included in our server's system. Please also avoid using terms that are too modern, such as internet slang.

=== M.4 - Dispute Resolution ===
If you find yourself in a dispute with another player, try to cooperate and resolve it together. However, do not argue and do not attempt to enforce rules yourself, rather let us know through a ticket. You shall never threaten anyone with a moderation action nor with a ticket.

Do not freeze roleplay to wait for staff involvement, keep the scenes rolling. An exception to this rule is if your consent is violated. In such a case, you may remove yourself from the scene at any time to ensure your personal comfort.

== Roleplaying Rules ==
=== R.1 - Character Creation ===
All players must follow and complete the whitelisting process before engaging in roleplay on the server. You are expected to follow the guidance provided by staff in your whitelisting ticket.

Characters are expected to follow the server lore in both their behavior and visuals. Please refer to the corresponding [[Races|race]] page for average height and other requirements. Characters should originate either from Toril or the Domains of Dread, including Avardon. Allowable exceptions are the Feywilds (Satyr, Eladrin) and Shadowfell (Shadar-Kai) if appropriate for the character race.

Once your whitelist is approved, you may only make realistic changes to the design of your character, such as changing hair style and warpaints. Your body and face should remain the same.

The depiction of your character should reflect your character sheet and equipment runes. Do not depict or roleplay abilities or equipment your character does not have.

=== R.2 - Roleplay Etiquette ===
When not in the spawn area, you are always considered to be ''In Character'' and should try your best to contribute to the immersive narrative experience with other players. While the concept of good etiquette may be difficult to define exhaustively, we expect you to at the very least:
* Minimize OOC chatter during roleplay scenes.
* React appropriately to the use of social rolls.
* Respect the agency of other players, do not force your actions on them without letting them react (powergaming).
* Do not play omniscient characters. Your character does not have access to an online wiki. Minimise the knowledge of your character to what they reasonably know, and do not 'lore-dump' information on other players.
* Take responsibility in being courteous and understanding towards players even if OOC tension arises. Step away if necessary.
* Respect and value the life of your own character, ensuring that they act in a way that best suits the situation (especially when they are in mortal danger, or at the mercy of another character).

=== R.3 - Metagaming ===
You are not allowed to take ''In Character'' actions based on knowledge you obtained as a player ''Out of Character''. This is known as ''metagaming'' and is strictly forbidden on Avardon.

You should also avoid sharing any information OOC that could influence stories if acted upon IC. Especially if it relates to instances of on-going or very recent combat, details about other characters or their actions. Use common sense, don't ruin stories by enabling others to ''metagame''.

It is important to maintain an immersive atmosphere where players are mostly only aware of what their character would know. Therefore, when in any doubt at all, do not share meta-knowledge with other players.

However, there are exceptions to this rule. You are allowed to share adventures of your own character, and discuss non-actionable things that have happened in the game. You can also look for roleplay and schedule roleplay through OOC means.

=== R.4 - Consent Sheets ===
Players are encouraged to create a consent sheet in their RPR profile to show what themes they are not comfortable with. It is the responsibility of every player to be aware of consent preferences of other players in a scene, as to not violate consent.

When unsure of a particular sensitive theme, the player wanting to initiate this theme is responsible for communicating to all players involved to confirm their approval, as violating preferences due to ignorance will never be excused.

Sensitive themes include, but are not limited to: graphical descriptions of gore, surgeries, torture, mutilation, self harm, and anything of erotic or sexual nature, especially rape (including the mention of).

Be aware that consent sheets cannot be abused to avoid mechanical consequences, and it is the right of any player to request a ''fade-to-black'' (FTB) when wanting to carry out a sensitive topic but not wanting to write out the details of it.

When a player becomes part of a scene which does not conform to their consent sheet and where they are not a main actor, that player is to be given a chance to depart the scene without undue delay.

=== R.5 - Adult Content ===
While we allow the depiction of adult content (such as nudity and erotic roleplay) on our server, we expect players to do so in responsible manner.

Nudity is not allowed in main hub areas (with exception of player-owned houses). Characters are required to at the very least cover their genitals and breasts.

Scenes depicting sexual themes must take place in a private setting where it may be reasonably assumed that no other players may accidentally stumble upon them.

All scenes of this nature that could be considered non-consensual or dubious in any way require OOC consent that can be withdrawn at any time, allowing players to stop and even void such scene.

Interest in any sexual themes may not be advertised through consent sheets, character profiles, or global chat.

=== R.6 - Act Names ===
Players may use the <code>/act</code> command to change their display name in order to use an alias or conceal their identity, but must not use a name of another character, or one that impersonates them, including names of NPCs.

=== R.7 - LFRP Etiquette ===
When using the Looking for Roleplay functionality on the in-game map, players are expected to follow these guidelines:
* Disable your marker when your scene is locked (PvP intent is dropped).
* Do not approach LFRP marker promoting Solo/Duo/Trio with more than equal number of players if your intention is to take hostile actions.
* Do not use the Solo/Duo/Trio tags in a misleading way. It has to reflect the amount of people present in a scene. These tags also shouldn't be used to deliberately shield yourself against unfair odds when at your base.

Keep in mind the intention of this rule: LFRP etiquette exists to prevent large groups from metagaming information displayed on LFRP markers to secure unfair advantage in combat. LFRP in general serves as a tool to find roleplay, new contacts, new stories and start some narrative.

== Game Rules ==
=== G.1 - Bugs, Cheating, Exploits ===
It may occur that bugs appear in our systems such as the combat or economy related scripts. We expect players to collaborate with the staff team in spotting and mitigating these bugs by reporting them in a timely manner.

We have zero tolerance policy for cheating, exploiting bugs and security vulnerabilities, abusing and misusing systems or enacting DDoS attacks and similar malicious actions.

=== G.2 - Always in a Clan ===
Every player has to be in a clan at all times. Even if they play solo. Any buildings not belonging to a clan will get deleted.

=== G.3 - Showing Equipment ===
Your worn armor and all weapons you intend to use have to be properly shown on your character design (utilizing Tot Custom).

You may not use any weapon in combat that your character isn't visually carrying (exceptions apply, such as pact weapons).

=== G.4 - Climbing ===
You may not climb onto structures, terrain, or other obstacles to enter or leave a clan base without using the Climb or Misty Step ability in RPR. Descending walls or terrain also requires using the Climb ability.

== Building Rules ==
=== B.1 - Building Limits ===
Every clan may only have one base (with exception of '''temporary''' camps).

Do not build beyond boundaries of the map or under terrain.

Main entrance of any build must be accessible without climbing.

Build at least '''50 tiles''' from a base of another clan, 100 tiles from the main hubs, and 50 tiles from any public portal.

Exception to the above are decoration pieces (no buildings) in Durana Gate, as you are allowed to live there, and even if you don't live there, you can put down a mailbox in this town (one per clan).

You may not build inside base game dungeons (caves are allowed, when in doubt ask in a ticket). Special exception is the Wine Cellar dungeon, in which you may build and also the rule of base distances doesn't apply.

Land claim of your build should be proportionate to your clan size, it is not allowed to claim large area with sparsely placed building pieces.

Your build has to reasonably fit the setting and cannot be immersion breaking.

Always stay within the following limits:
{| class="wikitable"
! Players !! Building Pieces !! Decorations
|-
| 1 || 500 || 200
|-
| 2-3 || 800 || 400
|-
| 4-5 || 1500 || 600
|-
| 6-9 || 2500 || 1000
|-
| 10+ || 3500 || 1500
|}
Additionally, no clan should have more thralls/mounts than players.

These limits can be increased with donator building extensions.

=== B.2 - Performance Considerations ===
All clans have to keep server and client performance in mind when building their bases. Do not overuse trees, containers (decorations with inventory) and custom textures, do not put too many light sources close together. Build responsibly.

=== B.3 - Inactivity ===
Players that have been inactive for more than '''30''' days may be removed from their clan by our system. If the inactive player is a clan owner, their build will be transferred to active members or removed.

Builds that violate other rules (such as building limits) while also belonging to an inactive clan may be removed sooner, after 14 days since any member was last online, or 7 days since being brought into a build audit ticket.

== Combat Rules ==
=== C.1 - Scene Lock ===
Once PvP is declared (intent has been dropped), the scene is locked and no further players shall join the scene until the consequence phase is over. Everyone within the range of a PvP intent is locked into the scene unless they are not targeted by anyone else within the scene lock, in that case they can either join, leave or observe (declared using <code>/pvp observe</code>). Any player that stumbles upon the scene while it's locked has to leave the area immediately and isn't allowed to watch. Those players cannot roleplay witnessing anything they saw in the locked scene.

Exception from this rule are spars, tournaments, arena fights and friendly brawls, these do not lock the scene and people are free to come and go.

Once a scene is unlocked after the conclusion of consequences, all participants of the scene must be allowed to leave the area without being subject to any subsequent combat encounters.

No size of any group in combat may exceed 5. The total cap for any PvP is always 10 players.

=== C.2 - Combat Etiquette ===
As combat scenes tend to have high tension, it is especially important to be cordial to other players when you fight their characters. While the concept of good etiquette may be difficult to define exhaustively, we expect you to at the very least:
* Act in a friendly and respectful manner in OOC towards your IC foes (they're your fellow storytellers, not your enemies).
* Make sure your conflict has story, roleplay has to precede and follow a combat scene. PvP systems exist as a conflict resolution, to help you progress narrative.
* Emote only outside of your turn, ideally ''after''.
* Try to be swift with your turns, do not prolong combat with micro-optimizations or OOC arguments.
* Help new players and those who don't fight often, answer their questions, and be patient with them.
* Follow the official [[Combat Rulings]] in all niche cases we provided additional clarifications for.

=== C.3 - Consequences ===
The winning party may impose consequences on the losing party after a fight is concluded. While delivering those consequences, players are in a consequence phase.

This phase can only last 30 minutes. If consequences take longer time than that, the scene is no longer locked and other players may interact with it. Under no circumstances shall players slow down the roleplay to exploit this rule.

We differentiate four categories of consequences:
* Minor consequences are mechanical consequences that may be applied at any time.
* Major consequences are mechanical consequences that may only be applied if the winning party had at max +1 advantage in numbers (i.e. in 1v1 or 3v2, but not in 3v1 or 5v3).
* Escalated consequences are mechanical consequences that may only be applied if the previous level was already applied at least once by one of the victors against the defeated or by the defeated on one of the victors in previous fights (and at least one major consequence has to precede even the first escalated one) while also fulfilling the conditions for a major consequence.
* Consented consequences are non-mechanical consequences that may be applied only if the losing party actively consents to such consequences.

Keep in mind that any thievery consequences may be applied from you on a specific target only once per 24 hours. In other words, you may not rob the same person again after already doing so within the last 24 hours.

Only one consequence shall be applied on a character. Consequence stacking is not allowed.

Unmasking is not considered a consequence and can be done freely on the defeated party after combat.

All possible consequence options are listed in the [[Consequences|guide to consequences]].

=== C.4 - Mugging ===
You may mug someone and it may (or may not) be reasonable for the target character to give up their belongings without a fight. However same rules as with PvP consequences apply. Players can only take what consequences rules would allow them as if a fight was taking a place. If the target complies and PvP takes place anyway, the attackers shall not deliver any further consequences.

=== C.5 - Limits on Hostile Actions ===
While hostile actions are major and important part of our server, there are some limitations to when and where you may perform them.

Hostile actions include but are not limited to: combat, thievery, mugging, attempts to restrict, restrain, or forcefully hold a person, but also threats, harassment, intimidation, provocation, and any other acts that would likely lead to combat.

You may not perform hostile actions when:
* You are in a PvP restricted area (Livarun or Scarabend).
* You are within 20 tile radius of a public waypoint.

Monster Slots

2026-06-22T16:55:47Z

Rataj:

Monster slots allow players to step out of the usual roleplay and take on the role of a monster for other players to encounter.

== Players ==
As a player, you may encounter monsters in the world. Should they defeat you, there is nothing but wounds, scars, and a great story to tell. In case you manage to kill the monster, you will be rewarded 30 silver coins.

After an encounter, you are able to rate the monster player to give us a feedback on how enjoyable the experience was based on their roleplay. This is not a competition, just a way to ensure good etiquette.

If you want to increase your chances of encountering monsters and fight with them more often, you can use '''/settings''' to opt into having your position on the map shown to monster players. This can be changed at any time.

== Monsters ==
If you wish to play a monster you have to first and foremost familiarize yourself with the guidelines and expectations outlined below. Then you can head to [https://avardon.com/monsters/play avardon.com/monsters/play] and sign up. After some time, if you are lucky, you may be randomly picked for the monster slot. From there on it is up to you to do a good job at playing a monster to keep the monster slot access.

All players with monster slot access also get a Discord role with access to a special channel for monsters to organize group encounters with other players and DMs. They are also notified of events such as the blood moon.

Monsters have the option to teleport into a monster gallery using '''/warp monster''', and switch between player slot and monster slot in there as well as choose a specific monster sheet and character design and teleport around the map to find players by simply roaming around. They may also utilize their own LFRP to attract players to their position or chase after those who opted into being shown on a web map for monsters.

== Guidelines and Expectations ==
The monster system exists to help promote a more dangerous and immersive world within [[Avardon]], contributing to the dreadful atmosphere of the setting. Monsters are encouraged to engage with players creatively; instilling dread and frightening players through both combat and non-combat encounters. Monster slots are a part of collaborative, cooperative storytelling and writing and should be fun for both the monster and other players in the encounter.

=== 1. Monster Play Etiquette ===
Encounters should focus on the narrative and immersive experience of the receiving players. Do not engage in encounters for the purposes of winning or the competitive aspect of combat.

Do not start encounters for the purpose of harassing or targeting specific players.

You may not actively seek to engage the same player in an encounter more than once per week.

Communication is key. Always be open and willing to OOC communication when the situation requires it.

Ensure that the strength of your monster is appropriate for the encounter. Do not approach a solo player with a monster designed for 3 players.

Avoid approaching LFRPs unless they are specifically looking for Trouble or Conflict. Players with other LFRP markers shouldn't be disrupted and you shall rather use the monster map or have your own LFRP if you can't find players randomly.

Monster players should never discuss rewards and ratings with the players they encounter. Do not ask them if they got a reward, do not ask them for a good rating, do not remind them of either, everything is handled by the system notifications already.

=== 2. Combat Rules ===
Monsters are subject to the same rules as all other players.

A monster may approach the camp or settlement of other players. When doing so, interact with players from outside the settlement rather than entering it. Create noise, growl, stomp your feet; to lure players outside. Thus providing an opportunity for players to choose whether to engage.

=== 3. Monster Roleplay ===
Monster players are expected to understand the lore and traits of the monster they have selected, and to act accordingly. Your monster has limited knowledge of the world around them, based on the specific monster.

Provide a reasonable opportunity for players to react in their preferred fashion. Depending on the nature of the monster, provide chances for players to pursue alternate resolutions to combat such as trying to run or hide.

Each monster is a discrete, unique entity. You may not use knowledge gained as a monster on your player character, and vice versa.

A monster is not meant for social roleplay outside of encounters, nor should the monster's identity persist between encounters. A monster may not be captured or tamed.

You may not engage in erotic or sexual content of any nature at all when playing as a monster. There are no exceptions. Violating this rule will result in immediate revocation of the monster slot.

=== 4. Do not disturb events ===
Do not bring your monsters to events and large gatherings. If you become aware of an event only when you arrive at the scene, disengage when possible. Exceptions are if the organizers of the event specifically requested the presence of a monster either through their event listing on Discord or through OOC communication with you as a monster player.

=== 5. Usage of available tools ===
Monster players may use the monster map, teleport, and other features and tools available to them only when playing a monster and only for the purposes of monster encounters. All usage is logged and any misuse will be punished severely beyond just revoking a monster slot.

Many monsters come with descriptions or a set of instructions on how exactly they should be played. Monster players are expected to follow these instructions to help us ensure immersive experience for everyone.

For some monsters it is suitable, allowed, and even expected that the monster players will edit the character design or even create their own. These designs have to fit the theme and looks of the specific monster. When in doubt, show us the design and have it approved.

Shapeshifts and any other items obtained through the monster gallery systems have to be incinerated after use, they shall never be used on a player character or given to another person.

=== 6. Staff Authority ===
At any time, for any reason, staff have the authority to revoke the monster slot from any given player. This may happen even outside of rule breaks as we want to give other players a chance to play monsters.

Rules

2026-06-20T15:39:27Z

Rataj:

Hello there! We are glad that you are responsible and will dedicate a few minutes to read our rules.

Please don't just skip through the rules.
We want to keep our server friendly and immersive, prevent any possible attempts to spoil the game, and create a pleasant environment for '''all''' players to enjoy.
If you don't understand something, don't be afraid to ask us on [https://avardon.com/discord Discord] and we'll be more than happy to help you out.

At the same time we try to keep our rules concise and we rely on '''common sense''' of our players. These rules are not supposed to be exhaustive and all-encompassing. We expect our players to avoid any behavior such as ''rule-lawyering'' or acting against good faith and outside of the standards of our community, even if it doesn't break any specific rule outlined on this page.

We also want to make it very clear that no one is exempt from these rules. The rules apply equally to staff and players. In fact, staff members are under higher scrutiny to lead the community by example.

== Community Rules ==
=== M.1 - Server Culture ===
Avardon is an open and welcoming community founded on the expectation, that we treat each other as adults and as if we were all playing at a single table at a friend's house. We expect all players to recognize their peers as partners in collaborative writing and respect them as equals. [[Play-to-Lift]] mentality is expected, not optional.

Harassment, discrimination, or toxicity of any kind is absolutely unacceptable and has no place in our community. We want this community to be a place for you and for us to love coming back to.

=== M.2 - Adults Only ===
This server is only available to those of adult age (18+), who are also mature enough to not make us doubt it.

No representation of child or child-like characters is allowed. All characters must be at least the adult age for their respective species '''and''' also at least 20 years old. Portrayal of pregnancy is also not allowed.

=== M.3 - English Only ===
Avardon is an English speaking community, the sole language to be used in roleplay, tickets, and on any of our official channels is English.

Characters are allowed to use terms from other D&D languages (or suitable real-world languages in the case of regional dialects) as long as it is used sparsely for flavor, and other players whose characters know the language mechanically are helped to understand the phrase you used should they ask. You may not write entire sentences in these flavored languages, nor should you roleplay as knowing and speaking a language that is not included in our server's system. Please also avoid using terms that are too modern, such as internet slang.

=== M.4 - Dispute Resolution ===
If you find yourself in a dispute with another player, try to cooperate and resolve it together. However, do not argue and do not attempt to enforce rules yourself, rather let us know through a ticket. You shall never threaten anyone with a moderation action nor with a ticket.

Do not freeze roleplay to wait for staff involvement, keep the scenes rolling. An exception to this rule is if your consent is violated. In such a case, you may remove yourself from the scene at any time to ensure your personal comfort.

== Roleplaying Rules ==
=== R.1 - Character Creation ===
All players must follow and complete the whitelisting process before engaging in roleplay on the server. You are expected to follow the guidance provided by staff in your whitelisting ticket.

Characters are expected to follow the server lore in both their behavior and visuals. Please refer to the corresponding [[Races|race]] page for average height and other requirements. Characters should originate either from Toril or the Domains of Dread, including Avardon. Allowable exceptions are the Feywilds (Satyr, Eladrin) and Shadowfell (Shadar-Kai) if appropriate for the character race.

Once your whitelist is approved, you may only make realistic changes to the design of your character, such as changing hair style and warpaints. Your body and face should remain the same.

The depiction of your character should reflect your character sheet and equipment runes. Do not depict or roleplay abilities or equipment your character does not have.

=== R.2 - Roleplay Etiquette ===
When not in the spawn area, you are always considered to be ''In Character'' and should try your best to contribute to the immersive narrative experience with other players. While the concept of good etiquette may be difficult to define exhaustively, we expect you to at the very least:
* Minimize OOC chatter during roleplay scenes.
* React appropriately to the use of social rolls.
* Respect the agency of other players, do not force your actions on them without letting them react (powergaming).
* Do not play omniscient characters. Your character does not have access to an online wiki. Minimise the knowledge of your character to what they reasonably know, and do not 'lore-dump' information on other players.
* Take responsibility in being courteous and understanding towards players even if OOC tension arises. Step away if necessary.
* Respect and value the life of your own character, ensuring that they act in a way that best suits the situation (especially when they are in mortal danger, or at the mercy of another character).

=== R.3 - Metagaming ===
You are not allowed to take ''In Character'' actions based on knowledge you obtained as a player ''Out of Character''. This is known as ''metagaming'' and is strictly forbidden on Avardon.

You should also avoid sharing any information OOC that could influence stories if acted upon IC. Especially if it relates to instances of on-going or very recent combat, details about other characters or their actions. Use common sense, don't ruin stories by enabling others to ''metagame''.

It is important to maintain an immersive atmosphere where players are mostly only aware of what their character would know. Therefore, when in any doubt at all, do not share meta-knowledge with other players.

However, there are exceptions to this rule. You are allowed to share adventures of your own character, and discuss non-actionable things that have happened in the game. You can also look for roleplay and schedule roleplay through OOC means.

=== R.4 - Consent Sheets ===
Players are encouraged to create a consent sheet in their RPR profile to show what themes they are not comfortable with. It is the responsibility of every player to be aware of consent preferences of other players in a scene, as to not violate consent.

When unsure of a particular sensitive theme, the player wanting to initiate this theme is responsible for communicating to all players involved to confirm their approval, as violating preferences due to ignorance will never be excused.

Sensitive themes include, but are not limited to: graphical descriptions of gore, surgeries, torture, mutilation, self harm, and anything of erotic or sexual nature, especially rape (including the mention of).

Be aware that consent sheets cannot be abused to avoid mechanical consequences, and it is the right of any player to request a ''fade-to-black'' (FTB) when wanting to carry out a sensitive topic but not wanting to write out the details of it.

When a player becomes part of a scene which does not conform to their consent sheet and where they are not a main actor, that player is to be given a chance to depart the scene without undue delay.

=== R.5 - Adult Content ===
While we allow the depiction of adult content (such as nudity and erotic roleplay) on our server, we expect players to do so in responsible manner.

Nudity is not allowed in main hub areas (with exception of player-owned houses). Characters are required to at the very least cover their genitals and breasts.

Scenes depicting sexual themes must take place in a private setting where it may be reasonably assumed that no other players may accidentally stumble upon them.

All scenes of this nature that could be considered non-consensual or dubious in any way require OOC consent that can be withdrawn at any time, allowing players to stop and even void such scene.

Interest in any sexual themes may not be advertised through consent sheets, character profiles, or global chat.

=== R.6 - Act Names ===
Players may use the <code>/act</code> command to change their display name in order to use an alias or conceal their identity, but must not use a name of another character, or one that impersonates them, including names of NPCs.

=== R.7 - LFRP Etiquette ===
When using the Looking for Roleplay functionality on the in-game map, players are expected to follow these guidelines:
* Disable your marker when your scene is locked (PvP intent is dropped).
* Do not approach LFRP marker promoting Solo/Duo/Trio with more than equal number of players if your intention is to take hostile actions.
* Do not use the Solo/Duo/Trio tags in a misleading way. It has to reflect the amount of people present in a scene. These tags also shouldn't be used to deliberately shield yourself against unfair odds when at your base.

Keep in mind the intention of this rule: LFRP etiquette exists to prevent large groups from metagaming information displayed on LFRP markers to secure unfair advantage in combat. LFRP in general serves as a tool to find roleplay, new contacts, new stories and start some narrative.

== Game Rules ==
=== G.1 - Bugs, Cheating, Exploits ===
It may occur that bugs appear in our systems such as the combat or economy related scripts. We expect players to collaborate with the staff team in spotting and mitigating these bugs by reporting them in a timely manner.

We have zero tolerance policy for cheating, exploiting bugs and security vulnerabilities, abusing and misusing systems or enacting DDoS attacks and similar malicious actions.

=== G.2 - Always in a Clan ===
Every player has to be in a clan at all times. Even if they play solo. Any buildings not belonging to a clan will get deleted.

=== G.3 - Showing Equipment ===
Your worn armor and all weapons you intend to use have to be properly shown on your character design (utilizing Tot Custom).

You may not use any weapon in combat that your character isn't visually carrying (exceptions apply, such as pact weapons).

=== G.4 - Climbing ===
You may not climb onto structures, terrain, or other obstacles to enter or leave a clan base without using the Climb or Misty Step ability in RPR. Descending walls or terrain also requires using the Climb ability.

== Building Rules ==
=== B.1 - Building Limits ===
Every clan may only have one base (with exception of '''temporary''' camps).

Do not build beyond boundaries of the map or under terrain.

Main entrance of any build must be accessible without climbing.

Build at least '''50 tiles''' from a base of another clan, 100 tiles from the main hubs, and 50 tiles from any public portal.

Exception to the above are decoration pieces (no buildings) in Durana Gate, as you are allowed to live there, and even if you don't live there, you can put down a mailbox in this town (one per clan).

You may not build inside base game dungeons (caves are allowed, when in doubt ask in a ticket).

Land claim of your build should be proportionate to your clan size, it is not allowed to claim large area with sparsely placed building pieces.

Your build has to reasonably fit the setting and cannot be immersion breaking.

Always stay within the following limits:
{| class="wikitable"
! Players !! Building Pieces !! Decorations
|-
| 1 || 500 || 200
|-
| 2-3 || 800 || 400
|-
| 4-5 || 1500 || 600
|-
| 6-9 || 2500 || 1000
|-
| 10+ || 3500 || 1500
|}
Additionally, no clan should have more thralls/mounts than players.

These limits can be increased with donator building extensions.

=== B.2 - Performance Considerations ===
All clans have to keep server and client performance in mind when building their bases. Do not overuse trees, containers (decorations with inventory) and custom textures, do not put too many light sources close together. Build responsibly.

=== B.3 - Inactivity ===
Players that have been inactive for more than '''30''' days may be removed from their clan by our system. If the inactive player is a clan owner, their build will be transferred to active members or removed.

Builds that violate other rules (such as building limits) while also belonging to an inactive clan may be removed sooner, after 14 days since any member was last online, or 7 days since being brought into a build audit ticket.

== Combat Rules ==
=== C.1 - Scene Lock ===
Once PvP is declared (intent has been dropped), the scene is locked and no further players shall join the scene until the consequence phase is over. Everyone within the range of a PvP intent is locked into the scene unless they are not targeted by anyone else within the scene lock, in that case they can either join, leave or observe (declared using <code>/pvp observe</code>). Any player that stumbles upon the scene while it's locked has to leave the area immediately and isn't allowed to watch. Those players cannot roleplay witnessing anything they saw in the locked scene.

Exception from this rule are spars, tournaments, arena fights and friendly brawls, these do not lock the scene and people are free to come and go.

Once a scene is unlocked after the conclusion of consequences, all participants of the scene must be allowed to leave the area without being subject to any subsequent combat encounters.

No size of any group in combat may exceed 5. The total cap for any PvP is always 10 players.

=== C.2 - Combat Etiquette ===
As combat scenes tend to have high tension, it is especially important to be cordial to other players when you fight their characters. While the concept of good etiquette may be difficult to define exhaustively, we expect you to at the very least:
* Act in a friendly and respectful manner in OOC towards your IC foes (they're your fellow storytellers, not your enemies).
* Make sure your conflict has story, roleplay has to precede and follow a combat scene. PvP systems exist as a conflict resolution, to help you progress narrative.
* Emote only outside of your turn, ideally ''after''.
* Try to be swift with your turns, do not prolong combat with micro-optimizations or OOC arguments.
* Help new players and those who don't fight often, answer their questions, and be patient with them.
* Follow the official [[Combat Rulings]] in all niche cases we provided additional clarifications for.

=== C.3 - Consequences ===
The winning party may impose consequences on the losing party after a fight is concluded. While delivering those consequences, players are in a consequence phase.

This phase can only last 30 minutes. If consequences take longer time than that, the scene is no longer locked and other players may interact with it. Under no circumstances shall players slow down the roleplay to exploit this rule.

We differentiate four categories of consequences:
* Minor consequences are mechanical consequences that may be applied at any time.
* Major consequences are mechanical consequences that may only be applied if the winning party had at max +1 advantage in numbers (i.e. in 1v1 or 3v2, but not in 3v1 or 5v3).
* Escalated consequences are mechanical consequences that may only be applied if the previous level was already applied at least once by one of the victors against the defeated or by the defeated on one of the victors in previous fights (and at least one major consequence has to precede even the first escalated one) while also fulfilling the conditions for a major consequence.
* Consented consequences are non-mechanical consequences that may be applied only if the losing party actively consents to such consequences.

Keep in mind that any thievery consequences may be applied from you on a specific target only once per 24 hours. In other words, you may not rob the same person again after already doing so within the last 24 hours.

Only one consequence shall be applied on a character. Consequence stacking is not allowed.

Unmasking is not considered a consequence and can be done freely on the defeated party after combat.

All possible consequence options are listed in the [[Consequences|guide to consequences]].

=== C.4 - Mugging ===
You may mug someone and it may (or may not) be reasonable for the target character to give up their belongings without a fight. However same rules as with PvP consequences apply. Players can only take what consequences rules would allow them as if a fight was taking a place. If the target complies and PvP takes place anyway, the attackers shall not deliver any further consequences.

=== C.5 - Limits on Hostile Actions ===
While hostile actions are major and important part of our server, there are some limitations to when and where you may perform them.

Hostile actions include but are not limited to: combat, thievery, mugging, attempts to restrict, restrain, or forcefully hold a person, but also threats, harassment, intimidation, provocation, and any other acts that would likely lead to combat.

You may not perform hostile actions when:
* You are in a PvP restricted area (Livarun or Scarabend).
* You are within 20 tile radius of a public waypoint.

Monster Slots

2026-06-18T23:40:34Z

Rataj:

Monster slots allow players to step out of the usual roleplay and take on the role of a monster for other players to encounter.

== Players ==
As a player, you may encounter monsters in the world. Should they defeat you, there is nothing but wounds, scars, and a great story to tell. In case you manage to kill the monster, you will be rewarded 30 silver coins.

After an encounter, you are able to rate the monster player to give us a feedback on how enjoyable the experience was based on their roleplay. This is not a competition, just a way to ensure good etiquette.

If you want to increase your chances of encountering monsters and fight with them more often, you can use '''/settings''' to opt into having your position on the map shown to monster players. This can be changed at any time.

== Monsters ==
If you wish to play a monster you have to first and foremost familiarize yourself with the guidelines and expectations outlined below. Then you can head to [https://avardon.com/monsters/play avardon.com/monsters/play] and sign up. After some time, if you are lucky, you may be randomly picked for the monster slot. From there on it is up to you to do a good job at playing a monster to keep the monster slot access.

All players with monster slot access also get a Discord role with access to a special channel for monsters to organize group encounters with other players and DMs. They are also notified of events such as the blood moon.

Monsters have the option to teleport into a monster gallery using '''/warp monster''', and switch between player slot and monster slot in there as well as choose a specific monster sheet and character design and teleport around the map to find players by simply roaming around. They may also utilize their own LFRP to attract players to their position or chase after those who opted into being shown on a web map for monsters.

== Guidelines and Expectations ==
The monster system exists to help promote a more dangerous and immersive world within [[Avardon]], contributing to the dreadful atmosphere of the setting. Monsters are encouraged to engage with players creatively; instilling dread and frightening players through both combat and non-combat encounters. Monster slots are a part of collaborative, cooperative storytelling and writing and should be fun for both the monster and other players in the encounter.

=== 1. Monster Play Etiquette ===
Encounters should focus on the narrative and immersive experience of the receiving players. Do not engage in encounters for the purposes of winning or the competitive aspect of combat.

Do not start encounters for the purpose of harassing or targeting specific players.

You may not actively seek to engage the same player in an encounter more than once per week.

Communication is key. Always be open and willing to OOC communication when the situation requires it.

Ensure that the strength of your monster is appropriate for the encounter. Do not approach a solo player with a monster designed for 3 players.

Avoid approaching LFRPs unless they are specifically looking for Trouble or Conflict. Players with other LFRP markers shouldn't be disrupted and you shall rather use the monster map or have your own LFRP if you can't find players randomly.

=== 2. Combat Rules ===
Monsters are subject to the same rules as all other players.

A monster may approach the camp or settlement of other players. When doing so, interact with players from outside the settlement rather than entering it. Create noise, growl, stomp your feet; to lure players outside. Thus providing an opportunity for players to choose whether to engage.

=== 3. Monster Roleplay ===
Monster players are expected to understand the lore and traits of the monster they have selected, and to act accordingly. Your monster has limited knowledge of the world around them, based on the specific monster.

Provide a reasonable opportunity for players to react in their preferred fashion. Depending on the nature of the monster, provide chances for players to pursue alternate resolutions to combat such as trying to run or hide.

Each monster is a discrete, unique entity. You may not use knowledge gained as a monster on your player character, and vice versa.

A monster is not meant for social roleplay outside of encounters, nor should the monster's identity persist between encounters. A monster may not be captured or tamed.

You may not engage in erotic or sexual content of any nature at all when playing as a monster. There are no exceptions. Violating this rule will result in immediate revocation of the monster slot.

=== 4. Do not disturb events ===
Do not bring your monsters to events and large gatherings. If you become aware of an event only when you arrive at the scene, disengage when possible. Exceptions are if the organizers of the event specifically requested the presence of a monster either through their event listing on Discord or through OOC communication with you as a monster player.

=== 5. Usage of available tools ===
Monster players may use the monster map, teleport, and other features and tools available to them only when playing a monster and only for the purposes of monster encounters. All usage is logged and any misuse will be punished severely beyond just revoking a monster slot.

Many monsters come with descriptions or a set of instructions on how exactly they should be played. Monster players are expected to follow these instructions to help us ensure immersive experience for everyone.

For some monsters it is suitable, allowed, and even expected that the monster players will edit the character design or even create their own. These designs have to fit the theme and looks of the specific monster. When in doubt, show us the design and have it approved.

Shapeshifts and any other items obtained through the monster gallery systems have to be incinerated after use, they shall never be used on a player character or given to another person.

=== 6. Staff Authority ===
At any time, for any reason, staff have the authority to revoke the monster slot from any given player. This may happen even outside of rule breaks as we want to give other players a chance to play monsters.

Monster Slots

2026-06-18T22:52:41Z

Rataj:

Monster slots allow players to step out of the usual roleplay and take on the role of a monster for other players to encounter.

== Players ==
As a player, you may encounter monsters in the world. Should they defeat you, there is nothing but wounds, scars, and a great story to tell. In case you manage to kill the monster, you will be rewarded 30 silver coins.

After an encounter, you are able to rate the monster player to give us a feedback on how enjoyable the experience was based on their roleplay. This is not a competition, just a way to ensure good etiquette.

If you want to increase your chances of encountering monsters and fight with them more often, you can use '''/settings''' to opt into having your position on the map shown to monster players. This can be changed at any time.

== Monsters ==
If you wish to play a monster you have to first and foremost familiarize yourself with the guidelines and expectations outlined below. Then you can head to [https://avardon.com/monsters/play avardon.com/monsters/play] and sign up. After some time, if you are lucky, you may be randomly picked for the monster slot. From there on it is up to you to do a good job at playing a monster to keep the monster slot access.

All players with monster slot access also get a Discord role with access to a special channel for monsters to organize group encounters with other players and DMs. They are also notified of events such as the blood moon.

Monsters have the option to teleport into a monster gallery using '''/warp monster''', and switch between player slot and monster slot in there as well as choose a specific monster sheet and character design and teleport around the map to find players by simply roaming around. They may also utilize their own LFRP to attract players to their position or chase after those who opted into being shown on a web map for monsters.

== Guidelines and Expectations ==
The monster system exists to help promote a more dangerous and immersive world within [[Avardon]], contributing to the dreadful atmosphere of the setting. Monsters are encouraged to engage with players creatively; instilling dread and frightening players through both combat and non-combat encounters. Monster slots are a part of collaborative, cooperative storytelling and writing and should be fun for both the monster and other players in the encounter.

=== 1. Monster Play Etiquette ===
Encounters should focus on the narrative and immersive experience of the receiving players. Do not engage in encounters for the purposes of winning or the competitive aspect of combat.

Do not start encounters for the purpose of harassing or targeting specific players.

You may not actively seek to engage the same player in an encounter more than once per week.

Communication is key. Always be open and willing to OOC communication when the situation requires it.

Ensure that the strength of your monster is appropriate for the encounter. Do not approach a solo player with a monster designed for 3 players.

Avoid approaching LFRPs unless they are specifically looking for Trouble or Conflict. Players with other LFRP markers shouldn't be disrupted and you shall rather use the monster map or have your own LFRP if you can't find players randomly.

=== 2. Combat Rules ===
Monsters are subject to the same rules as all other players.

A monster may approach the camp or settlement of other players. When doing so, interact with players from outside the settlement rather than entering it. Create noise, growl, stomp your feet; to lure players outside. Thus providing an opportunity for players to choose whether to engage.

=== 3. Monster Roleplay ===
Monster players are expected to understand the lore and traits of the monster they have selected, and to act accordingly. Your monster has limited knowledge of the world around them, based on the specific monster.

Provide a reasonable opportunity for players to react in their preferred fashion. Depending on the nature of the monster, provide chances for players to pursue alternate resolutions to combat such as trying to run or hide.

Each monster is a discrete, unique entity. You may not use knowledge gained as a monster on your player character, and vice versa.

A monster is not meant for social roleplay outside of encounters, nor should the monster's identity persist between encounters. A monster may not be captured or tamed.

You may not engage in erotic or sexual content of any nature at all when playing as a monster. There are no exceptions. Violating this rule will result in immediate revocation of the monster slot.

=== 4. Do not disturb events ===
Do not bring your monsters to events and large gatherings. If you become aware of an event only when you arrive at the scene, disengage when possible. Exceptions are if the organizers of the event specifically requested the presence of a monster either through their event listing on Discord or through OOC communication with you as a monster player.

=== 5. Usage of available tools ===
Monster players may use the monster map, teleport, and other features and tools available to them only when playing a monster and only for the purposes of monster encounters. All usage is logged and any misuse will be punished severely beyond just revoking a monster slot.

Many monsters come with descriptions or a set of instructions on how exactly they should be played. Monster players are expected to follow these instructions to help us ensure immersive experience for everyone.

For some monsters it is suitable, allowed, and even expected that the monster players will edit the character design or even create their own. These designs have to fit the theme and looks of the specific monster. When in doubt, show us the design and have it approved.

=== 6. Staff Authority ===
At any time, for any reason, staff have the authority to revoke the monster slot from any given player. This may happen even outside of rule breaks as we want to give other players a chance to play monsters.

Monster Slots

2026-06-18T22:51:26Z

Rataj:

Monster slots allow players to step out of the usual roleplay and take on the role of a monster for other players to encounter.

== Players ==
As a player, you may encounter monsters in the world. Should they defeat you, there is nothing but wounds, scars, and a great story to tell. In case you manage to kill the monster, you will be rewarded 30 silver coins.

After an encounter, you are able to rate the monster player to give us a feedback on how enjoyable the experience was based on their roleplay. This is not a competition, just a way to ensure good etiquette.

If you want to increase your chances of encountering monsters and fight with them more often, you can use '''/settings''' to opt into having your position on the map shown to monster players. This can be changed at any time.

== Monsters ==
If you wish to play a monster you have to first and foremost familiarize yourself with the guidelines and expectations outlined below. Then you can head to [https://avardon.com/monsters/play avardon.com/monsters/play] and sign up. After some time, if you are lucky, you may be randomly picked for the monster slot. From there on it is up to you to do a good job at playing a monster to keep the monster slot access.

All players with monster slot access also get a Discord role with access to a special channel for monsters to organize group encounters with other players and DMs. They are also notified of events such as the blood moon.

Monsters have the option to teleport into a monster gallery using '''/warp monster''', and switch between player slot and monster slot in there as well as choose a specific monster sheet and character design and teleport around the map to find players by simply roaming around. They may also utilize their own LFRP to attract players to their position or chase after those who opted into being shown on a web map for monsters.

== Guidelines and Expectations ==
The monster system exists to help promote a more dangerous and immersive world within [[Avardon]], contributing to the dreadful atmosphere of the setting. Monsters are encouraged to engage with players creatively; instilling dread and frightening players through both combat and non-combat encounters. Monster slots are a part of collaborative, cooperative storytelling and writing and should be fun for both the monster and other players in the encounter.

=== 1. Monster Play Etiquette ===
Encounters should focus on the narrative and immersive experience of the receiving players. Do not engage in encounters for the purposes of winning or the competitive aspect of combat.

Do not start encounters for the purpose of harassing or targeting specific players.

You may not actively seek to engage the same player in an encounter more than once per week.

Communication is key. Always be open and willing to OOC communication when the situation requires it.

Ensure that the strength of your monster is appropriate for the encounter. Do not approach a solo player with a monster designed for 3 players.

Avoid approaching LFRPs unless they are specifically looking for Trouble or Conflict. Players with other LFRP markers shouldn't be disrupted and you shall rather use the monster map or have your own LFRP if you can't find players randomly.

=== 2. Combat Rules ===
Monsters are subject to the same rules as all other players.

A monster may approach the camp or settlement of other players. When doing so, interact with players from outside the settlement rather than entering it. Create noise, growl, stomp your feet; to lure players outside. Thus providing an opportunity for players to choose whether to engage.

=== 3. Monster Roleplay ===
Monster players are expected to understand the lore and traits of the monster they have selected, and to act accordingly. Your monster has limited knowledge of the world around them, based on the specific monster.

Provide a reasonable opportunity for players to react in their preferred fashion. Depending on the nature of the monster, provide chances for players to pursue alternate resolutions to combat such as trying to run or hide.

Each monster is a discrete, unique entity. You may not use knowledge gained as a monster on your player character, and vice versa.

A monster is not meant for social roleplay outside of encounters, nor should roleplay persist throughout or between encounters. A monster may not be captured.

You may not engage in erotic or sexual content of any nature at all when playing as a monster. There are no exceptions. Violating this rule will result in immediate revocation of the monster slot.

=== 4. Do not disturb events ===
Do not bring your monsters to events and large gatherings. If you become aware of an event only when you arrive at the scene, disengage when possible. Exceptions are if the organizers of the event specifically requested the presence of a monster either through their event listing on Discord or through OOC communication with you as a monster player.

=== 5. Usage of available tools ===
Monster players may use the monster map, teleport, and other features and tools available to them only when playing a monster and only for the purposes of monster encounters. All usage is logged and any misuse will be punished severely beyond just revoking a monster slot.

Many monsters come with descriptions or a set of instructions on how exactly they should be played. Monster players are expected to follow these instructions to help us ensure immersive experience for everyone.

For some monsters it is suitable, allowed, and even expected that the monster players will edit the character design or even create their own. These designs have to fit the theme and looks of the specific monster. When in doubt, show us the design and have it approved.

=== 6. Staff Authority ===
At any time, for any reason, staff have the authority to revoke the monster slot from any given player. This may happen even outside of rule breaks as we want to give other players a chance to play monsters.

Main Page

2026-06-18T22:47:41Z

Rataj:

__NOTOC__
<templatestyles src="Template:Main page/shared/styles.css" />
{{Main page/header}}

<div id="home-content" class="home-grid">
<div class="home-card home-card--col1 home-card--row1">
<div class="home-card__label">Featured Articles</div>
<div class="home-link">
<div class="home-link__button">[[Lore Introduction]]</div>
<div class="home-link__button">[[Timeline]]</div>
<div class="home-link__button">[[Ravenloft]]</div>
<div class="home-link__button">[[Count Farkas]]</div>
<div class="home-link__button">[[Avardon:Mission|Our Mission & Values]]</div>
<div class="home-link__button">[[Bonk's Survival Guide]]</div>
<div class="home-link__button">[[Notable Locations]]</div>
<div class="home-link__button">[[Monster Slots]]</div>
</div>
</div>
<div class="home-card home-card--col1 home-card--row2">
<div class="home-card__label">Guides</div>
<div class="home-link">
<div class="home-link__button">[[Rules|Server Rules]]</div>
<div class="home-link__button">[[New Players Guide]]</div>
<div class="home-link__button">[[Reroll]]</div>
<div class="home-link__button">[[Combat Primer]]</div>
<div class="home-link__button">[[Movement]]</div>
<div class="home-link__button">[[Chat Commands]]</div>
<div class="home-link__button">[[Consequences]]</div>
<div class="home-link__button">[[Combat Rulings]]</div>
</div>
</div>
<div class="home-card home-card--col1 home-card--row5">
<div class="home-card__label">Lists</div>
<div class="home-link">
<div class="home-link__button">[[Races]]</div>
<div class="home-link__button">[[Classes]]</div>
<div class="home-link__button">[[Professions]]</div>
<div class="home-link__button">[[Feats]]</div>
<div class="home-link__button">[[Traits]]</div>
<div class="home-link__button">[[Spell Lists]]</div>
<div class="home-link__button">[[Equipment List]]</div>
<div class="home-link__button">[[Status Effects]]</div>
</div>
</div>

</div>

[https://avardon.com Main website]

[https://avardon.com/discord Discord server]

This site is still being worked on and you won't find a lot of articles here just yet.

'''You can help us by contributing.'''

Monster Slots

2026-06-18T22:45:09Z

Rataj: Protected "Monster Slots" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

Monster slots allow players to step out of the usual roleplay and take on the role of a monster for other players to encounter.

== Players ==
As a player, you may encounter monsters in the world. Should they defeat you, there is nothing but wounds, scars, and a great story to tell. In case you manage to kill the monster, you will be rewarded 30 silver coins.

After an encounter, you are able to rate the monster player to give us a feedback on how enjoyable the experience was based on their roleplay. This is not a competition, just a way to ensure good etiquette.

If you want to increase your chances of encountering monsters and fight with them more often, you can use '''/settings''' to opt into having your position on the map shown to monster players. This can be changed at any time.

== Monsters ==
If you wish to play a monster you have to first and foremost familiarize yourself with the guidelines and expectations outlined below. Then you can head to [https://avardon.com/monsters/play avardon.com/monsters/play] and sign up. After some time, if you are lucky, you may be randomly picked for the monster slot. From there on it is up to you to do a good job at playing a monster to keep the monster slot access.

All players with monster slot access also get a Discord role with access to a special channel for monsters to organize group encounters with other players and DMs. They are also notified of events such as the blood moon.

Monsters have the option to teleport into a monster gallery using '''/warp monster''', and switch between player slot and monster slot in there as well as choose a specific monster sheet and character design and teleport around the map to find players by simply roaming around. They may also utilize their own LFRP to attract players to their position or chase after those who opted into being shown on a web map for monsters.

== Guidelines and Expectations ==
The monster system exists to help promote a more dangerous and immersive world within [[Avardon]], contributing to the dreadful atmosphere of the setting. Monsters are encouraged to engage with players creatively; instilling dread and frightening players through both combat and non-combat encounters. Monster slots are a part of collaborative, cooperative storytelling and writing and should be fun for both the monster and other players in the encounter.

=== 1. Monster Play Etiquette ===
Encounters should focus on the narrative and immersive experience of the receiving players. Do not engage in encounters for the purposes of winning or the competitive aspect of combat.

Do not start encounters for the purpose of harassing or targeting specific players.

You may not actively seek to engage the same player in an encounter more than once per week.

Communication is key. Always be open and willing to OOC communication when the situation requires it.

Ensure that the strength of your monster is appropriate for the encounter. Do not approach a solo player with a monster designed for 3 players.

Avoid approaching LFRPs unless they are specifically looking for Trouble or Conflict. Players with other LFRP markers shouldn't be disrupted and you shall rather use the monster map or have your own LFRP if you can't find players randomly.

=== 2. Combat Rules ===
Monsters are subject to the same rules as all other players.

A monster may approach the camp or settlement of other players. When doing so, interact with players from outside the settlement rather than entering it. Create noise, growl, stomp your feet; to lure players outside. Thus providing an opportunity for players to choose whether to engage.

=== 3. Monster Roleplay ===
Monster players are expected to understand the lore and traits of the monster they have selected, and to act accordingly. Your monster has limited knowledge of the world around them, based on the specific monster.

Provide a reasonable opportunity for players to react in their preferred fashion. Depending on the nature of the monster, provide chances for players to pursue alternate resolutions to combat such as trying to run or hide.

Each monster is a discrete, unique entity. You may not use knowledge gained as a monster on your player character, and vice versa.

A monster is not meant for social roleplay outside of encounters, not should roleplay persist throughout or between encounters. A monster may not be captured.

You may not engage in erotic or sexual content of any nature at all when playing as a monster. There are no exceptions. Violating this rule will result in immediate revocation of the monster slot.

=== 4. Do not disturb events ===
Do not bring your monsters to events and large gatherings. If you become aware of an event only when you arrive at the scene, disengage when possible. Exceptions are if the organizers of the event specifically requested the presence of a monster either through their event listing on Discord or through OOC communication with you as a monster player.

=== 5. Usage of available tools ===
Monster players may use the monster map, teleport, and other features and tools available to them only when playing a monster and only for the purposes of monster encounters. All usage is logged and any misuse will be punished severely beyond just revoking a monster slot.

Many monsters come with descriptions or a set of instructions on how exactly they should be played. Monster players are expected to follow these instructions to help us ensure immersive experience for everyone.

For some monsters it is suitable, allowed, and even expected that the monster players will edit the character design or even create their own. These designs have to fit the theme and looks of the specific monster. When in doubt, show us the design and have it approved.

=== 6. Staff Authority ===
At any time, for any reason, staff have the authority to revoke the monster slot from any given player. This may happen even outside of rule breaks as we want to give other players a chance to play monsters.

Monster Slots

2026-06-18T22:44:54Z

Rataj:

Monster slots allow players to step out of the usual roleplay and take on the role of a monster for other players to encounter.

== Players ==
As a player, you may encounter monsters in the world. Should they defeat you, there is nothing but wounds, scars, and a great story to tell. In case you manage to kill the monster, you will be rewarded 30 silver coins.

After an encounter, you are able to rate the monster player to give us a feedback on how enjoyable the experience was based on their roleplay. This is not a competition, just a way to ensure good etiquette.

If you want to increase your chances of encountering monsters and fight with them more often, you can use '''/settings''' to opt into having your position on the map shown to monster players. This can be changed at any time.

== Monsters ==
If you wish to play a monster you have to first and foremost familiarize yourself with the guidelines and expectations outlined below. Then you can head to [https://avardon.com/monsters/play avardon.com/monsters/play] and sign up. After some time, if you are lucky, you may be randomly picked for the monster slot. From there on it is up to you to do a good job at playing a monster to keep the monster slot access.

All players with monster slot access also get a Discord role with access to a special channel for monsters to organize group encounters with other players and DMs. They are also notified of events such as the blood moon.

Monsters have the option to teleport into a monster gallery using '''/warp monster''', and switch between player slot and monster slot in there as well as choose a specific monster sheet and character design and teleport around the map to find players by simply roaming around. They may also utilize their own LFRP to attract players to their position or chase after those who opted into being shown on a web map for monsters.

== Guidelines and Expectations ==
The monster system exists to help promote a more dangerous and immersive world within [[Avardon]], contributing to the dreadful atmosphere of the setting. Monsters are encouraged to engage with players creatively; instilling dread and frightening players through both combat and non-combat encounters. Monster slots are a part of collaborative, cooperative storytelling and writing and should be fun for both the monster and other players in the encounter.

=== 1. Monster Play Etiquette ===
Encounters should focus on the narrative and immersive experience of the receiving players. Do not engage in encounters for the purposes of winning or the competitive aspect of combat.

Do not start encounters for the purpose of harassing or targeting specific players.

You may not actively seek to engage the same player in an encounter more than once per week.

Communication is key. Always be open and willing to OOC communication when the situation requires it.

Ensure that the strength of your monster is appropriate for the encounter. Do not approach a solo player with a monster designed for 3 players.

Avoid approaching LFRPs unless they are specifically looking for Trouble or Conflict. Players with other LFRP markers shouldn't be disrupted and you shall rather use the monster map or have your own LFRP if you can't find players randomly.

=== 2. Combat Rules ===
Monsters are subject to the same rules as all other players.

A monster may approach the camp or settlement of other players. When doing so, interact with players from outside the settlement rather than entering it. Create noise, growl, stomp your feet; to lure players outside. Thus providing an opportunity for players to choose whether to engage.

=== 3. Monster Roleplay ===
Monster players are expected to understand the lore and traits of the monster they have selected, and to act accordingly. Your monster has limited knowledge of the world around them, based on the specific monster.

Provide a reasonable opportunity for players to react in their preferred fashion. Depending on the nature of the monster, provide chances for players to pursue alternate resolutions to combat such as trying to run or hide.

Each monster is a discrete, unique entity. You may not use knowledge gained as a monster on your player character, and vice versa.

A monster is not meant for social roleplay outside of encounters, not should roleplay persist throughout or between encounters. A monster may not be captured.

You may not engage in erotic or sexual content of any nature at all when playing as a monster. There are no exceptions. Violating this rule will result in immediate revocation of the monster slot.

=== 4. Do not disturb events ===
Do not bring your monsters to events and large gatherings. If you become aware of an event only when you arrive at the scene, disengage when possible. Exceptions are if the organizers of the event specifically requested the presence of a monster either through their event listing on Discord or through OOC communication with you as a monster player.

=== 5. Usage of available tools ===
Monster players may use the monster map, teleport, and other features and tools available to them only when playing a monster and only for the purposes of monster encounters. All usage is logged and any misuse will be punished severely beyond just revoking a monster slot.

Many monsters come with descriptions or a set of instructions on how exactly they should be played. Monster players are expected to follow these instructions to help us ensure immersive experience for everyone.

For some monsters it is suitable, allowed, and even expected that the monster players will edit the character design or even create their own. These designs have to fit the theme and looks of the specific monster. When in doubt, show us the design and have it approved.

=== 6. Staff Authority ===
At any time, for any reason, staff have the authority to revoke the monster slot from any given player. This may happen even outside of rule breaks as we want to give other players a chance to play monsters.

Monster Slots

2026-06-18T22:37:58Z

Rataj:

Monster slots allow players to step out of the usual roleplay and take on the role of a monster for other players to encounter.

== Players ==
As a player, you may encounter monsters in the world. Should they defeat you, there is nothing but wounds, scars, and a great story to tell. In case you manage to kill the monster, you will be rewarded 30 silver coins.

After an encounter, you are able to rate the monster player to give us a feedback on how enjoyable the experience was based on their roleplay. This is not a competition, just a way to ensure good etiquette.

If you want to increase your chances of encountering monsters and fight with them more often, you can use '''/settings''' to opt into having your position on the map shown to monster players. This can be changed at any time.

== Monsters ==
If you wish to play a monster you have to first and foremost familiarize yourself with the guidelines and expectations outlined below. Then you can head to [https://avardon.com/monsters/play avardon.com/monsters/play] and sign up. After some time, if you are lucky, you may be randomly picked for the monster slot. From there on it is up to you to do a good job at playing a monster to keep the monster slot access.

All players with monster slot access also get a Discord role with access to a special channel for monsters to organize group encounters with other players and DMs. They are also notified of events such as the blood moon.

Monsters have the option to teleport into a monster gallery using '''/warp monster''', and switch between player slot and monster slot in there as well as choose a specific monster sheet and character design and teleport around the map to find players. They may utilize their own LFRP to attract players to their position or chase after those who opted into being shown on a web map for monsters.

== Guidelines and Expectations ==
The monster system exists to help promote a more dangerous and immersive world within [[Avardon]], contributing to the dreadful atmosphere of the setting. Monsters are encouraged to engage with players creatively; instilling dread and frightening players through both combat and non-combat encounters. Monster slots are a part of collaborative, cooperative storytelling and writing and should be fun for both the monster and other players in the encounter.

=== 1. Monster Play Etiquette ===
Encounters should focus on the narrative and immersive experience of the receiving players. Do not engage in encounters for the purposes of winning or the competitive aspect of combat.

Do not start encounters for the purpose of harassing or targeting specific players.

You may not actively seek to engage the same player in an encounter more than once per week.

Communication is key. Always be open and willing to OOC communication when the situation requires it.

Ensure that the strength of your Monster is appropriate for the encounter.

=== 2. Combat Rules ===
Monsters are subject to the same rules as all other players.

A monster may approach the camp or settlement of other players. When doing so, interact with players from outside the settlement rather than entering it. Create noise, growl, stomp your feet; to lure players outside. Thus providing an opportunity for players to choose whether to engage.

=== 3. Monster Roleplay ===
Monster players are expected to understand the lore and traits of the monster they have selected, and to act accordingly. Your monster has limited knowledge of the world around them, based on the specific monster.

Provide a reasonable opportunity for players to react in their preferred fashion. Depending on the nature of the monster, provide chances for players to pursue alternate resolutions to combat such as trying to run or hide.

Each monster is a discrete, unique entity. You may not use knowledge gained as a monster on your player character, and vice versa.

A monster is not meant for social roleplay outside of encounters, not should roleplay persist throughout or between encounters. A monster may not be captured.

You may not engage in erotic or sexual content of any nature at all when playing as a monster. There are no exceptions. Violating this rule will result in immediate revocation of the monster slot.

=== 4. Do not disturb events ===
Do not bring your monsters to events and large gatherings. If you become aware of an event only when you arrive at the scene, disengage when possible. Exceptions are if the organizers of the event specifically requested the presence of a monster either through their event listing on Discord or through OOC communication with you as a monster player.

=== 5. Usage of available tools ===
Monster players may use the monster map, teleport, and other features and tools available to them only when playing a monster and only for the purposes of monster encounters. All usage is logged and any misuse will be punished severely beyond just revoking a monster slot.

Many monsters come with descriptions or a set of instructions on how exactly they should be played. Monster players are expected to follow these instructions to help us ensure immersive experience for everyone.

For some monsters it is suitable, allowed, and even expected that the monster players will edit the character design or even create their own. These designs have to fit the theme and looks of the specific monster. When in doubt, show us the design and have it approved.

=== 6. Staff Authority ===
At any time, for any reason, staff have the authority to revoke the monster slot from any given player. This may happen even outside of rule breaks as we want to give other players a chance to play monsters.

Monster Slots

2026-06-18T22:29:16Z

Rataj: guidelines (written by Elvka, Raz, Pineapple, and me)

Combat Rulings

2026-06-15T17:26:39Z

Rataj: hiding rulings

Rules

2026-06-13T21:41:57Z

Rataj:

Hello there! We are glad that you are responsible and will dedicate a few minutes to read our rules.

Please don't just skip through the rules.
We want to keep our server friendly and immersive, prevent any possible attempts to spoil the game, and create a pleasant environment for '''all''' players to enjoy.
If you don't understand something, don't be afraid to ask us on [https://avardon.com/discord Discord] and we'll be more than happy to help you out.

At the same time we try to keep our rules concise and we rely on '''common sense''' of our players. These rules are not supposed to be exhaustive and all-encompassing. We expect our players to avoid any behavior such as ''rule-lawyering'' or acting against good faith and outside of the standards of our community, even if it doesn't break any specific rule outlined on this page.

We also want to make it very clear that no one is exempt from these rules. The rules apply equally to staff and players. In fact, staff members are under higher scrutiny to lead the community by example.

== Community Rules ==
=== M.1 - Server Culture ===
Avardon is an open and welcoming community founded on the expectation, that we treat each other as adults and as if we were all playing at a single table at a friend's house. We expect all players to recognize their peers as partners in collaborative writing and respect them as equals. [[Play-to-Lift]] mentality is expected, not optional.

Harassment, discrimination, or toxicity of any kind is absolutely unacceptable and has no place in our community. We want this community to be a place for you and for us to love coming back to.

=== M.2 - Adults Only ===
This server is only available to those of adult age (18+), who are also mature enough to not make us doubt it.

No representation of child or child-like characters is allowed. All characters must be at least the adult age for their respective species '''and''' also at least 20 years old. Portrayal of pregnancy is also not allowed.

=== M.3 - English Only ===
Avardon is an English speaking community, the sole language to be used in roleplay, tickets, and on any of our official channels is English.

Characters are allowed to use terms from other D&D languages (or suitable real-world languages in the case of regional dialects) as long as it is used sparsely for flavor, and other players whose characters know the language mechanically are helped to understand the phrase you used should they ask. You may not write entire sentences in these flavored languages, nor should you roleplay as knowing and speaking a language that is not included in our server's system. Please also avoid using terms that are too modern, such as internet slang.

=== M.4 - Dispute Resolution ===
If you find yourself in a dispute with another player, try to cooperate and resolve it together. However, do not argue and do not attempt to enforce rules yourself, rather let us know through a ticket. You shall never threaten anyone with a moderation action nor with a ticket.

Do not freeze roleplay to wait for staff involvement, keep the scenes rolling. An exception to this rule is if your consent is violated. In such a case, you may remove yourself from the scene at any time to ensure your personal comfort.

== Roleplaying Rules ==
=== R.1 - Character Creation ===
All players must follow and complete the whitelisting process before engaging in roleplay on the server. You are expected to follow the guidance provided by staff in your whitelisting ticket.

Characters are expected to follow the server lore in both their behavior and visuals. Please refer to the corresponding [[Races|race]] page for average height and other requirements. Characters should originate either from Toril or the Domains of Dread, including Avardon. Allowable exceptions are the Feywilds (Satyr, Eladrin) and Shadowfell (Shadar-Kai) if appropriate for the character race.

Once your whitelist is approved, you may only make realistic changes to the design of your character, such as changing hair style and warpaints. Your body and face should remain the same.

The depiction of your character should reflect your character sheet and equipment runes. Do not depict or roleplay abilities or equipment your character does not have.

=== R.2 - Roleplay Etiquette ===
When not in the spawn area, you are always considered to be ''In Character'' and should try your best to contribute to the immersive narrative experience with other players. While the concept of good etiquette may be difficult to define exhaustively, we expect you to at the very least:
* Minimize OOC chatter during roleplay scenes.
* React appropriately to the use of social rolls.
* Respect the agency of other players, do not force your actions on them without letting them react (powergaming).
* Do not play omniscient characters. Your character does not have access to an online wiki. Minimise the knowledge of your character to what they reasonably know, and do not 'lore-dump' information on other players.
* Take responsibility in being courteous and understanding towards players even if OOC tension arises. Step away if necessary.
* Respect and value the life of your own character, ensuring that they act in a way that best suits the situation (especially when they are in mortal danger, or at the mercy of another character).

=== R.3 - Metagaming ===
You are not allowed to take ''In Character'' actions based on knowledge you obtained as a player ''Out of Character''. This is known as ''metagaming'' and is strictly forbidden on Avardon.

You should also avoid sharing any information OOC that could influence stories if acted upon IC. Especially if it relates to instances of on-going or very recent combat, details about other characters or their actions. Use common sense, don't ruin stories by enabling others to ''metagame''.

It is important to maintain an immersive atmosphere where players are mostly only aware of what their character would know. Therefore, when in any doubt at all, do not share meta-knowledge with other players.

However, there are exceptions to this rule. You are allowed to share adventures of your own character, and discuss non-actionable things that have happened in the game. You can also look for roleplay and schedule roleplay through OOC means.

=== R.4 - Consent Sheets ===
Players are encouraged to create a consent sheet in their RPR profile to show what themes they are not comfortable with. It is the responsibility of every player to be aware of consent preferences of other players in a scene, as to not violate consent.

When unsure of a particular sensitive theme, the player wanting to initiate this theme is responsible for communicating to all players involved to confirm their approval, as violating preferences due to ignorance will never be excused.

Sensitive themes include, but are not limited to: graphical descriptions of gore, surgeries, torture, mutilation, self harm, and anything of erotic or sexual nature, especially rape (including the mention of).

Be aware that consent sheets cannot be abused to avoid mechanical consequences, and it is the right of any player to request a ''fade-to-black'' (FTB) when wanting to carry out a sensitive topic but not wanting to write out the details of it.

When a player becomes part of a scene which does not conform to their consent sheet and where they are not a main actor, that player is to be given a chance to depart the scene without undue delay.

=== R.5 - Adult Content ===
While we allow the depiction of adult content (such as nudity and erotic roleplay) on our server, we expect players to do so in responsible manner.

Nudity is not allowed in main hub areas (with exception of player-owned houses). Characters are required to at the very least cover their genitals and breasts.

Scenes depicting sexual themes must take place in a private setting where it may be reasonably assumed that no other players may accidentally stumble upon them.

All scenes of this nature that could be considered non-consensual or dubious in any way require OOC consent that can be withdrawn at any time, allowing players to stop and even void such scene.

Interest in any sexual themes may not be advertised through consent sheets, character profiles, or global chat.

=== R.6 - Act Names ===
Players may use the <code>/act</code> command to change their display name in order to use an alias or conceal their identity, but must not use a name of another character, or one that impersonates them, including names of NPCs.

=== R.7 - LFRP Etiquette ===
When using the Looking for Roleplay functionality on the in-game map, players are expected to follow these guidelines:
* Disable your marker when your scene is locked (PvP intent is dropped).
* Do not approach LFRP marker promoting Solo/Duo/Trio with more than equal number of players if your intention is to take hostile actions.
* Do not use the Solo/Duo/Trio tags in a misleading way. It has to reflect the amount of people present in a scene. These tags also shouldn't be used to deliberately shield yourself against unfair odds when at your base.

Keep in mind the intention of this rule: LFRP etiquette exists to prevent large groups from metagaming information displayed on LFRP markers to secure unfair advantage in combat. LFRP in general serves as a tool to find roleplay, new contacts, new stories and start some narrative.

== Game Rules ==
=== G.1 - Bugs, Cheating, Exploits ===
It may occur that bugs appear in our systems such as the combat or economy related scripts. We expect players to collaborate with the staff team in spotting and mitigating these bugs by reporting them in a timely manner.

We have zero tolerance policy for cheating, exploiting bugs and security vulnerabilities, abusing and misusing systems or enacting DDoS attacks and similar malicious actions.

=== G.2 - Always in a Clan ===
Every player has to be in a clan at all times. Even if they play solo. Any buildings not belonging to a clan will get deleted.

=== G.3 - Showing Equipment ===
Your worn armor and all weapons you intend to use have to be properly shown on your character design (utilizing Tot Custom).

You may not use any weapon in combat that your character isn't visually carrying (exceptions apply, such as pact weapons).

=== G.4 - Climbing ===
You may not climb onto structures, terrain, or other obstacles to enter or leave a clan base without using the Climb or Misty Step ability in RPR. Descending walls or terrain also requires using the Climb ability.

== Building Rules ==
=== B.1 - Building Limits ===
Every clan may only have one base (with exception of '''temporary''' camps).

Do not build beyond boundaries of the map or under terrain.

Main entrance of any build must be accessible without climbing.

Build at least '''50 tiles''' from a base of another clan, 100 tiles from the main hub, and 50 tiles from any public portal.

You may not build inside base game dungeons (caves are allowed, when in doubt ask in a ticket).

Land claim of your build should be proportionate to your clan size, it is not allowed to claim large area with sparsely placed building pieces.

Your build has to reasonably fit the setting and cannot be immersion breaking.

Always stay within the following limits:
{| class="wikitable"
! Players !! Building Pieces !! Decorations
|-
| 1 || 500 || 200
|-
| 2-3 || 800 || 400
|-
| 4-5 || 1500 || 600
|-
| 6-9 || 2500 || 1000
|-
| 10+ || 3500 || 1500
|}
Additionally, no clan should have more thralls/mounts than players.

These limits can be increased with donator building extensions.

=== B.2 - Performance Considerations ===
All clans have to keep server and client performance in mind when building their bases. Do not overuse trees, containers (decorations with inventory) and custom textures, do not put too many light sources close together. Build responsibly.

=== B.3 - Inactivity ===
Players that have been inactive for more than '''30''' days may be removed from their clan by our system. If the inactive player is a clan owner, their build will be transferred to active members or removed.

Builds that violate other rules (such as building limits) while also belonging to an inactive clan may be removed sooner, after 14 days since any member was last online, or 7 days since being brought into a build audit ticket.

== Combat Rules ==
=== C.1 - Scene Lock ===
Once PvP is declared (intent has been dropped), the scene is locked and no further players shall join the scene until the consequence phase is over. Everyone within the range of a PvP intent is locked into the scene unless they are not targeted by anyone else within the scene lock, in that case they can either join, leave or observe (declared using <code>/pvp observe</code>). Any player that stumbles upon the scene while it's locked has to leave the area immediately and isn't allowed to watch. Those players cannot roleplay witnessing anything they saw in the locked scene.

Exception from this rule are spars, tournaments, arena fights and friendly brawls, these do not lock the scene and people are free to come and go.

Once a scene is unlocked after the conclusion of consequences, all participants of the scene must be allowed to leave the area without being subject to any subsequent combat encounters.

No size of any group in combat may exceed 5. The total cap for any PvP is always 10 players.

=== C.2 - Combat Etiquette ===
As combat scenes tend to have high tension, it is especially important to be cordial to other players when you fight their characters. While the concept of good etiquette may be difficult to define exhaustively, we expect you to at the very least:
* Act in a friendly and respectful manner in OOC towards your IC foes (they're your fellow storytellers, not your enemies).
* Make sure your conflict has story, roleplay has to precede and follow a combat scene. PvP systems exist as a conflict resolution, to help you progress narrative.
* Emote only outside of your turn, ideally ''after''.
* Try to be swift with your turns, do not prolong combat with micro-optimizations or OOC arguments.
* Help new players and those who don't fight often, answer their questions, and be patient with them.
* Follow the official [[Combat Rulings]] in all niche cases we provided additional clarifications for.

=== C.3 - Consequences ===
The winning party may impose consequences on the losing party after a fight is concluded. While delivering those consequences, players are in a consequence phase.

This phase can only last 30 minutes. If consequences take longer time than that, the scene is no longer locked and other players may interact with it. Under no circumstances shall players slow down the roleplay to exploit this rule.

We differentiate four categories of consequences:
* Minor consequences are mechanical consequences that may be applied at any time.
* Major consequences are mechanical consequences that may only be applied if the winning party had at max +1 advantage in numbers (i.e. in 1v1 or 3v2, but not in 3v1 or 5v3).
* Escalated consequences are mechanical consequences that may only be applied if the previous level was already applied at least once by one of the victors against the defeated or by the defeated on one of the victors in previous fights (and at least one major consequence has to precede even the first escalated one) while also fulfilling the conditions for a major consequence.
* Consented consequences are non-mechanical consequences that may be applied only if the losing party actively consents to such consequences.

Keep in mind that any thievery consequences may be applied from you on a specific target only once per 24 hours. In other words, you may not rob the same person again after already doing so within the last 24 hours.

Only one consequence shall be applied on a character. Consequence stacking is not allowed.

Unmasking is not considered a consequence and can be done freely on the defeated party after combat.

All possible consequence options are listed in the [[Consequences|guide to consequences]].

=== C.4 - Mugging ===
You may mug someone and it may (or may not) be reasonable for the target character to give up their belongings without a fight. However same rules as with PvP consequences apply. Players can only take what consequences rules would allow them as if a fight was taking a place. If the target complies and PvP takes place anyway, the attackers shall not deliver any further consequences.

=== C.5 - Limits on Hostile Actions ===
While hostile actions are major and important part of our server, there are some limitations to when and where you may perform them.

Hostile actions include but are not limited to: combat, thievery, mugging, attempts to restrict, restrain, or forcefully hold a person, but also threats, harassment, intimidation, provocation, and any other acts that would likely lead to combat.

You may not perform hostile actions when:
* You are in a PvP restricted area (Livarun or Scarabend).
* You are within 20 tile radius of a public waypoint.

Combat Rulings

2026-06-13T20:58:03Z

Rataj: added ruling on crouching (LoS)

Monster Slots

2026-06-10T18:20:45Z

Rataj: Created page with "Monster slots allow players to step out of the usual roleplay and take on the role of a monster for other players to encounter. == Guidelines and Expectations == [ Work in progress ]"

Monster slots allow players to step out of the usual roleplay and take on the role of a monster for other players to encounter.

== Guidelines and Expectations ==
[ Work in progress ]

Compelled Duel

2026-06-04T18:17:56Z

Rataj: fixed

{{Infobox Ability
|image=Compelled_Duel.png
|type=Spell
|level=1
|school=Enchantment
|target=Single Target
|cost=Bonus Action
|range=3
|radius=None
|concentration=3
|saves=Wisdom
}}
'''Description:'''

You try to compel a creature into a duel. One creature that you can see within range makes a Wisdom saving throw. On a failed save, the target has Disadvantage on attack rolls against creatures other than you.

* Intended for '''combat use only'''.

Rules

2026-06-04T01:44:43Z

Rataj:

Hello there! We are glad that you are responsible and will dedicate a few minutes to read our rules.

Please don't just skip through the rules.
We want to keep our server friendly and immersive, prevent any possible attempts to spoil the game, and create a pleasant environment for '''all''' players to enjoy.
If you don't understand something, don't be afraid to ask us on [https://avardon.com/discord Discord] and we'll be more than happy to help you out.

At the same time we try to keep our rules concise and we rely on '''common sense''' of our players. These rules are not supposed to be exhaustive and all-encompassing. We expect our players to avoid any behavior such as ''rule-lawyering'' or acting against good faith and outside of the standards of our community, even if it doesn't break any specific rule outlined on this page.

We also want to make it very clear that no one is exempt from these rules. The rules apply equally to staff and players. In fact, staff members are under higher scrutiny to lead the community by example.

== Community Rules ==
=== M.1 - Server Culture ===
Avardon is an open and welcoming community founded on the expectation, that we treat each other as adults and as if we were all playing at a single table at a friend's house. We expect all players to recognize their peers as partners in collaborative writing and respect them as equals. [[Play-to-Lift]] mentality is expected, not optional.

Harassment, discrimination, or toxicity of any kind is absolutely unacceptable and has no place in our community. We want this community to be a place for you and for us to love coming back to.

=== M.2 - Adults Only ===
This server is only available to those of adult age (18+), who are also mature enough to not make us doubt it.

No representation of child or child-like characters is allowed. All characters must be at least the adult age for their respective species '''and''' also at least 20 years old. Portrayal of pregnancy is also not allowed.

=== M.3 - English Only ===
Avardon is an English speaking community, the sole language to be used in roleplay, tickets, and on any of our official channels is English.

Characters are allowed to use terms from other D&D languages (or suitable real-world languages in the case of regional dialects) as long as it is used sparsely for flavor, and other players whose characters know the language mechanically are helped to understand the phrase you used should they ask. You may not write entire sentences in these flavored languages, nor should you roleplay as knowing and speaking a language that is not included in our server's system. Please also avoid using terms that are too modern, such as internet slang.

=== M.4 - Dispute Resolution ===
If you find yourself in a dispute with another player, try to cooperate and resolve it together. However, do not argue and do not attempt to enforce rules yourself, rather let us know through a ticket. You shall never threaten anyone with a moderation action nor with a ticket.

Do not freeze roleplay to wait for staff involvement, keep the scenes rolling. An exception to this rule is if your consent is violated. In such a case, you may remove yourself from the scene at any time to ensure your personal comfort.

== Roleplaying Rules ==
=== R.1 - Character Creation ===
All players must follow and complete the whitelisting process before engaging in roleplay on the server. You are expected to follow the guidance provided by staff in your whitelisting ticket.

Characters are expected to follow the server lore in both their behavior and visuals. Please refer to the corresponding [[Races|race]] page for average height and other requirements. Characters should originate either from Toril or the Domains of Dread, including Avardon. Allowable exceptions are the Feywilds (Satyr, Eladrin) and Shadowfell (Shadar-Kai) if appropriate for the character race.

Once your whitelist is approved, you may only make realistic changes to the design of your character, such as changing hair style and warpaints. Your body and face should remain the same.

The depiction of your character should reflect your character sheet and equipment runes. Do not depict or roleplay abilities or equipment your character does not have.

=== R.2 - Roleplay Etiquette ===
When not in the spawn area, you are always considered to be ''In Character'' and should try your best to contribute to the immersive narrative experience with other players. While the concept of good etiquette may be difficult to define exhaustively, we expect you to at the very least:
* Minimize OOC chatter during roleplay scenes.
* React appropriately to the use of social rolls.
* Respect the agency of other players, do not force your actions on them without letting them react (powergaming).
* Do not play omniscient characters. Your character does not have access to an online wiki. Minimise the knowledge of your character to what they reasonably know, and do not 'lore-dump' information on other players.
* Take responsibility in being courteous and understanding towards players even if OOC tension arises. Step away if necessary.
* Respect and value the life of your own character, ensuring that they act in a way that best suits the situation (especially when they are in mortal danger, or at the mercy of another character).

=== R.3 - Metagaming ===
You are not allowed to take ''In Character'' actions based on knowledge you obtained as a player ''Out of Character''. This is known as ''metagaming'' and is strictly forbidden on Avardon.

You should also avoid sharing any information OOC that could influence stories if acted upon IC. Especially if it relates to instances of on-going or very recent combat, details about other characters or their actions. Use common sense, don't ruin stories by enabling others to ''metagame''.

It is important to maintain an immersive atmosphere where players are mostly only aware of what their character would know. Therefore, when in any doubt at all, do not share meta-knowledge with other players.

However, there are exceptions to this rule. You are allowed to share adventures of your own character, and discuss non-actionable things that have happened in the game. You can also look for roleplay and schedule roleplay through OOC means.

=== R.4 - Consent Sheets ===
Players are encouraged to create a consent sheet in their RPR profile to show what themes they are not comfortable with. It is the responsibility of every player to be aware of consent preferences of other players in a scene, as to not violate consent.

When unsure of a particular sensitive theme, the player wanting to initiate this theme is responsible for communicating to all players involved to confirm their approval, as violating preferences due to ignorance will never be excused.

Sensitive themes include, but are not limited to: graphical descriptions of gore, surgeries, torture, mutilation, self harm, and anything of erotic or sexual nature, especially rape (including the mention of).

Be aware that consent sheets cannot be abused to avoid mechanical consequences, and it is the right of any player to request a ''fade-to-black'' (FTB) when wanting to carry out a sensitive topic but not wanting to write out the details of it.

When a player becomes part of a scene which does not conform to their consent sheet and where they are not a main actor, that player is to be given a chance to depart the scene without undue delay.

=== R.5 - Adult Content ===
While we allow the depiction of adult content (such as nudity and erotic roleplay) on our server, we expect players to do so in responsible manner.

Nudity is not allowed in main hub areas (with exception of player-owned houses). Characters are required to at the very least cover their genitals and breasts.

Scenes depicting sexual themes must take place in a private setting where it may be reasonably assumed that no other players may accidentally stumble upon them.

All scenes of this nature that could be considered non-consensual or dubious in any way require OOC consent that can be withdrawn at any time, allowing players to stop and even void such scene.

=== R.6 - Act Names ===
Players may use the <code>/act</code> command to change their display name in order to use an alias or conceal their identity, but must not use a name of another character, or one that impersonates them, including names of NPCs.

=== R.7 - LFRP Etiquette ===
When using the Looking for Roleplay functionality on the in-game map, players are expected to follow these guidelines:
* Disable your marker when your scene is locked (PvP intent is dropped).
* Do not approach LFRP marker promoting Solo/Duo/Trio with more than equal number of players if your intention is to take hostile actions.
* Do not use the Solo/Duo/Trio tags in a misleading way. It has to reflect the amount of people present in a scene. These tags also shouldn't be used to deliberately shield yourself against unfair odds when at your base.

Keep in mind the intention of this rule: LFRP etiquette exists to prevent large groups from metagaming information displayed on LFRP markers to secure unfair advantage in combat. LFRP in general serves as a tool to find roleplay, new contacts, new stories and start some narrative.

== Game Rules ==
=== G.1 - Bugs, Cheating, Exploits ===
It may occur that bugs appear in our systems such as the combat or economy related scripts. We expect players to collaborate with the staff team in spotting and mitigating these bugs by reporting them in a timely manner.

We have zero tolerance policy for cheating, exploiting bugs and security vulnerabilities, abusing and misusing systems or enacting DDoS attacks and similar malicious actions.

=== G.2 - Always in a Clan ===
Every player has to be in a clan at all times. Even if they play solo. Any buildings not belonging to a clan will get deleted.

=== G.3 - Showing Equipment ===
Your worn armor and all weapons you intend to use have to be properly shown on your character design (utilizing Tot Custom).

You may not use any weapon in combat that your character isn't visually carrying (exceptions apply, such as pact weapons).

=== G.4 - Climbing ===
You may not climb onto structures, terrain, or other obstacles to enter or leave a clan base without using the Climb or Misty Step ability in RPR. Descending walls or terrain also requires using the Climb ability.

== Building Rules ==
=== B.1 - Building Limits ===
Every clan may only have one base (with exception of '''temporary''' camps).

Do not build beyond boundaries of the map or under terrain.

Main entrance of any build must be accessible without climbing.

Build at least '''50 tiles''' from a base of another clan, 100 tiles from the main hub, and 50 tiles from any public portal.

You may not build inside base game dungeons (caves are allowed, when in doubt ask in a ticket).

Land claim of your build should be proportionate to your clan size, it is not allowed to claim large area with sparsely placed building pieces.

Your build has to reasonably fit the setting and cannot be immersion breaking.

Always stay within the following limits:
{| class="wikitable"
! Players !! Building Pieces !! Decorations
|-
| 1 || 500 || 200
|-
| 2-3 || 800 || 400
|-
| 4-5 || 1500 || 600
|-
| 6-9 || 2500 || 1000
|-
| 10+ || 3500 || 1500
|}
Additionally, no clan should have more thralls/mounts than players.

These limits can be increased with donator building extensions.

=== B.2 - Performance Considerations ===
All clans have to keep server and client performance in mind when building their bases. Do not overuse trees, containers (decorations with inventory) and custom textures, do not put too many light sources close together. Build responsibly.

=== B.3 - Inactivity ===
Players that have been inactive for more than '''30''' days may be removed from their clan by our system. If the inactive player is a clan owner, their build will be transferred to active members or removed.

Builds that violate other rules (such as building limits) while also belonging to an inactive clan may be removed sooner, after 14 days since any member was last online, or 7 days since being brought into a build audit ticket.

== Combat Rules ==
=== C.1 - Scene Lock ===
Once PvP is declared (intent has been dropped), the scene is locked and no further players shall join the scene until the consequence phase is over. Everyone within the range of a PvP intent is locked into the scene unless they are not targeted by anyone else within the scene lock, in that case they can either join, leave or observe (declared using <code>/pvp observe</code>). Any player that stumbles upon the scene while it's locked has to leave the area immediately and isn't allowed to watch. Those players cannot roleplay witnessing anything they saw in the locked scene.

Exception from this rule are spars, tournaments, arena fights and friendly brawls, these do not lock the scene and people are free to come and go.

Once a scene is unlocked after the conclusion of consequences, all participants of the scene must be allowed to leave the area without being subject to any subsequent combat encounters.

No size of any group in combat may exceed 5. The total cap for any PvP is always 10 players.

=== C.2 - Combat Etiquette ===
As combat scenes tend to have high tension, it is especially important to be cordial to other players when you fight their characters. While the concept of good etiquette may be difficult to define exhaustively, we expect you to at the very least:
* Act in a friendly and respectful manner in OOC towards your IC foes (they're your fellow storytellers, not your enemies).
* Make sure your conflict has story, roleplay has to precede and follow a combat scene. PvP systems exist as a conflict resolution, to help you progress narrative.
* Emote only outside of your turn, ideally ''after''.
* Try to be swift with your turns, do not prolong combat with micro-optimizations or OOC arguments.
* Help new players and those who don't fight often, answer their questions, and be patient with them.
* Follow the official [[Combat Rulings]] in all niche cases we provided additional clarifications for.

=== C.3 - Consequences ===
The winning party may impose consequences on the losing party after a fight is concluded. While delivering those consequences, players are in a consequence phase.

This phase can only last 30 minutes. If consequences take longer time than that, the scene is no longer locked and other players may interact with it. Under no circumstances shall players slow down the roleplay to exploit this rule.

We differentiate four categories of consequences:
* Minor consequences are mechanical consequences that may be applied at any time.
* Major consequences are mechanical consequences that may only be applied if the winning party had at max +1 advantage in numbers (i.e. in 1v1 or 3v2, but not in 3v1 or 5v3).
* Escalated consequences are mechanical consequences that may only be applied if the previous level was already applied at least once by one of the victors against the defeated or by the defeated on one of the victors in previous fights (and at least one major consequence has to precede even the first escalated one) while also fulfilling the conditions for a major consequence.
* Consented consequences are non-mechanical consequences that may be applied only if the losing party actively consents to such consequences.

Keep in mind that any thievery consequences may be applied from you on a specific target only once per 24 hours. In other words, you may not rob the same person again after already doing so within the last 24 hours.

Only one consequence shall be applied on a character. Consequence stacking is not allowed.

Unmasking is not considered a consequence and can be done freely on the defeated party after combat.

All possible consequence options are listed in the [[Consequences|guide to consequences]].

=== C.4 - Mugging ===
You may mug someone and it may (or may not) be reasonable for the target character to give up their belongings without a fight. However same rules as with PvP consequences apply. Players can only take what consequences rules would allow them as if a fight was taking a place. If the target complies and PvP takes place anyway, the attackers shall not deliver any further consequences.

=== C.5 - Limits on Hostile Actions ===
While hostile actions are major and important part of our server, there are some limitations to when and where you may perform them.

Hostile actions include but are not limited to: combat, thievery, mugging, attempts to restrict, restrain, or forcefully hold a person, but also threats, harassment, intimidation, provocation, and any other acts that would likely lead to combat.

You may not perform hostile actions when:
* You are in a PvP restricted area (Livarun or Scarabend).
* You are within 20 tile radius of a public waypoint.

Rules

2026-06-03T15:06:20Z

Rataj: typo (preceed->precede)

Hello there! We are glad that you are responsible and will dedicate a few minutes to read our rules.

Please don't just skip through the rules.
We want to keep our server friendly and immersive, prevent any possible attempts to spoil the game, and create a pleasant environment for '''all''' players to enjoy.
If you don't understand something, don't be afraid to ask us on [https://avardon.com/discord Discord] and we'll be more than happy to help you out.

At the same time we try to keep our rules concise and we rely on '''common sense''' of our players. These rules are not supposed to be exhaustive and all-encompassing. We expect our players to avoid any behavior such as ''rule-lawyering'' or acting against good faith and outside of the standards of our community, even if it doesn't break any specific rule outlined on this page.

We also want to make it very clear that no one is exempt from these rules. The rules apply equally to staff and players. In fact, staff members are under higher scrutiny to lead the community by example.

== Community Rules ==
=== M.1 - Server Culture ===
Avardon is an open and welcoming community founded on the expectation, that we treat each other as adults and as if we were all playing at a single table at a friend's house. We expect all players to recognize their peers as partners in collaborative writing and respect them as equals. [[Play-to-Lift]] mentality is expected, not optional.

Harassment, discrimination, or toxicity of any kind is absolutely unacceptable and has no place in our community. We want this community to be a place for you and for us to love coming back to.

=== M.2 - Adults Only ===
This server is only available to those of adult age (18+), who are also mature enough to not make us doubt it.

No representation of child or child-like characters is allowed. All characters must be at least the adult age for their respective species '''and''' also at least 20 years old. Portrayal of pregnancy is also not allowed.

=== M.3 - Dispute Resolution ===
If you find yourself in a dispute with another player, try to cooperate and resolve it together. However, do not argue and do not attempt to enforce rules yourself, rather let us know through a ticket. You shall never threaten anyone with a moderation action nor with a ticket.

Do not freeze roleplay to wait for staff involvement, keep the scenes rolling. An exception to this rule is if your consent is violated. In such a case, you may remove yourself from the scene at any time to ensure your personal comfort.

== Roleplaying Rules ==
=== R.1 - Character Creation ===
All players must follow and complete the whitelisting process before engaging in roleplay on the server. You are expected to follow the guidance provided by staff in your whitelisting ticket.

Characters are expected to follow the server lore in both their behavior and visuals. Please refer to the corresponding [[Races|race]] page for average height and other requirements. Characters should originate either from Toril or the Domains of Dread, including Avardon. Allowable exceptions are the Feywilds (Satyr, Eladrin) and Shadowfell (Shadar-Kai) if appropriate for the character race.

Once your whitelist is approved, you may only make realistic changes to the design of your character, such as changing hair style and warpaints. Your body and face should remain the same.

The depiction of your character should reflect your character sheet and equipment runes. Do not depict or roleplay abilities or equipment your character does not have.

=== R.2 - Roleplay Etiquette ===
When not in the spawn area, you are always considered to be ''In Character'' and should try your best to contribute to the immersive narrative experience with other players. While the concept of good etiquette may be difficult to define exhaustively, we expect you to at the very least:
* Minimize OOC chatter during roleplay scenes.
* React appropriately to the use of social rolls.
* Respect the agency of other players, do not force your actions on them without letting them react (powergaming).
* Do not play omniscient characters. Your character does not have access to an online wiki. Minimise the knowledge of your character to what they reasonably know, and do not 'lore-dump' information on other players.
* Take responsibility in being courteous and understanding towards players even if OOC tension arises. Step away if necessary.
* Respect and value the life of your own character, ensuring that they act in a way that best suits the situation (especially when they are in mortal danger, or at the mercy of another character).

=== R.3 - Metagaming ===
You are not allowed to take ''In Character'' actions based on knowledge you obtained as a player ''Out of Character''. This is known as ''metagaming'' and is strictly forbidden on Avardon.

You should also avoid sharing any information OOC that could influence stories if acted upon IC. Especially if it relates to instances of on-going or very recent combat, details about other characters or their actions. Use common sense, don't ruin stories by enabling others to ''metagame''.

It is important to maintain an immersive atmosphere where players are mostly only aware of what their character would know. Therefore, when in any doubt at all, do not share meta-knowledge with other players.

However, there are exceptions to this rule. You are allowed to share adventures of your own character, and discuss non-actionable things that have happened in the game. You can also look for roleplay and schedule roleplay through OOC means.

=== R.4 - Consent Sheets ===
Players are encouraged to create a consent sheet in their RPR profile to show what themes they are not comfortable with. It is the responsibility of every player to be aware of consent preferences of other players in a scene, as to not violate consent.

When unsure of a particular sensitive theme, the player wanting to initiate this theme is responsible for communicating to all players involved to confirm their approval, as violating preferences due to ignorance will never be excused.

Sensitive themes include, but are not limited to: graphical descriptions of gore, surgeries, torture, mutilation, self harm, and anything of erotic or sexual nature, especially rape (including the mention of).

Be aware that consent sheets cannot be abused to avoid mechanical consequences, and it is the right of any player to request a ''fade-to-black'' (FTB) when wanting to carry out a sensitive topic but not wanting to write out the details of it.

When a player becomes part of a scene which does not conform to their consent sheet and where they are not a main actor, that player is to be given a chance to depart the scene without undue delay.

=== R.5 - Adult Content ===
While we allow the depiction of adult content (such as nudity and erotic roleplay) on our server, we expect players to do so in responsible manner.

Nudity is not allowed in main hub areas (with exception of player-owned houses). Characters are required to at the very least cover their genitals and breasts.

Scenes depicting sexual themes must take place in a private setting where it may be reasonably assumed that no other players may accidentally stumble upon them.

All scenes of this nature that could be considered non-consensual or dubious in any way require OOC consent that can be withdrawn at any time, allowing players to stop and even void such scene.

=== R.6 - Act Names ===
Players may use the <code>/act</code> command to change their display name in order to use an alias or conceal their identity, but must not use a name of another character, or one that impersonates them, including names of NPCs.

=== R.7 - LFRP Etiquette ===
When using the Looking for Roleplay functionality on the in-game map, players are expected to follow these guidelines:
* Disable your marker when your scene is locked (PvP intent is dropped).
* Do not approach LFRP marker promoting Solo/Duo/Trio with more than equal number of players if your intention is to take hostile actions.
* Do not use the Solo/Duo/Trio tags in a misleading way. It has to reflect the amount of people present in a scene. These tags also shouldn't be used to deliberately shield yourself against unfair odds when at your base.

Keep in mind the intention of this rule: LFRP etiquette exists to prevent large groups from metagaming information displayed on LFRP markers to secure unfair advantage in combat. LFRP in general serves as a tool to find roleplay, new contacts, new stories and start some narrative.

== Game Rules ==
=== G.1 - Bugs, Cheating, Exploits ===
It may occur that bugs appear in our systems such as the combat or economy related scripts. We expect players to collaborate with the staff team in spotting and mitigating these bugs by reporting them in a timely manner.

We have zero tolerance policy for cheating, exploiting bugs and security vulnerabilities, abusing and misusing systems or enacting DDoS attacks and similar malicious actions.

=== G.2 - Always in a Clan ===
Every player has to be in a clan at all times. Even if they play solo. Any buildings not belonging to a clan will get deleted.

=== G.3 - Showing Equipment ===
Your worn armor and all weapons you intend to use have to be properly shown on your character design (utilizing Tot Custom).

You may not use any weapon in combat that your character isn't visually carrying (exceptions apply, such as pact weapons).

=== G.4 - Climbing ===
You may not climb onto structures, terrain, or other obstacles to enter or leave a clan base without using the Climb or Misty Step ability in RPR. Descending walls or terrain also requires using the Climb ability.

== Building Rules ==
=== B.1 - Building Limits ===
Every clan may only have one base (with exception of '''temporary''' camps).

Do not build beyond boundaries of the map or under terrain.

Main entrance of any build must be accessible without climbing.

Build at least '''50 tiles''' from a base of another clan, 100 tiles from the main hub, and 50 tiles from any public portal.

You may not build inside base game dungeons (caves are allowed, when in doubt ask in a ticket).

Land claim of your build should be proportionate to your clan size, it is not allowed to claim large area with sparsely placed building pieces.

Your build has to reasonably fit the setting and cannot be immersion breaking.

Always stay within the following limits:
{| class="wikitable"
! Players !! Building Pieces !! Decorations
|-
| 1 || 500 || 200
|-
| 2-3 || 800 || 400
|-
| 4-5 || 1500 || 600
|-
| 6-9 || 2500 || 1000
|-
| 10+ || 3500 || 1500
|}
Additionally, no clan should have more thralls/mounts than players.

These limits can be increased with donator building extensions.

=== B.2 - Performance Considerations ===
All clans have to keep server and client performance in mind when building their bases. Do not overuse trees, containers (decorations with inventory) and custom textures, do not put too many light sources close together. Build responsibly.

=== B.3 - Inactivity ===
Players that have been inactive for more than 45 days may be removed from their clan by our system. If the inactive player is a clan owner, their build will be transferred to active members or removed.

== Combat Rules ==
=== C.1 - Scene Lock ===
Once PvP is declared (intent has been dropped), the scene is locked and no further players shall join the scene until the consequence phase is over. Everyone within the range of a PvP intent is locked into the scene unless they are not targeted by anyone else within the scene lock, in that case they can either join, leave or observe (declared using <code>/pvp observe</code>). Any player that stumbles upon the scene while it's locked has to leave the area immediately and isn't allowed to watch. Those players cannot roleplay witnessing anything they saw in the locked scene.

Exception from this rule are spars, tournaments, arena fights and friendly brawls, these do not lock the scene and people are free to come and go.

Once a scene is unlocked after the conclusion of consequences, all participants of the scene must be allowed to leave the area without being subject to any subsequent combat encounters.

No size of any group in combat may exceed 5. The total cap for any PvP is always 10 players.

=== C.2 - Combat Etiquette ===
As combat scenes tend to have high tension, it is especially important to be cordial to other players when you fight their characters. While the concept of good etiquette may be difficult to define exhaustively, we expect you to at the very least:
* Act in a friendly and respectful manner in OOC towards your IC foes (they're your fellow storytellers, not your enemies).
* Make sure your conflict has story, roleplay has to precede and follow a combat scene. PvP systems exist as a conflict resolution, to help you progress narrative.
* Emote only outside of your turn, ideally ''after''.
* Try to be swift with your turns, do not prolong combat with micro-optimizations or OOC arguments.
* Help new players and those who don't fight often, answer their questions, and be patient with them.
* Follow the official [[Combat Rulings]] in all niche cases we provided additional clarifications for.

=== C.3 - Consequences ===
The winning party may impose consequences on the losing party after a fight is concluded. While delivering those consequences, players are in a consequence phase.

This phase can only last 30 minutes. If consequences take longer time than that, the scene is no longer locked and other players may interact with it. Under no circumstances shall players slow down the roleplay to exploit this rule.

We differentiate four categories of consequences:
* Minor consequences are mechanical consequences that may be applied at any time.
* Major consequences are mechanical consequences that may only be applied if the winning party had at max +1 advantage in numbers (i.e. in 1v1 or 3v2, but not in 3v1 or 5v3).
* Escalated consequences are mechanical consequences that may only be applied if the previous level was already applied at least once by one of the victors against the defeated or by the defeated on one of the victors in previous fights (and at least one major consequence has to precede even the first escalated one) while also fulfilling the conditions for a major consequence.
* Consented consequences are non-mechanical consequences that may be applied only if the losing party actively consents to such consequences.

Keep in mind that any thievery consequences may be applied from you on a specific target only once per 24 hours. In other words, you may not rob the same person again after already doing so within the last 24 hours.

Only one consequence shall be applied on a character. Consequence stacking is not allowed.

Unmasking is not considered a consequence and can be done freely on the defeated party after combat.

All possible consequence options are listed in the [[Consequences|guide to consequences]].

=== C.4 - Mugging ===
You may mug someone and it may (or may not) be reasonable for the target character to give up their belongings without a fight. However same rules as with PvP consequences apply. Players can only take what consequences rules would allow them as if a fight was taking a place. If the target complies and PvP takes place anyway, the attackers shall not deliver any further consequences.

=== C.5 - Limits on Hostile Actions ===
While hostile actions are major and important part of our server, there are some limitations to when and where you may perform them.

Hostile actions include but are not limited to: combat, thievery, mugging, attempts to restrict, restrain, or forcefully hold a person, but also threats, harassment, intimidation, provocation, and any other acts that would likely lead to combat.

You may not perform hostile actions when:
* You are in a PvP restricted area (Livarun or Scarabend).
* You are within 20 tile radius of a public waypoint.

Flavor Spells

2026-05-31T14:29:44Z

Rataj:

Flavor spells may be used to enhance your roleplay and give it flavor. You may not use a flavor spell to provide yourself a mechanical advantage in any fashion, in particular in relation to PvP. To be affected by a flavor spell is based on consent, you cannot force the effects of a flavor spell on another player. You should not roleplay using multiple flavor spells that require concentration. Be mindful of component requirements, range, and duration when casting flavor spells. Your use of flavor spells in roleplay should be limited to their spell description on this wiki.

=== Continual Flame ===

* Range: Touch
* Components: V, S, M
* Duration: Until dispelled

A flame, equivalent in brightness to a torch, springs forth from an object that you touch. The effect looks like a regular flame, but it creates no heat and doesn’t use oxygen. A continual flame can be covered or hidden but not smothered or quenched.

=== Control Flames ===

* Range: 6 tiles
* Components: S
* Duration: Instantaneous or 1 hour

You choose an existing non-magical flame that you can see within range and that fits within a 5-foot cube. You affect it in one of the following ways:

* You instantaneously extinguish the flames within the cube.
* You double or halve the area of bright light and dim light cast by the flame, change its color, or both. The change lasts for 1 hour.
* You cause simple shapes—such as the vague form of a creature, an inanimate object, or a location—to appear within the flames and animate as you like. The shapes last for 1 hour or until dismissed.

=== Create Water ===

* Range: 3 tiles
* Components: V, S, M (a drop of water if creating water or a few grains of sand if destroying it)
* Duration: Instantaneous

You either create or destroy water.

Create Water. You create up to 2 litres of clean water within range in an open container. Alternatively, the water falls as rain in a 5-foot cube within range, extinguishing exposed flames in the area.
=== Dancing Lights ===

* Range: 12 tiles
* Components: V, S, M (a bit of phosphorus or wychwood, or a glowworm)
* Duration: Concentration, up to 1 minute

You create up to four torch-sized lights within range, making them appear as torches, lanterns, or glowing orbs that hover in the air for the duration. You can also combine the four lights into one glowing vaguely humanoid form of Medium size. Whichever form you choose, each light sheds dim light in a 10-foot radius.

=== Druidcraft ===

* Range: 3 tiles
* Components: V, S
* Duration: Instantaneous

Whispering to the spirits of nature, you create one of the following effects within range:

* You create a tiny, harmless sensory effect that predicts what the weather will be at your location for the next 24 hours. The effect might manifest as a golden orb for clear skies, a cloud for rain, falling snowflakes for snow, and so on. This effect persists for 1 round.
* You instantly make a flower blossom, a seed pod open, or a leaf bud bloom.
* You create an instantaneous, harmless sensory effect, such as falling leaves, a puff of wind, the sound of a small animal, or the faint odor of skunk. The effect must fit in a 5-foot cube.
* You instantly light or snuff out a candle, a torch, or a small campfire.

=== Illusory Script ===

* Range: Touch
* Components: S, M (a lead-based ink worth at least 10 gp, which the spell consumes)
* Duration: 10 days

You write on parchment, paper, or some other suitable writing material and imbue it with a potent illusion that lasts for the duration.

To you and any creatures you designate when you cast the spell, the writing appears normal, written in your hand, and conveys whatever meaning you intended when you wrote the text. To all others, the writing appears as if it were written in an unknown or magical script that is unintelligible. Alternatively, you can cause the writing to appear to be an entirely different message, written in a different hand and language, though the language must be one you know.

Should the spell be dispelled, the original script and the illusion both disappear.

=== Levitate ===

* Range: 6 tiles
* Components: V, S, M
* Duration: Concentration, up to 10 minutes

One creature or loose object of your choice that you can see within range rises vertically, up to 5 feet from the original point of casting, and remains suspended there for the duration. The spell can levitate a target that weighs up to 500 pounds. An unwilling creature cannot be affected.

The target can move only by pushing or pulling against a fixed object or surface within reach. The affected creature cannot freely move around without such leverage. The effect can be dismissed at any time by the affected creature to safely float back down. If the affected creature inadvertently finds themselves more than 5 feet of the ground after being displaced, the creature will fall and the levitation spell will not cushion their fall.

=== Light ===

* Range: Touch
* Components: V, M (a firefly or phosphorescent moss)
* Duration: 1 hour

You touch one object that is no larger than 10 feet in any dimension. Until the spell ends, the object sheds bright light in a 20-foot radius and dim light for an additional 20 feet. The light can be colored as you like. Completely covering the object with something opaque blocks the light. The spell ends if you cast it again or dismiss it as an action.

=== Mage Hand ===

* Range: 3 tiles
* Components: V, S
* Duration: 1 minute

A spectral, floating hand appears at a point you choose within range. The hand lasts for the duration or until you dismiss it as an action. The hand vanishes if it is ever more than 30 feet away from you or if you cast this spell again.

You can use your action to control the hand. You can use the hand for things such as manipulating an object, opening an unlocked door or container, stowing or retrieving an item from an open container, or pouring the contents out of a vial or bottle. You can move the hand up to 30 feet away from your location.

The hand can’t attack, activate magical items, or carry more than 10 pounds.

=== Major Image ===

* Range: 12 tiles
* Components: V, S, M (a bit of fleece)
* Duration: Concentration, up to 10 minutes

You create the image of an object, a creature, or some other visible phenomenon that is no larger than a 20-foot cube. The image appears at a spot that you can see within range and lasts for the duration, including sounds, smells, and temperature appropriate to the thing depicted. You can’t create sufficient heat or cold to cause damage, a sound loud enough to deal damage or deafen a creature, or a smell that might sicken a creature.

While the image can be animated, the image itself cannot change location. Specifically it cannot move along with your character. If you leave the range of the image it disappears.

Physical interaction with the image reveals it to be an illusion, because things can pass through it. A creature that uses its action to examine the image can determine that it is an illusion with a successful Intelligence (Investigation) check against your spell save DC. If a creature discerns the illusion for what it is, the creature can see through the image, and its other sensory qualities become faint to the creature.

=== Mending ===

* Range: Touch
* Components: V, S, M (two lodestones)
* Duration: Instantaneous

This spell repairs a single break or tear in an object you touch, such as a broken chain link, two halves of a broken key, a torn cloak, or a leaking wineskin. As long as the break or tear is no larger than 0.5 foot in any dimension, you mend it, leaving no trace of the former damage.

This spell can physically repair a magic item or construct, but the spell can’t restore magic to such an object.

=== Minor Illusion ===

* Range: 3 tiles
* Components: S, M (a bit of fleece)
* Duration: 1 minute

You create a sound or an image of an object within range that lasts for the duration. The illusion also ends if you dismiss it as an action or cast this spell again.

If you create a sound, its volume can range from a whisper to a scream. It can be your voice, someone else’s voice, a lion’s roar, a beating of drums, or any other sound you choose. The sound continues unabated throughout the duration, or you can make discrete sounds at different times before the spell ends.

If you create an image of an object—such as a chair, muddy footprints, or a small chest—it must be no larger than a 5-foot cube. The image can’t create sound, light, smell, or any other sensory effect. Physical interaction with the image reveals it to be an illusion, because things can pass through it.

While the image can be animated, the image itself cannot change location. Specifically it cannot move along with your character. If you leave the range of the image it disappears.

If a creature uses its action to examine the sound or image, the creature can determine that it is an illusion with a successful Intelligence (Investigation) check against your spell save DC. If a creature discerns the illusion for what it is, the illusion becomes faint to the creature.

''Note: You may not impersonate the voice of other characters.''

=== Mold Earth ===

* Range: 3 tiles
* Components: S
* Duration: Instantaneous or 1 hour

You choose a portion of dirt or stone that you can see within range and that fits within a 5-foot cube. You manipulate it in one of the following ways:

* If you target an area of loose earth, you can instantaneously excavate it, move it along the ground, and deposit it up to 5 feet away. This movement doesn’t have enough force to cause damage.
* You cause shapes, colors, or both to appear on the dirt or stone, spelling out words, creating images, or shaping patterns. The changes last for 1 hour.

=== Plant Growth ===

* Range: 15 tiles
* Components: V, S
* Duration: Instantaneous

This spell channels vitality into plants within a specific area. It causes plants to grow rapidly and increases their vitality over a longer period of time, causing them to blossom, grow fruit, and for fruit to ripen. This spell can be cast on individual plants or multiple plants within a small area.

=== Prestidigitation ===

* Range: 1 tile
* Components: V, S
* Duration: Up to 1 hour

This spell is a minor magical trick that novice spellcasters use for practice. You create one of the following magical effects within range:

* You create an instantaneous, harmless sensory effect, such as a shower of sparks, a puff of wind, faint musical notes, or an odd odor.
* You instantaneously light or snuff out a candle, a torch, or a small campfire.
* You instantaneously clean or soil an object no larger than 1 cubic foot.
* You chill, warm, or flavor up to 1 cubic foot of nonliving material for 1 hour.
* You make a color, a small mark, or a symbol appear on an object or a surface for 1 hour.
* You create a nonmagical trinket or an illusory image that can fit in your hand and that lasts until the end of your next turn.

=== Purify Food and Drink ===

* Range: 1 tile
* Components: V, S
* Duration: Instantaneous

All nonmagical food and drink within a 5-foot-radius sphere centered on a point of your choice within range is purified and rendered free of poison and disease. The spell cannot undo the natural rotting process of food.

=== Shape Water ===

* Range: 3 tiles
* Components: S
* Duration: Instantaneous or 1 hour

You choose an area of water that you can see within range and that fits within a 5-foot cube. You manipulate it in one of the following ways:

* You instantaneously move or otherwise change the flow of the water as you direct, up to 5 feet in any direction. This movement doesn’t have enough force to cause damage.
* You cause the water to form into simple shapes and animate at your direction. This change lasts for 1 hour.
* You change the water’s color or opacity. The water must be changed in the same way throughout. This change lasts for 1 hour.
* You freeze the water, provided that there are no creatures in it. The water unfreezes in 1 hour.

=== Silent Image ===

* Range: 6 tiles
* Components: V, S, M (a bit of fleece)
* Duration: Concentration, up to 10 minutes

You create the image of an object, a creature, or some other visible phenomenon that is no larger than a 15-foot cube. The image appears at a spot within range and lasts for the duration. The image is purely visual; it isn’t accompanied by sound, smell, or other sensory effects.

While the image can be animated, the image itself cannot change location. Specifically it cannot move along with your character. If you leave the range of the image it disappears.

Physical interaction with the image reveals it to be an illusion, because things can pass through it. A creature that uses its action to examine the image can determine that it is an illusion with a successful Intelligence (Investigation) check against your spell save DC. If a creature discerns the illusion for what it is, the creature can see through the image.

=== Thaumaturgy ===

* Range: 3 tiles
* Components: V
* Duration: Up to 1 minute

You manifest a minor wonder, a sign of supernatural power, within range. You create one of the following magical effects within range:

* Your voice booms up to three times as loud as normal for 1 minute.
* You cause flames to flicker, brighten, dim, or change color for 1 minute.
* You cause harmless tremors in the ground for 1 minute.
* You create an instantaneous sound that originates from a point of your choice within range, such as a rumble of thunder, the cry of a raven, or ominous whispers.
* You instantaneously cause an unlocked door or window to fly open or slam shut.

=== Tenser's Floating Disk ===

* Range: 3 tiles
* Components: V, S, M (a drop of mercury)
* Duration: 1 hour

This spell creates a circular, horizontal plane of force, 3 feet in diameter and 1 inch thick, that floats 3 feet above the ground in an unoccupied space of your choice that you can see within range. The disk remains for the duration, and can hold up to 500 pounds. If more weight is placed on it, the spell ends, and everything on the disk falls to the ground.

The disk is immobile while you are within 20 feet of it. If you move more than 15 feet away from it, the disk follows you so that it remains within 15 feet of you. It can move across uneven terrain, up or down stairs, slopes, and the like, but it can’t cross an elevation change of 5 feet or more. For example, the disk can’t move across a 5-foot-deep pit, nor could it leave such a pit if it were created at the bottom.

If you move more than 50 feet from the disk (typically because it can’t move around an obstacle to follow you), the spell ends.

A creature cannot stand on the disk, directly or indirectly, and the disk cannot be moved in any other way than described above.

=== Unseen Servant ===

* Range: 6 tiles
* Components: V, S, M (a piece of string and a bit of wood)
* Duration: 1 hour

This spell creates an invisible, mindless, shapeless, Medium force that performs simple tasks at your command until the spell ends. The servant springs into existence in an unoccupied space on the ground within range.

You can mentally command the servant to move up and interact with an object. The servant can perform simple tasks that a human servant could do, such as fetching things, cleaning, mending, folding clothes, lighting fires, serving food, and pouring wine. Once you give the command, the servant performs the task to the best of its ability until it completes the task, then waits for your next command.

If you command the servant to perform a task that would move it more than 60 feet away from you, the spell ends. The servant cannot damage other entities.

Consequences

2026-05-25T18:44:36Z

Rataj: added flowchart