2b2t Wiki:Conflict Events

From 2b2t Wiki
Jump to navigation Jump to search

Conflict Events is an editing guide meant to demonstrate how to approach the composition of pages on so-called 'conflict events'. It demonstrates how they start and end, who they include, and their involvement to a larger more long-term association, among a myriad of other informational segments.

What is a conflict?

At its most basic definition, a conflict is simply a 'serious disagreement or argument, typically a protracted one' according to Oxford Dictionary.

2b2t is an anarchy server, after all, and to apply a rigid cause-and-effect relationship on a chain of events may result in an inaccurate understanding of events being conveyed. It is also extremely important to note that to talk about every minuscule detail of a conflict, its long-term causes, and all related events, would result in text walls that are difficult to properly understand. A middle ground must therefore be approached that acknowledges long-term causes of a conflict, while focusing on the specific segment of said conflict the page is actually about. This turns a conflict into a so-called 'conflict event', which has a limitable scope. This page is about conflict events; long-term conflicts are discussed in 2b2tWiki:Relations To this effect, a conflict on its own page should satisfy the following criteria:

  1. Have a specific event that sparks it (this does not preclude other long-term causes from being mentioned)
  2. Have an endpoint to the event (this does not necessarily mean all related conflicts suddenly end or that a resolution occurs)
  3. Have at least two parties in conflict with each other (these can be players, groups, or bases, for example; anything that includes a collection of players on both sides)
  4. Include consistently reciprocated actions from opposing sides towards each other

Scope of Conflict

Conflict events must have a 'start' and 'end' so that there is a proper scope for the page, otherwise it becomes unclear what the full contents of the page are actually meant to be. Conflict events must specifically have an endpoint as they are otherwise open-ended, which results in the page contents being being more-or-less ongoing, which may pose an obstacle to page objectivity as the benefit of hindsight is not afforded. There is some room for this where a page details the long-term relationship between two entities as opposed to a specific event in that relationship. More information can be found on 2b2tWiki:Relations. In such cases where there is an ongoing conflicted relationship, it may be appropriate to segment such a conflict into different 'stages', broken up by individual events of far-reaching results, or into stages where the nature of the conflict changes significantly.

Appropriately addressing long-term causes

Conflicts and conflict events often have long-term causes. Just because the long-term causes might not be within the time span between the 'beginning' and 'end' of a conflict event discussed on a page doesn't mean the long-term causes should not be addressed. It should simply be noted that a specific conflict event page is not about the long-term causes of the conflict event, and that the inclusion of the long-term causes on that specific page should simply address the long-term causes and direct to the appropriate pages that, in turn, should have sections discussing their contribution to a respective conflict event. Long-term causes such as 'opinions', should be used with caution, preferably where something can be pointed to that reasonably demonstrates either this opinion in action or why this opinion is held; direct quotes are the best. While opinions can be construed as long-term causes, it is extremely important to express great caution when discussing any opinions period and to ensure that a party's opinions as a long-term cause not influence the writing on the page itself to be provocative or inflammatory as that is considered editing in bad faith.

A conflict's 'starting point'

The 'starting point' of a conflict event may prove to be difficult to isolate from a long-term cause. As a general rule of thumb, the sparking event to a conflict event is when one involved party does something to another involved party on the opposite side of the conflict event that causes a significant escalation in hostilities between them in some way. Some examples include Leaks and Griefs, as well as other things like doxxes or discord nukes. A sparking event is an event that can easily be pointed to as a direct cause in a sudden increase in hostilities between opposing parties. Long-term opinions of one party towards another (and vice versa) are not considered to be a sparking events.

A conflict's 'end'

To say that a conflict ends on 2b2t is generally incorrect; the environment of the community is often too unforgiving and dynamic for that to be the case. While conflicts can end in some sort of resolution, they more often fizzle out and occasionally flare up again perpetually afterwards. This is a major reason of why pages on conflict events are preferred over those on garden-variety long-term conflicts themselves. Time between specific events in a conflict and the magnitude of said events should generally not be considered a strong indicator that the window of respective conflict event has passed. Other factors should be looked at to determine when a conflict event has ended, such as individual parties' responses to events of the conflicts that are not designed to harm the opposing parties. Perhaps the actions of party 'A' onto party 'B' result in actions by party 'B' that significantly decrease the severity of the conflict without necessarily being aimed to harm party 'A'. Such a response from party 'B' could be considered a reliable indicator that that conflict event as a limited period of a respective conflict has ended, even if hostilities continue beyond that. To further elaborate, two parties harming eachother less frequently might not be an accurate representation of the end of a conflict event, while one of the groups taking direct actions that can be pointed to as assisting this decrease in frequency can be considered the end of a conflict event. Beyond this, if both parties agree that a conflict event has ended, it is over.

Parties to a conflict

While any conflict must have at least two parties, there is no limit to how many participants there are to a conflict. To be listed as a participant, participation must have actually occurred. Participation in a conflict can take many forms, although it generally entails activities such as griefing, insiding, and leaking; something that serves to meaningfully perpetuate or change the severity of the conflict. If there is a party involved in a conflict that does not align with the other major parties, they are to be listed in the 'Other Parties' field of the Conflict Infobox. Third parties may align with the interests of one of the main two; this does not make the third party one of the main two. To be one of the main two, leaders of one of the main two have to take steps that result in that party being involved, as opposed to them involving themselves to achieve their own goals.