Tools•analyzer
Script Package Scope Checker
This planning tool helps scripters decide whether a new automation idea should live as a simple alias, a trigger, a timer, or a larger reusable package.
Try the tool
client runnerRecommended script scope
Run the tool to see output.
Examples
Simple buff alias
{
"behavior_summary": "Send three prep commands before I leave town",
"uses_game_output": false,
"needs_schedule": false,
"shared_across_characters": false,
"primary_client": "Mudlet"
}Expected output
Start with a single alias; you only need one user-invoked command sequence.
Combat warning trigger pack
{
"behavior_summary": "Watch combat text and highlight dangerous status lines for every character",
"uses_game_output": true,
"needs_schedule": false,
"shared_across_characters": true,
"primary_client": "TinTin++"
}Expected output
Use a trigger-based package so the parsing logic can be reused and versioned.
How it works
The checker looks at how the automation is triggered, whether it depends on parsing output, whether it repeats on a schedule, and whether it should be portable across characters. Those signals map naturally to aliases, triggers, timers, or a package-level structure.