The Tools Module in BAS: Log, Result, JS and Random

Every toolkit needs a drawer of small, sharp utilities. In BAS that drawer is the Tools module — the bits you use to see what your bot is doing, hand back a result, and drop into raw code when the visual blocks run out.

What the Tools module is for

The module displays useful information in the log, outputs the script’s results, runs JavaScript inside a scenario, parses a string and generates random numbers. Small actions, but you’ll reach for them constantly.

The actions

Log. Prints a value or checkpoint to the log while the bot runs. This is your primary debugging tool — drop logs at key steps and the log becomes a live trace of what happened and where it broke.

Clear log. Wipes the log back to empty, so a long run or a fresh iteration starts clean.

Result. Outputs the script’s result — the value the run is meant to produce, surfaced where you can read or collect it.

Execute code. Runs JavaScript inside the scenario. This is the escape hatch: anything the visual blocks don’t cover directly, you can do in a few lines of JS — custom string manipulation, math, reading page variables, building a payload.

Parse string. Pulls a piece out of a string by a simple rule — quick extraction without reaching for a full regular expression.

Random number. Generates a random number, the basis for human-like variation: randomised delays, pauses and counts so your bot doesn’t behave with robotic regularity.

How they fit together

These small tools glue a scenario together. You log to see what’s happening, execute code when a step needs logic the blocks don’t express, random number to keep timing human, and result to deliver the output. None of them is glamorous — and you’ll use every one of them in almost every bot you build.