Skip to main content
erlc.dev Studio gives you several blocks for sending commands directly into your ERLC server, listening for players who type custom in-game commands, and logging output to the Studio panel — all without writing a single line of code.
ERLC commands are executed in the context of your linked server. Make sure your server’s API key is connected and that your bot has the appropriate permissions before using any command block.

​
Running Commands

Use these blocks to send commands to your ERLC server from inside an automation. Connect a value block to the COMMAND input to supply the command string.

erlc_command

Run any ERLC command. Connect a value block (such as a text or variable block) to the COMMAND input. This is the recommended block for most use cases.

erlc_command_legacy

A legacy block that accepts a static command string directly in its COMMAND field. Use erlc_command for new automations — this block exists only for backward compatibility.

erlc_dynamic_command

Build and send a command from a dynamically constructed string. Connect any value block to the COMMAND input, including concatenated text or variable references.

erlc_run_command_with_api_key

Run a command using a specific API key rather than the default server key. Provide both the COMMAND and API_KEY value inputs. Useful when managing multiple servers from one automation.

​
Block Inputs & Fields

​
Custom Game Commands

You can define your own in-game slash commands that players type inside ERLC. When a player uses one of these commands, your automation fires and receives the command data.

erlc_when_game_command

Trigger an automation when a player types a specific command in-game. Set the COMMAND field to the command name (without a leading slash).

erlc_when_event (custom_command)

An alternative event trigger. Use the erlc_when_event block and set its EVENT_TYPE to custom_command to catch any custom command generically.

​
Reading Command Data

Once inside a custom command automation, use the erlc_event_value block to read details about the command that was called. Set its FIELD dropdown to one of the following:

​
Log Output

These blocks write messages to the Studio log panel, which is useful for debugging your automations.

erlc_log

Log a message to the Studio panel. Connect a value block to the MESSAGE input.

erlc_dynamic_log

Same as erlc_log but designed for dynamically built strings. Connect any value block to the MESSAGE input.

​
Example: Custom Command with Arguments

The following automation fires when a player runs the /announce custom command in-game, reads the arguments they passed, and sends a server-wide ERLC command using those arguments.
Use erlc_dynamic_command instead of erlc_command when you need to concatenate the command string from multiple parts — for example, prepending a prefix to the player-supplied arguments.

​
How This Works

1

Trigger on the custom command

The erlc_when_game_command block listens for a player typing /announce in-game and fires the automation.
2

Log the arguments

The erlc_log block reads the CommandArguments field via erlc_event_value and prints it to the Studio log panel so you can verify the input.
3

Run the command

The erlc_command block reads the full Command field and sends it to the ERLC server, executing it in the context of your linked server.