Where the build data comes from
Automation watches official Netmarble pages, a credited public community sheet, and revision-pinned Wiki facts. It imports stated fields; it never invents one.
Automatic publish rule
The scheduled job imports only deterministic, structured fields from the credited public sheet: role, awakening recommendation, skill priority, stat priority, score, and rotation. Every published record carries the source sheet, fetch time, editorial change date, and revision hash.
Image-only cells, ambiguous merged fields, unlicensed media, unsupported drop routes, and tier lists remain unpublished until a structured source can identify them safely.
Database attribution
The character, Artifact, equipment, and Monsterling name-level library is derived from revision-pinned factual fields on MONGIL: Star Dive Wiki. The source is attributed under CC BY-SA 4.0. No game images are mirrored.
Current coverage: 28 characters, 5 Artifacts, 9 equipment pieces, and 165 Monsterling names. 20 Monsterlings also have effects from the credited current community guide. Name-only details remain noindex.
Build verification rule
An indexable recommendation needs a complete parsed record, a source trail, a recent source changelog, and a successful daily fetch. “Source current” means the site matches the live sheet; it does not claim an independent damage test in the game client.
Player problem test
Every indexable page must help a player make a decision or complete an action: what to equip, how to rotate, where or when to obtain something, what changed, or what to do next. A name without supported mechanics remains available in the browsable Codex but stays out of search results until it can answer one of those questions.
How guide requests become topics
The daily demand job combines approved public community questions, official Known Issues, anonymous site-search misses, guide-request submissions, and Search Console query aggregates. It groups repeated intent and entity combinations, then assigns a candidate score from recurrence, source diversity, and search demand.
The output is an editorial queue, not an automatic article generator. Private submissions are never committed to the public repository, and no community content is sent to a language model. A source-backed human review is still required before a guide can be published.
Blocked inputs
- game client files
- closed-test material
- NDA material
- leaks
- private Discord
- datamined files
- player account data
- automatic build recommendations