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.

PvPBet

by Mad
for 7 Days to Die
Let players bet Takaro currency on PvP battles. PvPBet supports player challenges, accepted duels, and winner-takes-pot rewards for communities that want structured PvP wagering.
Use this module to:
  • Let one player challenge another to a PvP bet.
  • Require the opponent to accept before the wager starts.
  • Pay the pot to the battle winner.
  • Add a currency sink and competitive PvP loop to the server.
Good fit for 7 Days to Die PvP communities that already use the required PrismaCore dependency and want betting around player fights.
communityTakaro v0.4.10

Components Overview

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

New Module: PvPBet

NEW
January 23, 2026
Updated to version latest. Added 2 commands: pvpbet, pvpaccept. Added 1 hook: PvP Bet Kill Tracker (log). Added 1 scheduled task: PvP Bet Announcement & Leaderboard. New permission: PVP_BET_USE. New configuration options: minimumBetAmount, xLocation, zLocation, discordChannelId.

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

minimumBetAmount*number
minimumBetAmount

Minimum currency amount required to create a PvP bet

Default: 100
Constraints: min: 1
xLocation*number
xLocation

X coordinate for PvP arena center

Default: 0
zLocation*number
zLocation

Z coordinate for PvP arena center

Default: 0
discordChannelIdstring
discordChannelId

Discord channel ID for posting leaderboard (optional)

Default:

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.

Commands (2)

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

pvpbet

/pvpbetTrigger Command

Description

Challenge another player to a PvP battle with a currency bet. Usage: /pvpbet [amount]

Arguments (1)

amount
numberPosition 0
Help: Amount of currency to bet
Default: None

Function Implementation

pvpbet Function

JAVASCRIPT

Usage Example

Player types: /pvpbet <amount>

pvpaccept

/pvpacceptTrigger Command

Description

Accept an active PvP bet challenge

Function Implementation

pvpaccept Function

JAVASCRIPT

Usage Example

Player types: /pvpaccept

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.

System Events

1 hook

PvP Bet Kill Tracker

logEvent Type
Pattern Match
playerKilledByPlayer

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

Function Implementation

PvP Bet Kill Tracker Hook Function

JAVASCRIPT
Event Details
Event Type:log
Trigger:Pattern Match Required
Category:System 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.

Scheduled Jobs (1)

These jobs run automatically on a schedule defined by cron expressions. Each job executes JavaScript code at specific times or intervals.

PvP Bet Announcement & Leaderboard

22 */2 * * *Schedule

Schedule Details

Cron Expression
22 */2 * * *
Human-Readable Schedule

At minute 22 of every 2 hours on every day of the month in every month on every day of the week

Function Implementation

PvP Bet Announcement & Leaderboard Function

JAVASCRIPT

Cron Expression Format

minute hour day-of-month month day-of-week

Each field can contain numbers, ranges (1-5), lists (1,3,5), or wildcards (*). Use */n for intervals (e.g., */5 for every 5 units).

About Scheduled Jobs

Cron jobs allow your module to execute code automatically on a schedule. Each job has a cron expression that defines when it runs, and a JavaScript function that executes at those times. Jobs run server-side and can perform maintenance tasks, send notifications, or update game state automatically.

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

Use PvP Betting

PVP_BET_USEPermission Key
Description

Allows players to create and accept PvP bets

Permission Details
Full Key:PVP_BET_USE
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.