Board Hex Cube Axial Converter

Convert validated zero-sum integer hex cube coordinates to axial q=x,r=z; invalid cube coordinates are rejected.

Description

Convert validated zero-sum integer hex cube coordinates to axial q=x,r=z; invalid cube coordinates are rejected.

A chosen axial hex convention retains cube x as q and cube z as r. The omitted coordinate follows from the zero-sum rule.

When to use this tool

Convert validated zero-sum integer hex cube coordinates to axial q=x,r=z; invalid cube coordinates are rejected.

  • Prepare the supplied x, y, z 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

  1. Enter x, y, z. Use the exact text syntax, units and index conventions explained below.
  2. Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
  3. Read result.q, result.r. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.

Validate integer x, y and z within plus or minus one billion and require x+y+z=0. Return q=x and r=z.1

Input fieldMeaning and representationAccepted input
xx.Safe integer
yy.Safe integer
zz.Safe integer
Output fieldInterpretation
resultObject containing the named outputs below.
result.qThe q value under the stated formula or text convention.
result.rThe r value under the stated formula or text convention.
json
{
  "input": {
    "x": 2,
    "y": -1,
    "z": -1
  },
  "output": {
    "result": {
      "q": 2,
      "r": -1
    }
  }
}

Limitations and assumptions

  • The coordinate convention is explicit. No pixel projection, board bound or alternative axial orientation is inferred.
  • 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

  1. Tool behavior and example: Board Hex Cube Axial Converter — tool.io

Similar or alternative tools

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies