Getting started

This page will help you get started with the Modiplex Configuration Language (MCL for short)

Please note that the developer cloud is currently not available - the only way to upload your custom package is to contact the developer on our support server.

Requirements

• Internet access

• Text editor (Notepad, Visual Studio Code ...)

• Access to Modiplex's developer cloud

Creating a sample package

MCL consists of per-line commands named calls. Each call represents an action, a value or an I/O string. If you want to start creating a package, you'll first have to define that. Every package must also contain an end call.

<Mdplx-encoder-payload_1.0>
.... some code....
<end payload>

Next, we're gonna have to set some configuration values that are necessary for the package to be installable. For this, we'll use the use and setcalls. We'll also have to identify the config's starting point and end point.

> start config

# use lvd
# set creator=MODIPLEX
# set version=1.0
# set name=Antiscam
# set description=This is a sample package.

> end config

This is now a valid package, however Modiplex will not accept it because it does not do anything. So let's add a response. We'll start by defining the response section starting point and then add an input, trigger value that is specified using decimals with 0 being 0% similarity and 1 being 100% similarity, then we'll choose an outgoing action and whether we want to delete the message or no.

> start resp

# in This is an input message
# trigger 0.8
# out action .kick
# delete true

# next

Notice the #next at the end. This has to be included after every response function, or Modiplex will not parse it. Also keep in mind that all calls must be on one line only. We will then close off the response section and our package is done.

> end resp

The finished package:

<Mdplx-encoder-payload_1.0>

> start config

# use lvd
# set creator=MODIPLEX
# set version=1.0
# set name=Antiscam
# set description=This is a sample package.

> end config
> start resp

# in This is an input message
# trigger 0.8
# out action .kick
# delete true

# next

> end resp

<end payload>