06d742a7f3
*All* RAM calculations must take place in units of hundredths-of-a-GB in order for there not to be issues. Also adds slightly more verbose logging when the dynamic RAM check fails.
1.7 KiB
Home > bitburner > RunOptions
RunOptions interface
Signature:
interface RunOptions
Properties
| Property | Modifiers | Type | Description |
|---|---|---|---|
| preventDuplicates? | boolean | (Optional) Should we fail to run if another instance is running with the exact same arguments? This used to be the default behavior, now defaults to false. | |
| ramOverride? | number | (Optional) The RAM allocation to launch each thread of the script with. Lowering this will not automatically let you get away with using less RAM: the dynamic RAM check enforces that all NS functions actually called incur their cost. However, if you know that certain functions that are statically present (and thus included in the static RAM cost) will never be called in a particular circumstance, you can use this to avoid paying for them. You can also use this to increase the RAM if the static RAM checker has missed functions that you need to call. Must be greater-or-equal to the base RAM cost. Will be rounded to the nearest hundredth-of-a-GB, which is the granularity of all RAM calculations. Defaults to the statically calculated cost. |
|
| temporary? | boolean | (Optional) Whether this script is excluded from saves, defaults to false | |
| threads? | number | (Optional) Number of threads that the script will run with, defaults to 1 |