mirror of
https://github.com/bitburner-official/bitburner-src.git
synced 2024-12-11 08:53:18 +01:00
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.
20 lines
1.1 KiB
Markdown
20 lines
1.1 KiB
Markdown
<!-- Do not edit this file. It is automatically generated by API Documenter. -->
|
|
|
|
[Home](./index.md) > [bitburner](./bitburner.md) > [RunOptions](./bitburner.runoptions.md) > [ramOverride](./bitburner.runoptions.ramoverride.md)
|
|
|
|
## RunOptions.ramOverride property
|
|
|
|
The RAM allocation to launch each thread of the script with.
|
|
|
|
Lowering this will <i>not</i> automatically let you get away with using less RAM: the dynamic RAM check enforces that all [NS](./bitburner.ns.md) 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 <i>increase</i> 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.
|
|
|
|
**Signature:**
|
|
|
|
```typescript
|
|
ramOverride?: number;
|
|
```
|