RO Codex aims to give players clear, consistent, and actionable information about ROM Eternal Love. These standards explain where published facts and explanations come from, how pages qualify for search, and what players should verify in game.
Catalog records and editorial articles follow different paths, but both must produce a page that answers a real player question. A record is not treated as useful content merely because it has a name and a public URL.
-
1 · Establish the facts
Published game records supply identities, values, requirements, and relationships. Unresolved names or ambiguous links are treated as gaps, not displayed as confident answers.
-
2 · Add player context
Related effects, targets, costs, sources, progression, and conditions are brought together so a player can understand when a value applies and what to do with it.
-
3 · Explain and demonstrate
Guides and formula references add original explanation, stated assumptions, ordered mechanics, and worked examples. They separate a general method from a result that applies only to one setup.
-
4 · Qualify for publication
Pages with too little resolved information are kept out of search. Published pages retain their limitations, while reproducible reports are used to correct the underlying relation or explanation.
Effects are presented with their conditions, targets, restrictions, costs, and progression requirements whenever those details are available. Raw identifiers are not substitutes for understandable mechanics.
Build comparisons should use the same character state, target, assumptions, and activation conditions. Qualified bonuses remain attached to the race, size, element, class, skill, or equipment they affect.
Incomplete or ambiguous entries are not presented as settled facts. Pages may be withheld from search indexing until they contain enough resolved information to be useful to players.
Reproducible reports are reviewed against the affected page and observable in-game behavior. Confirmed issues are corrected at their source instead of being hidden by unsupported display text.
- Friendly names and complete gameplay qualifiers instead of unexplained technical references.
- Stable public links for catalog entries whenever the underlying game identity remains the same.
- Guide examples that state their assumptions and avoid inventing unavailable values.
- Clear limitations when server behavior, timing, regional differences, or undocumented rules may affect a result.