mirror of
https://github.com/bitburner-official/bitburner-src.git
synced 2026-04-16 06:18:42 +02:00
b51ed8fd59
There were two large holes in the existing offline server handling: 1. It didn't include IPs, so scripts that used IPs instead of hostnames would get exceptions thrown for "server not found." 2. Coverage was very low for non-Darknet APIs. Maybe most of them don't need to be covered, but many obvious ones like "ps", "killall" and "hasRootAccess" were missing. IMO the only reliable answer is one that enforces *all* are covered via the type system. To accomplish the second part, helpers.getServer() was changed to return null when a server is offline. This intentionally breaks a lot of its utility, which was to return a server unconditionally. To compensate, its utility was increased - it now also does unknown argument processing, allowing it to subsume a common line that all callers were repeating. Some callers switched to ctx.workerScript.getServer(), because they didn't actually need to be using helpers.getServer(). Similarly, a few callsites switched to GetServerOrThrow(), for the cases where it should be guaranteed that the server is valid. The rest are returning a default/failure response when the server is offline. (Except for contracts, which threw on failure already anyway.)
1.1 KiB
1.1 KiB
Home > bitburner > NS > hackAnalyzeSecurity
NS.hackAnalyzeSecurity() method
Get the security increase for a number of threads.
Signature:
hackAnalyzeSecurity(threads: number, host?: string): number;
Parameters
|
Parameter |
Type |
Description |
|---|---|---|
|
threads |
number |
Amount of threads that will be used. |
|
host |
string |
(Optional) Hostname/IP of the target server. Optional. If unspecified, the threads are not capped. |
Returns:
number
The security increase.
Remarks
RAM cost: 1 GB
Returns the security increase that would occur if a hack with this many threads happened. The number of threads is limited to the number needed to hack the server's maximum amount of money.