feat(client): hunting-ground waypoint from the M map guide (Experimental, port-only)

Open
#3,394 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
frontend

Research direction

Start with guideMonsterTarget in foundation/ui/worldmap-guide.ts to see how a picked monster's ground point is derived, then read experimental-options.ts for how an Experimental row is declared. The minimap and M map rendering paths need tracing before any change. Done means the Experimental row exists and defaults off, a guide pick marks the point on the minimap (edge-clamped) and the M map, and tests cover the row on and off.

Written by the indexing model from the issue text.

Description

area: client enhancement priority: high

The owner chose four uses for the M map guide's unread columns (2026-11-13). Three ship in #3381 (cap gate, greyed locked rows, instance badge). This is the fourth.

What: a monster picked in the guide's Monster tab sets a hunting-ground waypoint: the picked ground's point (its wmap_monster_icon position, guideMonsterTarget in foundation/ui/worldmap-guide.ts) is also marked on the minimap, with the minimap's edge arrow when the point is off the ring, until the player picks another row or clears it.

Port-only, not native: the v1.696 client only tints the ground and draws the icon on the M map (sub_e75d50). So this ships behind an Experimental row (experimental-options.ts), off by default, and is tested with the row on and off.

Done when:

  • The Experimental row exists, off by default.
  • With it on, a guide pick shows the point on the minimap (edge-clamped) and the M map; picking a main row or another monster moves or clears it.
  • With it off, the minimap is unchanged.
  • Tests cover both settings.
Dominant language
Go
Stars
97
Forks
61
Avg merge
4h 14m
Merged PRs (30d)
913

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from opensro-dev/opensro

All issues in opensro-dev/opensro

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.