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.

DiedTeleport

by Limon
Let players return to their last death location with a permissioned /died command. DiedTeleport records death positions and gives admins a controlled recovery workflow for communities that allow death-location teleports.
Use this module to:
  • Save a player's death location automatically.
  • Let permitted players run /died to teleport back.
  • Manage access with Takaro roles and permissions.
  • Reduce manual staff help for death recovery requests.
Good fit for PvE, casual, or community servers where death recovery is part of the player experience.
communityTakaro main
(2 versions available)

Components Overview

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

New Module: DiedTeleport

NEW
August 12, 2025
Updated to version latest. Added 1 command: died. Added 1 hook: Death Location Capture (player-death). New permission: DIED_TELEPORT_USE. New configuration option: deathLocationExpiration.

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

deathLocationExpirationnumber

How long (in seconds) death locations remain valid before expiring. Default: 1 hour (3600 seconds), Min: 1 minute, Max: 24 hours

Default: 3600
Constraints: min: 60, max: 86400

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.

died

/diedTrigger Command

Description

Teleports you back to your last death location

Function Implementation

died Function

JAVASCRIPT

Usage Example

Player types: /died

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

Death Location Capture

player-deathEvent Type
Description
Captures the player's location when they die and stores it for the /died command
Pattern Match
.*

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

Function Implementation

Death Location Capture 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.

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 Died Teleport

DIED_TELEPORT_USEPermission Key
Description

Allows the player to use the /died command to return to their death location

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