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.

killEarner

by Limon
Reward players for PvP kills with Takaro currency and configurable combat messages. killEarner turns player-versus-player activity into an economy and engagement loop for game server communities.
Use this module to:
  • Pay players currency when they get PvP kills.
  • Send configurable messages to the killer and victim.
  • Choose whether kill messages are public or private.
  • Let players check their PvP reward stats with a command.
Good fit for PvP servers that want kill rewards, combat incentives, and lightweight player stats without running the reward workflow manually.
communityTakaro main
(2 versions available)

Components Overview

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

New Module: killEarner

NEW
August 12, 2025
Updated to version 0.0.1. Added 1 command: killstats. Added 1 hook: PvP Kill Detector (player-death). New configuration options: killReward, enableKillerMessages, enableVictimMessages, usePublicMessages, killerMessages, victimMessages.

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 (6)

killRewardnumber

Currency reward for killing another player

Default: 100
Constraints: min: 0
enableKillerMessagesboolean

Send messages to the killer

Default: true
enableVictimMessagesboolean

Send messages to the victim

Default: true
usePublicMessagesboolean

Send messages publicly instead of as PMs

Default: false
killerMessagesarray

Random messages for killers

Default:Array of 5 items
"Nice kill!"
"You're on fire!"
... and 3 more items
victimMessagesarray

Random messages for victims

Default:Array of 5 items
"Better luck next time!"
"Ouch!"
... and 3 more items

UI Schema

No configuration properties defined. This module uses default settings.

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.

Commands (1)

These commands can be executed by players in-game. Each command has a trigger word, optional arguments, and executes JavaScript code on the server.

killstats

/killstatsTrigger Command

Description

Use /killstats to see your own stats, or /killstats [playername] to see another player's stats

Arguments (1)

player
playerPosition 0
Help: The player to view stats for (optional - defaults to yourself)
Default: ""

Function Implementation

killstats Function

JAVASCRIPT

Usage Example

Player types: /killstats <player>

About Module Commands

Commands allow players to interact with your module through chat. Each command has a trigger word that players type (prefixed with /), optional arguments for parameters, and a JavaScript function that executes when the command is used. Arguments are automatically validated and passed to the function.

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.

Custom Events

1 hook

PvP Kill Detector

player-deathEvent Type
Description
Detects when a player is killed by another player and triggers rewards and messages
Pattern Match
.*

This hook only triggers when the event data matches this regular expression pattern.

Function Implementation

PvP Kill Detector Hook Function

JAVASCRIPT
Event Details
Event Type:player-death
Trigger:Pattern Match Required
Category:Custom 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.