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 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, Coordinate Exploits (such as Nocom) sometimes remain unknown publicly for years.

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 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 enough 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. Accusations of leaks may be discussed in a base's article as events in an of themselves, although pure accusations alone should not be conveyed as fact.

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
A base is griefed when it is meaningfully destroyed either fully or in part. Anyone can grief a base; this includes any players regardless of membership status within the base, Server Administration when builds are worldedited or terrain is reverted, or even environmental if griefing is done by mobs, lava, lightning, etc without player intervention. Only players who were themselves at a grief in-game should be listed as griefers of a base.

Self-Griefs
A self-grief occurs when the members of a base or friends specifically invited by the members of the base grief it. Self-griefs tend to occur after a base is known or thought to have been leaked. Whether or not a base is griefed by nonmembers or members, it is still considered a grief, and should be listed in the Base Template as such, using the format 'Self-grief (List of players who self griefed).

How does a base end?
A base does not necessarily end when it is griefed, although that tends to anyways be the result. A base ends in grief and abandonment. As an illustration of this, take NFE for example,

Abandonment
Base abandonment is simply when a base is vacated by its builders. This on its own does not end a base as they can return there as long as it is still standing.

Post-grief Repairs
Sometimes bases meaningfully continue after a grief without going fully public. Multiple griefs section discussion..........

Re-Griefs
Re-griefs occur when a base has already been griefed and abandoned (in other words, after the base has ended). Re-griefs should absolutely not be listed in any infoboxes. Taken to its logical extension, the train of thought considering re-griefs the same as other griefs would more or less enable any and all player pages to include Spawn in the 'Griefs' field of the Player Template by simply going to spawn and creating or destroying lavacasts. Re-griefs as events may certainly be discussed in articles where applicable, but should clearly be labeled as 're-griefs' and kept out of any infoboxes.