D_Gaming BG.png
D_Gaming BG.png

InXA-GC/Conduct Breakdown


Visit to learn about the
CONDUCT
Required Within [InXA]

SCROLL DOWN

InXA-GC/Conduct Breakdown


Visit to learn about the
CONDUCT
Required Within [InXA]

THE INXA-GC CONDUCT STANDARD
"SELF-CRITICAL PROTOCOLS"


ARTICLE 1→Applies to All community members

 

I. PROPER CONDUCT IN THE NAME OF THE GROUP; A BALANCED AND UNDERSTANDING ATTITUDE TOWARDS ANY COMPETITIVE SITUATION AND OR ARRANGEMENT.

a. Where it is obvious that people will get heated during these scenarios, it is acceptable that someone curse to themselves or make statements of bewilderment. However anyone that becomes belligerent and offensive in any way will face disciplinary actions from the community. If any member is observed while acting in an unforgivable way in other communities, they will still face disciplinary actions from InXA-GC, should the event be reported in a verified/verifiable style.

ii. No cheating is permitted within the group.

a. Cheating is seen as the act of using any method of unintended interaction to gain advantage over others. This statement is left intentionally vague due to the nature of cheating in gaming.

b. Cheating in the form of glitch exploitation, third party code, etc. with the intent of an unfair advantage over another player(s). does not include single player games, monitoring programs to ensure others dont cheat, etc. Just don't mess with any other players experience using means outside of a games intended mechanics as a rule of thumb, and you should be fine.

iii. No hateful behavior will be tolerated (Racism, Sexism, hate crimes, etc.)

a. Should a member be approached about hateful/intolerant behavior, and refuse to reason with the staff member, we'll have no option but to remove the offending member until discussion can be conducted to halt the behavior.

b. It is our intention to discuss any and all topics with the community. Our first reaction to hostile behavior will always be to attempt to discuss with the member before ever taking disciplinary actions. However, should the member be actively targeting the community, they'll receive expedited disciplinary actions.

iv. MEmbers with GRIEVANCEs with other members should consult the staff of InXA-GC in order to find the most efficient route to common ground and aligned perspectives.

a. This will help to avoid failed communication between members by adding an intermediary for situations of heated conflict.

b. Obviously not all situations can be reported and discussed, we understand that. This rule is here simply to remind members that they don't have to simply sit with their discontent. If you can't find common ground, lean on your friends to help solve the issue.

v. Members who are FICKLE with the InXA-GC Badge (the "[InXA]" before member names) Shall face disciplinary actions from administrative staff.

a. The [InXA] badge should only be worn by those looking to promote their pride for the community. Those who are indecisive in the presence of the badge should hold off on adding it to their name. Also members should review the mission statement to best understand whether or not the community is truly something they wish to support and be a part of.


ARTICLE 2→Applies to ABYSION DIVISION and up

 

i. As a member of abysion division, your place within the division is determined by your badge.

a. Basically if you've been recruited into the ABYSION (or higher) division, its because you fulfilled the requirements to become a member of it in the first place. Should you for any reason decide that you are no longer wishing to keep your badge, it'd be respectful to let staff know so that they can properly understand and record your reasoning. You'd then be moved back into the BRIGADE division.

b. Should you fail to notify staff about a dropped badge, we can only assume you are actively, or are preparing to, ghost(ing) out of the community. We'll do our best to help you have a happy departure and we'll still reach out to the moment we notice a dropped badge to see what's going on. Should we receive no reply to our inquiry after 24 hours, we'll remove your roles/perms and place your membership in a suspended state. After 72 hours of no contact, we'll remove all membership to InXA-GC servers/services.


Article 3→Applies to Command division

 

I. ALL MEMBERS JOINING COMMAND WILL BE PLACED WITHIN A PROBATIONARY PERIOD

a. Without this period prior to becoming a staff member, we have no way to judge whether or not you are truly a good fit for the Command division. No one is exempt from this period. Any violations of the guidelines while in this probationary period will serve to extend your time spent as a probationary staff member.


article 4→applies to the office of overwatch

 

I. OVERWATCH OFFICE MEMBERS MUST BE 18 YEARS OF AGE OR OLDER

a. Command Overwatch is a platform meant for our community envoys. Even though one might be fitting for the role of OVERWATCH, we cannot accept those under 18 for reasons of both law and administration.


What does "Self-Critical Protocols" Mean?

When we say that our Conduct standard is self-critical, we mean to say that no matter the event that causes us to need to reference the standard, we'll always be considerate of the totality of your situation. We are only human, so mistakes and accidents are not only understood, but expected. We take any matter of administration extremely seriously, so you can bet that should you ever feel as though something is wrong you can definitely approach our admins/mods to discuss. If your hard pressed to find a mod/admin to speak with then you are more than welcome to email the office of OVERWATCH Directly with your concerns. We'll do our best to get back to ASAP.

What does Self-Critical Protocols Mean.png

WE ENCOURAGE YOU TO ASK QUESTIONS!


Conduct Standards V4.0 | May 15th, 2018

  • VERSION v4.0 | May 15th, 2018

    • All conduct standards brought into compliance with OP-Cinderschal. Addition of self-critical section and subtitle.
  • VERSION V3.0 | DEC 12TH, 2017

    • First addition of CONDUCT standard. First document still stored in archive.