# ManYue fictional board scenes: check positions against stated rules

Language: en
Canonical: [ManYue fictional board scenes: check positions against stated rules](<https://allluckly.cn/en/guides/manyue-fictional-board-position-evidence/>)
中文：[中文 HTML](<https://allluckly.cn/guides/manyue-fictional-board-position-evidence/>)
English: [English HTML](<https://allluckly.cn/en/guides/manyue-fictional-board-position-evidence/>)
Published: 2026-11-05T00:00:00+08:00
Modified: 2026-11-05T09:38:59+08:00
Author: Bison

Log coordinates, piece identity and turns for an invented board scene, testing one change only against rules actually stated in the work.

English translation of the [Chinese original](<https://allluckly.cn/guides/manyue-fictional-board-position-evidence/>), translated on 2026-11-05. Original publication dates, attribution, code and version notes are retained.

A depicted board and a victory claim do not establish its rules. In ManYue, compare adjacent states of an invented board scene while separating positions, actor and established rules. This involves no wagering or real-game strategy and assumes no board recognition, best-move calculation or automatic cheating verdict.

## Choose a simple scene with stated rules

Choose a completed scene of an invented game with few pieces and readable grid lines. Record the edition, chapter, participants and location of the rule explanation. A chess-like appearance does not import all real chess rules; it may be a variant. Begin with two adjacent actions rather than a full match. Without rules, log positional change but not legality. A character’s victory claim remains a statement needing relevant rules and state evidence, not an independently checked result.

## Create a fixed observation coordinate system

Establish view, board rotation and identifiable corners. In your own record, label columns A, B, C and so on and rows 1, 2, 3 and so on. State which currently visible corner you start from; these personal coordinates are not the work’s official notation. After a camera change, recover orientation through marks, seats or distinctive corners. Mark occluded cells unknown, not empty. Coordinates apply to this evidence set; screen right is not permanently one player’s forward direction without orientation checks.

## Inventory pieces beyond colour alone

Record shape, marking, side and location, using colour only as support where monochrome or similar greys may be ambiguous. Give uncertain pieces provisional labels. Identical shapes may permit only a class-distribution comparison, not individual identity. Keep reserve or removed pieces outside active-board counts. Establish the state before judging moves, excluding shadows and decorative marks from the inventory.

## Write stated rules as conditional statements

Log only rules explicitly established within completed material and cite their location. An invented rule might allow one round piece per turn to move one cell orthogonally into an empty cell. Turn, piece, direction, distance and vacancy all matter. Preserve exceptions alongside the rule. This is not a real-game rule. Leave capturing, diagonal moves or bonus turns unknown unless stated rather than filling gaps to fabricate completeness.

## Compare actual before-and-after changes

Compare vacated and occupied cells, actor and possible omitted turns in fixed coordinates. In an invented four-by-four example, column B row 2 to B3 is orthogonal one-step movement, but vacancy, turn and other conditions still matter. B2 to C3 is diagonal and not the same permitted move. Establish changes before checking conditions, regardless of confident dialogue. Omitted turns can contain several moves, so endpoint displacement alone does not prove one illegal action.

## Separate visible state from claimed outcome

Keep visible position, rule-supported conclusion and character claim in separate fields. A triumphant face does not certify an outcome where error, bluff or hidden rules are possible. Without a victory condition, check movement only. When later rules emerge, record their location and effect without pretending prior knowledge. No best-strategy calculation is needed; verify one concrete change rather than expanding the audit into a full-match analysis.

## Preserve both positions and rule references

Save supported references or an external log for before, after and rules, including orientation, cells and provisional labels. Leave the reader and return, reading the coordinates again to check that a rotated board has not been treated as the original orientation. Label hand sketches approximate rather than replacements for source detail. Recheck after source changes, restored missing pages or revisions without assuming automatic board-note synchronisation. Discuss necessary references and your own diagram instead of copying the match, respecting unreached special-rule spoilers.

## Finish one position check rather than a global verdict

Finish with coordinates, distribution, established rules, one change and unknowns. Appearance does not import real rules, distant endpoints may include omitted turns, and vacancy alone does not establish direction or turn compliance. Leave unsupported legality unresolved rather than labelling a character a cheat. Keep one useful rule question for later so the exercise helps follow the story instead of inventing an omniscient referee.

## Related guides and sources

[ManYue character identity checks: evidence through disguise and style changes](<https://allluckly.cn/en/guides/manyue-character-identity-disguise-check/>); [ManYue maps inside comics: read the legend before checking a route](<https://allluckly.cn/en/guides/manyue-in-world-map-legend-route/>).

Checked on November 5, 2026: [Apple public version information](<https://itunes.apple.com/lookup?id=6753895889&country=cn>) lists ManYue 2.0.4, requiring iOS / iPadOS 15.0 or later. Feature scope follows the [official App Store description](<https://apps.apple.com/cn/app/id6753895889>) and the installed version. This article provides reading and checking methods you can perform; it does not claim step-by-step physical-device or private-server testing. Manual records, external tools and actually visible controls are identified separately, and reading analysis is not presented as an existing automatic application feature.

