Rules - Revision history

Possum at 20:48, 14 October 2025

2025-10-14T20:48:02Z

← Older revision		Revision as of 16:48, 14 October 2025
Line 218:		Line 218:
	== You are expected to perform the job you signed up for ==		== You are expected to perform the job you signed up for ==
	When your character joins the round, you are accepting the responsibilities that the job you have chosen brings with it. Remember: if you are playing in a slot, you are likely preventing other players from performing that role. It is important that you fulfill the tasks that you have signed up for!		When your character joins the round, you are accepting the responsibilities that the job you have chosen brings with it. Remember: if you are playing in a slot, you are likely preventing other players from performing that role. It is important that you fulfill the tasks that you have signed up for!
	*Breakers should protect the safe zone from danger, the Ascendant should ensure that power is up and should provide treatment to injuries and other services, the ~~Ashwood~~ should bring in needed supplies on request.		*Breakers should protect the safe zone from danger, the Ascendant should ensure that power is up and should provide treatment to injuries and other services, the blackwood should bring in needed supplies on request.

	*A player must take into account the qualifications (both physical and mental) of their character’s role before placing them into it. If staff find your character to be unsatisfactory in fulfilling the requirements of the role, we may instruct you to revise your character.		*A player must take into account the qualifications (both physical and mental) of their character’s role before placing them into it. If staff find your character to be unsatisfactory in fulfilling the requirements of the role, we may instruct you to revise your character.

R4d6: /* You are expected to forget events that are deemed non-canon */ Another typo

2023-08-13T16:00:52Z

You are expected to forget events that are deemed non-canon: Another typo

← Older revision		Revision as of 12:00, 13 August 2023
Line 247:		Line 247:
	*This rule also applies to events that cause catastrophic damage to the safe zone, such as a Code Ruby/Onyx scenario. As a general rule event coordinators '''should''' say before or after an event if it is non-canon or not.		*This rule also applies to events that cause catastrophic damage to the safe zone, such as a Code Ruby/Onyx scenario. As a general rule event coordinators '''should''' say before or after an event if it is non-canon or not.

	*If you are killed in a round and then revived in the same round, ~~you're~~ memory is entirely intact and may act accordingly.		*If you are killed in a round and then revived in the same round, your memory is entirely intact and may act accordingly.

	= <b>The intent of the rules is more important than the letter</b> =		= <b>The intent of the rules is more important than the letter</b> =

R4d6: /* You are expected to forget events that are deemed non-canon */ Forgotten space

2023-08-13T15:59:25Z

You are expected to forget events that are deemed non-canon: Forgotten space

← Older revision		Revision as of 11:59, 13 August 2023
Line 245:		Line 245:
	*The round ending does not make you immune to a character perma-kill. Just because you evaded capture or was not killed by the time it restarted does not mean everyone forgets what your character did. If you get caught and the evidence is ironclad enough, you will be PK'd.		*The round ending does not make you immune to a character perma-kill. Just because you evaded capture or was not killed by the time it restarted does not mean everyone forgets what your character did. If you get caught and the evidence is ironclad enough, you will be PK'd.

	*This rule also applies to events that cause catastrophic damage to the safe zone, such as a ~~code ruby~~/~~onyxscenario~~. As a general rule event coordinators '''should''' say before or after an event if it is non-canon or not.		*This rule also applies to events that cause catastrophic damage to the safe zone, such as a Code Ruby/Onyx scenario. As a general rule event coordinators '''should''' say before or after an event if it is non-canon or not.

	*If you are killed in a round and then revived in the same round, you're memory is entirely intact and may act accordingly.		*If you are killed in a round and then revived in the same round, you're memory is entirely intact and may act accordingly.

Possum: /* You are expected to perform the job you signed up for */

2023-08-13T15:58:45Z

You are expected to perform the job you signed up for

← Older revision		Revision as of 11:58, 13 August 2023
Line 233:		Line 233:
	*Do not hijack other people's jobs. For example, breakers are for making arrests, agents are for investigating crimes. While you might be able to do both, you likely are not suited for it, let others help you if their available.		*Do not hijack other people's jobs. For example, breakers are for making arrests, agents are for investigating crimes. While you might be able to do both, you likely are not suited for it, let others help you if their available.

	*Playing jobs that can be called upon at any time to assist other crew members in emergencies waives your right to have interruption-free (E)RP sessions in private, including the dorms. If you join as a rosaria, expect to be interrupted out of private scenes. If you’re a ~~breaker~~, you are expected to set up power systems and repair any large-scale damage that hampers the rest of the residents, regardless of your intent to have sex with the whatever hole is nearby.		*Playing jobs that can be called upon at any time to assist other crew members in emergencies waives your right to have interruption-free (E)RP sessions in private, including the dorms. If you join as a rosaria, expect to be interrupted out of private scenes. If you’re a rune master, you are expected to set up power systems and repair any large-scale damage that hampers the rest of the residents, regardless of your intent to have sex with the whatever hole is nearby.

	*Dungeon diving is not a valid reason to be busy from your assigned job. If your job has multiple positions or is intended to dungeon dive, inform others and ensure someone is there to cover for you until you get back.		*Dungeon diving is not a valid reason to be busy from your assigned job. If your job has multiple positions or is intended to dungeon dive, inform others and ensure someone is there to cover for you until you get back.

Possum: /* Dungeoneering */

2023-08-13T15:27:31Z

Dungeoneering

← Older revision		Revision as of 11:27, 13 August 2023
Line 266:		Line 266:


	~~= Dungeoneering =~~
	A core aspect of our server is our PvE content, this can range from going into randomly generated dungeons, leaving the safety of the colony, or simply crawling through maintenance. However, we also have specific jobs for this and ones who should be doing this. As such, '''jobs discouraged or disallowed from dungeoneering are actively targeted by staff when spotted.''' Refer to the list below of jobs allowed to or dungeoneer.
	~~===Core Dungeoneering===~~
	~~These jobs are allowed to enter and leave the colony, and dungeons at will. There expected to do a wide range of things and will never be targeted for being in these areas.~~
	* Foreman \| Salvager \| Prospector
	* Lodge Hunt Master \| Lodge Hunter
	* Outsider

	~~=== The Junkfield ===~~
	~~The Junkfield has no restrictions on any role or job, do to its infinitely reproducible allowing no gameplay or fun to be lost by people using it.~~
	* Anyone - Any reason as long as they are not ignoring or breaking their job.

	~~===Staff Guide for Handling Dungeoneering===~~
	When someone not in the listed jobs above is caught in a dungeon, admin staff are not only instructed to but '''encouraged''' to decide if the player is affecting the overall round to a negative effect and use in-game traps and mobs to kill the respective offender using the listed guide when needed. (Keep in mind we're here to have fun not punish people like robots following stonecold laws for breaking the rules. Use your best mindset for this.) However, this comes with a check list of things that need to be verified.

	# Is the person apart of an event (official, mini-event, player run) that gives them a good roleplay reason to be in the area? I.E. the prospectors wanted extra hands and church litanies for healing, so they paid a vector to come with them.
	~~# Is the person there for a reason that isn't looting? I.E. are they rescuing someone who is injured, etc. etc.~~
	# If both answer to both is no, all staff must first subtle message the player in question with a warning of some kind such as "Something doesn't feel right, you're being watched..." or "An unearthly silence fills the space around you." or similar foreboding messages.
	~~# '''Give them a reasonable amount of time to flee the area''' (usually 5 minutes) after the warning is given so they can avoid being killed.~~
	# If they have not left, start by adding additional mobs/traps in their way as they continue. Under no circumstances should a player ever see the mobs or traps spawned, this means you cannot as staff randomly spawn mobs on top of, in front of, or in implausible locations to harm the offender. This includes spawning hard to spot traps in the path of a walking player, '''do not do this'''. As a rule, all additional spawns should be 7 or more tiles away from the player at all times. All methods to ramp the difficulty must be done in such a way that it makes perfect sense in-character, using thematically appropriate traps/enemies. I.E. You shouldn't be spawning primal renders inside the greyson field offices, etc. etc.
	# Ramp up the pressure until they are dead. Do not begin with 10-20 spiders, start with 3-4 and keep progressing until they are overwhelmed or use lethal traps that they could avoid but will kill them if they're not careful. The goal is first to scare them to flee and only kill them if they persist. Staff who actively and badly enforce this rule without properly adhering to this list will get a [[Job_Strikes_and_You \| Strike]]. If they get 3 or more strikes, they are no longer allowed to enforce this rule and may be demoted.
	# The body should remain intact and reviable '''the first time this happens.''' The second time in the same round, a guilty offender should be rendered unreviable via being devoured by roaches. '''Do not gib or severely fuck up a body beyond repair on the first offense.'''


	[[Category:Guides]]		[[Category:Guides]]
	[[Category:Rules]]		[[Category:Rules]]

Possum: /* Create and play server-appropriate characters */

2023-08-13T15:26:46Z

Create and play server-appropriate characters

Show changes

Possum: /* Keep IC and OOC separate */

2023-08-13T15:03:29Z

Keep IC and OOC separate

← Older revision		Revision as of 11:03, 13 August 2023
Line 100:		Line 100:
	== Keep IC and OOC separate ==		== Keep IC and OOC separate ==
	*Don't complain in OOC or LOOC when your actions IC get you in trouble. If its a rules violation then Ahelp or open a ticket on the discord.		*Don't complain in OOC or LOOC when your actions IC get you in trouble. If its a rules violation then Ahelp or open a ticket on the discord.
	*IC (In-character) and OOC (Out-of-Character) actions and knowledge should be separated as much as possible. Don't use OOC channels to discuss what's going on IC until after the round is finished, don't use OOC knowledge to do things your character wouldn't know, such as ~~operate medical~~ machines ~~when~~ a ~~cargo technician~~. You are not playing yourself in the game, you are controlling a character with their own wants and knowledge and the IC/OOC boundary is to help reflect that.		*IC (In-character) and OOC (Out-of-Character) actions and knowledge should be separated as much as possible. Don't use OOC channels to discuss what's going on IC until after the round is finished, don't use OOC knowledge to do things your character wouldn't know, such as operating the weaving machines as a custodian. You are not playing yourself in the game, you are controlling a character with their own wants and knowledge and the IC/OOC boundary is to help reflect that.
	**Note that these same rules apply to LOOC as well.		**Note that these same rules apply to LOOC as well.
	*Disconnecting or using other OOC means to avoid IC consequences is against the rules. If you do urgently need to leave the server even though you're being punished, your options are either to surrender and get it over with, or use admin help to inform the admins, "I know ~~Security is~~ after me, but I have to go because (some emergency)." Failure to take ten seconds to tell an admin before disconnecting may result in harsher punishment.		*Disconnecting or using other OOC means to avoid IC consequences is against the rules. If you do urgently need to leave the server even though you're being punished, your options are either to surrender and get it over with, or use admin help to inform the admins, "I know enforcers are after me, but I have to go because (some emergency)." Failure to take ten seconds to tell an admin before disconnecting may result in harsher punishment.

	=== Metacomms, metagaming, multi-keying, (etc) are not allowed ===		=== Metacomms, metagaming, multi-keying, (etc) are not allowed ===

Possum: /* Do not misuse Global OOC */

2023-08-13T15:02:06Z

Do not misuse Global OOC

← Older revision		Revision as of 11:02, 13 August 2023
Line 90:		Line 90:

	=== Do not misuse Global OOC ===		=== Do not misuse Global OOC ===
	~~Many servers simply mute global~~ OOC~~. We do not~~, ~~because the OOC command~~ is ~~useful~~ to ~~have on in an RP heavy server~~.		Global OOC begins muted, it being turned on is not a chance to abuse it.

	* Global OOC is used, for instance, to contact someone you were typing a reply to had walked out of the room before you were done, and you're trying to ask them to come back. It's also useful if you're a new player, or an old player exploring new mechanics, who asks something like, "How do I make Tricord again?" or something short and similar. Short, sweet, and relevant OOC messages are generally okay. Welcoming old players returning, or new players joining, is also generally okay.		* Global OOC is used, for instance, to contact someone you were typing a reply to had walked out of the room before you were done, and you're trying to ask them to come back. It's also useful if you're a new player, or an old player exploring new mechanics, who asks something like, "How do I make Tricord again?" or something short and similar. Short, sweet, and relevant OOC messages are generally okay. Welcoming old players returning, or new players joining, is also generally okay.

Possum: /* Roleplay as long as it's feasible */

2023-08-13T15:01:14Z

Roleplay as long as it's feasible

← Older revision		Revision as of 11:01, 13 August 2023
Line 82:		Line 82:
	*Death is not uncommon, even in the safe zone, but it is still impactful. When a character dies, or your own character dies and is revived, death should be considered an immensely painful and graphic experience. One should stay in character during said experiences, statements of ‘oh well’ or mutilating a corpse for ‘fun’ would not be reasonable responses.		*Death is not uncommon, even in the safe zone, but it is still impactful. When a character dies, or your own character dies and is revived, death should be considered an immensely painful and graphic experience. One should stay in character during said experiences, statements of ‘oh well’ or mutilating a corpse for ‘fun’ would not be reasonable responses.

	*'''You are to have fleshed out character records.''' These are used not only for roleplay but are to be utilized, if specified by staff, for long-term consequences for actions. Players are supported to use these as roleplay documents and treat others with these seriously. Our expectations for what should be in these can be found [[Example Paperwork]].		*'''You are to have fleshed out character records.''' These are used not only for roleplay but are to be utilized, if specified by staff, for long-term consequences for actions. Players are supported to use these as roleplay documents and treat others with these seriously. Our expectations for what should be in these can be found in [[Example Paperwork]].

	=== Do not join with an inappropriate ckey ===		=== Do not join with an inappropriate ckey ===

Possum: /* Roleplay as long as it's feasible */

2023-08-13T15:01:05Z

Roleplay as long as it's feasible

← Older revision		Revision as of 11:01, 13 August 2023
Line 82:		Line 82:
	*Death is not uncommon, even in the safe zone, but it is still impactful. When a character dies, or your own character dies and is revived, death should be considered an immensely painful and graphic experience. One should stay in character during said experiences, statements of ‘oh well’ or mutilating a corpse for ‘fun’ would not be reasonable responses.		*Death is not uncommon, even in the safe zone, but it is still impactful. When a character dies, or your own character dies and is revived, death should be considered an immensely painful and graphic experience. One should stay in character during said experiences, statements of ‘oh well’ or mutilating a corpse for ‘fun’ would not be reasonable responses.

	*'''You are to have fleshed out character records.''' These are used not only for roleplay but are to be utilized, if specified by staff, for long-term consequences for actions. Players are supported to use these as roleplay documents and treat others with these seriously. Our expectations for what should be in these can be found on [[~~https://hammersfall.wiki/index.php/Example_Paperwork\|the Character Records page of our~~ Example Paperwork ~~wiki.~~]]		*'''You are to have fleshed out character records.''' These are used not only for roleplay but are to be utilized, if specified by staff, for long-term consequences for actions. Players are supported to use these as roleplay documents and treat others with these seriously. Our expectations for what should be in these can be found [[Example Paperwork]].

	=== Do not join with an inappropriate ckey ===		=== Do not join with an inappropriate ckey ===