Rules - Revision history

Rataj: limited Skirmish cooldown to 3+

2026-08-30T00:20:10Z

limited Skirmish cooldown to 3+

← Older revision		Revision as of 00:20, 30 August 2026
Line 256:		Line 256:
	There are two cooldowns in place to protect players from a chain of hostile actions unfolding at their base:		There are two cooldowns in place to protect players from a chain of hostile actions unfolding at their base:
	* Global cooldown of 3 days automatically protects the clan from '''anyone''' declaring a ''Raid'' on them after they were victim of a ''Raid'', unless they waive this protection using the /raid menu, and by doing so they are consenting to subsequent raids.		* Global cooldown of 3 days automatically protects the clan from '''anyone''' declaring a ''Raid'' on them after they were victim of a ''Raid'', unless they waive this protection using the /raid menu, and by doing so they are consenting to subsequent raids.
	* Per-clan cooldown of 7 days protects a clan from being attacked by the same attackers, whether it is a ''Raid'' or a ''Skirmish'', after being subjected to a ''Raid'' or a ''Skirmish'' by the same clan or group of attackers. This is not automatic, and it is the responsibility of the raid leader's clan, but also each attacker as an individual to not be part of any ''Raid'' or ''Skirmish'' against the same defending clan within this period, unless waived by consent.		* Per-clan cooldown of 7 days protects a clan from being attacked by the same attackers, whether it is a ''Raid'' or a ''Skirmish'', after being subjected to a ''Raid'' or a ''Skirmish'' (with 3+ attackers) by the same clan or group of attackers. This is not automatic, and it is the responsibility of the raid leader's clan, but also each attacker as an individual to not be part of any ''Raid'' or ''Skirmish'' against the same defending clan within this period, unless waived by consent.

	The per-clan cooldown is voided when the previously attacked clan engages in a raid against the previously attacking clan.		The per-clan cooldown is voided when the previously attacked clan engages in a raid against the previously attacking clan.

Rataj: clarifications

2026-08-29T23:39:20Z

clarifications

← Older revision		Revision as of 23:39, 29 August 2026
Line 260:		Line 260:
	The per-clan cooldown is voided when the previously attacked clan engages in a raid against the previously attacking clan.		The per-clan cooldown is voided when the previously attacked clan engages in a raid against the previously attacking clan.

	If a clan approaches another with no hostile intentions during a protection cooldown, it is their responsibility not to escalate, and to leave when asked to. They may never take hostile actions or declare a PvP intent themselves while on cooldown.		If a clan approaches another's base with no hostile intentions during a protection cooldown, it is their responsibility not to escalate, and to leave when asked to. They may never take hostile actions or declare a PvP intent themselves while on cooldown and on the other clan's land claim.

	=== N.9 - Player Agency over Conflict ===		=== N.9 - Player Agency over Conflict ===

Rataj: added conflict rules

2026-08-29T23:25:14Z

added conflict rules

@@ Line 111: / Line 111: @@
 === 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 ==
@@ Line 208: / Line 210: @@
 * You are in a PvP restricted area (Livarun or Scarabend).
 * You are within 20 tile radius of a public waypoint.

Rataj at 21:50, 18 July 2026

2026-07-18T21:50:10Z

← Older revision		Revision as of 21:50, 18 July 2026
Line 29:		Line 29:

	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.		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 ==		== Roleplaying Rules ==
Line 68:		Line 70:

	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.		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 ===		=== R.5 - Adult Content ===
Line 151:		Line 155:

	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.		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 ==		== Combat Rules ==
	=== C.1 - Scene Lock ===		=== 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.		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.		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.
Line 174:		Line 181:
	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.		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~~.		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:		We differentiate four categories of consequences:
	* Minor consequences are mechanical consequences that may be applied at any time.		* 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).		* 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.		* 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.		* Consented consequences are non-mechanical consequences that may be applied only if the losing party actively consents to such consequences.

Rataj at 20:57, 22 June 2026

2026-06-22T20:57:00Z

← Older revision		Revision as of 20:57, 22 June 2026
Line 120:		Line 120:
	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).		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).		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.		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.

Rataj at 15:39, 20 June 2026

2026-06-20T15:39:27Z

← Older revision		Revision as of 15:39, 20 June 2026
Line 116:		Line 116:
	Main entrance of any build must be accessible without climbing.		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.		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).		You may not build inside base game dungeons (caves are allowed, when in doubt ask in a ticket).

Rataj at 21:41, 13 June 2026

2026-06-13T21:41:57Z

← Older revision		Revision as of 21:41, 13 June 2026
Line 77:		Line 77:

	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.		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 ===		=== R.6 - Act Names ===

Rataj at 01:44, 4 June 2026

2026-06-04T01:44:43Z

← Older revision		Revision as of 01:44, 4 June 2026
Line 20:		Line 20:
	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.		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 ===		=== 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.		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.

Line 139:		Line 144:

	=== B.3 - Inactivity ===		=== 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.		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 ==		== Combat Rules ==

Rataj: typo (preceed->precede)

2026-06-03T15:06:20Z

typo (preceed->precede)

← Older revision		Revision as of 15:06, 3 June 2026
Line 154:		Line 154:
	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:		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).		* 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 ~~preceed~~ and follow a combat scene. PvP systems exist as a conflict resolution, to help you progress narrative.		* 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''.		* 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.		* Try to be swift with your turns, do not prolong combat with micro-optimizations or OOC arguments.

Pineapple: /* R.4 - Consent Sheets */ added self harm to sensitive themes

2026-05-27T15:25:32Z

R.4 - Consent Sheets: added self harm to sensitive themes

← Older revision		Revision as of 15:25, 27 May 2026
Line 58:		Line 58:
	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.		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, and anything of erotic or sexual nature, especially rape (including the ~~mentions~~ of).		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.		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.