Takaro module library
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.
/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 eventsbuystock, triggerevent, sellstock, markets, stockinfo, stockportfolio. Added 2 scheduled tasks: updatestockprices, marketnews. New permissions: STOCK_MARKET_USE, STOCK_MARKET_TRADE, STOCK_MARKET_BROKER, STOCK_MARKET_TRIGGER_EVENT. New configuration options: sectors, stocks, marketEvents, eventFrequency, defaultEventDuration, transactionFee, vipDiscount, priceAlertThreshold, marketNewsChannelId.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.
Define economic sectors relevant to survival in Navezgane
List of stocks representing Navezgane entities and resources
Events impacting the Navezgane economy
Average number of update cycles between market events (0 to disable). Depends on mod's update frequency (e.g., per in-game hour?).
8Default number of update cycles an event lasts.
3Percentage fee charged on all buy/sell transactions (5 = 5%)
3Percentage discount on transaction fees for players with 'STOCK_MARKET_BROKER' permission (50 = 50%)
50Percentage change that triggers a market alert (15 = 15%)
15The ID of the Discord channel where market news messages should be posted. Leave empty to disable.
No configuration properties defined. This module uses default settings.
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.
These commands can be executed by players in-game. Each command has a trigger word, optional arguments, and executes JavaScript code on the server.
"""""all""""""all""all"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.
These jobs run automatically on a schedule defined by cron expressions. Each job executes JavaScript code at specific times or intervals.
At minute 0 of every 1 hours on every day of the month in every month on every day of the 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).
At minute 1 of every 1 hours on every day of the month in every month on every day of the 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).
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.
These permissions control who can access different features of this module. Administrators can assign these permissions to roles, allowing fine-grained access control.
STOCK_MARKET_BROKERPermission KeyVIP status that reduces transaction fees
STOCK_MARKET_BROKERSTOCK_MARKET_TRADEPermission KeyAllows the player to buy and sell stocks
STOCK_MARKET_TRADESTOCK_MARKET_TRIGGER_EVENTPermission KeyAllows admins to manually trigger market events
STOCK_MARKET_TRIGGER_EVENTSTOCK_MARKET_USEPermission KeyAllows the player to view market prices and their portfolio
STOCK_MARKET_USEPermissions 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.