1. Home
  2. Docs
  3. Playground
  4. Automation – Settings

Automation – Settings

Automation settings control various aspects of the automation algorithm. Settings are located on the settings tab and will appear if the user selects the “Prompt setting every automation run” option.

  • Prompt setting every automation run – toggles if the automation setting popup appears every time automation is initiated.
  • Don’t break mod sets – sets the global don’t break mod sets rule for all units. Don’t break mod sets will ensure that the full mod sets are used when automating the unit.
    Note: This will be used for units that have “Use global setting” set for their per unit set breaking. You can overwrite this value on a per unit basis on the sets tab on the units stat definition.
  • Limit searches with stat targets – this option is used to limit the amount of time spent on units with stat targets. Due to the complexity of the automating with multiple stat targets, fully optimized searching can take an extraordinary amount of time when a very strong set that matches the stat requirements has been found. This option allows the user to perform a set number of compares, and if a matching set has been found exit early. The automation will not exit early if no match is found.
    Note: mods are sorted in order from highest to lowest strength, so generally a strong match will be returned, but since the tool automates one slot at a time, it is possible that a combination that meets stats has a higher score.
    Example 1: Minimum compares is set to 200k. The automation tool find a matching set after 50k compares. Automation will perform and additional 150k searches and then exit
    Example 2: Minimum compares is set to 200k. The automation tool find a matching set after 350k compares. Automation will immediately exit after finding the match.
    • Minimum compares with match found: the minimum number of searches to perform.
  • Simulate Mods as SixE – the automation tool will automate as if mods with a minimum speed secondary are sliced to six e. This can be useful if you are trying to create an event set with very hard to reach stat targets.
    • Simulate as SixE min speed: The minimum speed that will be considered to slice as six e. This can be used to help only simulate mod slicing for “good” mods.
  • ¬†Auto-reorder on failed target – reorders units if they fail required stat targets Automation – Ordering for more details.
  • Smooth Speed on required Targets – attempts to use even speed secondaries when the unit has a speed minimum. For instance, if you target requires +100 speed across 5 mods, attempts to use +20 mod secondaries for each mod, instead of one mod with +28 and another mod with +12. The calculation for the average mod to aim for uses speed sets and speed arrow to derive average speed secondary. Configuring the Set and primary restrictions to disallow for these will adjust the average speed required.
    • Speed smoothing factor: the factor on how strong the tool tries to smooth speed. Set this factor very high to get the smoothest speed, but it may come at some expense of your other stat weights.
  • Attempt desired targets – the tool will attempt to reach desired stat targets. If all desired stat targets cannot be met, the last desired stat target is dropped and automation is retried.
    NOTE: while this can be used to scale requirements, it also comes at the expense of performance. If you have 6 desired stat targets, and are unable to hit any of them, you will attempt to automate the unit six times.
  • Use derived requirements – attempts to derive requirements for units to improve results based on dependent sort order.
    Example: Darth Revan’s min speed is set to 330. Bastilla Fallen’s speed is set to > Darth Revan. Bastilla has a derived requirement of 330 speed. If Bastilla is automated first, and has it produces a set with 310 speed, it would be impossible to achieve both Darth Revan and Bastilla’s requirements.
Was this article helpful to you? Yes 2 No

How can we help?