• Regex-based URL detection
• Warning and punishment system
• Custom messages for violations
• Configurable punishment and reset timing

• Blocking phishing or spam links
• Promoting safer communication environments

• Customize your list of prohibited words: Easily add, remove, or modify the list of offensive terms you want to filter.
• Choose from various punishment options: Issue warnings, impose fines (in-game currency), kick, or even ban players for using inappropriate language.
• Set up a swear jar: Encourage players to watch their language by adding a fine to the swear jar for each infraction.
• Configure warnings and reset times: Fine-tune the module's sensitivity by adjusting the number of warnings before punishment and how long it takes for warnings to reset.
• Send customizable messages: Inform players about the rules, warn them about their language, or notify them of the consequences of continued profanity.

• Customizable profanity list
• Flexible punishment options (warnings, fines, kicks, bans)
• Swear jar functionality
• Configurable warnings and reset times
• Customizable messages

• Creates a more welcoming and inclusive gaming environment
• Reduces toxic behavior and promotes positive interactions
• Encourages players to be mindful of their language
• Provides a clear and consistent system for moderating profanity

Key Functionality

• VAC Ban Detection: The module retrieves player VAC ban information (number of bans, days since last ban) from the game server.
• Configurable Threshold: Administrators can set a threshold for the number of days since the last VAC ban. Players with bans within this threshold are subject to punishment.
• Punishment Options: The module supports two punishment types: * Kick: Removes the player from the server. * Ban: Temporarily bans the player.
• Customizable Messages: Kick and ban messages can be customized to inform players of the reason for the action.
• Immunity Permission: A permission can be granted to exempt specific players from VAC ban checks and punishments.

How to Use

1. Configuration:
   • PunishmentType: Choose the punishment to apply (kick or ban). Default: kick.
   • Ban Duration: If PunishmentType is ban, set the duration of the ban (in milliseconds).
   • PunishmentMessage: Customize the message shown to the player when they are kicked or banned. Use {days} as a placeholder for the number of days since the player's last VAC ban and {threshold} for the configured DaysThreshold.
   • DaysThreshold: Set the number of days. Players with a VAC ban within this many days will be punished.
2. Permissions:
   • Grant the VAC_BAN_IMMUNITY permission to players who should be exempt from VAC ban checks.
3. Module Operation:
   • The module automatically checks players when they connect to the server. No manual commands are required.

Important Considerations

• Game Server Compatibility: Ensure that your game server provides the necessary player VAC ban information for this module to function correctly.
• Threshold Setting: Carefully consider the DaysThreshold to balance enforcement with player leniency.
• Immunity Usage: Use the VAC_BAN_IMMUNITY permission judiciously.
• Message Clarity: Customize the PunishmentMessage to provide clear and informative reasons for kicks or bans.

Community Fund

What it does

• Players run /fund <amount> to contribute their own currency toward the active goal.
• /fundstatus shows the current total, target, progress percentage, and round count.
• /fundhistory shows total completions and the last player who pushed the fund over the line.
• Contributions can be globally broadcast so the server sees momentum build.
• When the target is reached, the module broadcasts a configurable completion message.
• Completion commands let staff unlock server-wide rewards, effects, events, or other game-server actions.
• Overshoot carries into the next round instead of being discarded.

Verified dashboard chat flow

1. Bot1_fund90dj runs !fundstatus and sees 0/50.
2. Bot1_fund90dj contributes 20 currency with !fund 20.
3. Bot1_pool90dj runs !fundstatus and sees 20/50 (40%).
4. Bot1_pool90dj contributes 35 currency with !fund 35.
5. The fund reaches the 50 threshold, broadcasts the unlock message, executes the configured completion command, and starts round #1.
6. !fundhistory confirms 1 completion total and records Bot1_pool90dj as the player who completed the round.

Player commands

Permissions

Install configuration

• fundThreshold: target amount that completes a round.
• minimumContribution: minimum currency amount a player can contribute per command.
• completionMessage: broadcast message sent when the threshold is reached. Supports {threshold}.
• completionCommands: raw game-server commands executed after completion, for rewards or server events.
• broadcastContributions: whether each contribution is announced globally.

Verified sandbox result

• fundThreshold: 50
• minimumContribution: 5
• completionMessage: Community Fund reached {threshold}! Server-wide bonus unlocked!
• completionCommands: say Community Fund complete: reward unlocked
• broadcastContributions: true

• First contribution: 20 currency from Bot1_fund90dj
• Second contribution: 35 currency from Bot1_pool90dj
• Threshold reached: 50
• Carryover into next round: 5
• Completion count: 1
• Last completion: Round #1, 2026-04-27, by Bot1_pool90dj

Readable variable evidence

MeeBob_Donator: Premium VIP Kit System

Key Benefits:

• Seamless VIP Recognition: Automatically identifies players with VIP permissions
• Configurable Item Bundles: Customize exactly what items, qualities, and quantities VIP players receive
• Anti-Abuse Protection: One-time redemption system prevents multiple claims
• Personalized Welcome Messages: Greet players with custom messages when they connect
• Easy Administration: Simple configuration through JSON schema

Features:

• Permission-based access control
• One-time redemption functionality per server
• Customizable welcome messages
• Automated item delivery system
• Quality and quantity settings for each item

How It Works

1. Add commands to the Dynamic Commands list in the config form
2. The cronjob syncs your configuration every 15 minutes
3. Commands are created, updated, or removed to match your config
4. Permissions are auto-created when referenced

Argument Types

Example: Teleport to Player

Example: Give Item

Example: Admin Command with Permission

Placeholders

Dynamic CronJob Manager: Automated Game Server Command Scheduler

🎥 SETUP TUTORIAL
► Watch the Complete Guide
Learn how to set up and configure dynamic cronjobs

• Dynamic Updates: The module's cronJobGenerator cronjob automatically checks for and adapts to changes in the user configuration. This ensures that any modifications to commands or schedules are applied dynamically.
• Cron Syntax Validation: The module validates the syntax of cron expressions. If an invalid expression is provided, that specific cronjob will be skipped, preventing errors and ensuring only valid schedules are applied. For assistance with cron syntax, you can use a tool like crontab.guru.
• Command Sequencing: You can define multiple commands within a single cronjob entry, separated by semicolons. These commands will be executed sequentially according to the defined schedule.
• Game Server Specificity: It is crucial to install the latest version of this module and create a separate copy for each game server. This ensures that cronjobs are executed on the intended server and avoids unintended cross-server execution.
• Automated Management: The module handles the creation, updating, and cleanup of cronjobs. It removes any cronjobs that are no longer present in the configuration, maintaining a clean and accurate schedule.
• Internal Synchronization: To ensure proper synchronization of cron schedules, the module may perform internal operations to update its configuration. This process is automated and does not require manual intervention from the user.

Dynamic CronJob Manager: Automated Game Server Command Scheduler

🎥 SETUP TUTORIAL
► Watch the Complete Guide
Learn how to set up and configure dynamic cronjobs

• Dynamic Updates: The module's cronJobGenerator cronjob automatically checks for and adapts to changes in the user configuration. This ensures that any modifications to commands or schedules are applied dynamically.
• Cron Syntax Validation: The module validates the syntax of cron expressions. If an invalid expression is provided, that specific cronjob will be skipped, preventing errors and ensuring only valid schedules are applied. For assistance with cron syntax, you can use a tool like crontab.guru.
• Command Sequencing: You can define multiple commands within a single cronjob entry, separated by semicolons. These commands will be executed sequentially according to the defined schedule.
• Game Server Specificity: It is crucial to install the latest version of this module and create a separate copy for each game server. This ensures that cronjobs are executed on the intended server and avoids unintended cross-server execution.
• Automated Management: The module handles the creation, updating, and cleanup of cronjobs. It removes any cronjobs that are no longer present in the configuration, maintaining a clean and accurate schedule.
• Internal Synchronization: To ensure proper synchronization of cron schedules, the module may perform internal operations to update its configuration. This process is automated and does not require manual intervention from the user.

• Automatically identifies each player's VIP tier level based on their permissions
• Players receive the highest tier rewards they qualify for
• No complex commands - just type /vipkit and get your rewards

• Support for unlimited VIP tiers (Bronze, Silver, Gold, Platinum, Diamond, etc.)
• Easy to add new tiers without code modifications
• Count-based permission system grows with your community

• One-time redemption per tier per server
• Prevents multiple claims and exploits
• Secure variable tracking system

• Configure unique item packages for each VIP tier
• Set item quantities, qualities, and types per tier
• Personalized welcome messages with dynamic tier names
• Professional admin interface for easy management

1. Configure VIP Tiers - Set up your tier structure (Level 1 = Bronze, Level 2 = Silver, etc.)
2. Assign Permissions - Give players VIP_ACCESS permission with count values matching their tier
3. Customize Items - Configure unique item packages for each tier level

Referral Program

What it does

• Referrers run /refcode to generate or view a shareable code.
• New players run /referral <code> during the configured referral window.
• Referees can receive an immediate welcome currency bonus.
• Referrers are paid once the referee reaches the configured playtime threshold.
• Rewards can be currency or items, with VIP reward multipliers for donor/supporter roles.
• Daily and lifetime caps help prevent referral farming.
• Admin commands let staff force-link or unlink referrals when needed.
• /refstats and /reftop make the program visible to players.

Verified dashboard chat flow

1. Bot1_rafo2g0 runs !refcode and receives referral code N4A46Q.
2. Bot1_rabo2g0 runs !referral N4A46Q.
3. The referee receives the 17 currency welcome bonus.
4. The payout sweep completes the referral and sends the referrer a chat PM for 123 currency.
5. !refstats shows the referrer has 1 paid referral and 123 currency earned.
6. !refstats for the referee shows they were referred by Bot1_rafo2g0.
7. !reftop shows the referrer at the top of the leaderboard.

Player commands

Staff commands

Install configuration

User config fields

• prizeIsCurrency: pay referrers currency when enabled; use item rewards when disabled.
• referrerCurrencyReward: currency paid to the referrer after the referee qualifies.
• refereeCurrencyReward: immediate welcome currency bonus paid to the referred player.
• items: item prize pool used when prizeIsCurrency is false.
• playtimeThresholdMinutes: minutes the referee must play before the referrer is paid.
• referralWindowHours: how long after first connect a player can still claim a referral code.
• maxReferralsPerDay: daily cap for successful referrals a player can earn.
• maxReferralsLifetime: lifetime cap for paid referrals a player can earn.

System config shown during install

Verified sandbox result

• Referral code generated: N4A46Q
• Referral link status: paid
• Referee welcome bonus: 17 currency
• Referrer reward: 123 currency
• referralsTotal: 1
• referralsPaid: 1
• referralsRejected: 0
• currencyEarned: 123

Readable variable evidence

• Permission-based access: Only players with the 'Whitelist Access' permission can join the server.
• Customizable kick message: Set what rejected players see when attempting to connect.
• Role integration: Works seamlessly with Takaro's role system for easy management.
• Global or per-server: Apply whitelist roles to specific servers or globally across all servers.

• Simple setup - just assign permissions to roles
• No complex configuration needed
• Works across all supported game types
• Instantly denies access to unauthorized players

1. Install the module on your server
2. Configure the kick message
3. Create or edit roles with the 'Whitelist Access' permission
4. Assign roles to players either globally or per server

• Private servers for friends and communities
• Premium/VIP game servers
• Testing environments
• Scheduled events with limited participation
• Temporarily restricting access during maintenance

Limon_triviaTime: Interactive Trivia Game System

Key Benefits:

• Dual Question Sources: Choose between Open Trivia Database API or custom questions
• Rich Category Selection: Access to 20+ categories from the API including General Knowledge, Science, Sports, History, and more
• Difficulty Control: Easy, Medium, and Hard difficulty levels
• Flexible Question Types: Support for True/False and Multiple Choice questions
• Flexible Reward System: Choose between currency or item rewards for winners
• Automated Scheduling: Set trivia events to run at specified intervals
• Player Engagement Tool: Keeps your community active and entertained
• Simple Answer Validation: Easy command-based answer submission system

Features:

• Open Trivia Database API integration with 4000+ verified questions
• Configurable question database with pre-populated examples as fallback
• Dual reward types (currency or items)
• Customizable item quality and quantity settings
• Permission-based participation control
• Automated trivia scheduling with cron jobs
• Real-time feedback on incorrect answers
• Server-wide announcements for winners
• HTML entity decoding for proper question display
• Session token support to prevent duplicate questions

• 8-Ball Command: Players can use a designated command (default: 8ball) to ask the Magic 8-Ball a question.
• Random Responses: The module provides a list of configurable responses. When the command is used, the module selects a random response from this list and displays it to the player.
• Configurable Output: The module allows server administrators to choose whether the 8-Ball's response is sent as a global server message or as a private message (PM) to the player.
• Customizable Responses: The list of 8-Ball responses can be fully customized, allowing server administrators to tailor the module to their server's theme or language.
• Permission Control: Usage of the 8-Ball command can be restricted using a configurable permission.

1. Configuration:
   • sendMessage: Choose whether the 8-Ball's response is sent as a serverMessage (to all players) or a playerPM (private message to the player who used the command).
   • responses: Edit the array of strings to customize the 8-Ball's possible answers. Ensure there is at least one response.
2. Permissions: Assign the MAGIC_8BALL_USE permission to the player groups or individuals who should be able to use the 8ball command.
3. In-Game Usage: Players use the /8ball command (or the configured trigger) followed by their question. The 8-Ball's response will be displayed according to the sendMessage configuration.

• Ensure there is at least one response in the responses configuration to avoid errors.
• Customize the responses to fit your server's style and language.
• Use the permission system to control who can use the command.

• Complete Blackjack Experience: Play the classic casino card game directly in your game chat with simple commands
• Economy Integration: Connect with Takaro's economy system - bet, win, and lose in-game currency

• /bjplay - Start a new game with your bet

• /bjstatus - Check your current game status

• /bjhit - Draw another card

• /bjstand - End your turn

• Clear Visual Interface: Card values and suits display with intuitive symbols
• Real-time Information: See your hand total, the dealer's visible card, and your current balance
• In-game Betting: Place wagers directly from your in-game currency balance
• Standard Casino Rules: Beat the dealer without going over 21
• Multiple Card Draws: Take as many cards as you dare with the /bjhit command
• Bust Detection: Immediate feedback when you go over 21 and lose your bet
• Automated Dealer: When you stand, the dealer follows standard Blackjack rules
• Transparent Results: See both hands with their totals when the game concludes
• Automatic Currency Management: Winnings are instantly credited to your account

• Adding entertainment options to your server
• Providing fun ways for players to use in-game currency
• Increasing player engagement with mini-games
• Creating a social casino experience in your game

• Takaro's economy system must be enabled

Key Functionality

• Game Hosting: Players can create new Hangman games by specifying a secret word or phrase for others to guess.
• Player Participation: Multiple players can join ongoing games, creating a social, competitive experience.
• Letter Guessing: Players take turns guessing letters or attempting the full word, with visual feedback after each guess.
• Progressive Difficulty: Wrong guesses accumulate toward a maximum limit, creating tension as the game progresses.
• Economic Integration: Full support for your server's economy with:
  • Hosting fees for creating games
  • Entry fees for joining games
  • Optional costs per guess
  • Currency rewards for winners
• Game Management: Commands for checking game status, revealing answers, or canceling games as needed.

How to Use

1. Configuration:
   • maxWrongGuesses: Set the number of incorrect guesses allowed before the game ends.
   • minWordLength and maxWordLength: Define valid word length parameters.
   • entryFee: Cost for players to join a game.
   • hostingFee: Cost to start a new game.
   • guessPrice: Optional cost per letter guess.
   • winReward: Currency awarded to successful players.
   • hostReward: Currency awarded to hosts when no player solves the puzzle.
   • gameTimeout: Maximum duration a game can run.
2. Commands:
   • /hangmanstart [word]: Create a new game or start a waiting game.
   • /hangmanjoin: Join an existing game that hasn't started.
   • /hangmanguess [letter/word]: Make a guess during an active game.
   • /hangmanstatus: Check the current state of the game.
   • /hangmanreveal: Reveal the answer and end the game (host/admin only).
   • /hangmancancel: Cancel the current game (host/admin only).
3. Permissions:
   • HANGMAN_HOST: Allows players to create and host games.
   • HANGMAN_PLAY: Allows players to join games and make guesses.
   • HANGMAN_ADMIN: Grants administrative control over all games.

Game Flow

1. A player with hosting permissions creates a new game with a secret word.
2. Other players join the waiting game.
3. The host starts the game when enough players have joined.
4. Players take turns guessing letters or the complete word.
5. With each guess, the game displays the current word state and remaining guesses.
6. The game ends when:
   • A player correctly guesses the word (player wins the pot)
   • Players reach the maximum wrong guesses (host wins the pot)
   • An admin or host cancels or reveals the game

Important Considerations

• Configuring appropriate fees and rewards helps balance your server economy.
• The word validation ensures fair gameplay (letters and spaces only).
• Players cannot join games that have already started.
• The host cannot participate in guessing since they know the word.
• Currency features require the economy system to be enabled.

Roulette Module: Casino-Style Gambling for Your Game Server

Key Features

• Authentic Gameplay: Simple, realistic roulette with true-to-life odds and mechanics.
• Multiple Bet Types: Various betting options with different risk/reward ratios.
• Accurate Validation: Color and number validation matching a real roulette wheel.
• Statistics Tracking: Monitor your gambling performance over time.
• Configurable Settings: Adjustable house edge and betting limits.
• Optional Cooldown: Set time between spins to prevent excessive gambling.
• VIP Permissions: Special access for VIP players to higher betting limits.
• Admin Controls: Commands to view and reset player statistics.

How to Play

• /roulette red 100 - Bet 100 on any red number
• /roulette black 200 - Bet 200 on any black number
• /roulette even 150 - Bet 150 on even numbers
• /roulette odd 150 - Bet 150 on odd numbers
• /roulette high 100 - Bet 100 on high numbers (19-36)
• /roulette low 100 - Bet 100 on low numbers (1-18)
• /roulette 17 200 - Bet 200 specifically on number 17
• /roulette red17 300 - Bet 300 specifically on red 17 (higher payout)
• /roulettestats - View your personal roulette statistics
• /rouletterules - Display roulette rules and payouts

Payouts

• Red/Black: 1:1
• Even/Odd: 1:1
• High/Low: 1:1
• Single Number: 35:1
• Color+Number: 70:1

Configuration Options

• Minimum bet amount
• Maximum bet amount
• House edge percentage
• Cooldown time between spins

• Authentic Casino Experience: Three-reel slot machine with multiple symbols and varied payouts
• Visual Animation: Progressive reel reveals with suspenseful animations
• Big Win Announcements: Server-wide jackpot notifications for big winners
• Statistics Tracking: Detailed personal gambling stats for each player

• /slots [amount] - Place a bet and spin the slot machine
• /slotsstats - View your personal gambling statistics
• /slotsrules - Check payouts, rules and betting information
• /slotsreset [player] - Admin command to reset player statistics

• Three matching symbols (Three sevens: 25x your bet!)
• Three bells: 10x your bet
• Three plums: 6x your bet
• Three oranges: 4x your bet
• Three lemons: 3x your bet
• Three cherries: 2x your bet
• Any combination ending with seven: 1.5x your bet

• Games played, wins, losses, and total currency wagered
• Win rate percentage calculation

• minimumBet: Lowest possible wager amount
• maximumBet: Highest possible wager amount
• houseEdge: Percentage profit margin for the server

• SLOTS_PLAY: Basic permission to use the slot machine
• SLOTS_HIGHER_LIMITS: VIP permission allowing higher maximum bets
• SLOTS_ADMIN: Administrative access to reset stats and manage the module

Limon_triviaTime: Interactive Trivia Game System

Key Benefits:

• Customizable Question Library: Build your own collection of trivia questions and answers
• Flexible Reward System: Choose between currency or item rewards for winners
• Automated Scheduling: Set trivia events to run at specified intervals
• Player Engagement Tool: Keeps your community active and entertained
• Simple Answer Validation: Easy command-based answer submission system

Features:

• Configurable question database with pre-populated examples
• Dual reward types (currency or items)
• Customizable item quality and quantity settings
• Permission-based participation control
• Automated trivia scheduling with cron jobs
• Real-time feedback on incorrect answers
• Server-wide announcements for winners

Dynamic Buff Manager

Features

• ✅ Unlimited buff packages (add as many as you need)
• ✅ Role-based access control per package
• ✅ Time-based expiration system
• ✅ Auto-apply buffs on player connect
• ✅ Currency costs and cooldowns per package
• ✅ Automatic maintenance to keep buffs active

Quick Start

1. Add a Buff Package
   • Click "Add Item" under Buff Packages
   • Set Command Name (e.g., "vipbuff")
   • Set Display Name (e.g., "VIP Speed Package")
   • Add buff names from your XML (e.g., "SpeedbuffVip")
2. Get Role ID
   • Go to Settings → Roles in Takaro
   • Click on the role you want (e.g., "VIP")
   • Look at the browser address bar: https://your-takaro.com/settings/roles/743b9623-ad09-4cf2-86c0-3d7faed57a88
   • Copy the UUID from the URL (the part after /roles/)
   • Example: 743b9623-ad09-4cf2-86c0-3d7faed57a88
   • Paste into "Required Role ID" field
   • Leave empty to allow everyone
3. Configure Duration
   • Set how long buffs should last in minutes
   • 0 = never expires (maintenance keeps them active forever)
   • 60 = expires after 1 hour
4. Save and Install

Configuration Fields

Buff Package Settings

• Command Name: What players type (creates /getbuff commandName)
• Display Name: Friendly name in messages
• Description: Explanation of what the package does
• Buff Names: Array of buff codes from your buffs.xml
• Required Role ID: UUID of the role (copy from browser URL). Empty = everyone
• Duration (Minutes): Expiration time. 0 = never expires
• Auto-Apply on Connect: Give buff automatically when player joins
• Currency Cost: Price to use the command
• Cooldown (Seconds): Per-player cooldown

Examples

• Command: "vipbuff"
• Buffs: ["SpeedbuffVip", "ExpBuffVip"]
• Role: 743b9623-ad09-4cf2-86c0-3d7faed57a88
• Duration: 0 (permanent)
• Auto-apply: Yes
• Cost: 0
• Cooldown: 0

• Command: "donorbuff"
• Buffs: ["SuperSpeed", "SuperJump"]
• Role: abc-123-donor-role-id
• Duration: 120 (2 hours)
• Auto-apply: No
• Cost: 1000
• Cooldown: 3600 (1 hour)

How It Works

1. On Player Connect: Module checks all packages with auto-apply enabled and matching roles
2. Manual Command: Player uses /getbuff to activate a specific package
3. Expiration Tracking: Module stores expiration timestamp per player per package
4. Maintenance: Cronjob re-applies non-expired buffs every 15 minutes

Troubleshooting

• Check buff names match your buffs.xml exactly (case-sensitive)
• Verify role ID is correct UUID from browser URL
• Check player actually has the role assigned
• Look at module execution events for detailed logs

• Check duration - may be expiring
• Verify maintenance cronjob is enabled
• Check game server console for buff command errors

• Verify economy is enabled in Takaro settings
• Check currency cost is set correctly per package

• Daily Rewards: Players can claim a base reward that increases with their daily login streak.
• Streak Tracking: The module tracks players' consecutive daily logins, encouraging consistent engagement.
• Milestone Rewards: Configurable bonus rewards are granted to players for reaching specific streak milestones, providing long-term goals.
• Random Item Rewards: Players have a chance to receive random in-game items as part of their daily reward, with configurable item chances and a streak-based multiplier.
• Customizable Rewards: The base reward amount, maximum streak, milestone rewards, possible items, and item chances are all configurable.
• Permission System: Supports permissions to control who can claim rewards and to allow for reward multipliers (e.g., for donors).
• Player Notifications: Provides in-game messages to inform players about their streak, next claim time, milestones, and rewards.

• Multiple Economic Sectors: Configure various industry sectors (Technology, Healthcare, Energy, etc.) each with their own market dynamics.
• Realistic Stock Behavior: Stocks have configurable volatility, sector-based pricing, and react differently to market events.
• Dynamic Market Events: Random or admin-triggered events like "Global Pandemic" or "Tech Boom" impact different sectors in realistic ways.

• Buy & Sell Shares: Players can purchase stocks and sell them later for profit or loss.
• Transaction Fees: Configurable fee percentage on all trades creates a realistic market economy.
• VIP Benefits: Special permissions for designated "Stock Brokers" who receive fee discounts.

• Portfolio Tracking: Players can view their holdings, average purchase prices, and current profit/loss.
• Transaction History: System tracks all buy/sell transactions for each player.
• Summary Statistics: See overall portfolio performance and value across all holdings.

• Detailed Stock Info: Players can research specific stocks, including risk levels and sector trends.
• Industry Filters: View stocks by specific sectors to better understand market segments.
• Market Alerts: Server-wide notifications for significant price changes keep players engaged.

• Sectors & Stocks: Define your own market sectors and individual stocks with customizable starting prices and volatility.
• Market Events: Create unique events with specific sector impacts to drive market dynamics.
• Transaction Settings: Configure fee percentages, VIP discounts, and alert thresholds.
• Event Frequency: Control how often random market events occur and how long they last.

• /markets [industry] - View all stocks or filter by industry
• /stockinfo [ticker] - Get detailed information about a specific stock
• /buystock <ticker> <amount> - Purchase shares of a stock
• /sellstock <ticker> <amount> - Sell shares from your portfolio
• /stockportfolio - View your current holdings and performance
• /triggerevent [event] - Admin command to trigger specific market events

Playtime Buff Rewards

What it does

• Hourly online-player rewards: The grant-playtime-rewards cronjob finds online players and grants one random configured reward to each player.
• 7 Days to Die buff support: buffCommandTemplate defaults to buffplayer {playerName} {buffName}, with placeholders for {playerName}, {playerId}, {gameId}, and {buffName}.
• Mixed reward pools: Combine buff rewards, generic console commands, and Takaro currency grants in the same weighted pool.
• Staff testing command: /grantbuff <player> <buffName> is guarded by PLAYTIME_BUFF_ADMIN for manual buff grants.
• Optional announcements: Broadcast configurable reward messages with placeholders like {playerName}, {buffName}, {rewardName}, and {amount}.

Example reward setup

{
  "buffCommandTemplate": "buffplayer {playerName} {buffName}",
  "buffRewards": [
    { "buffName": "WellFed", "weight": 2, "enabled": true },
    { "buffName": "MegaCrush", "weight": 1, "enabled": true }
  ],
  "commandRewards": [
    { "name": "Ammo bundle", "command": "give {playerName} ammo762mmBulletBall 30", "weight": 1 }
  ],
  "currencyRewards": [
    { "name": "Pocket money", "amount": 25, "weight": 1 }
  ]
}

Commands

Permissions

Configuration

• buffCommandTemplate: Console command template for buff grants. Defaults to buffplayer {playerName} {buffName}.
• buffRewards: Weighted list of buff names eligible for the hourly reward cycle.
• commandRewards: Weighted list of generic console commands for item, ammo, food, or custom rewards.
• currencyRewards: Weighted list of Takaro currency grants.
• announceRewards: Toggle broadcast messages for reward grants.
• defaultRewardMessage: Fallback announcement when a reward does not define its own message.

Verified sandbox result

• grant-playtime-rewards found Bot1_BuffTester online.
• Buff reward path executed say [PlaytimeBuff] Bot1_BuffTester received WellFed with 200 OK from the game-server command API.
• Announcement path broadcast Bot1_BuffTester got the WellFed buff reward.
• Currency reward path called add-currency with 25 and emitted a currency-added event.
• The cronjob result logged success: true and granted 1 reward(s) to 1 online player(s).

How it Works

• A cronjob runs periodically (default: every 10 minutes)
• All online players receive currency silently each time it runs
• Simple and straightforward

Configuration

• currencyReward: Amount of currency given each time the cronjob runs (default: 10)

System Config

• Cronjob frequency: Configure how often the cronjob runs (default: */10 * * * * = every 10 minutes)

Permissions

• PLAYTIME_CURRENCY_OVERRIDE: Override currency amount for specific players/roles (uses count value)

Example

• Cronjob runs every 10 minutes
• currencyReward = 17
• Result: Players get 17 currency every 10 minutes = 102 currency per hour

• Timed Rewards: Configure how often players receive rewards while online. The reward interval and cronjob schedule should be synchronized for best results (e.g., set both to 5 minutes).
• Currency Rewards: Automatically grant in-game currency to active players based on your configuration.
• Random Item Rewards: Set up a customizable chance to give random items from your configured list.

• Role-Based Rewards: Use permission overrides to give VIP players increased rewards or higher chances for items.
• Playtime Tracking: The included /playtime command lets players check their current session time, server playtime, and community-wide playtime statistics.
• Customizable Messages: Personalize the reward notifications with dynamic placeholders for playtime, currency, and items.

• rewardInterval: Set how frequently rewards are given (should match cronjob schedule)
• baseReward: Amount of currency to award each interval
• possibleItems: List of items that can be randomly awarded
• itemChance: Percentage chance (1-100) to receive an item
• rewardMessage: Customize notification with placeholders {minutes}, {currency}, {item}

• PLAYTIME_REWARD_OVERRIDE: Customize currency rewards for specific roles
• PLAYTIME_ITEM_CHANCE_OVERRIDE: Modify item drop chances for specific roles

Stock Market: A Dynamic Virtual Trading System

🎥 SETUP TUTORIAL
► Watch the Complete Guide
Learn how to set up and use the Stock Market module

• Multiple Economic Sectors: Configure various industry sectors (Resource Extraction, Manufacturing, Defense, etc.) each with their own market dynamics.
• Realistic Stock Behavior: Stocks have configurable volatility, sector-based pricing, and react differently to market events.
• Dynamic Market Events: Random or admin-triggered events like "Horde Night Approaching" or "Societal Collapse Setback" impact different sectors in realistic ways.

• Buy & Sell Shares: Players can purchase stocks and sell them later for profit or loss.
• Transaction Fees: Configurable fee percentage on all trades creates a realistic market economy.
• VIP Benefits: Special permissions for designated "Stock Brokers" who receive fee discounts.

• Portfolio Tracking: Players can view their holdings, average purchase prices, and current profit/loss.
• Transaction History: System tracks all buy/sell transactions for each player.
• Summary Statistics: See overall portfolio performance and value across all holdings.

• Detailed Stock Info: Players can research specific stocks, including risk levels and sector trends.
• Industry Filters: View stocks by specific sectors to better understand market segments.
• Market Alerts: Server-wide notifications for significant price changes keep players engaged.

• Sectors & Stocks: Define your own market sectors and individual stocks with customizable starting prices and volatility.
• Market Events: Create unique events with specific sector impacts to drive market dynamics.
• Transaction Settings: Configure fee percentages, VIP discounts, and alert thresholds.
• Event Frequency: Control how often random market events occur and how long they last.

• /markets [industry] - View all stocks or filter by industry
• /stockinfo [ticker] - Get detailed information about a specific stock
• /buystock <ticker> <amount> - Purchase shares of a stock
• /sellstock <ticker> <amount> - Sell shares from your portfolio
• /stockportfolio - View your current holdings and performance
• /triggerevent [event] - Admin command to trigger specific market events

Zombie Racing

What it does

• Configurable racers: Define racers as Name; Odds entries. The default setup uses zombies, but the labels and entrants are fully configurable.
• Currency betting: Players use /racebet <racer> <amount> to place or replace their bet for the next race.
• Race state tracking: Current bets, last results, race number, and player stats are stored in Takaro variables.
• Scheduled or manual races: A cronjob can run races every two hours, and admins can manually trigger one with /startrace.
• Player stats and leaderboard: Players can check their own race stats, last race result, current bets, and top bettors.
• Safer completion logic: The module uses locking/recovery state to avoid dropped bets, double payouts, and duplicate stat updates.

Commands

Permissions

Configuration

• minBet: Minimum currency amount for a bet.
• maxBet: Maximum currency amount for a bet.
• raceName: Display name used in messages, e.g. Zombie Race or Paper Horse Derby.
• racerTypeLabel: Singular label used in command help, e.g. zombie or horse.
• racerTypePluralLabel: Plural label used in output, e.g. zombies or horses.
• entrants: List of racers in Name; Odds format.

{
  "minBet": 10,
  "maxBet": 250,
  "raceName": "Paper Horse Derby",
  "racerTypeLabel": "horse",
  "racerTypePluralLabel": "horses",
  "entrants": ["Comet; 2", "Thunder; 3", "Pickle; 4", "Mango; 5"]
}

Verified sandbox result

1. Imported and installed the module on koji-paper-1.
2. Configured it as Paper Horse Derby with custom horse labels and entrants.
3. Spawned Bot1_RaceTester and confirmed the player was online in both Minecraft and Takaro.
4. Granted RACING_BET and RACING_ADMIN to the player for the test.
5. Added test currency, then ran /racers, /racebet Comet 50, /myracebets, /nextrace, /startrace, /lastrace, and /racestats through Takaro's command trigger path.
6. Confirmed Takaro deducted 50 currency for the bet, stored the bet in zombie_racing_state_v1, completed race #1, advanced to race #2, and persisted player stats in zombie_racing_stats_v1.

• Bet: Bot1_RaceTester wagered 50 on Comet at 2:1 odds.
• Race winner: Thunder.
• Final standings: Thunder, Pickle, Mango, Comet.
• Player stats: 1 bet, 50 wagered, 0 wins, 1 loss, favorite racer Comet.

• Two-Way Chat Relay: Forward messages between your game and Discord in real-time. Improve player interaction and build a stronger community.
• Customizable Channel Filtering: Control exactly which chat channels get relayed to Discord:
  • Global chat for server-wide messages
  • Optional Party/Team chat integration
  • Optional Friends chat integration
• Player Connection/Disconnection Notifications: Get automated Discord messages when players join or leave your server.

• Advanced Filtering Options:
  • Command Filtering: Prevent in-game command messages (e.g., /ban) from cluttering your Discord.
  • System Message Filtering: Keep your Discord clean by blocking system (non-player) messages.

• Global chat appears normally
• Party chat is prefixed with [Party]
• Friends chat is prefixed with [Friends]

• Track player connections with links to Steam profiles
• Monitor server status events
• Support for 7 Days to Die bloodmoon countdown tracking

• sendPlayerConnected: Enable player connect notifications
• sendPlayerDisconnected: Enable player disconnect notifications
• onlyGlobalChat: Restrict to global chat only (can be fine-tuned below)
• includePartyChat: Include party/team chat in Discord (overrides onlyGlobalChat restriction)
• includeFriendsChat: Include friends chat in Discord (overrides onlyGlobalChat restriction)
• filterCommands: Filter out in-game command messages
• filterSystemMessages: Filter out system messages
• useMonitoring: Enable a dedicated monitoring channel for all messages
• showPlayerDetails: Show Steam profile and Takaro profile links in notifications

• Communities that want to bridge in-game and Discord chat
• Servers with active Discord communities
• Admins who want to monitor server activity from Discord
• Multi-server networks with centralized Discord channels
• 7 Days to Die servers wanting to share bloodmoon information

Limon_chatbridge: Discord Chat Integration for Your Game Server

Key Features

• Two-Way Chat Relay: Forward messages between your game and Discord in real-time. Improve player interaction and build a stronger community.
• Player Connection/Disconnection Notifications: Optionally send automated Discord messages when players join or leave your server.
• Advanced Filtering Options:
  • Global Chat Only: Restrict messages to your game's global chat channel, excluding team chat and private messages.
  • Command Filtering: Prevent in-game command messages (e.g., /ban) from cluttering your Discord.
  • System Message Filtering: Keep your Discord clean by blocking system (non-player) messages.
• Dedicated Monitoring Channel (Optional): Create a separate Discord channel for all server activity, including chat, commands, and logs. Ideal for moderation and debugging.
• Easy Configuration: Customize settings quickly and easily with a straightforward configuration schema.

Configuration Options

• sendPlayerConnected: (true/false, default: true) Enable player connect notifications.
• sendPlayerDisconnected: (true/false, default: true) Enable player disconnect notifications.
• onlyGlobalChat: (true/false, default: true) Restrict to global chat only.
• filterCommands: (true/false, default: false) Filter out in-game command messages.
• filterSystemMessages: (true/false, default: false) Filter out system messages.
• useMonitoring: (true/false, default: false) Enable a dedicated monitoring channel.
• monitoringChannelId: (string) Discord channel ID for monitoring (required if useMonitoring is enabled).

Hooks

• PlayerDisconnected / PlayerConnected: Handles player join/leave notifications.
• DiscordToGame: Relays messages from your Discord server to the game.
• GameToDiscord: Relays in-game chat messages to Discord, applying all configured filters.

Key Functionality

• Two-Way Translation: Translates chat messages between players speaking different languages.
• Automatic Translation: Can automatically translate messages based on players' configured language preferences.
• On-Demand Translation: Players can translate specific messages or recent messages from other players using commands.
• Configurable Languages: Server administrators can define the list of supported languages.
• Google Translate Integration: Leverages the Google Cloud Translation API for accurate and comprehensive language support.
• Permission Control: Granular permissions allow administrators to control who can use translation features.

How to Use

1. Configuration:
   • googleApiKey: (Required) Enter your Google Cloud API key with access to the Cloud Translation API.
   • maxMessageLength: Set the maximum character length for messages to be translated (to manage API usage/costs). Default: 500.
   • defaultLanguage: Set the default language code (ISO 639-1) for translations when a player hasn't specified their preference. Default: en.
   • supportedLanguages: Define an array of ISO 639-1 language codes (e.g., ["en", "es", "fr"]) for the languages supported by the module.
   • commandPrefixes: (Optional) An array of prefixes that are used to identify commands. Messages that start with these prefixes will not be translated. Default: ["/"]
2. Permissions:
   • TRANSLATE_PERMISSION: Grants players access to basic translation commands (/translate, /setlanguage, /toggletranslation, /translateme).
   • TRANSLATE_ADMIN: Allows administrators to set language preferences for other players (/setplayerlanguage).
   • AUTO_TRANSLATE_PERMISSION: Allows players to receive automatically translated messages.
3. In-Game Usage:
   • /translate <language> "text": Translates the provided text into the specified language and sends it to the global chat.
   • /setlanguage <code>: Sets the player's preferred language for receiving translations (e.g., /setlanguage es).
   • /toggletranslation on/off: Enables or disables automatic translation for the player.
   • /translateme <player> [count]: Translates the last count messages from the specified player and sends them to the user via DM. If count is omitted, translates the last message.
   • /setplayerlanguage <player> <language>: (Admin only) Sets the preferred language for another player.

Important Considerations

• Google Cloud API Key: A valid Google Cloud API key with the Cloud Translation API enabled is essential for this module to function.
• Language Codes: Use correct ISO 639-1 two-letter language codes (e.g., 'en', 'es', 'fr'). Refer to the Google Cloud Translation API documentation for a full list.
• Permissions Management: Carefully manage the module's permissions to control access to translation features.
• Message Length: Be mindful of the maxMessageLength setting to avoid excessive API usage and potential costs.
• Error Handling: The module includes error handling, but it's important to monitor server logs for any translation-related issues.

Key Functionality

• Vehicle Retrieval:
  • /bike: Teleports the player's min-bike to their location (if nearby).
  • /4x4: Teleports the player's 4x4 to their location (if nearby).
  • /gyro: Teleports the player's gyrocopter to their location (if nearby).
  • /motorcycle: Teleports the player's motorcycle to their location (if nearby).
  • /bicycle: Teleports the player's bicycle to their location (if nearby).
  • /drone: Teleports the player's drone to their location (if nearby).
• Teleportation:
  • /home: Teleports the player to their set home location (bedroll).
  • /visit <playerTarget>: Allows a player to teleport to another player on the server, provided they are friends in-game and the target player is online.
• Player Status:
  • /debuff: Removes common debuffs from the player (broken bones, sprains, etc.).
• Graphics Settings:
  • /gfxon: Enables low graphics mode for improved performance.
  • /gfxoff: Disables low graphics mode, restoring normal graphics.
  • /gfx: Toggles gfx mode.
• Account Linking
  • /link Shows the player how to link their account to the server.

How to Use

1. Installation: Install the module on your Takaro instance.
2. PrismaCore Requirement: Ensure that PrismaCore is installed and configured on your 7 Days to Die server. This module relies on PrismaCore's functionality for vehicle retrieval.
3. Permissions: Grant the appropriate permissions to the player groups or individuals who should have access to these commands: * inGameCommands: General permission for most of the module's commands. * HOME_PERMISSION: Permission to use the /home command. * VISIT_PERMISSION: Permission to use the /visit command.
4. In-Game Usage: Players can use the commands as described in the "Key Functionality" section.

Important Considerations

• PrismaCore Dependency: This module is tightly integrated with PrismaCore. It will not function correctly without PrismaCore being present on the server.
• Vehicle Proximity: The vehicle retrieval commands (/bike, /4x4, /gyro, etc.) typically require the player to be within a certain proximity of their vehicle for the command to work. The exact range is defined by PrismaCore.
• Home Location: The /home command requires players to have a valid bedroll set as their home location.
• Friend System: The /visit command relies on 7 Days to Die's in-game friend system. Players must be friends with the target player to teleport to them.
• Graphics Settings: The /gfxon and /gfxoff commands may not be effective in all game settings or configurations. Their functionality depends on how the game handles graphics settings.
• Permission Management: Use the provided permissions to control access to the module's commands.

Trevor_RegionResetRandomiser: Map Region Reset Manager

Key Benefits:

• Reset Regions: Keeps the game world fresh with renewed resources in selected areas
• Performance Optimization: Targeted resets help maintain server performance
• Balanced Gameplay: Prevents complete resource depletion while preserving player builds
• Selective Regeneration: Only resets a configurable subset of regions
• Administrator Control: Allows manual triggering via Discord commands

Features:

• Configurable number of regions to reset at each interval
• Automatic daily region reset via cron job scheduling
• Manual reset capability through Discord commands
• Permission-based control with authorized user list
• Custom activation phrase for manual triggering
• Detailed debug logging to Discord channels
• Smart region selection algorithm
• Error handling for various edge cases
• Unicode support for international player names
• Timestamp logging for audit trails

Module Importer: Cross-Server Module Configuration Replication

🎥 SETUP TUTORIAL
► Watch the Complete Guide
Learn how to replicate module configurations between servers

Key Benefits:

• Time-Saving Setup: Instantly replicate complex module configurations instead of manual setup
• Configuration Consistency: Ensure identical module setups across multiple servers
• Template Server Approach: Use one server as a master template for others
• Exact Configuration Copying: Preserves both system and user configurations precisely
• Administrative Control: Manual execution prevents accidental triggers

Features:

• Manual execution through module builder for controlled deployment
• Copies all installed modules from specified source server
• Preserves exact user and system configurations
• Updates existing modules with source server settings
• Installs new modules that don't exist on target server
• Detailed logging of installation, update, and skip operations
• Source server identification via gameserver ID from dashboard URL
• Built specifically for administrative use outside of gameplay
• Progress tracking with comprehensive operation reporting

Important Notes:

• Best used between servers running the same game type
• Cross-game compatibility may cause issues with game-specific configurations
• Requires administrator knowledge of module management
• Manual trigger recommended for careful timing and control

MAD_CPMStaffCommands Module

Key Functionality

• Enable Better Blood Moons: The /BBM command automatically sets the necessary server commands to activate 'Better Blood Moons'. It also provides a reminder about a recommended XML setting change.
• Disable Better Blood Moons: The /BBMoff command reverts the server settings to their default, effectively disabling 'Better Blood Moons'. It also provides a reminder about reverting the XML setting if changed.
• Simplified Management: This module eliminates the need for manual editing of the CPMsettings.xml file, reducing the risk of errors and making it easier to switch between default and enhanced Blood Moon settings.
• Permission Control: Access to the /BBM and /BBMoff commands is controlled by a dedicated permission.

How to Use

1. Installation: Install the module on your Takaro instance.
2. Configuration: (Optional) No configuration is typically needed for this module.
3. Permissions: Grant the BETTER_BLOOD_MOONS permission to the user roles or players who should be able to use the /BBM and /BBMoff commands.
4. In-Game Usage:
   • /BBM: Executes the commands to enable 'Better Blood Moons' and displays a recommended XML setting.
   • /BBMoff: Executes the commands to disable 'Better Blood Moons' and displays a reminder about the XML setting.

Important Considerations

• CPM Mod Dependency: This module is designed to work in conjunction with the 'CPM' (Custom Prefabs Mod) for 7 Days to Die. Ensure that CPM is installed and configured on your server.
• XML Setting Awareness: The module provides reminders about a specific setting (BloodmoonSpawner_DespawnAllOnStart) in the CPMsettings.xml file. While the module automates other settings, this XML setting might need manual adjustment for optimal behavior.
• Permission Management: Control access to the module's commands using the provided permission to prevent unintended changes to Blood Moon settings.