Rules - Revision history

Pineapple: /* B.1 - Building Limits */ Spelling correction

2026-10-13T14:38:31Z

B.1 - Building Limits: Spelling correction

← Older revision		Revision as of 14:38, 13 October 2026
Line 127:		Line 127:
	Do not build beyond boundaries of the map or under terrain.		Do not build beyond boundaries of the map or under terrain.

	~~Main~~ entrance of any build must be accessible without climbing.		The 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.		Build at least '''50 tiles''' from a base of another clan, 100 tiles from the main hubs, and 50 tiles from any public portal.

Rataj: raid rules adjustments (mostly)

2026-10-11T20:55:17Z

raid rules adjustments (mostly)

← Older revision		Revision as of 20:55, 11 October 2026
Line 36:		Line 36:
	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.		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. Characters should be original creations, and not look similar to known characters from ~~DnD~~ settings or other popular media.		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. Characters should be original creations, and not look similar to known characters from D&D settings or other popular media.

	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.		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.
Line 59:		Line 59:

	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.		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.

			Characters are not allowed to share any knowledge off-screen, that means through Discord, or in between your own characters.

	=== R.4 - Consent Sheets ===		=== R.4 - Consent Sheets ===
Line 113:		Line 115:

	If you are overcoming obstacles to get into a base of another clan, this is also considered ''Breaking and Entering'' and may only be done after declaring a ''Burglary'' or ''Raid''.		If you are overcoming obstacles to get into a base of another clan, this is also considered ''Breaking and Entering'' and may only be done after declaring a ''Burglary'' or ''Raid''.

			=== G.5 - Muling Items ===
			You may not store items outside of your inventory for the purpose of retrieving those items with a future character. When joining the same clan of your previous character with a new character, you may not acquire items from said clan for the first week after the reroll.

			You may also not assist other players with this or any other form of subverting our systems for unfair economical benefit.

	== Building Rules ==		== Building Rules ==
Line 259:		Line 266:

	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.

			Per-clan cooldown is also activated when 3+ attackers extort or mug any individual on defender's land claim and their conditions are met. For example, if you're threatened with combat unless you pay some silver, and you abide by this request, your base cannot be subject to any hostile actions from the same perpetrators for 7 days, just like it would be protected if a fight did break out.

	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.		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.

Pineapple: /* R.1 - Character Creation */ Added rule about lookalike characters from popular settings

2026-10-09T15:33:04Z

R.1 - Character Creation: Added rule about lookalike characters from popular settings

← Older revision		Revision as of 15:33, 9 October 2026
Line 36:		Line 36:
	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.		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.		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. Characters should be original creations, and not look similar to known characters from DnD settings or other popular media.

	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.		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.

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 ===