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.

Rampage

by Mad
Create permissioned PvE rampage events with arena teleportation, hostile entity spawns, health boosts, and server announcements. Rampage gives admins a repeatable combat event workflow inside Takaro.
Use this module to:
  • Let permitted players start a rampage event.
  • Teleport participants to configured arena coordinates.
  • Spawn configurable hostile entities around the event area.
  • Broadcast event messages and apply temporary boosts.
  • Control access through Takaro permissions.
Good fit for servers that want PvE challenges, arena events, wave combat, and permission-gated player activities managed through Takaro.

Module details

A permission-based combat module that teleports players to a designated arena and spawns waves of hostile entities for intense PvE challenges. Key Features
Permission-Gated Access: Only players with RAMPAGE_PERMISSION can activate Arena Teleportation: Instantly transports players to configured combat coordinates Random Entity Spawning: Spawns configurable entities around the arena with random positioning Health Boosts: Provides temporary health increases during combat Server Announcements: Broadcasts rampage notifications to all players
Configuration
Set custom arena coordinates (X, Y, Z) Define which entities spawn during rampage mode Control access through Takaro's permission system
Perfect for PvE challenges, special events, and rewarding VIP players with exclusive combat content.RetryClaude can make mistakes. Please double-check responses.
communityTakaro v0.3.3

Components Overview

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

New Module: Rampage

NEW
August 6, 2025
Updated to version latest. Added 1 command: rampage. New permission: RAMPAGE_PERMISSION. New configuration options: rLocationX, rLocationY, rLocationZ, spawnEntities.

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)

rLocationX*string
rLocationX

Teleport player location x

rLocationY*string
rLocationY

Height of teleport

rLocationZstring
rLocationZ

Teleport player location z

spawnEntities*array
spawnEntities

List of Bosses/zombies to spawn

Default: [] (empty array)
Constraints: minItems: 1, maxItems: 100, uniqueItems

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 (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.

rampage

/rampageTrigger Command

Description

Calls in a crazy fight! Don't go alone

Function Implementation

rampage Function

JAVASCRIPT

Usage Example

Player types: /rampage

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.

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

Rampage

RAMPAGE_PERMISSIONPermission Key
Description

Rampaage module

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