Differences

This shows you the differences between two versions of the page.

--- en:rules:start [2022/11/02 00:05] – Maria_Taylor
+++ en:rules:start [2026/03/14 23:35] (current) – Arrowspeeed_Bounty
@@ Line 3: / Line 3: @@
 <fs 1.5em>Constitution: **Be friendly and honest. Never harm others for your benefit.**</fs>
-The sidebar lists all the rules in effect.
+Tips for communication across different languages:
+  * It is polite to do the translation for the person you are sending the message to and to send both EN and CN versions.   Google translate is OK,  Deep Translate (https://www.deepl.com/en/translator) is better
+  * Use short sentences, subject-verb.  Do not leave out words that are part of  standard English sentence structure.   Do not abbreviate.  Do not use jargon.  Do not joke or banter (these do not translate well).
+  * Swear words usually DO translate well -- do not use them.
+  * If they say something that sounds insulting to you, double check on intent before reacting.  A translation error could be the cause.  Give the benefit of the doubt.
+  * Speak more politely than you normally would.  This is generally received well, even if an imperfect translation.
+The sidebar lists the rules in effect. These rules apply to Fraternity space in sov null areas. Fraternity does not enforce these rules outside of sov null Fraternity space, other than the rule not to AWOX.
 ===== General Terms =====
+  * Any agreements or promises that will potentially require enforcement or implimentation by diplo team or coalition leadership must:
+    * be reasonable and clear
+    * be in writing with screen shots or document available
+    * include an end date
+    * communicated to Arrowspeeed.
+  * Protocols for corps moving between WinCo alliances:
+    * No poaching allowed -- no alliance can approach a corp from another alliance in order to invite -- or hint to invite -- to switch alliances
+    * The transferring corp informs the leadership of current alliance and gives summary of reasons
+    * Current alliance can respond to the reasons -- and can agree or dis-agree to the transfer
+    * If the current alliance dis-agrees with the transfer, the reasons should be given along with evidence if possible.  It should be made clear if the problem is a personal issue with current alliance -- or if there is a problem that will likely be carried to other alliances.  If a problem that will likely be carried to other alliances, blacklist or greylist may be considered with appropriate reason and evidence.
+    * All of the above must happen before any in-game progress and before any promises are made
+    * Transfers will be recorded on diplo internal spreadsheet with appropriate reason and evidence
   * There are only two chances should you violate these rules. There will be punishments of docking bans, fines, or kicking for repeated violations.
   * Special issues, problems, penalties, or complaints that are not covered in the rules may be addressed with a full discussion by leaders. The discussion should be recorded for future reference and any loopholes within the rule document are expected to be amended in time.
   * When disputes happen between different language speakers, you may ask the corporation and alliance directors for communication assistance.
 ===== Rule Violation Reporting =====
@@ Line 23: / Line 42: @@
 Do not shoot blues unless:
   * Need to take reasonable measures to defend yourself when you're being attacked and can't escape.
-  * Instructed by an FC during a fleet.
+  * Instructed by an FC during a fleet.  This must be rare and for a good reason.  FC may be asked to explain the reason.
+  * In rare cases, an accidental shooting might be claimed (such as when using a Vorton Projector or smart bomb), in which case a diplo must be consulted.