moss-world-grid

Convert coordinates and manage paging for Subspace Infinity voxel grids.

25|5|Updated Apr 22, 2017

Search Tags:#moss #coordinate conversion #voxel grid #subspace infinity #map placement #world paging #tileid

Ready to run

npx skills add https://github.com/assofohdz/subspace-infinity --skill moss-world-grid

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: moss-world-grid
Source: https://github.com/assofohdz/subspace-infinity/tree/main/.claude/skills/moss-world-grid
Command: npx skills add https://github.com/assofohdz/subspace-infinity --skill moss-world-grid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually implementing coordinate conversions, paging logic, and map boundary handling for Subspace Infinity's voxel world is error-prone and requires duplicating complex grid math already provided by the Moss library.

Core Features & Use Cases

Native TileId Alignment: Directly corresponds to Subspace's 1024×1024 map size, eliminating manual *1024 calculations for map placement and coordinate translation.
Automated Coordinate Conversion: Handles translation between world, cell, and grid coordinate spaces without custom implementation.
Common Use Cases: Place multiple maps in a grid, translate ship positions to their containing map ID, debug .col file paging issues, and perform bulk cell writes that span tile or leaf boundaries.

Quick Start

Use the moss-world-grid skill to load a 3x3 neighborhood of maps centered on the origin tile for your Subspace Infinity server.

Frequently Asked Questions about moss-world-grid

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I convert world positions to map IDs in Subspace Infinity?▼

To convert world positions to map IDs in Subspace Infinity, you need automated coordinate conversion logic. This skill provides native TileId APIs aligned with the 1024x1024 map size to handle translation without custom grid math.

Why are .col files proliferating during voxel map paging?▼

Excessive .col file proliferation during voxel map paging often stems from incorrect manual leaf lifecycle management. Using native LeafId and ColumnId APIs eliminates these custom paging errors and properly handles bulk cell writes across boundaries.

What is the best way to place multiple voxel maps in a grid?▼

The best way to place multiple voxel maps in a grid is using native TileId alignment. It directly corresponds to Subspace's 1024x1024 map size, eliminating manual calculations for map placement and coordinate translation.

Can I perform bulk cell writes that span tile and leaf boundaries?▼

Yes, you can perform bulk cell writes spanning tile and leaf boundaries. This skill provides native TileId, LeafId, and ColumnId APIs that automatically handle the complex grid math and boundary logic required for these operations.

Does this skill require manual coordinate conversion setup for Subspace?▼

No, it does not require manual coordinate conversion setup. The skill automates translation between world, cell, and grid coordinate spaces, directly replacing the complex grid math previously provided by the Moss library.