User:Joey Coconut1/Drafts/Base Destruction

Base Destruction is an editing guideline meant to demonstrate what constitutes the leak of a base, what constitutes a grief, and how a base specifically ends.

What is a Leak?
Leaks of a base can take many shapes. Reduced to its most simple definition, a leak is when the location of a base (or any other privileged information) passes to someone that should not have it. Leaks do not have to be conducted by a member of a base, although most tend to be from members. Leaks from members generally are the result of 2b2tWiki:Insiding or mistakes (such as misplaced copy-pastes, failed /msg's, or misdirected streams).

As not all leaks are necessarily the result of malicious intent, it is extremely important that the nature of any base's leak be discussed within the respective article in the 'Grief' section (or a section of similar nature or topic) as to not convey an unfair understanding of the situation. [2b2tWiki:Group and Base Membership#Uninvited Resident Guidelines|Uninvited Residents]] or even outright nonmembers also certainly can leak a base because, again, a leak is simply the exchange of privileged information passes to someone that is not meant to know it; this definition does not take into account whether or not the conveyor of that information should know that information.

Exploits
Not all leaks have to be conducted by people. Coordinate Exploits are oftentimes a major source of leaks. For example, Hopen was leaked by the Nocom exploit; Nocom is therefore listed as the leaker of the base on the article. While it its face this may appear odd, it's because it was the exploit that conveyed the location of the base to 0x22 to grief it; 0x22 did not convey the information to himself. As a general statement of caution,

What if the exact leaker is unknown?
Sometimes bases are leaked and the leaker is not easy to pick out; oftentimes, this is the result of 2b2tWiki:Insiding. It is important to refrain from picking a Scapegoat as this is unfair to the person blamed for leaking, as has previously happened with Zetrax being blamed for leaking Menegroth. If there is no proof for how a base was leaked, no leaker should be listed in the [|Base Template]. Likewise, if the potential leakers have been reduced to a Short list through a simple process of elimination, it would be wholly unfair to those within that list to be placed on the wiki article in a list of potential leakers without proof to that effect.

If significant proof exists that implicates one or more people as being the leakers of a base, it should be discussed within the article and also within the article's talk page if necessary, as with Corner Base. It cannot be stated that while the griefers of a base may be in a better position to know who leaked a base when compared with the residents of said base, the griefers have a vested interest in protecting the identity of the leaker. Conversely, base members may also jump to conclusions and publicly accuse other members of the base for leaking, correctly or incorrectly. Accusations of leaks ought not to be taken at face value as a result of a myriad of potential underlying motivations.

To also reiterate, sometimes the leaker of a base is not a player at all, and is in fact an exploit. Sometimes Coordinate Exploits (such as Nocom) remain unknown publicly for years.

Griefs
==Abandonment