Board Square Neighborhood
Enumerate bounded orthogonal or eight-neighbor square-board cells with explicit edge clipping; origin is excluded.
Description
Enumerate bounded orthogonal or eight-neighbor square-board cells with explicit edge clipping; origin is excluded.
A square-grid neighborhood can use four orthogonal or eight surrounding cells. Border clipping changes the available count.
When to use this tool
Enumerate bounded orthogonal or eight-neighbor square-board cells with explicit edge clipping; origin is excluded.
- Prepare the supplied x, y, width, height, diagonal fields for this operation.
- Compare the complete example with the representation used by your own input before carrying the result into another step.
How to use the tool and how it works
- Enter x, y, width, height, diagonal. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.cells. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Validate an in-bounds x/y position and positive integer width/height. Enumerate neighboring offsets, include diagonals only when requested and retain destinations within the rectangle.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| x | x. | Integer from 0 to width - 1 inclusive |
| y | y. | Integer from 0 to height - 1 inclusive |
| width | width. | Integer from 1 to 1e6 inclusive |
| height | height. | Integer from 1 to 1e6 inclusive |
| diagonal | Explicit choice for diagonal; supply a boolean rather than a text label. | true or false |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.cells | The cells list in the ordering and representation described above. |
{
"input": {
"x": 0,
"y": 0,
"width": 3,
"height": 3,
"diagonal": false
},
"output": {
"result": {
"cells": [
[
1,
0
],
[
0,
1
]
]
}
}
}Limitations and assumptions
- The starting cell is excluded. No occupied-cell, movement-cost or game-legality filtering occurs.
- Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
- Lists are limited to 128 entries. JSON text must meet bounded size and depth checks, and numeric outputs beyond the safe finite magnitude are rejected. Exact large integers use decimal strings.
- Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.
Alternative or Complementary methods
Use a game-state-aware rules engine when occupancy, legal moves or scoring rules matter. These operations calculate coordinates, local geometry or supplied ledger totals without inferring a complete position.
References
Similar or alternative tools
- Board Hex Axial Neighborhood
Enumerate six infinite axial hex-grid neighbors in a fixed direction order; no board clipping or geographic coordinates.
- Board Captured Piece Ledger
Aggregate explicit captured-piece events by side and piece name; no inferred moves, scoring or game legality.