https://gravitton.github.io/blog/Recent content on GravittonHugoenFri, 06 Nov 2026 00:00:00 +0000https://gravitton.github.io/blog/posts/gravitton-libraries/Fri, 06 Nov 2026 00:00:00 +0000https://gravitton.github.io/blog/posts/gravitton-libraries/<p>A 2D game asks the same two things of its map over and over: what can a unit see, and how does it get where it is going. <a href="https://github.com/gravitton">Gravitton</a> is a set of Go libraries for 2D games, written while building a game engine on top of them, and three of them take that task, each at its own level:</p> <ul> <li><a href="https://github.com/gravitton/geometry"><code>geometry</code></a>: points, vectors, shapes, paths and the collisions between them.</li> <li><a href="https://github.com/gravitton/hexagon"><code>hexagon</code></a>: hexagonal coordinates, ranges, lines and sight, with no pixels and no storage.</li> <li><a href="https://github.com/gravitton/grid"><code>grid</code></a>: a value per cell on a rectangular, isometric or hexagonal layout, with sight and pathfinding, built on the other two.</li> </ul> <p>Beside them are smaller ones: <a href="https://github.com/gravitton/spatial"><code>spatial</code></a> for the broad phase of collision, <a href="https://github.com/gravitton/container"><code>container</code></a> for the storage under a grid, <a href="https://github.com/gravitton/errors"><code>errors</code></a> and <a href="https://github.com/gravitton/assert"><code>assert</code></a>. This post is the map of the series: what the three libraries do on one map, the rules they share, and the posts that each take one decision from them and show the code and the measurements behind it.</p>