Skip to main content
Version: Current

Behavior Tags

Behavior Tags

These tags affect how CasualOS allows the users to interact with bots.

draggable

Whether the bot is able to be moved by the built-in CasualOS system.

Note that this value only controls whether CasualOS can move bots automatically as the result of user interaction. If set to false, then CasualOS will not change any tags, but it will still send events for the bot (e.g. @onDrag, @onAnyBotDrag, @onDrop, @onAnyBotDrop, etc.).

Possible values are:

ValueDescription
true

The bot is able to be dragged. (default)

false

The bot cannot be dragged.

pointable

Whether the bot interacts with the pointer.

Bots that are pointable can receive clicks, pointer enter/exit, and drop events. Note that the #pointable tag also affects whether the content inside an iframe form is interactable.

Possible values are:

ValueDescription
true

The bot interacts with the pointer. (default)

false

The bot does not interact with the pointer.

focusable

Whether the bot is able to be focused.

Bots that are focusable can receive focus events like @onFocusEnter.

Possible values are:

ValueDescription
true

The bot is focusable. (default)

false

The bot is not focusable.

destroyable

Whether the bot is able to be destroyed.

Possible values are:

ValueDescription
true

The bot will be able to be destroyed. (default)

false

The bot will not be able to be destroyed.

editable

Whether the bot is able to be edited in the sheet in Channel Designer.

Possible values are:

ValueDescription
true

The bot can be edited via the sheet. (default)

false

The bot cannot be edited via the sheet. (including being able to set editable back to true)

listening

Determines whether this bot responds to whispers or shouts. If this tag is set to true it will respond to them. If set to false, it will not.

Possible values are:

ValueDescription
true

The bot will respond to whispers and shouts. (default)

false

The bot will not respond to whispers or shouts.

system

The "system" that this bot represents. Bots with a #system tag will be able to appear in the systemPortal. The you can kinda think of the #system tag as the name that the systemPortal uses for bots. #system tag values should ideally be three sections separated by a ..

Note that this tag can be changed by using the #systemTagName tag.

For example, the first section might be the name of the app bundle, the second section would be the area that the bot belongs in, and the third section would be the name of the bot. e.g. myAppBundle.managers.timeline would specify that a bot belongs in myAppBundle and is one of the manager bots. The systemPortal would then show each bot organized by #system tag.

Image of bots in the systemPortal

Possible values are:

ValueDescription
null(default)
Any StringThe system that this bot belongs to.