Documentation

Break profiles allow you to schedule automatic breaks during bot sessions. Breaks help simulate natural player behavior by periodically pausing activity, optionally logging out, and resuming after a specified duration.

Understanding Breaks

A break profile consists of two main components:

  • Active Times - Time windows during which the bot can be logged in and running
  • Breaks - Scheduled pauses that occur during active times

Breaks only trigger during active time windows. If no active times are configured, the bot can run at any time (when not on a break).

Creating Break Profiles

Via Launcher

  1. Open the Tribot Launcher
  2. Navigate to the Break Profiles section in the sidebar
  3. Click Add Profile
  4. Enter a name for your profile
  5. Click Create

Configuring Break Settings

After creating a profile, click Edit to configure its settings.

Active Times

Active times define when the bot is allowed to be logged in. Outside of these windows, the bot will remain logged out.

  • Start Time - When the active period begins (HH:MM format)
  • End Time - When the active period ends (HH:MM format)

Active times can span midnight. For example, setting start to 22:00 and end to 06:00 creates an overnight active window.

Click Add Active Time to add a time window. Use the Randomize button to generate random values for testing.

Tip: If no active times are configured, the bot can log in at any time (when not taking a break). Add active times if you want to restrict play to specific hours.

Break Configuration

Each break profile can have multiple break configurations. For each break, you can configure:

  • Break Every - How often breaks occur (in seconds)
  • Break At Randomization - Adds variation to when breaks trigger
  • Break Length - How long each break lasts (in seconds)
  • Break Length Randomization - Adds variation to break duration
  • Logout - Whether to log out during the break

Click Add Break to add a break configuration.

Randomization Types

Two randomization methods are available for both break timing and duration:

Even Distribution:

  • Minus - Maximum seconds to subtract from the base value
  • Plus - Maximum seconds to add to the base value

For example, with a 3600 second (1 hour) break interval and +/- 600 seconds randomization, breaks will occur between 50 and 70 minutes apart.

Standard Deviation:

  • Std - Standard deviation in seconds for a normal distribution

This creates more natural variation where most values cluster around the base time, with occasional larger deviations.

Visualizing Break Profiles

Click Visualize on any break profile to see a 24-hour simulation of how breaks will occur.

The visualization shows:

  • Green regions - Active time windows (when logged in)
  • Blue bars - Breaks without logout
  • Red bars - Breaks with logout

Click Regenerate to see different randomized outcomes based on your settings.

Example Configuration

Here is a typical break profile for moderate botting:

Active Times:

  • 09:00 to 18:00 (9 hours of play time)

Break 1 (Short breaks):

  • Break Every: 3600 seconds (1 hour)
  • Break At Randomization: Even Distribution, -600/+600 seconds
  • Break Length: 300 seconds (5 minutes)
  • Break Length Randomization: Even Distribution, -60/+120 seconds
  • Logout: No

Break 2 (Longer breaks):

  • Break Every: 7200 seconds (2 hours)
  • Break At Randomization: Standard Deviation, 900 seconds
  • Break Length: 900 seconds (15 minutes)
  • Break Length Randomization: Standard Deviation, 180 seconds
  • Logout: Yes

Assigning Break Profiles

Via Bulk Launch

Break profiles can be assigned to accounts in the Bulk Launch view:

  1. Navigate to Bulk Launch in the sidebar
  2. Select an account and click to open its settings
  3. Click Edit
  4. Enter the break profile name in the Break Profile field
  5. Click Save

Via CLI

When launching via the CLI, specify a break profile using the --break-profile-name option:

./tribot run \
  --legacy-username "[email protected]" \
  --script-name "MyScript" \
  --break-profile-name "My Break Profile"

The break profile must already exist in the launcher database.

Best Practices

  • Use randomization - Avoid predictable, fixed-interval breaks
  • Vary break lengths - Mix short and longer breaks throughout sessions
  • Set realistic active times - Match typical player schedules in your timezone
  • Test with visualization - Preview your configuration before running
  • Multiple break types - Combine frequent short breaks with occasional longer ones

Troubleshooting

Breaks Not Triggering

  • Verify the break profile name matches exactly (case-sensitive)
  • Ensure you are within an active time window
  • Check that the break interval has elapsed since the session started

Too Many Breaks

  • Review your break intervals - they may be set too short
  • If using multiple break configurations, their breaks can overlap
  • Use the visualization tool to preview actual break frequency