A strongly-typed index into various LOD-indexed arrays. 0 is the highest LOD. Ordering is "backwards": x > y means that x is bigger (lower level of de

Instead of storing individual vertices, normals, etc. in VRAM, store them in chunks. This makes it much faster to unload things.

Position of blocks on an "infinite" regular grid. The position is implicitly in units of chunk::WIDTH.

Unique client ID.

Client handle

The main client state.

Messages the client sends to the server.

A color with RGB channels.

A color with RGBA channels.

An untextured rendering vertex, with position and color.

A single tuft of grass to be loaded

SDL Font datatype.

Information required to load a grass tuft into vram, transformed to refer to vram terrain chunks. TODO: Consider making fields non-pub and exposing re

Timer to keep track of repeating intervals. This struct keeps track of passage of repeated intervals (like bars of music).

What to do with a loaded block

The type of message emitted by `T`. This stream of messages maintains an owner's desired surroundings.

Data structure to keep track of a position's owners, requested LODs, and current T.

Terrain materials

TODO: allow inserting things with a "mobile" flag; don't subdivide those objects.

Produce numbers in increasing absolute value order to some max, like [0, 1, -1, 2, -2].

A receive-only socket.

Run a collection of closures in series. Signals returned from constituent closures.

A send-only socket.

Messages the server sends to the client.

Colored sun data structure.

TODO: Consider making fields non-pub and exposing read-only accessors.

Struct for loading/unloading/maintaining terrain data in VRAM.

This data structure keeps tracks of mob data in VRAM.

The state associated with perceiving the world state.

T representation as 3 distinct matrices, as well as a position + two rotations.

This data structure keeps tracks of mob data in VRAM.

Struct for loading/unloading/maintaining terrain data in VRAM.

The game's custom shader structs.

TODO: Rename this to something more memorable.

Load and unload terrain::TerrainBlocks from the game. Each terrain::TerrainBlock can be owned by a set of owners, each of which can independently requ

Data structure to produce unique IDs.

Iteratively load points cube-shaped layers around the some point. That point can be updated with calls to `update`. What "load" exactly means depends

Messages from the client to the view.

Level of detail a block can be loaded at.

A point in the world with corresponding texture data. The texture position is [0, 1].

one independent audio track