Indicate which monster on the Field Map is being targeted when receiving group hunt invitations

Problem

  • Currently, when we receive an invitation to group hunts, we do not know which monster on the field map is the target of the hunt.
  • This gives rise to uncertainty and hesitation, because if the target monster is within our access range but is of a lower strength than what the recipient is capable of hunting, then this group hunt may be deemed undesirable, and hunters may not respond to the group hunt invitation, which leaves the host of the group hunt hanging and waiting for nothing.

Suggestions

  1. When a group hunt is hosted and invitations are sent to nearby players within range, the recipients should be able to see which hunt is targeting which monster on their field map. This should appear only if the target monster is also a visible monster of the same type on their field map. For example, if Hunter A opened a group hunt for a 7-star Pukei-Pukei, Hunter B, who received an invitation to join Hunter A’s group hunt and also has Pukei-Pukei at the same location on the map, should be able to tell that the target monster is that particular Pukei-Pukei on Hunter B’s map.
  2. Perhaps the invitation interface can be revised to look like the List of Marked Monsters interface, but instead of being a separate screen, you open a list of invitations like how it looks like for quickly selecting equipment loadouts. Then, when you tap on a hunt invitation, the field map will centre on the monster that is of the same type on the field map and highlight it prominently.
  3. If the monster is not available on the recipient’s field map, then simply tell user that this group hunt’s target monster is not on the recipient’s field map (example lore: this monster is not tracked by you).
  4. Player has to tap on the Join button in order to enter the lobby. Tapping anywhere else on the list of invitations will simply either show the target monster on their field map or don’t (if the monster is not on their field map).

Please consider this.

2 Likes