felixfoertsch/bitburner-src
1
0
Fork 0
mirror of https://github.com/bitburner-official/bitburner-src.git synced 2026-04-18 07:18:38 +02:00
Code Issues Packages Projects Releases Wiki Activity

DOC: Add FAQ and another JIT batcher illustration to documentation (#2400)

Browse Source
This commit is contained in:
EntenBu
2025-12-18 04:30:58 +07:00
committed by GitHub
parent 968c0c2a8c
commit 6f9447e27e
5 changed files with 85 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
src/Documentation/doc/en/programming/hackingalgorithms.md
View File

@@ -29,7 +29,7 @@ Cons:
- Limits income generation
- Extremely [RAM](../basic/ram.md) inefficient
- Utilizes script online time poorly
- Risk of over hacking
- Risk of over-hacking
- Slow to start producing money
This is the self-contained algorithm implemented in `early-hack-template.js`. Each script is tasked with choosing which function to execute based on the status of the target server.
@@ -186,6 +186,23 @@ Shotgun batchers are not very RAM efficient because the scripts take up RAM duri
|=Weaken=============|
|=Weaken=============|
Or:
|Hack=|
|=Weaken=============|
|=Grow===========|
|=Weaken=============|
|Hack=|
|=Weaken=============|
|=Grow===========|
|=Weaken=============|
|Hack=|
|=Weaken=============|
|=Grow===========|
|=Weaken=============|
\*For illustrative purposes only.
By weaving batches between each other, JIT batchers maximise the effectiveness of the RAM at the cost of very precise timing constraints.
Good communication between worker scripts and the controller is necessary to schedule the next batch at the right time.
The controller must have an effective method to predict which scripts need to be launched.