Go to documentation repository
Page History
...
The message parameters are described in the table below.
Parameter | Description |
source_type<obj> | Object type (see the DDI file ( [OBJTYPE] section) ) |
source_id<id> | The object ID set when creating the object in Intellect (see Intellect's settings tree) |
action<react> | Action (see the DDI file (the [REACT] section) ) |
params<number> | The number of parameters passed, in decimal format |
param0_name<str1> | Parameter name |
param0_val<str2> | Parameter value |
To check the network, you can use the <trash:N> parameter, where N is the length of the parameter in bytes. As a result, a text string of a given length will be generated in the message, containing numbers and Latin letters. The parameter name can be anything. For example, if you add the following parameter to the message
| Code Block |
|---|
param1<trash:128> |
the following text string will be generated in response
| Code Block |
|---|
param1<88n9ESCAFyBfHyXzIoPpOF1GirSmlMJ1Ahh9oYZDIQou2RgWY0jXlaL2HhaX9ZY2oKfkQYLuPLg8bGNQK6OumvQjVp1G7BEt1wFsw6FApzIZ3NbBUJNCKnP335OlgEwN> |
| Info | ||
|---|---|---|
| ||
| For working with DDI files, we recommend using the ddi.exe utility (see Section Using the ddi.exe Tool to Work with DDI files). |
...
Overview
Content Tools