pko-client-reference

Document PKO binary asset parsing across Engine, Client, and Common layers.

8|5|Updated Jan 20, 2025
One-click install
npx skills add https://github.com/Perseus/pko-tools --skill pko-client-reference
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pko-client-reference
Source: https://github.com/Perseus/pko-tools/tree/main/.claude/skills/pko-client-reference
Command: npx skills add https://github.com/Perseus/pko-tools --skill pko-client-reference

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps engineers understand the PKO game client source code to interpret file formats and engine usage for models, animations, textures, and maps.

Core Features & Use Cases

  • Understand PKO binary asset formats (.lgo, .lmo, .lws, .lac) and how the engine loads them.
  • Locate and cross-reference code across Engine, Client, and Common layers to validate imports/exports and data flow.
  • Debug bone/skeleton hierarchies, link points, and attachment systems for character models.
  • Verify consistency between PKO formats and tooling (e.g., glTF export/import flows) and usage in the Rust side.

Quick Start

Open client-src/ to locate parsers for binary PKO assets and compare them with the Rust reference in src-tauri to validate format handling.

Frequently Asked Questions about pko-client-reference

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

FAQPage Schema
How do I parse PKO binary asset formats like .lgo and .lmo file structures?

You can locate the parsers for PKO binary assets by opening the client-src/ directory and comparing them with the Rust reference in src-tauri. This cross-references the Engine, Client, and Common layers to validate data flow and format handling.

How does the PKO game engine handle bone and skeleton hierarchies for character models?

The PKO engine processes bone and skeleton hierarchies through dedicated attachment and link systems. This skill documents these structures across engine layers to help debug character model attachments and validate link points.

Can I validate glTF export and import flows against the PKO client binary format specifications?

Yes, you can verify consistency between PKO formats and tooling like glTF export/import flows. This skill maps the parsing logic to support validation of imports and exports across the game client and the Rust side in src-tauri.

What is the best way to cross-reference PKO client source code across different engine layers?

The best way to cross-reference PKO client source code is to map data structures and parsing logic across the Engine, Client, and Common layers. This produces a concise mapping that supports verification and future tooling integration.

Why do my PKO model imports fail when validating bone structures in the src-tauri Rust environment?

PKO model imports may fail due to inconsistencies between the binary parsing logic and the Rust reference in src-tauri. This skill helps identify and document data structure mappings to validate bone and skeleton structures accurately.