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

DOCUMENTATION: Fix newline issues in IPvGO docs and add missing RAM cost (#2602)

Browse Source
This commit is contained in:
catloversg
2026-03-28 00:26:45 +07:00
committed by GitHub
parent 3d5079a4e6
commit e3ae5478d5
17 changed files with 251 additions and 144 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
markdown/bitburner.goanalysis.getvalidmoves.md
View File

@@ -6,15 +6,17 @@
Shows if each point on the board is a valid move for the player. By default, analyzes the current board state. Takes an optional boardState (and an optional prior-move boardState, if desired) to analyze a custom board.
The true/false validity of each move can be retrieved via the X and Y coordinates of the move. `const validMoves = ns.go.analysis.getValidMoves();`
`const moveIsValid = validMoves[x][y];`
The true/false validity of each move can be retrieved via the X and Y coordinates of the move.
```js
const validMoves = ns.go.analysis.getValidMoves();
const moveIsValid = validMoves[x][y];
```
Note that the \[0\]\[0\] point is shown on the bottom-left on the visual board (as is traditional), and each string represents a vertical column on the board. In other words, the printed example above can be understood to be rotated 90 degrees clockwise compared to the board UI as shown in the IPvGO subnet tab.
Also note that, when given a custom board state, only one prior move can be analyzed. This means that the superko rules (no duplicate board states in the full game history) is not supported; you will have to implement your own analysis for that.
The current valid moves for white can also be seen by simply calling `ns.go.analysis.getValidMoves(true)` .
The current valid moves for white can also be seen by simply calling `ns.go.analysis.getValidMoves(true)`<!-- -->.
**Signature:**