The Semotto Incident of September 26
The Semotto Incident of September 26th
On September 26th, 2025, server owner Sebastian took in-game action against player Semotto following a prolonged period of out-of-game harassment. This event was the culmination of numerous warnings regarding Semotto's behavior on the community Discord, which he had been asked to cease multiple times.
Background: A Pattern of Disruptive Behavior
Prior to the incident, Semotto had established a long history of harassing Sebastian via Discord pings. This often involved reporting vanilla Minecraft mechanics or client-side issues as server bugs, making unreasonable demands, and engaging in lengthy, condescending arguments. Even after being temporarily removed from the support channel and explicitly told to "cool-off," the behavior continued despite being given many chances.
The following gallery provides a sample of these interactions, which created a toxic environment and wasted significant development time.
(Full chat history can be found by searching from: il_seminoso mentions: treeofself
in the Discord)
-
Claiming server joins are a DDOS attack.
-
Reporting a vanilla statistic ("Distance Flown") as a server bug.
-
Pinging the owner over client-side FPS drops.
-
Demanding support for what appears to be a hacked client crash.
-
Insisting a server anticheat be disabled for his client.
-
Arguing after being proven wrong about a bug.
-
Accusing the owner of changing Nether fog, which is not possible.
-
Pinging about the "XP bottles crafted" statistic, a known vanilla feature from villager trading.
-
Derailing a discussion with demands after his terribly unbalanced suggestion was not accepted.
-
Private DMs from other community members reacting to his public behavior.
-
Arguing about game design, shifting goalposts when proven wrong about farm mechanics.
-
Arguing about the riptide speed cap, refusing to accept screenshot evidence.
-
Having a tantrum over a new feature before even seeing it in-game.
-
Arguing that all players should just use hacked clients instead of adding features to the server.
-
Continuing his tantrum with baseless claims about the player base.
-
Abusing the support channel to lie about bugs that benefit him.
-
Believing a universal bug fix was a personal attack.
The Incident
The event was triggered when Sebastian was woken up by another "urgent" ping from Semotto regarding the logoff spot mod.

As was typical, the bug report was found to be false. The behavior Semotto described was impossible, as the plugin's code has a hard-coded 5-minute timer for the logoff display.
ScheduledFuture<?> removalTask = scheduler.schedule(() -> { removeDisplay(playerId); }, PandaLogoffSpotConfig.getDurationSeconds(), TimeUnit.SECONDS);
This incident was a direct violation of the warning Semotto had received about abusing the support system.

In response to the continued harassment and false reports, Sebastian took in-game action. Semotto was trapped in a bedrock box with lava, which was removed before he took fatal damage. However, upon logging in later, he died from the residual burning effect.

Aftermath and Fallout
Following his in-game death, Semotto began a campaign against the server.



- He published a YouTube video claiming he was a victim of admin abuse.
- He joined the associated Skyblock server to spam slurs.
- He vandalized this wiki with a biased and incorrectly formatted article.
- He attempted to rally his friends to leave the server and harass the owner, a tactic referred to as "weaponizing friendships."
This campaign was largely unsuccessful. When presented with the chat logs, most of his friends chose not to get involved. Sebastian also offered to remove the 7-day deathban and restore all of Semotto's items, but the offer was declined. Semotto showed he was more interested in pursuing his "revenge," demonstrating his goal was not resolution but continued drama.