InfoCommands

InfoCommands lets you build your own chat commands like /rules and /links from one config file, plus a join welcome, so new players get their answers fast.

Sooner or later every server needs a rules command, a links command, and a friendly line for fresh joins. InfoCommands covers the lot from one config file and you never touch code to do it. Each block in the config becomes one chat command with its own colour, its own cooldown, and either plain lines or a list of links. Staff only commands and a help menu that builds itself come along for the ride.

Supported Features

• Chat commands you invent: add as many as you like in config.json. Each block makes one command, like /rules or /links.
• Headers, lines and links: give a command a header, a list of lines, or a list of label and url pairs. Mix them however suits you.
• Live text tags: drop {server}, {online}, {map}, {player}, {time} or {date} into any line and I fill them in as the command runs.
• A colour per command: set a colour name on each command and a default for the rest. I know the common ARK colour names already.
• A help menu that builds itself: the /help list only shows the commands that player is actually allowed to use, so it never goes stale.
• Staff only commands: put a permission node on any command and only your staff can see it or run it.
• Cooldowns: set a wait per command, or one wait across the lot, so nobody can spam your chat.
• A welcome for new joins: switch the join message on and a new player gets your lines a few seconds after they load in.
• Change commands live: edit the config and reload from the console or RCON, and I add, drop and rename commands with no restart.
• Send a block to Discord: one console or RCON command posts any info block into your Discord channel as an embed.
• Every line in your language: point the config at a language file and my own lines follow it, so a server running in French or Polish reads properly. Your command text was always yours to write.

Console & RCON Commands

Player Commands

You name every player command yourself in config.json, so rename or remove any of these. This is the set that ships in the default config.

Permissions

Put a Permission field on any command block and only players holding that node see it in /help or may run it. When the Permissions plugin is missing or the check is off, a gated command stays hidden and locked for everybody. That is fail closed on purpose, so a staff note can never leak. Commands with no node are open to all.

Config

To see every configuration option, visit our docs. To edit your config files the easy way, open our configuration editor.

Requirements

• AsaApi v2.01 or newer
• A Windows server running ArkAscendedServer through the AsaApi loader
• Permissions (optional, works without it, only needed for staff only commands)
• A Discord webhook (optional, works without it, only feeds the Post command)

Installation

1. Unzip the download and put the InfoCommands folder into ArkApi/Plugins/. Keep the folder named InfoCommands, since AsaApi will not load a plugin whose folder and DLL names differ.
2. Open InfoCommands/config.json and set up your commands, your tags and your colours.
3. Save the file.
4. Bring the server back up with AsaApiLoader.exe.
5. Watch ArkApi.log for the loaded line, then try /help in game.

Support & Help

Stuck on a step, or seeing an error you do not like? Come and ask in the Discord and I will sort it out with you: https://discord.gg/8GGaEzWk9p

Frequently Asked Questions

What does InfoCommands do?

InfoCommands turns one config file into all the info commands your server needs. Every block you write becomes a chat command with its own colour, cooldown and text, so a rules command, a links menu, a wipe date and a staff note all come from the same place with no code involved.

How do I install InfoCommands?

Unzip the download and drop the InfoCommands folder into ArkApi/Plugins/, keeping the folder name so it matches the DLL. Set up your commands in config.json, then restart the server through the AsaApi loader and look for the loaded line in ArkApi.log.

Can I add my own commands and rename the ones that ship?

Yes, that is the whole point of it. Each block in config.json makes one command with its own colour, cooldown, header, lines or links. Add, drop or rename blocks whenever you like, run InfoCommands.Reload, and the new set is live.

Does it need Permissions or ArkShop?

No. InfoCommands runs on its own and never touches a shop. Permissions is only checked when you put a node on a command, and without it those gated commands stay hidden and locked while everything else carries on as normal.

Are the online and map tags live?

Yes. Tags are filled in the moment a player runs the command, so {online} shows the count right then and not a number from when the server booted. The same goes for {map}, {time}, {date}, {server} and {player}.

Does it add a welcome message for new joins?

It can. Switch the join message block on and a new player gets your lines a few seconds after they load in. It ships off, because it is the one game hook I use, and if a game patch ever breaks that hook I turn the welcome off myself and write a note in the log.

Was any AI content used in the making of this?

The source code itself was fully created by myself. I do use ChatGPT occasionally to generate product images, and I do use ChatGPT to generate the website descriptions. I do this because I don't speak native English perfectly. I am natively from Sweden, so I use GPT to help translate and write product descriptions. I also will sometimes use GPT to write better English logs. Majority of my Free plugins are open source, so you can review the code yourself and freely fork and edit it to your liking.