LibertyTools / Docs
Make a command without code
Let LibertyTools respond when a player runs a custom ER:LC command. This guide makes ;help send that player a private message. You do not need to run a bot or write code.
Before you start
You need an ER:LC private server with API access, permission to set its Event Webhook URL, and the server's API key. The server owner will also need to approve LibertyTools as a public app before hosted commands can send messages back into the game.
1. Connect your server
- Open the dashboard and sign in with Roblox.
- Under Your servers, create a connection and name it after your ER:LC server.
- Click Copy ER:LC URL. Paste that URL into the Event Webhook setting for the same ER:LC server.
- Return to the dashboard's Events tab. When ER:LC sends an event, you will see it there. A probe event is normal; it checks that the webhook can be reached.
Keep each server's URL with its own connection. A connection controls where that server's events go.
2. Build the command
- Open Commands for your connection.
- In When this command is run, enter
;help. - In Do this, choose Privately message the player.
- Write a short message, such as
Need help? Ask a staff member or run ;rules. - Click Preview result to see the action LibertyTools would send. Then click Save draft.
A draft does nothing in-game. This gives you time to check the name and message before publishing.
3. Enable and test it
- Open Settings and connect the ER:LC server key for this connection. The dashboard uses it to identify the server automatically.
- Ask the server owner to click Authorize LibertyTools in ER:LC and approve the app for that server.
- Go back to Commands and publish your draft.
- Join the server and run
;help. You should receive a private message. - Look at Recent command runs to see whether ER:LC accepted the action.
When commands have to wait
Commands share an API safety limit. If your command has not been sent yet and capacity is busy, it stays queued and retries automatically. Recent command runs shows Command waiting; do not repeat it just because it is waiting. Unsent commands expire after five minutes rather than replying much later.
User cooldowns, safety stops, and commands that ER:LC has rejected are not automatically replayed. If a request may already have reached ER:LC but its result is uncertain, LibertyTools does not resend it automatically. Pausing or restricting the connection cancels pending work.
If it does not work
- No event in Events: check that the webhook URL is in the correct ER:LC server's settings.
- Event appears, but no command run: make sure the rule is published and the command name matches.
- Command run says authorization is needed: have the server owner use the authorization link in Settings.
- Command run failed or was rate-limited: read the reason in Recent command runs. LibertyTools limits remote commands to protect the ER:LC API.
For more checks, use the troubleshooting guide.