Skip to content

Getting Started

AsperTheDog edited this page May 7, 2022 · 5 revisions

Boards??

Basically, the way the system works is you have a set of canvas to work on. Each guild has its own set and you can do a bunch of stuff with it like putting actions and connecting them together

There are two types of canvas in a guild:

  • Main: There can only be one of these in the system. This is the actual board where you will define what the bot does. In this board you can place Global event nodes
  • Custom: These boards can be used to create behaviors that you can then use in other boards as custom action nodes. In these boards you cannot place global event nodes, but you can put Pipeline nodes

Seems like I have to log in...

Yes!! But worry not, No one will make you create a new account so you have to save a password yet again in your very safe browser. This app works with Discord's accounts to both identify you and get very private data what servers you are in.

Sooo... How do I get the bot to do things?

Okay, here's the thing. Discord has a set of events that are triggered by things like someone sending a message or leaving a server. These events are represented as Global Event Nodes. These global events have two outputs (colored arrows), if you click and drag one of them you'll see a line appears. This is how you connect things. Every node will have inputs and outputs, and the way you program things is by connecting them.

As a quick overview, the event outputs (gray arrows) are the ones deciding what happens in the program. That is, the gray arrow in the event node can be connected to an action. This means when the event is triggered that action will be executed. Action event outputs woirk the same way. The name of the event output helps you get an idea on when that arrow is going to execute the connection it has (for example if an action compares two numbers, the event output called "equal" will be triggered when the two numbers are equal).

Value outputs help you decide what data to pass the actions. For example if you have an action that has a numeric output (blue arrow) then that action will output a specific number when executed. Thus, the numberic input you connect it to will receive that number.

That's the gist of it. You can look up things like variable nodes to make your work easier or pipelines to see how things work in custom action boards.

Clone this wiki locally