Takaro module library

Takaro Modules

Takaro is a game server management platform for running, automating, and moderating multiplayer communities. These modules install into Takaro to add server automation, Discord workflows, economy systems, and moderation tools.

ProfanityFilter

by Limon
Moderate chat by detecting blocked words and applying configurable responses. This module helps community managers keep server chat healthier with automated warnings, actions, and permissions.
Use this module to:
  • Configure profanity and phrase filters.
  • Reduce manual chat moderation work.
  • Support a safer player experience with Takaro hooks.
communityTakaro main

Components Overview

1
config
0
commands
1
hooks
0
Cron Jobs
0
functions
1
permissions

New Module: ProfanityFilter

NEW
August 6, 2025
Updated to version latest. Added 1 hook: profanityChecker (chat-message). New permission: profanity_immunity. New configuration options: HVB_Profanity, noPunishmentMessage, punishmentType, banDuration, warningsBeforePunishment, warningResetTime, kickMessage, banMessage, enableSwearJar, swearJarAmount.

Configuration

Configure this module using the schemas below. The JSON schema defines the data structure, while the UI schema customizes how the configuration form is displayed.

Configuration Schema

Configuration Properties (10)

HVB_Profanityarray
HVB_Profanity

add the words you want

Default:Array of 8 items
"faggot"
"shit"
... and 6 more items
Constraints: minItems: 1, maxItems: 10
noPunishmentMessagestring
noPunishmentMessage

Send a message top make the player know that he should not swear.

Default: Please stop swearing!
Constraints: minLength: 1, maxLength: 100
punishmentTypeenum
punishmentType

this is to decide what to do kick ban

Default: kick
Allowed values (3):
kickbannone
banDurationnumberduration
banDuration

If you choose ban, you can decide how long

Default: 300000
warningsBeforePunishmentnumber
warningsBeforePunishment
Default: 1
Constraints: max: 100
warningResetTimenumberduration
warningResetTime
Default: 600000
kickMessagestring
kickMessage

Continuing will result in being kicked.

Default: Continuing will result in being kicked.
Constraints: minLength: 1, maxLength: 100
banMessagestring
banMessage

Continuing will result in a {duration} ban

Default: Continuing will result in a {duration} ban
Constraints: minLength: 1, maxLength: 100
enableSwearJarboolean
enableSwearJar

Enable the swear jar

Default: false
swearJarAmountnumber
swearJarAmount

swearJarAmount

Default: 0

UI Schema

No UI schema defined. Configuration form will use default rendering.

About Configuration Schemas

The Configuration Schema defines the structure and validation rules for module settings. The UI Schema customizes how the configuration form is displayed in the Takaro interface, including field ordering, labels, and input types.

Hooks (1)

These hooks respond to various game events automatically. Each hook executes JavaScript code when its specific event type occurs, allowing modules to react to player actions, system changes, and more.

Real-time Events

1 hook

profanityChecker

chat-messageEvent Type
Function Implementation

profanityChecker Hook Function

JAVASCRIPT
Event Details
Event Type:chat-message
Trigger:Automatic
Category:Real-time Events

About Module Hooks

Hooks allow your module to respond automatically to game events like player actions, server status changes, and chat messages. Each hook has an event type that determines when it triggers, optional regex patterns for filtering specific events, and a JavaScript function that executes when the conditions are met. Hooks are grouped by category for better organization.

Permissions (1)

These permissions control who can access different features of this module. Administrators can assign these permissions to roles, allowing fine-grained access control.

General Permissions

1 permission

HVB_PROFANITY_FILTER_v3_HVB_PROFANITY_FILTER_v2_profanity_immunity

profanity_immunityPermission Key
Description

This grants immunity for profanity

Permission Details
Full Key:profanity_immunity
Can Have Count:No
Category:General

About Module Permissions

Permissions control access to module features and functionality. Each permission has a unique key for identification, a friendly name for display, and a description explaining what it allows. Some permissions are countable, meaning they can have numeric values or limits assigned. Administrators assign these permissions to user roles to control who can use different module features.