nScript Queue User Manual

Chain multiple nScripts together into an automated task queue with stop conditions and retry logic.

Links: TRiBot Store | Forum Thread | Discord

Table of Contents

• Quick Start
  • Script Arguments
• Requirements
• How It Works
• Settings Reference
  • Main Queue Interface
  • Task Configuration
  • Stop Conditions
  • Advanced Settings
• Supported Stop Conditions
• Troubleshooting
• Getting Help
• Tips

Quick Start

1. Launch any nScripts All-In-One bundle (Combat, Skilling, Money Making, or Ultimate)
2. Select nScript Queue from the script selection menu
3. Click Add Task to add your first script to the queue
4. Select a script from the available bundle scripts
5. Enter the settings file name (the saved profile name for that script)
6. Optionally configure stop conditions and retry settings
7. Repeat steps 3-6 for each script you want to run
8. Click Start nScriptQueue! to begin running the queue

Script Arguments

Load a saved settings profile by passing the profile name as a script argument:

MyProfile

This loads <tribot-folder>/nScripts/nScript Queue/settings/MyProfile.ini and starts immediately without showing the GUI. Useful for automation and automatically starting scripts on clients.

Additional options:

• last - Load the most recently used settings
• Profiles saved to nScripting.com Settings Storage can also be loaded by name

Requirements

Bundle Membership

nScript Queue is only available as part of nScripts All-In-One bundles. It cannot be purchased or run separately. You must have an active subscription to one of the following bundles:

• Combat Bundle - Includes combat-focused scripts
• Skilling Bundle - Includes training scripts for various skills
• Money Making Bundle - Includes profit-generation scripts
• Ultimate Bundle - Includes all scripts from all bundles

Pre-Saved Settings

Each script task in the queue requires a saved settings profile. Before using nScript Queue:

1. Run each script you want to queue individually
2. Configure the settings as desired
3. Save the settings with a memorable name
4. Note the profile name for use in the queue

How It Works

nScript Queue runs scripts sequentially from your configured task list. Here's the execution flow:

1. Task Evaluation: The queue checks if the current task's stop conditions are already met
2. Script Launch: If conditions aren't met, the bundled script launches with your specified settings
3. Monitoring: While the script runs, nScript Queue monitors both:
   • The task's configured stop conditions
   • Global stop conditions (if configured)
4. Transition: When stop conditions are met (or the script ends), the queue moves to the next task
5. Retry Logic: If retries are enabled and the script ends before conditions are met, it restarts automatically
6. Completion: After all tasks complete, the queue stops

Scripts run as child processes within the bundle context, meaning:

• No additional TRiBot instances are consumed
• Scripts share the same client session
• Transitions between scripts are seamless

Settings Reference

Main Queue Interface

The main GUI displays your task queue as a list. Each task shows:

• The script name
• The settings file name (or custom task name if set)

Buttons:

• Add Task - Opens the task configuration dialog to add a new script
• Edit - Modify the selected task (double-click also works)
• Delete - Remove the selected task from the queue

Task Reordering:

• Drag and drop tasks to reorder them
• Use keyboard arrows to move selected tasks

Task Configuration

When adding or editing a task, you'll configure:

Script Selection

• Click Select Script to choose from available bundled scripts
• Only scripts included in your bundle are available

Settings File Name

• Enter the saved profile name for the script to load
• This is the name you used when saving settings in that script's GUI
• Example: my_cooking_setup or crab_killer_config

Retry Settings

• Enable retries if script ends prematurely - Automatically restart the script if it ends before stop conditions are met
• Retry Count - Number of retry attempts (1-100, default: 3)

Stop Conditions

• Click Configure Stop Conditions to set when the task should end
• See Stop Conditions for details

Stop Conditions

Stop conditions determine when a task ends and the queue advances. Configure them via the Configure Stop Conditions button.

Condition Matching:

• All conditions must be true - Every condition must be satisfied
• At least one condition must be true - Any single condition triggers advancement

Available Actions:

• Create Condition - Add a new stop condition from the dropdown menu
• Edit Selected - Modify an existing condition (double-click also works)
• Delete Selected - Remove a condition
• Info - Learn more about stop conditions

Right-click Context Menu:

• Negate - Invert the condition (stop when NOT true)
• Delete / Clear - Remove conditions
• Copy to clipboard / Import from clipboard - Transfer conditions via clipboard
• Test condition - Check if a condition is currently true
• Test entire condition group - Evaluate all conditions together

Advanced Settings

Access via the Advanced button in the GUI shell.

Stop Conditions (Global)

• Configure conditions that stop the entire queue (not just the current task)
• Useful for time limits, membership expiration, or level goals across all tasks

Supported Stop Conditions

Troubleshooting

"All script tasks completed."

Cause: The queue finished running all tasks successfully.

Fix: This is normal completion, not an error. Add more tasks if you want the queue to continue.

"Script not available in bundle: [name]"

Cause: The script specified in a task is not included in your current bundle.

Fix:

• Verify the script name is spelled correctly
• Ensure your bundle includes the script (e.g., mining scripts require Skilling or Ultimate bundle)
• Upgrade to a bundle that includes the script

"Task failed to complete stop conditions after retries: [task]"

Cause: A task with retry enabled ran out of retry attempts without meeting its stop conditions.

Fix:

• Review your stop conditions - they may be unrealistic or take longer than expected
• Increase the retry count
• Check if the underlying script has issues preventing goal completion
• Verify the settings file exists and loads correctly

"Cannot run bundled script task outside of script bundles"

Cause: Attempting to run nScript Queue standalone instead of through an All-In-One bundle.

Fix: Launch one of the nScripts All-In-One bundles first, then select nScript Queue from within it.

"Script name is required" / "Settings file name is required"

Cause: Attempting to add a task without selecting a script or entering a settings file name.

Fix: Ensure you've clicked "Select Script" and entered the saved profile name in the Settings File Name field.

Getting Help

If you run into issues not covered in Troubleshooting:

1. Generate a bug report - In TRiBot: Dev Tab → Generate Bug Report (includes logs, settings, and screenshot)
2. Post on Discord - Share the zip and describe what happened vs. what you expected at discord.gg/BFtypSSbjp

For issues that are hard to capture in a screenshot, a short screen recording helps.

Tips

• Test scripts individually first: Before queuing a script, run it standalone to verify your settings work correctly and save the profile.

• Use descriptive profile names: Name your saved settings clearly (e.g., wines_to_99 or crabs_nmz_prep) so you can easily identify them in the queue.

• Combine stop conditions strategically: Use "at least one" matching when you want multiple ways to advance (e.g., reach level 70 OR run for 2 hours).

• Enable retries for unreliable tasks: If a script might end unexpectedly (due to random events, disconnections, etc.), enable retries to ensure progress continues.

• Use global stop conditions for session limits: Set a system time stop condition globally to end your entire botting session at a specific time.

• Chain progressive training: Create queues that train through skill brackets, e.g., one task for levels 1-30, another for 30-50, etc., each with appropriate methods.

• Skip already-completed tasks: If a task's stop conditions are already met when the queue reaches it, nScript Queue automatically skips to the next task.

• Copy conditions between tasks: Use the right-click context menu to copy stop conditions to clipboard and import them into other tasks.