en:rules:start

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
en:rules:start [2026-07-01 23:53] – Arrowspeeed_Bountyen:rules:start [2026-10-13 22:36] (current) – [General Terms] Arrowspeeed_Bounty
Line 12: Line 12:
  
 Tips for communication across different languages:  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 +  * 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,  [[https://www.deepl.com/en/translator|Deep Translate]] 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).   * 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.    * Swear words usually DO translate well -- do not use them. 
Line 19: Line 19:
  
 Basic Regulations:  All activities of WC members in the game are subject to these rules. WC members include alliances, corps, and individuals. Basic Regulations:  All activities of WC members in the game are subject to these rules. WC members include alliances, corps, and individuals.
-  * Members of the WC shall comply with the EULA Convention: https://support.eveonline.com/hc/en-us/sections/8413327523612-EULA-ToS-Policies.+  * Members of the WC shall comply with the [[https://support.eveonline.com/hc/en-us/sections/8413327523612-EULA-ToS-Policies|EULA Convention]].
   * Attacking WC members and allies is prohibited (for those with standings with WC > 0). Exceptions: When attacked by WC members or allied forces and unable to disengage, or when receiving orders from fleet command during fleet operations.   * Attacking WC members and allies is prohibited (for those with standings with WC > 0). Exceptions: When attacked by WC members or allied forces and unable to disengage, or when receiving orders from fleet command during fleet operations.
   * Scamming Prohibited: Any fraudulent activity within WC is prohibited, including but not limited to impersonating a Coalition Director or using a neutral, unregistered account to commit fraud.   * Scamming Prohibited: Any fraudulent activity within WC is prohibited, including but not limited to impersonating a Coalition Director or using a neutral, unregistered account to commit fraud.
Line 28: Line 28:
  
   * Pay attention to the purpose and audience of the channel.  Post only what is relevant to that audience and purpose.  If there is a channel available more specific or applicable to your audience, use that instead of a channel for wider audiences (E.G a Fraternity channel if you are posting Fraternity-specific topics).    * Pay attention to the purpose and audience of the channel.  Post only what is relevant to that audience and purpose.  If there is a channel available more specific or applicable to your audience, use that instead of a channel for wider audiences (E.G a Fraternity channel if you are posting Fraternity-specific topics). 
-  * Do not use an @everyone unless you are a coalition exec, an FC pinging a stratop, CTA, or other important fleet, or you have a very good reason to believe that it is time sensitive inforamtion that needs to be acted on right away.  Note that with this command, you are often pinging people's phones.   +  * Do not use an ''@everyone'' unless you are a coalition exec, an FC pinging a stratop, CTA, or other important fleet, or you have a very good reason to believe that it is time sensitive inforamtion that needs to be acted on right away.  Note that with this command, you are often pinging people's phones.   
-  * Use @here only if you are a coalition exec, an FC pinging a fleet, or you have good reason to believe it is important information for people to see and act on.  +  * Use ''@here'' only if you are a coalition exec, an FC pinging a fleet, or you have good reason to believe it is important information for people to see and act on.  
   * If you find yourself in a debate with someone, move to a private PM channel.    * If you find yourself in a debate with someone, move to a private PM channel. 
   * If you find yourself in a debate a group of people, stop typing if you are getting angry or if the same arguments are being repeated over and over, personal insults are being used, it goes off-topic, or if it is just gone on for some length of time.  If a critical issue that needs a resolution, take to diplos.    * If you find yourself in a debate a group of people, stop typing if you are getting angry or if the same arguments are being repeated over and over, personal insults are being used, it goes off-topic, or if it is just gone on for some length of time.  If a critical issue that needs a resolution, take to diplos. 
Line 41: Line 41:
     * include an end date     * include an end date
     * communicated to Arrowspeeed.      * communicated to Arrowspeeed. 
-  * Protocols for corps moving between Winter Coalition Alliances:+  * Protocols for corps or individuals moving between Winter Coalition Alliances:
     * No poaching allowed -- no alliance can approach a corp from another alliance in order to invite -- or hint to invite -- to switch 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.      * The transferring corp informs the leadership of current alliance. 
Line 50: Line 50:
   * 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.
 +  * It is recommended to avoid using a VPN. If you do use a VPN, know that there is a potential that you may be mistakenly identified as a spy or a fraudster.
 +
  
 ==== Rule Violation Reporting ==== ==== Rule Violation Reporting ====
Line 66: Line 68:
   * Instructed by an FC during a fleet.  This must be rare and for a good reason.  FC may be asked to explain the reason.    * 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.   * 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.
 +  * Alts of WinCo characters are also not allowed to AWOX.  This includes Faction Warfare. 
 +AWOX Compensation:
 +  * For ESI-compliant corps involved in awoxing incidents, the compensation cap will be based on the hull value of the affected ship.
 +  * For subcaps, up to an additional 2 billion ISK may be added based on the ship's modules.
 +  * Special Cases: 
 +    * Losses involving AT ships will not be eligible for compensation. 
 +    * If the responsible corp does not meet the ESI requirement, compensation must instead be paid based on the full ZKB loss value.
 +
 +
 +