Scenes and visual explanations
Paint a board-game path in Aquarell: clarify spaces, branches and symbols
Paint a fictional walking-game board, checking space count, sequence, branches and labels alongside illustration.
On this page
A beautiful forest does not make a board-game route clear. Design a fictional one-page path with a start, twelve stops, finish and one branch before scenery. This is a hand-painted information illustration, not an automatically connected or executable game.
Write the short rules before drawing
Define start, finish, direction, count and one branch rule first. On an approximately 1900×1500 px canvas, separate path, spaces, scenery and labels. Place twelve numbered stops and test the smallest numeral before decoration, avoiding symbols that introduce unexplained rules.
Curve the route without ambiguous crossings
Connect a few broad turns from lower-left start to upper-right finish, avoiding unnecessary crossings. Keep spaces visibly related along the route. Resolve any unavoidable crossing explicitly. Trace the path with a finger and repair hesitations before scenery; sequence is the core of the board.
Size spaces for their content
Use consistent ordinary-space shapes and modestly distinct special spaces. Reserve room for the longest message and separate numbers from icons. Improve small-size legibility through quieter background and larger numerals. Count all twelve spaces independently, checking copied numbers against the stated rules.
Explain branch destination and return
Use a clear branch instruction, distinct line or icon cues beyond colour, and an explicit rejoin point. Strengthen a decorative-looking connection or shorten a competing second main route. Keep the branch rule simple before adding extra actions such as reversal or swapping.
Include only symbols used on the board
Choose two fictional symbols and short explanations, matching their shapes exactly wherever used. Check the actual special spaces and omit unused legend entries. Separate the legend spatially from the route so its examples do not resemble additional playable spaces.
Keep scenery behind the route
Add a few subdued tree, lake or hill masses outside the route. Keep them away from numbers and avoid landscape lines that resemble path connections. Resolve tangencies explicitly. Preserve quiet space when the sequence works; the board should remain understandable without the artist explaining it.
Run a rules-only walkthrough
Hide scenery and trace start, numbered stops, branch and finish while reading every number. Check duplicates, missing numbers and ambiguous returns. Restore scenery to detect new confusion. Separate rules verification from visual polish: a neat board may still lack a crucial arrow.
Walk both branches
Trace each branch separately from the same fork to its rejoin, recording space numbers. Fix skipped instructions or paths ending in decorative unnumbered shapes. Both alternatives need checking even when the first works. A short return cue may help without implying an automatic rules engine.
Read numbering in reverse
Read numbers backward from finish to start against the twelve-space list to catch skipped values. This is proofreading, not a rule allowing reverse play. After corrections, recheck nearby arrows and trace the normal direction again, using editable labels to avoid repainting scenery.
Label the exercise and retain an editable master
Keep rules-only and finished versions with editable numbering. Describe it as a fictional route exercise requiring separately supplied pieces and rules. Next, expand twelve stops to sixteen and rebuild route spacing before scenery, recording where crowding begins for future numbered illustrations.
Related tutorials and sources
Routes and space, Sequence and visual instructions.
Checked on October 27, 2026 against the official Aquarell App Store listing and Apple’s public version lookup: current version 1.0.6, requiring iOS / iPadOS 15.0 or later. This exercise uses public brush, colour, layer and saving capabilities. Geometry, materials and motion cues are drawn manually; dimensions, palettes and simplified forms are suggestions. Check controls in your installed version. Keep the native project for editing and use PNG for previews. No step-by-step physical-device testing is claimed.