Mini-Map does not show all ranges.

[BearsMan]

https://gyazo.com/eff267f1f358e28d5ba38f3077c11a0e

It only shows EoE (Spirit Range at 2500) and HoS range if you have HoS or Vipers in the build.

[3vcloud]

@claude the latter issue is by design, but the former isn't. Is there some sort of vertices limitation that would prevent other ranges from being drawn, or is this more likely user error?

[claude]

Claude finished @3vcloud's task in 2m 56s —— View job

---

Investigating Mini-Map Range Rendering

• Read CLAUDE.md for repo guidelines
• Find mini-map range drawing code (GWToolboxdll/Widgets/Minimap/RangeRenderer.cpp)
• Check for vertices limitations or conditional rendering logic
• Answer the question

---

Short answer: no vertices limitation — almost certainly user configuration.

Here's why:

How the vertex buffer works

RangeRenderer inherits from D3DVertexBuffer. In Initialize() (RangeRenderer.cpp:252):

vertices.reserve(circle_points * (circles_.size() + 4) + 6);

The buffer is dynamically sized — it allocates exactly 192 vertices × (user_circles + 4 special circles). D3DVertexBuffer::UploadVertices then calls CreateVertexBuffer(byte_size, ...) with that exact size, with no hard cap. D3D9's MaxPrimitiveCount is ~16 million, so the device limit is nowhere near a problem.

The Render() loop uses an offset counter that advances by exactly circle_points = 192 per circle whether drawn or skipped:

for (const auto& c : circles_) {
    if (!c.visible || (c.color & IM_COL32_A_MASK) == 0) {
        SkipCircle(offset);   // offset += 192
    } else if (!c.on_target) {
        DrawCircle(offset);   // draws + offset += 192
    } ...
}

This is consistent with Initialize, so there's no offset drift or truncation for any number of circles.

Why only Spirit range would show

The five default circles all have visible=true and full alpha (0xFF______), so they should all render. The only way to end up showing only one circle is:

1. Settings file has range_circle_count=1 — if the user (or a previous GWToolbox version) wrote a settings file with only 1 circle entry, LoadSettings clears circles_ and re-populates it with just that one. The has_new_format branch (RangeRenderer.cpp:44) does circles_.clear() before loading, so defaults are discarded.

2. Other circles have visible=false or alpha=0 — they silently skip rendering.

3. The user previously deleted circles in the settings UI (the x delete button), leaving only Spirit, and those settings were persisted.

Recommendation for the reporter

The user should open Minimap settings → Ranges tab and verify the circle list. If circles are missing, they can use "Restore Defaults" to reset to the 5 standard circles. If the list shows all 5 but they're still invisible, check the color alpha on each one.

This is almost certainly user configuration, not a code bug.