* Update api-documentor and api-extractor. #1566 follow-up.
I have verified that the HTML/markdown table generation bug in
[#4878](https://github.com/microsoft/rushstack/issues/4878) in rushstack
for api-documentor has been fixed as per rushstack#5256. The testcase
[repro](https://github.com/catloversg/api-documenter-bug-pr-4578) now
produces the correct expected output.
I have confirmed that the generated output in bitburner from
`npm run doc` now generated HTML tables, and correctly inserts
a blank line between the </table> and the follow line (e.g. Returns).
Stylisticly it could use some whitespace, but it is correctly rendered.
This commit is only the updated packages, not the updated generated
documentation. I assume that is automatically generated by the GitHub
workflow.
* Follow up to 5f732a6f35, include `npm run doc` changed docs.
* Add missing license info
* Fix React warning
---------
Co-authored-by: CatLover <152669316+catloversg@users.noreply.github.com>
1.7 KiB
Home > bitburner > HackingFormulas > growThreads
HackingFormulas.growThreads() method
Calculate how many threads it will take to grow server to targetMoney. Starting money is server.moneyAvailable. Note that when simulating the effect of grow, what matters is the state of the server and player when the grow *finishes*, not when it is started.
The growth amount depends both linearly *and* exponentially on threads; see grow for more details.
The inverse of this function is formulas.hacking.growAmount, although it can work with fractional threads.
Signature:
growThreads(server: Server, player: Person, targetMoney: number, cores?: number): number;
Parameters
|
Parameter |
Type |
Description |
|---|---|---|
|
server |
Server info, typically from getServer | |
|
player |
Player info, typically from getPlayer | |
|
targetMoney |
number |
Desired final money, capped to server's moneyMax |
|
cores |
number |
(Optional) Number of cores on the computer that will execute grow. |
Returns:
number
The calculated grow threads as an integer, rounded up.