RPG Maps & Compass

Use the maps during play

Click the active game viewport first. Input belongs to its local player; typing a waypoint name does not toggle the map. Use the controls below with the world map open and its settings or waypoint prompt closed unless stated otherwise.

Customize appearance without losing progress

Open the gear and choose World Map or Minimap before changing appearance. Each map retains its own values. Use minimap colors / Use world map colors copies brightness and saturation once; later edits remain independent.

Appearance, marker visibility, minimap zoom and window placement save automatically through the settings path. World-map pan and zoom are session controls. A settings save is separate from a progress save; inspect the matching receipt in your Blueprint UI if you need confirmation.

Hide a category to filter its presentation; this does not delete saved markers. Remove selected waypoint deletes that selected entry. Clear my waypoints removes all user waypoints. Keep cursor visible is a standalone opt-in; a suite coordinator controls its own input.

Practical route: use an authored map image

1. Enable Show Plugin Content, duplicate BP_RMC_BuyerRegion into your game Content, and place your copy in the existing level. Keep the plugin example as a reference.

2. On MapSource, assign a north-up OverviewTexture. For fixed bounds, clear Use Owner Location as Center and enter the XY WorldCenter and positive XY half extents in centimeters. Set the source active and choose its priority deliberately when several regions overlap.

3. Call Start Buyer Navigation with the exact owning local PlayerController. Branch on readiness and operation results; wait for a valid player pose before showing a position or heading.

4. Check two known landmarks on opposite sides of the level. North is world +X, east is world +Y. UV (0.75,0.25) maps to XY (6000,4000) when center is (0,0) and half extents are (12000,8000). The ground trace determines Z when a suitable surface is found.

5. Create and rename a waypoint, retain its accepted GUID, save progress with the progress receipt, travel away and back, then restart the game. Confirm the same ID and name load. Verify settings independently through their settings receipt.

The existing Blueprint guide contains the saved wrapper wiring and result pins. The plugin includes the calibration scene and direct-caller Blueprint under RPGMapsCompass/Examples; the source validation project remains separate.

Practical route: generate a native capture

1. Place a Map Source Actor in your existing level, or create a Blueprint subclass of it. Inspect its MapSource component bounds before generating the overview.

2. Use automatic landscape discovery for loaded landscape terrain. For deliberately selected mesh terrain, tag the intended surfaces RMC.MapGeometry and the intended bounds RMC.MapBounds. Exclude unwanted scene meshes with RMC.MapIgnore. Discovery does not force-load World Partition cells.

3. Start with material base-color capture for opaque or masked surfaces. Call Capture Level Overview after changing topology, bounds or relief settings. Call Refresh Captured Image after surface material colors change without rebuilding terrain relief. Capture Live Minimap refreshes the player-centered image.

4. Check DetectionStatus, SampleCoverage and CapturedSceneMeshCount alongside the actual image. Confirm two landmarks, readable terrain colors and alignment with your markers. A nonempty render target alone is insufficient.

5. Legacy rendered terrain materials applies when material base-color mode is disabled. Tune CaptureExposureBias for this lit route; negative values darken bright capture output. Inspect the image again after the change.

Current native base-color orientation is verified against the northeast/southwest landmarks. Legacy lit exposure and world-map UI image proportions remain unapproved. No final gallery-quality claim is made.

Troubleshoot a concrete symptom