Kaboom Wiki - User contributions [en]

Filtering

2026-08-05T00:14:33Z

Troll ing: Some automated grammar corrections

'''Filtering''' is the act of automatically restricting a player's access to the server based on rules. For example, one may decide to create an [[Wikipedia:IP_address|IP address]] filter rule to restrict a player, even if they were to change their username.

Depending on the enabled enforcement types and implementation quality, filter activation can result in server lag, and as such, it is recommended to use efficient [[Kick exploits|kick exploits]] where possible or no kick exploits at all, especially when filtering spambots.

Filtering is extremely useful when the server is spambotted and the spambots contain predictable characteristics that can be expressed in one or more rule types.

=Rules=

Filtering based on arbitrary strings, like chat messages or commands, is commonly implemented via versatile [[Wikipedia:Regular expression|regular expressions]].

==IP address==

IP address rules are commonly used in lieu of exact username filters, as evasion requires the use of [[Wikipedia:Proxy_server|proxies]] (often provided by VPN services).

Due to most clones using [[IP masking]], it is impossible to filter [[Wikipedia:Subnet|subnets]] or [[Wikipedia:Autonomous system (Internet)|ASNs]] as one would expect from a [[Wikipedia:Firewall_(computing)|firewall]].

==Usernames==

Username filter rules are typically the first to be implemented when a bot or client developer is implementing a filter system. Due to most Kaboom clones being in offline mode, it is also the easiest to bypass, as players can just join under a different username.

However, in combination with regular expressions, username filters can be used to mitigate spambots that use fixed username lengths or a predictable username format. Luckily, most easily available or paid spambot services use a predictable username format, so this remains one of the most important filter types to implement.

==Commands==

Command rules can be effective to combat general command abuse as well as spambots that spam a certain command. For example, command rules have been used in the past to filter [[Skynet#Mountains of Lava Inc.|Skynet]].

In the past, bots like [[mewo]] have filtered [[iControlU]] command invocations in an attempt to prevent themselves from being [[iControlU#Locking|locked]]. Large scope blocks are discouraged unless you have a very good reason, as they have a noticeable impact on the [[Kaboom]] experience.

==Chat messages==

Chat message rules are also effective during spambot attacks and have been used in the past to implement general content filters instead of just mitigating spambot attempts. For example, [[KCB]] would clear the chat if it detected a Discord invite in chat. Other bots have filtered chat messages for things like swear words or slurs in the past.

=Enforcement=

Enforcement of filter rules is often achieved by repeatedly [https://minecraft.wiki/w/Commands/deop deopping] players, changing their [https://minecraft.wiki/w/Game_mode gamemode] to something that isn't [https://minecraft.wiki/w/Creative creative], and [https://minecraft.wiki/w/Commands/clear clearing] their inventories. [[Kick exploits|Kick]] and [[Crash exploits|crash]] exploits may also be used to enforce filter rules.

==Implementation details==

In the interest of server performance and bandwidth usage, it is recommended that extensive use of [https://minecraft.wiki/w/Target%20selectors target selector] predicates be made (except for the NBT predicate, as that requires exporting the entity to NBT, which is an expensive operation).

For example, filtered players should be added to [https://minecraft.wiki/w/Scoreboard teams] and selected via <code>@a[team=example]</code>.
Furthermore, team names should be randomized, and players should be added and removed from them based on the [https://minecraft.wiki/w/Java_Edition_protocol/Packets#Update_Teams Update Teams packet]. It's also a good idea to change the name of the team if it is removed, to prevent easy filter bypass.

=Whitelists=

A whitelist is a type of filter that only performs enforcement actions when a player doesn't match a rule, instead of only when a player matches the rule. Due to this, whitelists have no need to implement [[Filtering#Commands|command rules]] or [[Filtering#Chat messages|chat message rules]]. Whitelists can somewhat emulate the behavior of the [https://minecraft.wiki/w/Commands/whitelist <code>/whitelist</code>] command if it is paired with a kick exploit.

Filtering

2026-08-04T23:55:00Z

Troll ing: Minor spelling fix

'''Filtering''' is the act of automatically restricting a player's access to the server based on rules. For example, one may decide to create a [[Wikipedia:IP_address|IP address]] filter rule to restrict a player, even if they were to change their username.

Depending on the enabled enforcement types and implementation quality, filter activation can result in server lag and as such it is recommended to use efficient [[Kick exploits|kick exploits]] where possible or no kick exploits at all, especially when filtering spambots.

Filtering is extremely useful when the server is spambotted and the spambots contain predictable characteristics which can be expressed in one or more rule type.

=Rules=

Filtering based on arbitrary strings, like chat messages or commands, is commonly implemented via versatile [[Wikipedia:Regular expression|regular expressions]].

==IP address==

IP address rules are commonly used in lieu of exact username filters as evasion requires the use of [[Wikipedia:Proxy_server|proxies]] (often provided by VPN services).

Due to most clones using [[IP masking]], it is impossible to filter [[Wikipedia:Subnet|subnets]] or [[Wikipedia:Autonomous system (Internet)|ASNs]] as one would expect from a [[Wikipedia:Firewall_(computing)|firewall]].

==Usernames==

Username filter rules are often the first to be implemented when a bot or client developer is implementing a filter system. Due to most Kaboom clones being offline mode, it is also the easiest to bypass as players can just join under a different username.

However, in combination with regular expressions, username filters can be used to mitigate spambots that use fixed username lengths or a predictable username format. Luckily, most easily available or paid spambot services use a predictable username format, so this remains one of the most important filter types to implement.

==Commands==

Command rules can be effective to combat general command abuse as well as spambots which spam a certain command. For example, command rules have been used in the past to filter [[Skynet#Mountains of Lava Inc.|Skynet]].

In the past, bots like [[mewo]] have filtered [[iControlU]] command invocations in an attempt to prevent itself from being [[iControlU#Locking|locked]]. Large scope blocks are discouraged unless you have a very good reason, as they have a noticeable impact on the [[Kaboom]] experience.

==Chat messages==

Chat message rules are also effective during spambot attacks, and have been used in the past to implement general content filters instead of just mitigating spambot attempts. For example, [[KCB]] would clear the chat if it detected a Discord invite in chat. Other bots have filtered chat messages for things like swear words or slurs in the past.

=Enforcement=

Enforcement of filter rules is often achieved by repeatedly [https://minecraft.wiki/w/Commands/deop deopping] players, changing their [https://minecraft.wiki/w/Game_mode gamemode] to something that isn't [https://minecraft.wiki/w/Creative creative], and [https://minecraft.wiki/w/Commands/clear clearing] their inventories. [[Kick exploits|Kick]] and [[Crash exploits|crash]] exploits may also be used to enforce filter rules.

==Implementation details==

In the interest of server performance and bandwidth usage, it is recommended that extensive use of [https://minecraft.wiki/w/Target%20selectors target selector] predicates are made (with the exception of the NBT predicate as that requires exporting the entity to NBT which is an expensive operation).

For example, filtered players should be added to [https://minecraft.wiki/w/Scoreboard teams] and selected via <code>@a[team=example]</code>.
Furthermore, team names should be randomized, players should be added and removed from them based on the [https://minecraft.wiki/w/Java_Edition_protocol/Packets#Update_Teams Update Teams packet]. It's also a good idea to change the name of the team if it is removed, to prevent easy filter bypass.

=Whitelists=

A whitelist is a type of filter that only performs enforcement actions when a player doesn't match a rule, instead of only when a player matches the rule. Due to this, whitelists have no need to implement [[Filtering#Commands|command rules]] or [[Filtering#Chat messages|chat message rules]]. Whitelists can somewhat emulate the behavior of the [https://minecraft.wiki/w/Commands/whitelist <code>/whitelist</code>] command if it is paired with a kick exploit.

Filtering

2026-08-04T16:06:31Z

Troll ing: Might be useful to mention kick and crash exploits as many bots use them for filtering

'''Filtering''' is the act of automatically restricting a player's access to the server based on rules. For example, one may decide to create a [[Wikipedia:IP_address|IP address]] filter rule to restrict a player, even if they were to change their username.

Depending on the enabled enforcement types and implementation quality, filter activation can result in server lag and as such it is recommended to use efficient [[Kick exploits|kick exploit]] where possible or no kick exploits at all, especially when filtering spambots.

Filtering is extremely useful when the server is spambotted and the spambots contain predictable characteristics which can be expressed in one or more rule type.

=Rules=

Filtering based on arbitrary strings, like chat messages or commands, is commonly implemented via versatile [[Wikipedia:Regular expression|regular expressions]].

==IP address==

IP address rules are commonly used in lieu of exact username filters as evasion requires the use of [[Wikipedia:Proxy_server|proxies]] (often provided by VPN services).

Due to most clones using [[IP masking]], it is impossible to filter [[Wikipedia:Subnet|subnets]] or [[Wikipedia:Autonomous system (Internet)|ASNs]] as one would expect from a [[Wikipedia:Firewall_(computing)|firewall]].

==Usernames==

Username filter rules are often the first to be implemented when a bot or client developer is implementing a filter system. Due to most Kaboom clones being offline mode, it is also the easiest to bypass as players can just join under a different username.

However, in combination with regular expressions, username filters can be used to mitigate spambots that use fixed username lengths or a predictable username format. Luckily, most easily available or paid spambot services use a predictable username format, so this remains one of the most important filter types to implement.

==Commands==

Command rules can be effective to combat general command abuse as well as spambots which spam a certain command. For example, command rules have been used in the past to filter [[Skynet#Mountains of Lava Inc.|Skynet]].

In the past, bots like [[mewo]] have filtered [[iControlU]] command invocations in an attempt to prevent itself from being [[iControlU#Locking|locked]]. Large scope blocks are discouraged unless you have a very good reason, as they have a noticeable impact on the [[Kaboom]] experience.

==Chat messages==

Chat message rules are also effective during spambot attacks, and have been used in the past to implement general content filters instead of just mitigating spambot attempts. For example, [[KCB]] would clear the chat if it detected a Discord invite in chat. Other bots have filtered chat messages for things like swear words or slurs in the past.

=Enforcement=

Enforcement of filter rules is often achieved by repeatedly [https://minecraft.wiki/w/Commands/deop deopping] players, changing their [https://minecraft.wiki/w/Game_mode gamemode] to something that isn't [https://minecraft.wiki/w/Creative creative], and [https://minecraft.wiki/w/Commands/clear clearing] their inventories. [[Kick exploits|Kick]] and [[Crash exploits|crash]] exploits may also be used to enforce filter rules.

==Implementation details==

In the interest of server performance and bandwidth usage, it is recommended that extensive use of [https://minecraft.wiki/w/Target%20selectors target selector] predicates are made (with the exception of the NBT predicate as that requires exporting the entity to NBT which is an expensive operation).

For example, filtered players should be added to [https://minecraft.wiki/w/Scoreboard teams] and selected via <code>@a[team=example]</code>.
Furthermore, team names should be randomized, players should be added and removed from them based on the [https://minecraft.wiki/w/Java_Edition_protocol/Packets#Update_Teams Update Teams packet]. It's also a good idea to change the name of the team if it is removed, to prevent easy filter bypass.

=Whitelists=

A whitelist is a type of filter that only performs enforcement actions when a player doesn't match a rule, instead of only when a player matches the rule. Due to this, whitelists have no need to implement [[Filtering#Commands|command rules]] or [[Filtering#Chat messages|chat message rules]]. Whitelists can somewhat emulate the behavior of the [https://minecraft.wiki/w/Commands/whitelist <code>/whitelist</code>] command if it is paired with a kick exploit.

kono b

2026-08-04T10:38:26Z

Troll ing: Adding prefixes

{{Bot
| image1=kono_b.png
| caption1=kono_b's skin (belonging to the account [https://namemc.com/profile/sensen1234.1 sensen1234]
| name=kono_b
| main_developers=[[Plovie]]
| date_created={{date|04/09/2025}}
| currently_maintained=Yes
| library=
| language=[[Node.js]]
| prefixes=<nowiki>_</nowiki> (plobot part)<br>"hey kono_b" (LLM part)
}}
{{DISPLAYTITLE:kono_b}}'''kono_b''' is a [[Kaboom]] bot that is a clone of the old [[Plobot]]{{Citation needed}}. It wears a female skin, and uses a [[Wikipedia:Large_language_model|large language model]] to generate responses to chat messages that contain its username.

[[Category:Bots]]

Banning

2026-08-04T08:09:52Z

Troll ing: Redirect this too

#REDIRECT [[Filtering]]

Bans

2026-08-04T08:09:27Z

Troll ing: Redirecting

#REDIRECT [[Filtering]]

Ban

2026-08-04T08:08:49Z

Troll ing: Redirects

#REDIRECT [[Filtering]]

User talk:Troll ing

2026-08-04T07:36:35Z

Troll ing: /* Rewrite of Filtering article */ fixing link

== Rewrite of Filtering article ==

: Hey there. I've made a draft rewrite of the [[Filtering]] article at [[User:Opt/Drafts/Filtering]], as I felt the original revision was a little hard to read and contained information better documented in a dedicated article. I would appreciate if you looked through it and gave me any feedback on what you'd like to see included/changed. --[[User:Opt|Opt]] ([[User talk:Opt|talk]]) 01:30, 4 August 2026 (UTC)
::: I see, but I still feel like the original information may still be useful to certain players, maybe we should break each section in the original page down into separate individual pages so the information is not lost and link to them on the main Filtering page. For example, creating a page dedicated to the methods of filtering, instead of putting it all in one place? --[[User:Troll ing|troll_ing]] ([[User talk:Troll ing|talk]]) 06:54, 4 August 2026 (UTC)
::: Yeah, that was the idea behind the rewrite in the first place. Documenting kick exploits, crash exploits, freeze exploits etc in dedicated articles (although kick exploits should be documented in the kick exploit article, without good reason to split them into new articles). However, I don't think that filter rules deserved their own article, so I documented them all on the [[Filtering]] article. --[[User:Opt|Opt]] ([[User talk:Opt|talk]]) 07:17, 4 August 2026 (UTC)
:::: I have moved some of the original kick exploit section into the dedicated [[Kick exploits]] page, although it may require some cleaning up and expanding though. --[[User:Troll ing|troll_ing]] ([[User talk:Troll ing|talk]]) 07:34, 4 August 2026 (UTC)

User talk:Troll ing

2026-08-04T07:34:52Z

Troll ing: Forgot to sign

== Rewrite of Filtering article ==

: Hey there. I've made a draft rewrite of the [[Filtering]] article at [[User:Opt/Drafts/Filtering]], as I felt the original revision was a little hard to read and contained information better documented in a dedicated article. I would appreciate if you looked through it and gave me any feedback on what you'd like to see included/changed. --[[User:Opt|Opt]] ([[User talk:Opt|talk]]) 01:30, 4 August 2026 (UTC)
::: I see, but I still feel like the original information may still be useful to certain players, maybe we should break each section in the original page down into separate individual pages so the information is not lost and link to them on the main Filtering page. For example, creating a page dedicated to the methods of filtering, instead of putting it all in one place? --[[User:Troll ing|troll_ing]] ([[User talk:Troll ing|talk]]) 06:54, 4 August 2026 (UTC)
::: Yeah, that was the idea behind the rewrite in the first place. Documenting kick exploits, crash exploits, freeze exploits etc in dedicated articles (although kick exploits should be documented in the kick exploit article, without good reason to split them into new articles). However, I don't think that filter rules deserved their own article, so I documented them all on the [[Filtering]] article. --[[User:Opt|Opt]] ([[User talk:Opt|talk]]) 07:17, 4 August 2026 (UTC)
:::: I have moved some of the original kick exploit section into the dedicated [[kick exploit]] page, although it may require some cleaning up and expanding though. --[[User:Troll ing|troll_ing]] ([[User talk:Troll ing|talk]]) 07:34, 4 August 2026 (UTC)

User talk:Troll ing

2026-08-04T07:33:47Z

Troll ing: /* Rewrite of Filtering article */ reply 2 reply

== Rewrite of Filtering article ==

: Hey there. I've made a draft rewrite of the [[Filtering]] article at [[User:Opt/Drafts/Filtering]], as I felt the original revision was a little hard to read and contained information better documented in a dedicated article. I would appreciate if you looked through it and gave me any feedback on what you'd like to see included/changed. --[[User:Opt|Opt]] ([[User talk:Opt|talk]]) 01:30, 4 August 2026 (UTC)
::: I see, but I still feel like the original information may still be useful to certain players, maybe we should break each section in the original page down into separate individual pages so the information is not lost and link to them on the main Filtering page. For example, creating a page dedicated to the methods of filtering, instead of putting it all in one place? --[[User:Troll ing|troll_ing]] ([[User talk:Troll ing|talk]]) 06:54, 4 August 2026 (UTC)
::: Yeah, that was the idea behind the rewrite in the first place. Documenting kick exploits, crash exploits, freeze exploits etc in dedicated articles (although kick exploits should be documented in the kick exploit article, without good reason to split them into new articles). However, I don't think that filter rules deserved their own article, so I documented them all on the [[Filtering]] article. --[[User:Opt|Opt]] ([[User talk:Opt|talk]]) 07:17, 4 August 2026 (UTC)
:::: I have moved some of the original kick exploit section into the dedicated [[kick exploit]] page, although it may require some cleaning up and expanding though.

Kick exploits

2026-08-04T07:05:37Z

Troll ing: /* Serverside */ Moving some info from filtering into this article, may need some expanding though

{{Stub}}

'''Kick exploits''' are [[Wikipedia:Exploit (computer security)|exploits]] that can be abused to make an unpatched client disconnect itself or force the server to disconnect a player.

=Serverside=
==Vanilla Kick Exploits==
Vanilla kick exploits work by forcing the server to send a large amount of data to the client, causing the server to disconnect the player as a result.

==ViaVersion Kick Exploits==
ViaVersion kick exploits work by abusing a bug in the ViaVersion plugin to disconnect the player. These exploits only work on players who are on a different version than the server.

=Clientside=

Talk:Filtering

2026-08-04T06:56:29Z

Troll ing: Reply again

: Hello. Thanks for this contribution. However, this page is '''very long''', with lots of small sections. For example, I don't think that the article needs to document every type of kick and crash exploit, and that documentation efforts there would be done better in dedicated articles. I might clean up the page myself later, but this is a difficult rewrite. --[[User:Opt|Opt]] ([[User talk:Opt|talk]]) 22:30, 3 August 2026 (UTC)

:: I've made a draft of the rewrite at [[User:Opt/Drafts/Filtering]]. Notes would be appreciated. Thanks! --[[User:Opt|Opt]] ([[User talk:Opt|talk]]) 00:28, 4 August 2026 (UTC)

::: I see, but I still feel like the original information may still be useful to certain players, maybe we should break each section in the original page down into separate individual pages so the information is not lost and link to them on the main Filtering page. For example, creating a page dedicated to the methods of filtering, instead of putting it all in one place? --[[User:Troll ing|troll_ing]] ([[User talk:Troll ing|talk]]) 06:56, 4 August 2026 (UTC)

User talk:Troll ing

2026-08-04T06:54:33Z

Troll ing: /* Rewrite of Filtering article */ replying with thoughts

iControlU

2026-08-03T22:26:16Z

Troll ing: Linking the filter page

'''iControlU''' is a plugin that allows players to control others with the <code>/icu control</code> command.

Before the widespread use of [[Command cores]] and the advent of the connection limit, it was used by bots to provide a "locking" feature, as the plugin disables features such as chat and movement while a player is being controlled.

It has largely fallen out of use by bot developers as it requires you to have a Minecraft client connected to the server for each person you want to control. This spams chat, and will require the use of proxies if more than 4 locked players join the server at one time.

Instead, modern bots implement a "[[filter]]" system in their command core.

[[Category:Plugins]]

Filtering

2026-08-03T22:24:12Z

Troll ing: Rephrase

'''Filtering''' is the act of restricting the access of a certain player to the Kaboom server.

Filters are created by using bots that support it and are similar to how bans work on regular servers as they both restrict the access to their respective servers. These filters are typically used on players that bot owners dislike or are considered as harmful, such as spammers, people who run kill @e repeatedly, or players who are generally a nuisance.

==Methods of Filtering==

===iControlU===
iControlU is a plugin on Kaboom that allows for another player to "control" a player by taking over the player's movement, chat, and command access for themselves. Bots use this method by creating another bot which then controls the player, resulting in the player losing the ability to chat, move and run commands. However, this method is less frequently used nowadays due to it creating spam in the chat and requiring proxies to filter more than 4 players at a time.

===Kick Exploits===
A kick exploit is an exploit that allows for a player to be disconnected from the server without using the <code>/kick</code> command, which is currently blocked on the server.

====Vanilla Kick Exploits====
Vanilla kick exploits work by forcing the server to send a large amount of data to the client, causing the server to disconnect the player as a result.

====ViaVersion Kick Exploits====
ViaVersion kick exploits work by abusing a bug in the ViaVersion plugin to disconnect the player. These exploits only work on players who are on a different version than the server.

===Crash Exploits===
A crash exploit is an exploit that causes a player's client to crash. These exploits can be mitigated or blocked by a mod since they are client sided.

====Translate Crash Exploits====
Translate crash exploits work by abusing Minecraft's translation key feature by using it to recursively duplicate a string several times and then attempting to display it. This leads to the target crashing due to memory exhaustion.

====Particle Crash Exploits====
Particle crash exploits work by forcing the client to render a huge amount of laggy particles, which can be done by using area effect clouds. This method is not frequently used due to the risk of crashing unintended players.

===Gamemode Restrictions===
Gamemode restrictions do not cause the player to be disconnected from the server, but instead reduces the player's enjoyment by forcing the player into adventure or spectator mode repeatedly.

===Deopping===
Repeatedly deopping the player prevents them from utilizing operator commands, which serves to reduce the enjoyment of the player as well as preventing them from doing any more harm, leading them to disconnect on their own.

===Teleportation===
Repeatedly teleporting the player to a specific position prevents them from moving, which also reduces the player's enjoyment.

===Multiple Methods===
Most bots utilize multiple methods to cause a player to disconnect, leading to a higher chance of actually kicking the player.

==Methods of Detecting Filtered Players==

===Usernames===
Username detection is the simplest type of filtered player detection. It can be used by making a bot to simply read the tab list and kick anyone that is marked to be filtered on the list.

===IP addresses===
IP address detection is a more complex way of filtering. It involves running the <code>/seen</code> command on every player that joins, then parsing the result for the IP address, and finally kicking anyone who has the IP address on their filter list.

===Fingerprinting===
Fingerprinting is more frequently used on bots and works by searching for a pattern of commands a bot sends when first connecting to the server, and if the pattern matches a predefined entry on the filter list, the bot is kicked.

==Methods of Bypassing Filters==

===Alternative Accounts===
Using an alternative or "alt" account can be used to bypass simple username based filtering. Due to Kaboom being a "cracked" server, a player can simply use a "cracked" or pirate launcher to join with a custom name.

===VPNs and Proxies===
Using a VPN or a proxy can be used to bypass IP based filtering.

mqcore

2026-08-03T22:22:42Z

Troll ing: Linking to filtering

{{Bot|title1=mqcore|name=mqcore|date_created=Between February and March 2026|currently_maintained=Yes
|image1=Wood Pigeon.jpg
}}

'''mqcore''' is a [[Kaboom]] bot, named after its extensive use of the [[wikipedia:MQTT|MQTT]] protocol. However, it is also referred to as "schizo bot", and "1.12.2 bot" (as the author joined Kaboom on a modified 1.12.2 client).

Originally, the prefix for this bot was >>, but it has been changed to >. Both prefixes work.

==Features==

The bot implements session, playtime, IP, chat and command tracking to make these features possible.

{| class="wikitable"
|+ Features
|-
! Feature !! Description
|-
| Alts || Find alternative accounts & IPs of a given player
|-
| Firstseen and Lastseen || Shows the date, server and IP of a given players first or last join
|-
| Last || Shows recent sessions for a given player
|-
| Lastwords and Firstwords || Shows the first or last message sent by a given player
|-
| Nword || Shows the amount of times a given player said both variations of the N word
|-
| Parkourgenerator || Inspired by Blackilykat's pkgen from HermitBot, with some additional features.
|-
| Playtime || Gives a summary about playtime stats of a given player
|-
| Schizo || Forces a given player, or the whole server, to babble random nonsense sourced from the bot's database. Can babble both commands and chat messages
|-
| CA Pentesting || A few CA experiments, one of them caused [[ChomeNS Bot]] to freeze and disconnect, allowing the filter to be bypassed. This was quickly fixed by its developer.
|}

==Filtering==

The bot has participated in [[filter wars]], both between [[Taskmaster]] and [[mewo]] (operated by [[cxvqo]]). This resulted in the development of the bot's blacklist feature.

{| class="wikitable"
|-
! Target !! Justification !! Active
|-
| [[TrouserStreaks]] users || Spamming /fill and /setblock || Variable
|-
| Russians || Large volume of abuse & supporting the [[wikipedia:Russia_under_Vladimir_Putin|Putin regime]] || Putin supporters only
|-
| Spammers || Spamming chat or commands || Yes
|-
| Crashers || Crashing the server, preventing access for a few minutes || Yes
|-
| Toxic players || Generally bringing the mood down, yo. || Yes
|-
| Spambots || Pretty much the same as spammers, but usually with more accounts. || Yes
|}

Some [[filters]] were applied in the past which were not justifiable and have since been removed.

[[Category:Bots]]

Filters

2026-08-03T22:14:32Z

Troll ing: Redirect page

#REDIRECT [[Filtering]]

Filtering

2026-08-03T22:13:23Z

Troll ing: /* Multiple Methods */ phrasing change

'''Filtering''' is the act of restricting the access of a certain player to the Kaboom server.

Filters are created by using bots that support it and are similar to how bans work on regular servers as they both restrict the access to their respective servers. These filters are usually used on players that bot owners dislike or are considered as harmful, such as spammers, people who run kill @e repeatedly, or players who are generally a nuisance.

==Methods of Filtering==

===iControlU===
iControlU is a plugin on Kaboom that allows for another player to "control" a player by taking over the player's movement, chat, and command access for themselves. Bots use this method by creating another bot which then controls the player, resulting in the player losing the ability to chat, move and run commands. However, this method is less frequently used nowadays due to it creating spam in the chat and requiring proxies to filter more than 4 players at a time.

===Kick Exploits===
A kick exploit is an exploit that allows for a player to be disconnected from the server without using the <code>/kick</code> command, which is currently blocked on the server.

====Vanilla Kick Exploits====
Vanilla kick exploits work by forcing the server to send a large amount of data to the client, causing the server to disconnect the player as a result.

====ViaVersion Kick Exploits====
ViaVersion kick exploits work by abusing a bug in the ViaVersion plugin to disconnect the player. These exploits only work on players who are on a different version than the server.

===Crash Exploits===
A crash exploit is an exploit that causes a player's client to crash. These exploits can be mitigated or blocked by a mod since they are client sided.

====Translate Crash Exploits====
Translate crash exploits work by abusing Minecraft's translation key feature by using it to recursively duplicate a string several times and then attempting to display it. This leads to the target crashing due to memory exhaustion.

====Particle Crash Exploits====
Particle crash exploits work by forcing the client to render a huge amount of laggy particles, which can be done by using area effect clouds. This method is not frequently used due to the risk of crashing unintended players.

===Gamemode Restrictions===
Gamemode restrictions do not cause the player to be disconnected from the server, but instead reduces the player's enjoyment by forcing the player into adventure or spectator mode repeatedly.

===Deopping===
Repeatedly deopping the player prevents them from utilizing operator commands, which serves to reduce the enjoyment of the player as well as preventing them from doing any more harm, leading them to disconnect on their own.

===Teleportation===
Repeatedly teleporting the player to a specific position prevents them from moving, which also reduces the player's enjoyment.

===Multiple Methods===
Most bots utilize multiple methods to cause a player to disconnect, leading to a higher chance of actually kicking the player.

==Methods of Detecting Filtered Players==

===Usernames===
Username detection is the simplest type of filtered player detection. It can be used by making a bot to simply read the tab list and kick anyone that is marked to be filtered on the list.

===IP addresses===
IP address detection is a more complex way of filtering. It involves running the <code>/seen</code> command on every player that joins, then parsing the result for the IP address, and finally kicking anyone who has the IP address on their filter list.

===Fingerprinting===
Fingerprinting is more frequently used on bots and works by searching for a pattern of commands a bot sends when first connecting to the server, and if the pattern matches a predefined entry on the filter list, the bot is kicked.

==Methods of Bypassing Filters==

===Alternative Accounts===
Using an alternative or "alt" account can be used to bypass simple username based filtering. Due to Kaboom being a "cracked" server, a player can simply use a "cracked" or pirate launcher to join with a custom name.

===VPNs and Proxies===
Using a VPN or a proxy can be used to bypass IP based filtering.

Filtering

2026-08-03T22:12:13Z

Troll ing: /* Translate Crash Exploit */ consistency change

'''Filtering''' is the act of restricting the access of a certain player to the Kaboom server.

Filters are created by using bots that support it and are similar to how bans work on regular servers as they both restrict the access to their respective servers. These filters are usually used on players that bot owners dislike or are considered as harmful, such as spammers, people who run kill @e repeatedly, or players who are generally a nuisance.

==Methods of Filtering==

===iControlU===
iControlU is a plugin on Kaboom that allows for another player to "control" a player by taking over the player's movement, chat, and command access for themselves. Bots use this method by creating another bot which then controls the player, resulting in the player losing the ability to chat, move and run commands. However, this method is less frequently used nowadays due to it creating spam in the chat and requiring proxies to filter more than 4 players at a time.

===Kick Exploits===
A kick exploit is an exploit that allows for a player to be disconnected from the server without using the <code>/kick</code> command, which is currently blocked on the server.

====Vanilla Kick Exploits====
Vanilla kick exploits work by forcing the server to send a large amount of data to the client, causing the server to disconnect the player as a result.

====ViaVersion Kick Exploits====
ViaVersion kick exploits work by abusing a bug in the ViaVersion plugin to disconnect the player. These exploits only work on players who are on a different version than the server.

===Crash Exploits===
A crash exploit is an exploit that causes a player's client to crash. These exploits can be mitigated or blocked by a mod since they are client sided.

====Translate Crash Exploits====
Translate crash exploits work by abusing Minecraft's translation key feature by using it to recursively duplicate a string several times and then attempting to display it. This leads to the target crashing due to memory exhaustion.

====Particle Crash Exploits====
Particle crash exploits work by forcing the client to render a huge amount of laggy particles, which can be done by using area effect clouds. This method is not frequently used due to the risk of crashing unintended players.

===Gamemode Restrictions===
Gamemode restrictions do not cause the player to be disconnected from the server, but instead reduces the player's enjoyment by forcing the player into adventure or spectator mode repeatedly.

===Deopping===
Repeatedly deopping the player prevents them from utilizing operator commands, which serves to reduce the enjoyment of the player as well as preventing them from doing any more harm, leading them to disconnect on their own.

===Teleportation===
Repeatedly teleporting the player to a specific position prevents them from moving, which also reduces the player's enjoyment.

===Multiple Methods===
Most bots utilize multiple methods to cause a player to disconnect, leading to a higher chance of success.

==Methods of Detecting Filtered Players==

===Usernames===
Username detection is the simplest type of filtered player detection. It can be used by making a bot to simply read the tab list and kick anyone that is marked to be filtered on the list.

===IP addresses===
IP address detection is a more complex way of filtering. It involves running the <code>/seen</code> command on every player that joins, then parsing the result for the IP address, and finally kicking anyone who has the IP address on their filter list.

===Fingerprinting===
Fingerprinting is more frequently used on bots and works by searching for a pattern of commands a bot sends when first connecting to the server, and if the pattern matches a predefined entry on the filter list, the bot is kicked.

==Methods of Bypassing Filters==

===Alternative Accounts===
Using an alternative or "alt" account can be used to bypass simple username based filtering. Due to Kaboom being a "cracked" server, a player can simply use a "cracked" or pirate launcher to join with a custom name.

===VPNs and Proxies===
Using a VPN or a proxy can be used to bypass IP based filtering.

Filter

2026-08-03T22:10:47Z

Troll ing: Redirect to filtering

#REDIRECT [[Filtering]]

Filtering

2026-08-03T22:03:51Z

Troll ing: anti newline

'''Filtering''' is the act of restricting the access of a certain player to the Kaboom server.

Filters are created by using bots that support it and are similar to how bans work on regular servers as they both restrict the access to their respective servers. These filters are usually used on players that bot owners dislike or are considered as harmful, such as spammers, people who run kill @e repeatedly, or players who are generally a nuisance.

==Methods of Filtering==

===iControlU===
iControlU is a plugin on Kaboom that allows for another player to "control" a player by taking over the player's movement, chat, and command access for themselves. Bots use this method by creating another bot which then controls the player, resulting in the player losing the ability to chat, move and run commands. However, this method is less frequently used nowadays due to it creating spam in the chat and requiring proxies to filter more than 4 players at a time.

===Kick Exploits===
A kick exploit is an exploit that allows for a player to be disconnected from the server without using the <code>/kick</code> command, which is currently blocked on the server.

====Vanilla Kick Exploits====
Vanilla kick exploits work by forcing the server to send a large amount of data to the client, causing the server to disconnect the player as a result.

====ViaVersion Kick Exploits====
ViaVersion kick exploits work by abusing a bug in the ViaVersion plugin to disconnect the player. These exploits only work on players who are on a different version than the server.

===Crash Exploits===
A crash exploit is an exploit that causes a player's client to crash. These exploits can be mitigated or blocked by a mod since they are client sided.

====Translate Crash Exploit====
Translate crash exploits work by abusing Minecraft's translation key feature by using it to recursively duplicate a string several times and then attempting to display it. This leads to the target crashing due to memory exhaustion.

====Particle Crash Exploits====
Particle crash exploits work by forcing the client to render a huge amount of laggy particles, which can be done by using area effect clouds. This method is not frequently used due to the risk of crashing unintended players.

===Gamemode Restrictions===
Gamemode restrictions do not cause the player to be disconnected from the server, but instead reduces the player's enjoyment by forcing the player into adventure or spectator mode repeatedly.

===Deopping===
Repeatedly deopping the player prevents them from utilizing operator commands, which serves to reduce the enjoyment of the player as well as preventing them from doing any more harm, leading them to disconnect on their own.

===Teleportation===
Repeatedly teleporting the player to a specific position prevents them from moving, which also reduces the player's enjoyment.

===Multiple Methods===
Most bots utilize multiple methods to cause a player to disconnect, leading to a higher chance of success.

==Methods of Detecting Filtered Players==

===Usernames===
Username detection is the simplest type of filtered player detection. It can be used by making a bot to simply read the tab list and kick anyone that is marked to be filtered on the list.

===IP addresses===
IP address detection is a more complex way of filtering. It involves running the <code>/seen</code> command on every player that joins, then parsing the result for the IP address, and finally kicking anyone who has the IP address on their filter list.

===Fingerprinting===
Fingerprinting is more frequently used on bots and works by searching for a pattern of commands a bot sends when first connecting to the server, and if the pattern matches a predefined entry on the filter list, the bot is kicked.

==Methods of Bypassing Filters==

===Alternative Accounts===
Using an alternative or "alt" account can be used to bypass simple username based filtering. Due to Kaboom being a "cracked" server, a player can simply use a "cracked" or pirate launcher to join with a custom name.

===VPNs and Proxies===
Using a VPN or a proxy can be used to bypass IP based filtering.

Filtering

2026-08-03T22:02:59Z

Troll ing: Some body text

'''Filtering''' is the act of restricting the access of a certain player to the Kaboom server.

Filters are created by using bots that support it and are similar to how bans work on regular servers as they both restrict the access to their respective servers. These filters are usually used on players that bot owners dislike or are considered as harmful, such as spammers, people who run kill @e repeatedly, or players who are generally a nuisance.

==Methods of Filtering==

===iControlU===
iControlU is a plugin on Kaboom that allows for another player to "control" a player by taking over the player's movement, chat, and command access for themselves. Bots use this method by creating another bot which then controls the player, resulting in the player losing the ability to chat, move and run commands. However, this method is less frequently used nowadays due to it creating spam in the chat and requiring proxies to filter more than 4 players at a time.

===Kick Exploits===
A kick exploit is an exploit that allows for a player to be disconnected from the server without using the <code>/kick</code> command, which is currently blocked on the server.

====Vanilla Kick Exploits====
Vanilla kick exploits work by forcing the server to send a large amount of data to the client, causing the server to disconnect the player as a result.

====ViaVersion Kick Exploits====
ViaVersion kick exploits work by abusing a bug in the ViaVersion plugin to disconnect the player. These exploits only work on players who are on a different version than the server.

===Crash Exploits===
A crash exploit is an exploit that causes a player's client to crash. These exploits can be mitigated or blocked by a mod since they are client sided.

====Translate Crash Exploit====
Translate crash exploits work by abusing Minecraft's translation key feature by using it to recursively duplicate a string several times and then attempting to display it. This leads to the target crashing due to memory exhaustion.

====Particle Crash Exploits====
Particle crash exploits work by forcing the client to render a huge amount of laggy particles, which can be done by using area effect clouds. This method is not frequently used due to the risk of crashing unintended players.

===Gamemode Restrictions===
Gamemode restrictions do not cause the player to be disconnected from the server, but instead reduces the player's enjoyment by forcing the player into adventure or spectator mode repeatedly.

===Deopping===
Repeatedly deopping the player prevents them from utilizing operator commands, which serves to reduce the enjoyment of the player as well as preventing them from doing any more harm, leading them to disconnect on their own.

===Teleportation===
Repeatedly teleporting the player to a specific position prevents them from moving, which also reduces the player's enjoyment.

===Multiple Methods===
Most bots utilize multiple methods to cause a player to disconnect, leading to a higher chance of success.

==Methods of Detecting Filtered Players==

===Usernames===
Username detection is the simplest type of filtered player detection. It can be used by making a bot to simply read the tab list and kick anyone that is marked to be filtered on the list.

===IP addresses===
IP address detection is a more complex way of filtering. It involves running the <code>/seen</code> command on every player that joins, then parsing the result for the IP address, and finally kicking anyone who has the IP address on their filter list.

===Fingerprinting===
Fingerprinting is more frequently used on bots and works by searching for a pattern of commands a bot sends when first connecting to the server, and if the pattern matches a predefined entry on the filter list, the bot is kicked.

==Methods of Bypassing Filters==

===Alternative Accounts===
Using an alternative or "alt" account can be used to bypass simple username based filtering. Due to Kaboom being a "cracked" server, a player can simply use a "cracked" or pirate launcher to join with a custom name.

===VPNs and Proxies===
Using a VPN or a proxy can be used to bypass IP based filtering.

Filtering

2026-08-03T21:33:08Z

Troll ing: /* IP addresses */ fix again

'''Filtering''' is the act of restricting the access of a certain player to the Kaboom server.

==Methods of Filtering==

===iControlU===
iControlU is a plugin on Kaboom that allows for another player to "control" a player by taking over the player's movement, chat, and command access for themselves. Bots use this method by creating another bot which then controls the player, resulting in the player losing the ability to chat, move and run commands. However, this method is less frequently used nowadays due to it creating spam in the chat and requiring proxies to filter more than 4 players at a time.

===Kick Exploits===
A kick exploit is an exploit that allows for a player to be disconnected from the server without using the <code>/kick</code> command, which is currently blocked on the server.

====Vanilla Kick Exploits====
Vanilla kick exploits work by forcing the server to send a large amount of data to the client, causing the server to disconnect the player as a result.

====ViaVersion Kick Exploits====
ViaVersion kick exploits work by abusing a bug in the ViaVersion plugin to disconnect the player. These exploits only work on players who are on a different version than the server.

===Crash Exploits===
A crash exploit is an exploit that causes a player's client to crash. These exploits can be mitigated or blocked by a mod since they are client sided.

====Translate Crash Exploit====
Translate crash exploits work by abusing Minecraft's translation key feature by using it to recursively duplicate a string several times and then attempting to display it. This leads to the target crashing due to memory exhaustion.

====Particle Crash Exploits====
Particle crash exploits work by forcing the client to render a huge amount of laggy particles, which can be done by using area effect clouds. This method is not frequently used due to the risk of crashing unintended players.

===Gamemode Restrictions===
Gamemode restrictions do not cause the player to be disconnected from the server, but instead reduces the player's enjoyment by forcing the player into adventure or spectator mode repeatedly.

===Deopping===
Repeatedly deopping the player prevents them from utilizing operator commands, which serves to reduce the enjoyment of the player as well as preventing them from doing any more harm, leading them to disconnect on their own.

===Teleportation===
Repeatedly teleporting the player to a specific position prevents them from moving, which also reduces the player's enjoyment.

===Multiple Methods===
Most bots utilize multiple methods to cause a player to disconnect, leading to a higher chance of success.

==Methods of Detecting Filtered Players==

===Usernames===
Username detection is the simplest type of filtered player detection. It can be used by making a bot to simply read the tab list and kick anyone that is marked to be filtered on the list.

===IP addresses===
IP address detection is a more complex way of filtering. It involves running the <code>/seen</code> command on every player that joins, then parsing the result for the IP address, and finally kicking anyone who has the IP address on their filter list.

===Fingerprinting===
Fingerprinting is more frequently used on bots and works by searching for a pattern of commands a bot sends when first connecting to the server, and if the pattern matches a predefined entry on the filter list, the bot is kicked.

==Methods of Bypassing Filters==

===Alternative Accounts===
Using an alternative or "alt" account can be used to bypass simple username based filtering. Due to Kaboom being a "cracked" server, a player can simply use a "cracked" or pirate launcher to join with a custom name.

===VPNs and Proxies===
Using a VPN or a proxy can be used to bypass IP based filtering.

Filtering

2026-08-03T21:22:32Z

Troll ing: Fix bold

'''Filtering''' is the act of restricting the access of a certain player to the Kaboom server.

==Methods of Filtering==

===iControlU===
iControlU is a plugin on Kaboom that allows for another player to "control" a player by taking over the player's movement, chat, and command access for themselves. Bots use this method by creating another bot which then controls the player, resulting in the player losing the ability to chat, move and run commands. However, this method is less frequently used nowadays due to it creating spam in the chat and requiring proxies to filter more than 4 players at a time.

===Kick Exploits===
A kick exploit is an exploit that allows for a player to be disconnected from the server without the /kick command, which is currently blocked on the server.

====Vanilla Kick Exploits====
Vanilla kick exploits work by forcing the server to send a large amount of data to the client, causing the server to disconnect the player as a result.

====ViaVersion Kick Exploits====
ViaVersion kick exploits work by abusing a bug in the ViaVersion plugin to disconnect the player. These exploits only work on players who are on a different version than the server.

===Crash Exploits===
A crash exploit is an exploit that causes a player's client to crash. These exploits can be mitigated or blocked by a mod since they are client sided.

====Translate Crash Exploit====
Translate crash exploits work by abusing Minecraft's translation key feature by using it to recursively duplicate a string several times and then attempting to display it. This leads to the target crashing due to memory exhaustion.

====Particle Crash Exploits====
Particle crash exploits work by forcing the client to render a huge amount of laggy particles, which can be done by using area effect clouds. This method is not frequently used due to the risk of crashing unintended players.

===Gamemode Restrictions===
Gamemode restrictions do not cause the player to be disconnected from the server, but instead reduces the player's enjoyment by forcing the player into adventure or spectator mode repeatedly.

===Deopping===
Repeatedly deopping the player prevents them from utilizing operator commands, which serves to reduce the enjoyment of the player as well as preventing them from doing any more harm, leading them to disconnect on their own.

===Teleportation===
Repeatedly teleporting the player to a specific position prevents them from moving, which also reduces the player's enjoyment.

===Multiple Methods===
Most bots utilize multiple methods to cause a player to disconnect, leading to a higher chance of success.

==Methods of Detecting Filtered Players==

===Usernames===
Username detection is the simplest type of filtered player detection. It can be used by making a bot to simply read the tab list and kick anyone that is marked to be filtered on the list.

===IP addresses===
IP address detection is a more complex way of filtering. It involves running the /seen command on every player that joins, then parsing the result for the IP address, and finally kicking anyone who has the IP address on the filter list.

===Fingerprinting===
Fingerprinting is more frequently used on bots and works by searching for a pattern of commands a bot sends when first connecting to the server, and if the pattern matches a predefined entry on the filter list, the bot is kicked.

==Methods of Bypassing Filters==

===Alternative Accounts===
Using an alternative or "alt" account can be used to bypass simple username based filtering. Due to Kaboom being a "cracked" server, a player can simply use a "cracked" or pirate launcher to join with a custom name.

===VPNs and Proxies===
Using a VPN or a proxy can be used to bypass IP based filtering.

Filtering

2026-08-03T21:21:24Z

Troll ing: Remove some typos

"Filtering" is the act of restricting the access of a certain player to the Kaboom server.

==Methods of Filtering==

===iControlU===
iControlU is a plugin on Kaboom that allows for another player to "control" a player by taking over the player's movement, chat, and command access for themselves. Bots use this method by creating another bot which then controls the player, resulting in the player losing the ability to chat, move and run commands. However, this method is less frequently used nowadays due to it creating spam in the chat and requiring proxies to filter more than 4 players at a time.

===Kick Exploits===
A kick exploit is an exploit that allows for a player to be disconnected from the server without the /kick command, which is currently blocked on the server.

====Vanilla Kick Exploits====
Vanilla kick exploits work by forcing the server to send a large amount of data to the client, causing the server to disconnect the player as a result.

====ViaVersion Kick Exploits====
ViaVersion kick exploits work by abusing a bug in the ViaVersion plugin to disconnect the player. These exploits only work on players who are on a different version than the server.

===Crash Exploits===
A crash exploit is an exploit that causes a player's client to crash. These exploits can be mitigated or blocked by a mod since they are client sided.

====Translate Crash Exploit====
Translate crash exploits work by abusing Minecraft's translation key feature by using it to recursively duplicate a string several times and then attempting to display it. This leads to the target crashing due to memory exhaustion.

====Particle Crash Exploits====
Particle crash exploits work by forcing the client to render a huge amount of laggy particles, which can be done by using area effect clouds. This method is not frequently used due to the risk of crashing unintended players.

===Gamemode Restrictions===
Gamemode restrictions do not cause the player to be disconnected from the server, but instead reduces the player's enjoyment by forcing the player into adventure or spectator mode repeatedly.

===Deopping===
Repeatedly deopping the player prevents them from utilizing operator commands, which serves to reduce the enjoyment of the player as well as preventing them from doing any more harm, leading them to disconnect on their own.

===Teleportation===
Repeatedly teleporting the player to a specific position prevents them from moving, which also reduces the player's enjoyment.

===Multiple Methods===
Most bots utilize multiple methods to cause a player to disconnect, leading to a higher chance of success.

==Methods of Detecting Filtered Players==

===Usernames===
Username detection is the simplest type of filtered player detection. It can be used by making a bot to simply read the tab list and kick anyone that is marked to be filtered on the list.

===IP addresses===
IP address detection is a more complex way of filtering. It involves running the /seen command on every player that joins, then parsing the result for the IP address, and finally kicking anyone who has the IP address on the filter list.

===Fingerprinting===
Fingerprinting is more frequently used on bots and works by searching for a pattern of commands a bot sends when first connecting to the server, and if the pattern matches a predefined entry on the filter list, the bot is kicked.

==Methods of Bypassing Filters==

===Alternative Accounts===
Using an alternative or "alt" account can be used to bypass simple username based filtering. Due to Kaboom being a "cracked" server, a player can simply use a "cracked" or pirate launcher to join with a custom name.

===VPNs and Proxies===
Using a VPN or a proxy can be used to bypass IP based filtering.

Filtering

2026-08-03T21:01:13Z

Troll ing: Minor changes 1

'''Filtering''' is the act of restricting the access of a certain player to the kaboom server.

==Methods of Filtering==

===iControlU===
iControlU is a plugin on kaboom that allows for another player to "control" a player by taking over the player's movement, chat, and command access for themselves. Bots use this method by creating another bot which then controls the player, resulting in the player losing the ability to chat, move and run commands. However, this method is less frequently used nowadays due to it creating spam in the chat and requiring proxies to filter more than 4 players at a time.

===Kick Exploits===
A kick exploit is an exploit that allows for a player to be disconnected from the server without the /kick command, which is currently blocked on the server.

====Minecraft Kick Exploits====
Minecraft kick exploits work by forcing the server to send a large amount of data to the client, causing the server to disconnect the player as a result.

====ViaVersion Kick Exploits====
ViaVersion kick exploits work by abusing a bug in the ViaVersion plugin to disconnect the player. These exploits only work on players who are on a different version than the server.

===Crash Exploits===
A crash exploit is an exploit that causes a player's client to crash. These exploits are able to be mitigated or blocked by a mod since they are client sided.

====Translate Crash Exploit====
Translate crash exploits work by abusing Minecraft's translation key feature by using it to recursively duplicate a string several times and then attempting to display it. This leads to the target crashing due to memory exhaustion.

====Particle Crash Exploits====
Particle crash exploits work by forcing the client to render a huge amount of laggy particles, which can be done by using area effect clouds. This method is not frequently used due to the risk of crashing unintended players.

===Gamemode Restrictions===
Gamemode restrictions do not cause the player to be disconnected from the server, but instead reduces the player's enjoyment by forcing the player into adventure or spectator mode repeatedly.

===Deopping===
Repeatedly deopping the player prevents them from utilizing operator commands, which serves to reduce the enjoyment of the player as well as preventing them from doing anymore harm, leading them to disconnect on their own.

===Teleportation===
Repeatedly teleporting the player to a specific position prevents them from moving, which also reduces the player's enjoyment.

===Multiple Methods===
Most bots utilize multiple methods to cause a player to disconnect, leading to a higher chance of success.

==Methods of Detecting Filtered Players==

===Usernames===
Username detection is the most simple type of filtered player detection. It can by used by making a bot to simply read the tab list and kick anyone that is marked to be filtered on the list.

===IP addresses===
IP address detection is a more complex way of filtering. It involves running the /seen command on every player that joins, then parsing the result for the IP address, and finally kicking anyone who has the IP address on the filter list.

===Fingerprinting===
Fingerprinting is more frequently used on bots and works by searching for a pattern of commands a bot sends when first connecting to the server, and if the pattern matches a predefined entry on the filter list, the bot is kicked.

==Methods of Bypassing Filters==

===Alternative Accounts===
Using an alternative or "alt" account can be used to bypass simple username based filtering. Due to kaboom being a "cracked" server, a player can simply use a "cracked" or pirate launcher to join with a custom name.

===VPNs and Proxies===
Using a VPN or a proxy can be used to bypass IP based filtering.

Filtering

2026-08-03T20:56:05Z

Troll ing: Actually putting text on the page

'''Filtering''' is the act of restricting the access of a certain player to the kaboom server.

==Methods of Filtering==

===iControlU===
iControlU is a plugin on kaboom that allows for another player to "control" a player by taking over the player's movement, chat, and command access for themselves. Bots use this method by creating another bot which then controls the player, resulting in the player losing the ability to chat, move and run commands. However, this method is less frequently used nowadays due to it creating spam in the chat and requiring proxies to filter more than 4 players at a time.

===Kick Exploits===
A kick exploit is an exploit that allows for a player to be disconnected from the server without the /kick command, which is currently blocked on the server.

====Minecraft Kick Exploits====
Minecraft kick exploits work by forcing the server to send a large amount of data to the client, causing the server to disconnect the player as a result.

====ViaVersion Kick Exploits====
ViaVersion kick exploits work by abusing a bug in the ViaVersion plugin to disconnect the player. These exploits only work on players who are on a different version than the server due.

===Crash Exploits===
A crash exploit is an exploit that causes a player's client to crash. These exploits are able to be mitigated or blocked by a mod since they are client sided.

====Translate Crash Exploit====
Translate crash exploits work by abusing Minecraft's translation key feature by using it to recursively duplicate a string several times and then attempting to display it. This leads to the target crashing due to memory exhaustion.

====Particle Crash Exploits====
Particle crash exploits work by forcing the client to render a huge amount of laggy particles, which can be done by using area effect clouds. This method is not frequently used due to the risk of crashing unintended players.

===Gamemode Restrictions===
Gamemode restrictions do not cause the player to be disconnected from the server, but instead "kills the fun" by forcing the player into adventure or spectator mode repeatedly.

===Deopping===
Repeatedly deopping the player prevents them from utilizing operator commands, which serves to reduce the enjoyment of the player as well as preventing them from doing anymore harm, leading them to disconnect on their own.

===Teleportation===
Repeatedly teleporting the player to a specific position prevents them from moving, which also reduces the player's enjoyment.

===Multiple Methods===
Most bots utilize multiple methods to cause a player to disconnect, leading to a higher chance of success.

==Methods of Detecting Filtered Players==

===Usernames===
Username detection is the most simple type of filtered player detection. It can by used by making a bot to simply read the tab list and kick anyone that is marked to be filtered on the list.

===IP addresses===
IP address detection is a more complex way of filtering. It involves running the /seen command on every player that joins, then parsing the result for the IP address, and finally kicking anyone who has the IP address on the filter list.

===Fingerprinting===
Fingerprinting is more frequently used on bots and works by searching for a pattern of commands a bot sends when first connecting to the server, and if the pattern matches a predefined entry on the filter list, the bot is kicked.

==Methods of Bypassing Filters==

===Alternative Accounts===
Using an alternative or "alt" account can be used to bypass simple username based filtering. Due to kaboom being a "cracked" server, a player can simply use a "cracked" or pirate launcher to join with a custom name.

===VPNs and Proxies===
Using a VPN or a proxy can be used to bypass IP based filtering.