Roleplay First
This is a serious roleplay server. Roleplay comes before winning, mechanics, or personal outcomes.
All actions must make sense within the world, the situation, and your character.
AUSTRALISRPLoginAustralisRP is built around serious, collaborative roleplay. Read the rules before playing and use the search below whenever you need to find a specific standard quickly.
This is a serious roleplay server. Roleplay comes before winning, mechanics, or personal outcomes.
All actions must make sense within the world, the situation, and your character.
Players are expected to remain in character at all times while in the server unless explicitly told otherwise by staff through approved OOC methods.
Characters should behave consistently with their established background, experiences, profession, and knowledge.
Using unrealistic knowledge or abilities simply because the player possesses that knowledge OOC may be considered Fail RP or metagaming.
Characters must be believable within the setting.
Superhuman feats, unrealistic endurance, impossible actions, or behaviour that ignores reasonable consequences are prohibited. Example of unrealistic behaviour: "My character was born with this mask and it cannot be removed"
Fail RP occurs when a player:
Fail RP may result in escalating punishment.
Deliberately disrupting immersion for yourself or others is prohibited.
Any mention of tickets, staff actions, reports, moderation, or punishments in-character is strictly forbidden.
This includes:
All scenes must be played out fully in character.
Issues are to be raised after the scene has concluded.
Using OOC implications, including staff, rules, reports, or punishment, to influence an RP outcome is prohibited.
This is not a casual or semi-RP server.
Players are expected to remain in character and treat scenes seriously.
Humour and light-hearted RP are welcome where appropriate, but intentionally turning serious situations into unrealistic or disruptive scenes is not.
Referencing staff or tickets during RP to influence a scene is considered a severe immersion breach and may result in:
Players may choose how much their character values their life.
Fearless, reckless, or dangerous characters are allowed where that behaviour is consistent with the character.
If a player chooses reckless behaviour, they must fully roleplay the consequences.
Possible outcomes include:
Choosing not to value your life does not protect you from consequences.
A character being fearless does not mean they are immune to injury, capture, arrest, or death.
Staff may enforce or escalate consequences if a player deliberately avoids, ignores, or downplays reasonable outcomes.
You may not retcon, undo, or alter outcomes simply because the result was undesirable.
Violence must have clear RP justification.
Killing, shooting, attacking, or deliberately injuring another player without reasonable buildup or justification is prohibited.
Deliberately using your vehicle to injure or kill another player without reasonable buildup is prohibited.
Where reasonable, escalation should occur before violence.
Gunfire should not automatically be the opening action to every conflict.
The level of violence used should make sense for the situation and previous RP.
Rampages, griefing, mass violence, or violence without narrative purpose are prohibited.
Using information gained OOC while acting IC is prohibited.
This includes information obtained through:
If your character did not reasonably learn the information in-character, they may not act on it.
You may not force actions or outcomes onto other players.
All players must be given a reasonable opportunity to react.
Staff may enforce an action or consequence where a player is found to be deliberately avoiding the consequences outlined under Section 3.
Ignoring injuries, restraints, physical limitations, vehicle damage, environmental conditions, or reasonable realism is prohibited.
Transfer of items, vehicles, money or properties to another player or character with the intent to avoid OOC or roleplay consequences is prohibited.
All injuries must be roleplayed appropriately.
Serious injuries should have meaningful effects on your character and may carry lasting consequences.
Being mechanically healed does not automatically mean every injury has disappeared from RP.
Combat must serve the story, not replace it.
Repeatedly seeking PvP without developing RP around it may be treated as combat-focused or low-quality roleplay.
Torture or extreme RP requires explicit consent from all involved players.
The consent requirements under Section 13 apply.
Players who are able to stand or recover at the location they were downed must treat themselves as severely injured.
Recovering does not reset the scene or remove the injuries sustained.
After recovering from a downed state, players may not re-engage in the PvP situation in any way.
Players may not provide medical treatment to themselves until they are fully clear of the active scene.
The only permitted action after recovering from a downed state during an active hostile scene is attempting to escape.
Escape must be reasonable and roleplayed appropriately.
Severe injuries must continue to be roleplayed while escaping.
A recently downed player may not suddenly sprint, fight, climb, or perform physically demanding actions as though they were unharmed.
Breaches of downed-state rules may be treated as Fail RP and combat abuse.
A player who is downed and escapes may not re-engage in the active scene.
A scene remains active while:
Players may only return after the scene has fully concluded and may not return for the purpose of influencing its outcome.
Returning to or influencing an active scene after being removed from it is prohibited.
This includes returning with another character.
After a hostile scene concludes, involved players and groups must wait 30 minutes before intentionally beginning another hostile scene.
The cooldown applies to the entire involved group.
Rotating players, characters, vehicles, or participants to bypass the cooldown is prohibited.
Non-hostile RP is permitted.
Defensive action is allowed where another party initiates unavoidable hostility against you.
Deliberately bypassing the hostile-scene cooldown may be treated as Fail RP and combat abuse.
Weapons and game mechanics may not be used in ways intended primarily to gain an unrealistic mechanical advantage.
Examples may include:
Attempting to technically comply with a rule while deliberately bypassing its intent may still be treated as combat abuse.
Criminal roleplay must be intentional, story-driven, and grounded in character motivation.
Players engaging in criminal RP are expected to consider and develop the following:
Criminal characters should have a reason for being criminals.
This may include:
“They just like crime” or constant unexplained violence is not sufficient on its own.
Crimes should involve reasonable planning, preparation, and forethought.
This may include:
Poor planning is allowed.
Having no RP or planning whatsoever behind repeated major crimes is not.
Criminal RP should have clear short-term or long-term goals.
Goals may include:
Endless, directionless crime with no evolving objective is discouraged.
Criminal RP should create opportunities for other players.
This includes:
Crime should create ripples that affect the wider world.
Criminal activity should be paced appropriately.
Escalation should feel earned rather than immediate.
Repeated high-level crimes without downtime, consequences, or story development may be treated as Fail RP.
Criminals must accept the outcomes of their actions.
Being:
is not a failure of roleplay.
Consequences are a key part of meaningful criminal RP and often create stronger stories than constant success.
Using mechanics to avoid reasonable criminal consequences is prohibited.
Players must use /scene to leave clues, evidence, or indicators where information would reasonably exist but is not represented mechanically.
Examples include:
Example:
/scene Locals may have seen a black Sultan leaving northbound at high speed.
Criminal roleplay must leave behind a reasonable and discoverable trail where one would realistically exist.
Police should have the opportunity to:
Perfect, consequence-free crimes should not be the objective of RP.
Intentionally eliminating all possible clues, evidence, witnesses, or patterns solely to prevent investigation is prohibited.
If a crime would realistically leave evidence that is not mechanically represented, it must be represented through RP using /scene or another appropriate method.
Roleplay is not about winning or never being caught.
Being identified, investigated, pursued, arrested, or convicted can create more depth and longevity than constant success.
Players are expected to embrace consequences as part of meaningful RP.
Criminal scenes deliberately designed to provide no reasonable RP or investigative opportunity may be reviewed by staff.
Repeated attempts to avoid all evidence or consequences may be treated as Fail RP.
Police roleplay must be taken seriously by both police and civilian players.
Police officers are expected to behave professionally and consistently with their role, training, department policies, and the circumstances of the scene.
Police officers may not abuse their position, permissions, equipment, information, or game mechanics for personal or OOC advantage.
This includes using police-only information or equipment for another character.
Police corruption is prohibited by default.
Players may not engage in corrupt police RP unless the storyline and intended corruption have been discussed with and approved by server staff beforehand.
Approval must exist before corrupt behaviour begins.
Starting corruption RP and seeking approval afterwards is not permitted.
Where staff have approved a corruption storyline, the corruption must remain within the boundaries of that approval.
Approved corruption must be:
Possible motivations may include:
Staff approval for one corruption storyline does not grant blanket permission for unrelated corrupt behaviour.
Approved police corruption must contribute to ongoing RP.
“Silent corruption” designed solely to provide mechanical advantages is prohibited.
Corruption should create reasonable:
Even where corruption has been approved, corrupt officers may not use their position to provide unreasonable mechanical advantages.
Unless specifically included within staff approval, this includes:
Staff-approved corruption does not provide immunity from consequences.
A corrupt officer may face:
The possibility of being discovered is an expected part of corruption RP.
Any police corruption that has not received prior staff approval is prohibited.
Unapproved corruption may result in:
The seriousness of the action will determine the consequence.
Staff may modify or withdraw approval for corruption RP if:
If approval is withdrawn, corrupt behaviour must cease immediately.
Harassment, discrimination, hate speech, or personal attacks are prohibited.
In-character conflict does not justify out-of-character hostility.
Disrespect, harassment, or abuse toward staff is prohibited.
Disagreeing with a staff decision is permitted, but disputes must be handled through the appropriate process.
All players must remember that characters are fictional, but the people portraying them are real.
In-character actions, insults, threats, violence, arrests, betrayals, or rivalries are not personal and must not be treated as such outside RP.
Do not carry IC conflict into OOC spaces.
Targeting, harassing, or attacking a player personally because of in-character events is strictly prohibited.
Disagreements or emotions stemming from RP must not become OOC hostility.
After particularly heavy, intense, or emotionally charged scenes, it is acceptable and encouraged to check in with one another OOC.
A simple:
you all good after that?
is encouraged where appropriate.
Checking in OOC does not invalidate or undo the roleplay that occurred.
OOC care and IC consequences are not mutually exclusive and should coexist on a serious RP server.
Staff rulings are final.
Players must follow the ruling during the scene and raise any disagreement through the appropriate process afterwards.
Disputes, complaints, or disagreements with staff decisions must be raised through a ticket after the RP has concluded.
Do not interrupt or derail active RP to argue a staff decision.
Exploiting bugs, glitches, unintended mechanics, or server vulnerabilities is prohibited.
This applies regardless of whether the exploit provides money, items, combat advantages, information, or another benefit.
Use of cheats, injectors, mod menus, unauthorised third-party software, or other tools that provide an unfair advantage is prohibited and may result in permanent removal. This includes the use of graphic mods/packs and sound packs that provide an advantage.
Bugs must be reported immediately, not abused.
Discovering a bug does not give permission to continue using it.
Certain types of roleplay require explicit player consent before they may occur.
Consent must be clear, informed, and freely given.
Consent may be:
If consent is not given, the sensitive roleplay must not proceed.
Torture RP is opt-in only and requires explicit consent from all involved players.
Torture includes, but is not limited to:
Torture RP:
Unconsented torture RP may be treated as a severe rule violation.
Mutilation, dismemberment, or permanent physical alteration requires:
Permanent injuries must be:
Permanent physical harm may never be forced onto another character without consent.
Explicit erotic roleplay is not permitted in public spaces or public chat.
Any permitted intimate RP must:
ERP must never involve:
ERP must never be forced, aggressively implied, or used to corner another player.
Consent may be withdrawn at any time and for any reason.
When consent is withdrawn:
Questioning, mocking, or pressuring a player after consent has been withdrawn is prohibited.
Consent systems may not be abused to:
Misuse of consent rules may result in staff action.
Staff may intervene in sensitive RP to:
Staff decisions regarding consent are final during the situation.
The server uses the designated safety phrase:
“Hocus Pocus”
If this phrase is spoken in-character, it indicates that a player feels unsafe or uncomfortable with the direction of the scene.
When the phrase is used:
Respecting the safety phrase is mandatory.
Ignoring, questioning, mocking, or deliberately pushing beyond the safety phrase is strictly prohibited.
Failure to comply may result in severe staff action.
Situations involving the safety phrase may be reviewed by staff.
Staff may contact involved players to:
The safety phrase must not be used simply to:
Misuse of the safety phrase may result in disciplinary action.
Player safety and wellbeing take priority over continuing a sensitive scene.
Using the safety phrase does not automatically invalidate the RP that occurred before it was used.
RP quality, character development, and storytelling come before personal success.
There does not need to be a “winner” in every scene.
All players are expected to contribute to an enjoyable and collaborative RP environment.
Your actions should create opportunities for RP rather than intentionally removing them.
Players may only have one living character from the same family lineage at a time.
Players may not have two related characters alive and active at the same time.
If a character permanently dies, a family member may be created as a new character.
New family characters do not automatically inherit:
Information must be learned legitimately through RP.
Family members or alternate characters may not be used to bypass:
Alternate characters must be treated as genuinely separate people.