1. Username, UUID, IP(s), and short ban reason for each offender.
maniaplay:
uuid: 'f5ed01cd-3651-48af-99fc-d21a034583c7'
ips:
- 191.181.241.57
reason: 'Creating a self-replicating structure block that griefed the world spawn without a trace and caused extreme server instability - https://imgur.com/a/T8r2VLo'
2. What did they do?
Luna placed and activated a self-replicating structure block at the flatlands world spawn. Because of the lackluster protection TotalFreedomMod offers against Structure Blocks, it was still possible to use Structure Blocks if you knew how to do it. The structure selected caused the server to lag horrendously and destroyed several builds within the area without a trace. The admins around at the time were unsure about what to do (mainly because the server was so slow it was unusable), which likely allowed the structure to spread further.
Around 5:48 PM MDT, I stepped in to assess the situation, and after unsuccessfully attempting to clean up and stop the spread of the structure myself, made the decision to keep the server offline until a patch could be made, hoping to save some builds in the process. This resulted in an hour or two of downtime as I worked on a patch that allowed me to disable structure and jigsaw blocks completely. Once I pushed the patch to GitHub and the server, I began cleaning up the flatlands world spawn and restoring it using data extracted from a Replay Mod recording from earlier in the day (provided by Alco_Rs11).
The world spawn was fully repaired by 11:29 PM MDT.
3. What indefinitely bannable offense does this fall under according to the guidance for sanctions?
1a. Attempts at harming the server.
1g. Using an exploit that restricts a players experience.
4. Add logs and/or screenshots of the occurrence here, and tag any witnessing staff.
The structure blocks used a structure named "goingoutwithabang2". With that in mind, I believe that this was Luna attempting to go out with a bang.
The structure blocks were extremely effective, destroying a huge chunk of the world spawn and lagging clients that happened to be nearby.
To support my case, here's a screenshot of CoreProtect logs from right before the incident occurred:
5. Are they known under any other names or IPs, and if so, are they currently (indefinitely) banned under those names and IPs?
No.