Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| en:rules:start [2025/02/03 22:29] – Arrowspeeed_Bounty | en:rules:start [2026/03/14 23:35] (current) – Arrowspeeed_Bounty | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| <fs 1.5em> | <fs 1.5em> | ||
| + | |||
| + | 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. | ||
| + | * Use short sentences, subject-verb. | ||
| + | * 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. | ||
| + | * Speak more politely than you normally would. | ||
| 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. | 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 ===== | ===== 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. | ||
| + | * 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. | * 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. | * 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. | * When disputes happen between different language speakers, you may ask the corporation and alliance directors for communication assistance. | ||
| + | |||
| ===== Rule Violation Reporting ===== | ===== Rule Violation Reporting ===== | ||