Miliastra Sandbox Knowledge Base

Problem

Miliastra sandbox and Genshin's Miliastra playfields often rely on many nodes, system parameters, and trigger conditions. When developers or players need to decide how a node is configured, why a system did not fire, or which nodes a gameplay requirement should map to, reading raw docs can miss field names, trigger chains, and edge cases. This skill connects node descriptions, official documents, and semantic search into a query workflow for locating concrete configuration evidence.

How it works

The core tools are:
- get_node_info: look up node descriptions, parameter tables, categories, and source documents; supports fuzzy matching and batch queries, useful when node names are known.
- list_documents: browse or filter knowledge base documents, useful when exact document names are unknown.
- get_document: retrieve full official documents, with batch support for multiple related docs.
- rag_search: semantic search in natural language, useful for described features or troubleshooting questions.

A typical path is: use get_node_info or get_document with node/system names; if unsure whether a document exists, run list_documents(keywords=[...]) first; if full configuration details are needed, take source_doc_title and call get_document. Responses should preserve field names, parameter names, and source documents, and clearly separate “document text” from “inference based on materials”.

Boundaries

The skill is scoped to Miliastra knowledge-base queries; it does not modify player configuration or guarantee runtime behavior. If nodes, parameters, or official conclusions cannot be found, state that instead of inventing names. For systems such as hate, shop, backpack, transporter, or triggers, query nodes and documents before decomposing requirements.