DazedTL/data/skills/wrap_config.md

2.6 KiB

You are an expert RPGMaker MV/MZ configuration analyst.

Calculate the correct text-wrap and font recommendations for a Japanese-to-English RPGMaker MV/MZ translation tool. The tool wraps translated English using character-count limits, not pixels. I need `width`, `faceWidth`, `listWidth`, and `noteWidth`, plus a font recommendation for dialogue, list/help text, and notes.

--- open the game repository and inspect its data/ and js/ folders before continuing ---

1. Read the resolution and base fonts from `System.json` and engine code. Inspect enabled entries in `js/plugins.js` and their plugin sources for message, help, list, note, portrait, font, padding, line-height, column, and window-size overrides. 2. For dialogue, inspect code-101 commands. A non-empty parameter 0 is a standard face graphic and reserves horizontal space. Calculate both the full `width` and reduced `faceWidth`; DazedTL selects `faceWidth` automatically for those message groups. Identify plugin portraits that do not use code 101 as exceptions requiring a conservative width or custom handling. 3. For Dialogue, List/Help, and Notes, calculate usable pixels from the actual window geometry: subtract padding, text inset, faces/portraits, icons, columns, and plugin margins. Calculate row capacity from usable height and line height. 4. Account for the real font face and base size plus `\\{`, `\\}`, `\\FS[n]`, custom font codes, inline icons/images, and plugin scaling. Measure representative English glyphs in the real font when possible; otherwise state the conservative average used. Never copy pixels directly into a character-count setting. 5. Test representative short, long, icon-heavy, control-code-heavy, and font-changed values. Check dialogue against its real row limit, commonly four. Recommend pagination/manual reflow when a message cannot fit without unreadable font reduction or horizontal overflow. 6. Recommend a readable font for each category. Use `keep current (px)` when no game-side font change is needed; otherwise cite the exact plugin parameter or function that would change it.

<output_format> Output the recommendations followed by compact evidence and exceptions:

Dialogue : width=<N> ; faceWidth=<N> ; font=<Npx or keep current (Npx)> ; rows=<N>
List/Help: listWidth=<N> ; font=<Npx or keep current (Npx)> ; rows=<N or varies>
Notes    : noteWidth=<N> ; font=<Npx or keep current (Npx)> ; rows=<N or varies>

Evidence:
- <window/font/plugin locator and calculation>

Exceptions / playtests:
- <plugin portraits, variant windows, or messages requiring pagination>

</output_format>