History - Revision history

MrOmegaBeast at 11:50, 26 June 2022

2022-06-26T11:50:37Z

0:0:0:0:0:0:0:1 at 20:27, 2 October 2020

2020-10-02T20:27:50Z

Ingo at 20:23, 2 October 2020

2020-10-02T20:23:12Z

Ingo at 20:21, 2 October 2020

2020-10-02T20:21:58Z

0:0:0:0:0:0:0:1 at 20:19, 2 October 2020

2020-10-02T20:19:42Z

Ingo at 13:51, 1 October 2020

2020-10-01T13:51:41Z

Ingo at 19:36, 30 September 2020

2020-09-30T19:36:59Z

Ingo at 11:56, 30 September 2020

2020-09-30T11:56:10Z

Ingo: Created page with "==Start of the server== SimpleFlips' Minecraft server was launched on October 2nd, 2019. During the first month, SimpleFlips streamed several times on Facebook. After this..."

2020-09-30T11:54:32Z

Created page with "==Start of the server== SimpleFlips' Minecraft server was launched on October 2nd, 2019. During the first month, SimpleFlips streamed several times on Facebook. After this..."

New page

==Start of the server==
SimpleFlips' Minecraft server was launched on October 2nd, 2019.
During the first month, [[SimpleFlips]] streamed several times on Facebook. After this, he rarely ever joined the server. The last time he joined was on May 14th, 2020, for the SimpleFlips' Server Tour].
==The Fuckenings==
During the server's life, there have been several times where the world got corrupted in some way or shape. These events have been dubbed "The Fuckening" by the community.

===The Fuckening===
'''SimpleFlips' Server "DDoS"''' 
A crash occured on the server with the original host [[ServerMiner]], causing all of the users on the server to get disconnected at once.
During this time, a large number of users were online daily, around 35-45 or so at a time.
After recovering from the crash, many of the users tried to reconnect and login to the server at the same time. This caused a large amount of upload traffic to come from the server, to the point that ServerMiner flagged it as a DDoS attack against itself.
ServerMiner subsequently suspended the server for 12 hours afterwards. 
[https://media.discordapp.net/attachments/629053821087252501/645507141242716175/fuckening_1.png Victuracor's direct quote regarding this fuckening]

===The Fuckening 2===
'''Nether Water''' 
A power outage, caused by storms nearby, made the server stop incorrectly and improperly save chunks that were loaded at the time of the power outage. Region headers of the chunks that were loaded at the time became corrupted. Futhermore, when the server tried to fix the corrupted chunks by correcting the headers, it 'shuffled' them instead. Victuracor proceeded to fix this issue by creating a backup of the world after the corruption, and using CoreProtect, a minecraft data-logging plugin, to roll back actions performed by players in those chunks into a ''mimic world''. From here, he then copied the chunks from the mimic world to the backup that corrupted, creating, per him, a 99% honest-to-the-original copy.
Only 12 chunks of the world were actually corrupted, including some in the Nether. Amongst them was one, close to where the Nether Hub is today, that had a block of water for "some reason". This is what lead to the complete redesign of the Nether Hub at [0x,0z] and furthermore, the creation of the water elevator to the nether roof. 
[https://media.discordapp.net/attachments/629053821087252501/645507145051406357/fuckening_2.png Victuracor's direct quote regarding this fuckening]

===The Fuckening 3===
'''The Tubbening''' 
A set of players was stuck in the End due to the Ender Dragon going into unloaded chunks around the island. This caused players to be unable to leave the end completely. To remedy this, one of the server's [[Operators]], [[Little_Tub]] attempted to kill the dragon through the the '/kill' command. He partially typed in the command, and pressed tab to autocomplete the command, expecting the type to autocomplete to ender_dragon. Instead, it autocompleted to '''!'''ender_dragon ('''not''' ender_dragon). This meant he executed the command <code>/kill @e[type=!ender_dragon]</code>, killing everything '''except''' the Ender Dragon. In addition, [[SimpleFlips]] came onto the server shortly after the incident, and used <code>/kill @e</code> assuming that the server rolled back later that day, much to the dismay of the other operators.
From this, entities that had been lost had to be individually restored on a case-by-case basis. Some memorials have been created for some of the lost entites. 
This Fuckening is also this reason for dangerous commands being disabled. 
[https://media.discordapp.net/attachments/629053821087252501/645507213829341184/fuckening_3.png Victuracor's direct quote regarding this fuckening]

===The Fuckening 4===
'''Bee Update Woes''' 
At the release of Minecraft version 1.15, many of the underlying software that allowed the server to function properly began having issues which caused server instabilities.
The ''Initial'' Fuckening 4 was from the server deadlocking and rolling back 5 minutes, caused by the PaperMC server. The server didn't show any issues at first after the crash, and all issues with rollback were easily fixed with CoreProtect. A few days later a similar issue occured, where the server was not able to properly save the world itself. This time however, Coreprotect was also held up and had a large number of entries in queue waiting to be entered into the database. This prevented the server from being shut down gracefully, and lead to a potential 5 hour rollback. In addition, it was discovered that the server was not performing incremental saves, as well as that chunks were remaining loaded in the system and were increasing monotonically, or without decreasing. A restore to the latest version of the backup was performed and [[Victuracor]] had users who were online during the Fuckening contact him to manually restore or change any issues that were caused by this Fuckening. Thankfully, at the time of this book being signed, the issue with CoreProtect that caused the main issue of this fuckening has been resolved and the shouldn't happen again."} 
[https://discordapp.com/channels/137567383215800320/629053821087252501/657050481142530058 Message where the issue of this Fuckening was realized] (Link to message in SimpleFlips' Discord Server) 

===The Fuckening Museum===
[[plexzindu]] built a [[Fuckening Museum|museum]] to document the Fuckenings. Large parts of his documentation were used for this page. Besides the documentation, the museum also features dioramas for all of the Fuckenings. 
The museum can be visited at [-3171x, 200y, -3205z]

==SimpleFlips' Server Tour==

==References==
plexzindu's Fuckening Museum

@@ Line 34: / Line 34: @@
 ===The Fuckening Museum===
-[[plexzindu]] built a [[Fuckening Museum|museum]] to document the Fuckenings. Large parts of his documentation were used for this page. Besides the documentation, the museum also features dioramas for all of the Fuckenings.<br />
+[[plexzindu]] built a [[Fuckening Museum|museum]] to document the Fuckenings. Large parts of their documentation were used for this page. Besides the documentation, the museum also features dioramas for all of the Fuckenings.<br />
 The museum can be visited at [-3200x, 200y, -3200z]

@@ Line 30: / Line 30: @@
 '''Bee Update Woes'''<br />
 At the release of Minecraft version 1.15, many of the underlying software that allowed the server to function properly began having issues which caused server instabilities.
-The ''Initial'' Fuckening 4 was from the server deadlocking and rolling back 5 minutes, caused by the PaperMC server. The server didn't show any issues at first after the crash, and all issues with rollback were easily fixed with CoreProtect. A few days later a similar issue occured, where the server was not able to properly save the world itself. This time however, CoreProtect was also held up and had a large number of entries in queue waiting to be entered into the database. This prevented the server from being shut down gracefully, and lead to a potential 5 hour rollback. In addition, it was discovered that the server was not performing incremental saves, as well as that chunks were remaining loaded in the system and were increasing monotonically, or without decreasing. A restore to the latest version of the backup was performed and [[Victuracor]] had users who were online during the Fuckening contact him to manually restore or change any issues that were caused by this Fuckening. Thankfully, at the time of this book being signed, the issue with CoreProtect that caused the main issue of this fuckening has been resolved and the shouldn't happen again."}<br />
+The ''Initial'' Fuckening 4 was from the server deadlocking and rolling back 5 minutes, caused by the PaperMC server. The server didn't show any issues at first after the crash, and all issues with rollback were easily fixed with CoreProtect. A few days later a similar issue occured, where the server was not able to properly save the world itself. This time however, CoreProtect was also held up and had a large number of entries in queue waiting to be entered into the database. This prevented the server from being shut down gracefully, and lead to a potential 5 hour rollback. In addition, it was discovered that the server was not performing incremental saves, as well as that chunks were remaining loaded in the system and were increasing monotonically, or without decreasing. A restore to the latest version of the backup was performed and [[Victuracor]] had users who were online during the Fuckening contact him to manually restore or change any issues that were caused by this Fuckening. Thankfully, at the time of this book being signed, the issue with CoreProtect that caused the main issue of this fuckening has been resolved and the shouldn't happen again.<br />
 [https://discordapp.com/channels/137567383215800320/629053821087252501/657050481142530058 Message where the issue of this Fuckening was realized] (Link to message in SimpleFlips' Discord Server)<br />

@@ Line 30: / Line 30: @@
 '''Bee Update Woes'''<br />
 At the release of Minecraft version 1.15, many of the underlying software that allowed the server to function properly began having issues which caused server instabilities.
-The ''Initial'' Fuckening 4 was from the server deadlocking and rolling back 5 minutes, caused by the PaperMC server. The server didn't show any issues at first after the crash, and all issues with rollback were easily fixed with CoreProtect. A few days later a similar issue occured, where the server was not able to properly save the world itself. This time however, Coreprotect was also held up and had a large number of entries in queue waiting to be entered into the database. This prevented the server from being shut down gracefully, and lead to a potential 5 hour rollback. In addition, it was discovered that the server was not performing incremental saves, as well as that chunks were remaining loaded in the system and were increasing monotonically, or without decreasing. A restore to the latest version of the backup was performed and [[Victuracor]] had users who were online during the Fuckening contact him to manually restore or change any issues that were caused by this Fuckening. Thankfully, at the time of this book being signed, the issue with CoreProtect that caused the main issue of this fuckening has been resolved and the shouldn't happen again."}<br />
+The ''Initial'' Fuckening 4 was from the server deadlocking and rolling back 5 minutes, caused by the PaperMC server. The server didn't show any issues at first after the crash, and all issues with rollback were easily fixed with CoreProtect. A few days later a similar issue occured, where the server was not able to properly save the world itself. This time however, CoreProtect was also held up and had a large number of entries in queue waiting to be entered into the database. This prevented the server from being shut down gracefully, and lead to a potential 5 hour rollback. In addition, it was discovered that the server was not performing incremental saves, as well as that chunks were remaining loaded in the system and were increasing monotonically, or without decreasing. A restore to the latest version of the backup was performed and [[Victuracor]] had users who were online during the Fuckening contact him to manually restore or change any issues that were caused by this Fuckening. Thankfully, at the time of this book being signed, the issue with CoreProtect that caused the main issue of this fuckening has been resolved and the shouldn't happen again."}<br />
 [https://discordapp.com/channels/137567383215800320/629053821087252501/657050481142530058 Message where the issue of this Fuckening was realized] (Link to message in SimpleFlips' Discord Server)<br />

@@ Line 21: / Line 21: @@
 ===The Fuckening 3===
 '''The Tubbening'''<br />
-A set of players was stuck in the End due to the Ender Dragon going into unloaded chunks around the island. This caused players to be unable to leave the end completely. To remedy this, one of the server's [[Operators]], [[Little_Tub]] attempted to kill the dragon through the the '/kill' command. He partially typed in the command, and pressed tab to autocomplete the command, expecting the type to autocomplete to ender_dragon. Instead, it autocompleted to '''!'''ender_dragon ('''not''' ender_dragon). This meant he executed the command <code>/kill @e[type=!ender_dragon]</code>, killing everything '''except''' the Ender Dragon. In addition, [[SimpleFlips]] came onto the server shortly after the incident, and used <code>/kill @e</code> assuming that the server rolled back later that day, much to the dismay of the other operators.
+A set of players was stuck in the End due to the Ender Dragon going into unloaded chunks around the island. This caused players to be unable to leave the end completely. To remedy this, one of the server's [[:Category:Operators|Operators]], [[Little_Tub]] attempted to kill the dragon through the the '/kill' command. He partially typed in the command, and pressed tab to autocomplete the command, expecting the type to autocomplete to ender_dragon. Instead, it autocompleted to '''!'''ender_dragon ('''not''' ender_dragon). This meant he executed the command <code>/kill @e[type=!ender_dragon]</code>, killing everything '''except''' the Ender Dragon. In addition, [[SimpleFlips]] came onto the server shortly after the incident, and used <code>/kill @e</code> assuming that the server rolled back later that day, much to the dismay of the other operators.
 From this, entities that had been lost had to be individually restored on a case-by-case basis. Some memorials have been created for some of the lost entites.<br />
 This Fuckening is also this reason for dangerous commands being disabled.<br />

@@ Line 37: / Line 37: @@
 The museum can be visited at [-3200x, 200y, -3200z]
 ==SimpleFlips' Server Tour==
 ==References==
 plexzindu's Fuckening Museum

@@ Line 1: / Line 1: @@
 ==Start of the server==
 SimpleFlips' Minecraft server was launched on October 2nd, 2019.
-During the first month, [[SimpleFlips]] streamed several times on Facebook. After this, he rarely ever joined the server. The last time he joined was on May 14th, 2020, for the SimpleFlips' Server Tour].
+During the first month, [[SimpleFlips]] streamed several times on Facebook. After this, he rarely ever joined the server. The last time he joined was on May 14th, 2020, for the SimpleFlips' Server Tour.
 ==The Fuckenings==
 During the server's life, there have been several times where the world got corrupted in some way or shape. These events have been dubbed "The Fuckening" by the community.

@@ Line 7: / Line 7: @@
 ===The Fuckening===
 '''SimpleFlips' Server "DDoS"'''<br />
-A crash occured on the server with the original host [[ServerMiner]], causing all of the users on the server to get disconnected at once.
+A crash occured on the server with the original host ServerMiner, causing all of the users on the server to get disconnected at once.
 During this time, a large number of users were online daily, around 35-45 or so at a time.
 After recovering from the crash, many of the users tried to reconnect and login to the server at the same time. This caused a large amount of upload traffic to come from the server, to the point that ServerMiner flagged it as a DDoS attack against itself.