Little Accident

From MinecraftOnline
(Redirected from Little accident)
Jump to navigation Jump to search
A "litttle accident" involving fire in action
The admin-only warp Test1, where admins can practice with potentially destructive tools (and usually get little accidents out of their system). Players are warned to keep a distance from it, as sudden and violent landscaping is liable to occur in the area. This map screenshot demonstrates a selection of little accident remnants.
Little accident involving mob spawners.
Oops!
A minor incident with the degriefstick.
A crowd gathers around a mysterious bedrock block replacing a sign on the Visitor Centre, a protected area.

A general term of reference for accidents that tend to be far from "little" in reality, usually caused by typos or other dramatic fuckups when using admin tools. Associated with getplayerhead.sh?ToneDial&16.png ToneDial especially.

Such incidents usually involve the annihilation or irreversible alteration of large portions of landscape and man-made buildings, the spontaneous creation of horrible ugly unnatural monstrosities, and other misuse of dangerous admin and moderator commands resulting in general crashing of clients and servers alike.

Tools associated with little accidents

Notable little accidents

Night of A Million Torches

  • Millions of objects spawned causing any client loading the affected chunk to instantly crash.
  • Perpetrator: getplayerhead.sh?Causeless&16.png Causeless
  • Tool: /give
  • Cause: Trying to spawn ten million torches, thinking the command would instead produce a single unlimited block as a previous server bug caused it to. It didn't.
  • Solution: getplayerhead.sh?SlowRiot&16.png SlowRiot locating and deleting the entire affected chunk area.

Canal flood

Slimepocalypse

  • Millions of unkillable slime mobs spawned, server grinds to a halt.
  • Perpetrator: getplayerhead.sh?ToneDial&16.png ToneDial
  • Tool: /spawnmob
  • Cause: Thinking that spawning millions of bugged mobs would somehow be a good idea.
  • Solution: Backup restore of all of Freedonia.

The Cacticlysm

  • Half of Freedonia filled with a giant cactus cube, which spontaneously split apart into cactus items, crashing all connected clients, and finally the server itself.
  • Perpetrator: getplayerhead.sh?ToneDial&16.png ToneDial
  • Tool: Cuboid
  • Cause: right-clicking once at one end of the map, and once at spawn (thinking it was twice at spawn).
  • Solution: Killing the server to prevent a disk write, causing loss of all progress since last save.

Snowpocalypse

  • Effect: massive portions of Freedonia spontaneously covered in snow.
  • Perpetrator: getplayerhead.sh?ToneDial&16.png ToneDial
  • Tool: WorldEdit
  • Cause: typo (1000 radius instead of 100) for //freeze command.
  • Solution: getplayerhead.sh?SlowRiot&16.png SlowRiot manually going around and //thawing affected areas. Many artificially snowed-on areas still remain.
ToneDial's little accident with sniper at spawn.
...a well-documented incident!

Stone disc at spawn

  • Effect: entire spawn area filled with a giant stone disc at waist height.
  • Perpetrator: getplayerhead.sh?ToneDial&16.png ToneDial
  • Tool: VoxelSniper
  • Cause: Ignoring documented sniper bug where the first click often lands near spawn. Compounded by using a stupidly massive radius for a sniper command.
  • Solution: getplayerhead.sh?bastetfurry&16.png bastetfurry manually copying over the damaged part from a local backup with the help of WorldEdit.

Canal flood 2

  • Effect: Same as Canal Flood 1, except the subsequent cleanup operation drained part of a nearby sea.
  • Perpetrator: getplayerhead.sh?runechan&16.png runechan
  • Tool: WorldEdit
  • Cause: Same as canal flood 1, plus excessive radius specified when trying to clean up via //drain.
  • Solution: getplayerhead.sh?runechan&16.png runechan and getplayerhead.sh?SlowRiot&16.png SlowRiot manually performing //fixwater over small sections of the affected sea.

The Nothing

A corner of a deleted area
  • Effect: Wiped out a number of 512x512 chunks of the world, leaving only the void
  • Perpetrator: Not yet publically disclosed
  • Tool: VoxelSniper
  • Cause: someone tried to delete massive circle using voxelsniper
  • Solution: getplayerhead.sh?SlowRiot&16.png SlowRiot restoring the affected areas from backup, requiring a server restart. Some massive flat areas remain where chunk replacement failed.

Obby-lievable Redstone Spawn

Part of the affected area
  • Effect: Changed most of spawn's sand and sandstone to redstone block and obsidian
  • Perpetrator: Yet to come forward
  • Tool: WorldEdit
  • Cause: //replace sand,sandstone redstone,obsidian for reasons unknown
  • Solution: getplayerhead.sh?Palindrome7&16.png Palindrome7 uses //replace to restore the sand and sandstone back to its original state

Dirt Star

The Dirt Star as seen from bellow
  • Effect: Created a giant sphere of dirt encasing many floating islands in the town Batugus
  • Perpetrator: getplayerhead.sh?SlowRiot&16.png SlowRiot
  • Tool: VoxelSniper
  • Cause: getplayerhead.sh?Anna_28&16.png Anna_28 asking for some dirt to build floating islands.
  • Solution: Many players hand digging the entire sphere to collect all the dirt blocks.

Slimepocalypse

Slime on fire
  • Effect: Very very large slimes, very hard to kill. When killed, spawn more... also large... slimes
  • Perpetrators: getplayerhead.sh?Palindrome7&16.png Palindrome7, getplayerhead.sh?TheDarkrai85&16.png TheDarkrai85, getplayerhead.sh?SlowRiot&16.png SlowRiot
  • Tool: 1.7 NBT-specifying spawnmob command
  • Cause: wondering just how big a size-100 slime would be
  • Solution: Admins shooting and throwing potions at the slimes for an extended period of time, using modified superweapons, and generally calling everyone in to take a pot shot. Complicated somewhat by SlowRiot throwing invisibility potions at the slimes.

Tsunami

Meme relevant to Tsunami
  • Effect: Cascade effect of water movement resulting in extreme server lag
  • Perpetrators: getplayerhead.sh?Ted1246&16.png Ted1246
  • Tool: WorldEdit
  • Cause: getplayerhead.sh?Ted1246&16.png Ted1246 trying to drain an area.
  • Solution: Server worked itself out after the cascade effect was forcibly stopped, freezing the server for about ten minutes. getplayerhead.sh?Ted1246&16.png Ted1246 feels very very dumb.

The Hopper from Hell

<getplayerhead.sh?Krenath&16.png Krenath> I want to name it "Dennis"
<getplayerhead.sh?Krenath&16.png Krenath> Dennis the Hopper

  • Effect: Constant crashing of the server whenever the affected chunk is loaded
  • Perpetrators: getplayerhead.sh?Krenath&16.png Krenath and getplayerhead.sh?techkid6&16.png techkid6
  • Tool: WorldEdit
  • Cause: getplayerhead.sh?Krenath&16.png Krenath wondering what a hopper that faced all sides would look like, followed by getplayerhead.sh?techkid6&16.png techkid6 wondering what would happen if you put an item in the hopper
  • Solution: getplayerhead.sh?techkid6&16.png techkid6 rolling back the entire region from backup

The Sheepocalypse

  • Effect: Vast quantities of mobs; mostly sheep, and some horses and donkeys were wiped from existence, reported by multiple users. It likely wiped out all of the ones in loaded in chunks.
  • Perpetrator: getplayerhead.sh?Eclypto18&16.png Eclypto18 messing up /butcher
  • Solution: Admins and moderators had to manually respawn missing entities, within reason.

Chunks Restored..?

The Nether-ified spawn
Parts of the End replace spawn
  • Effect: Chunks from the Nether and the End appearing in spawn. Unfortunately, a handful of players died from either burning in lava or falling into the void.
  • Perpetrator: getplayerhead.sh?AlphaAlex115&16.png AlphaAlex115
  • Cause: While fixing a Nether chunk error, getplayerhead.sh?AlphaAlex115&16.png AlphaAlex115 accidentally caused the Nether to replace large parts of spawn. After stopping the server in an attempt to fix this problem, he then replaced the affected parts of spawn with chunks from the End.
  • Solution: After his first botched attempt, getplayerhead.sh?AlphaAlex115&16.png AlphaAlex115 used a backup to restore spawn.

Hard Wool

  • Effect: 1/3 of wool blocks within a certain radius of getplayerhead.sh?Prince__Valiant&16.png Prince__Valiant's chicken were turned to obsidian. Because of all the block changes, the server crashed.
  • Perpetrator: getplayerhead.sh?Palindrome7&16.png Palindrome7
  • Cause: While helping getplayerhead.sh?Prince__Valiant&16.png Prince__Valiant, getplayerhead.sh?Palindrome7&16.png Palindrome7 tried to turn the wool on their chicken farm to obsidian with /replacenear but messed up the parameters.
  • Solution: The server reboot itself up after processing all the blocks. Rogue Obsidian blocks have slowly been discovered by players and mined and replaced.