Separate categories from display styles
Rob Run’s Visuals tab puts player categories in a sidebar and the selected group of controls in the main panel. A category identifies which part of the configuration you are opening. A style selector changes a particular visual option. Keeping those two ideas separate makes the menu easier to understand when you first inspect it.
The supplied preview shows Extra Player Visuals selected. Other visible categories include Settler, Citizen, Robber, Cop, Clan Battle Member, Prisoner and Hubber. Radar has its own entry. Check the current product menu for the controls inside each category rather than assuming that every group uses identical settings.
Player Chams and Local Player Chams
The Extra Player Visuals panel contains two independently labeled chams controls: Player Chams and Local Player Chams. Each has a checkbox and a style dropdown. The example screenshot uses Cyan Glow for one and Cyan Blur for the other.
Those labels show that player visuals and local player visuals can have separate choices. They do not imply that selecting a color or style changes unrelated settings. When preparing a screenshot for support or recording a showcase, leave the relevant labels visible so another person can see which option you changed.
Off-screen arrows and readability
OOF Arrows has a category selector plus controls labeled Arrow Radius and Arrow Size. The screenshot expresses the slider values in pixels. Radius and size are different controls, so review them individually when you are adjusting the display.
For a readable showcase, change one option at a time and record a short comparison before starting a full session. Check the saved video, including its HUD and any on-screen labels. A menu that looks clear on your own monitor may be harder to read after recording and compression.
Use the correct support route
The Rob Run download guide is linked from the product page and the Downloads directory. When asking about a visual issue, include whether it happens in the menu, in gameplay or only in the recording. Send the exact setting name and a screenshot with your key hidden.
Compare changes with a repeatable recording
A useful visual comparison keeps the scene and recording conditions as consistent as possible. Capture a short baseline, change one control, then record the result. If you change player categories, style, radius and size together, it becomes difficult to tell which change produced the effect you are trying to show. A simple before-and-after comparison is also easier for support to assess than a long clip with unexplained menu changes.
Keep the game HUD, the selected menu entry and any relevant visual information in view when they are needed to explain the issue. If a recording tool adds captions or a camera overlay, check that it does not cover the part of the screen being discussed. For Nano gameplay submissions, use the recording requirements in Free Keys; an ordinary screenshot and a full gameplay submission serve different purposes.
Review the exported file as well as the live game. A problem that appears only in a recording may need different investigation from a problem you can see directly while playing. Tell support which of those cases applies. Include your recording resolution and whether the example was resized or recompressed before you sent it, because that context affects how a small visual detail can be interpreted.
Describe visual issues precisely
Separate missing visuals from moving, blurry or crowded visuals in your report. Those descriptions are not interchangeable. State whether the menu itself opens, which category you selected and whether the issue affects every relevant player or only a particular case. You do not need to diagnose the cause before asking for help; a careful description of what you actually see is more valuable than an untested explanation.
If a setting seems to have no effect, record its name and the steps you used to change it. Include the point at which you expected the display to change. Avoid repeatedly changing unrelated options while gathering the example, since that makes it harder to reproduce the starting state. Use the current Rob Run setup guide for troubleshooting rather than importing overlay instructions from another Pro game.
The preview is useful as a navigation reference even when you are not copying its configuration. It shows how Player Chams, Local Player Chams and OOF Arrows are labeled in the supplied menu. Use those labels when you discuss the product, and check your own current build if a label has changed. Clear terminology keeps both support conversations and feature showcases focused on the same control.
When comparing two recordings, label which option changed and keep their original resolution where possible. Repeated resizing can obscure fine details in arrows and outlines. Send a short original sample alongside a screenshot if the issue is difficult to explain with a still image. That gives the reviewer both the control context and the visible behavior.
Frequently asked questions
Are Player Chams and Local Player Chams the same switch?
The supplied screenshot shows two separately labeled controls, each with its own style selection.
Does the screenshot show all visual options?
No. It shows Extra Player Visuals. Other categories must be checked in the current menu.
Should I copy every slider value in the screenshot?
Treat the screenshot as a menu reference. Check the current defaults and review individual changes in your own setup.
What should I include with a visual bug report?
Describe the symptom, selected category and affected control, and say whether it appears in the game or only in a recording.
