mc-observe

To fetch Minecraft world state efficiently, use a single API call to an `/observe` endpoint that simultaneously retrieves block data, entity locations, and navigation surfaces. This unified observation method eliminates the need for separate network requests for each data type.

Observing a Minecraft world for map-building requires a running Minecraft bridge with an active `/observe` endpoint. You specify a radius around the agent to receive structured data on surrounding blocks, nearby mobs, dropped items, and the agent's current pose.

Yes, you can get navigation surface data and entity positions simultaneously. The observation process queries blocks, entities like items and mobs, and navigation surfaces together in a single operation, providing a complete environmental picture for pathfinding and awareness.

The best way to reduce network calls when scanning a Minecraft environment is to use a unified observation endpoint. By fetching blocks, entities, and navigation data in one request rather than querying each category separately, you significantly cut down network overhead.

No, this world observation approach relies on specific dependencies including `local_grid` and `nav_core` to process spatial data. Alongside a running Minecraft bridge exposing an `/observe` endpoint, these components are required to structure the fetched blocks and navigation surfaces.