Bring back the lobby tab's report button as a player alert for moderators

Open
  • Is something wrong?
#62 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
c
Domain
backend, game-dev, reverse-engineering

Research direction

Start with static inspection of the ReVault script DLLs, using evrcat and the Quest symbols or PC graph in resolve_next_node to locate the lobby player-view button and its visibility gate. Trace the press through the script node and native handler, checking dispatch_event and fire actions only for the later live verification. Done means the report reaches nakama with reporter, target, match, and time, and repeated reports create a moderation marker.

Written by the indexing model from the issue text.

Description

backlog enhancement

The arm computer's LOBBY tab used to show a report button on a player's view, before the official shutdown. We want to bring it back as a lightweight report. Pressing it would send an alert about that player to the game service. When several people report the same player, the game service creates a marker for moderators to follow up.

To find out first (statically, before any live run):

  • which script draws the button on the player view (lobby tab) and what gates its visibility, i.e. which feature flag, config or expression;
  • what pressing it calls in the game client: the script node, then the native handler, then which SNS message (if any) it sends today;
  • whether the game client already has a report message to the game service that we can receive in nakama, or whether the runtime must redirect the press to a new message.

Then: nakama receives the report and logs it (who, about whom, match, time). Multiple reports about one player raise a marker in the moderation tooling.

Owner, 2026-10-02: "for after we get all this working" (early quit lockout, social).

Tools that apply: ReVault script DLLs (Quest lib<hash>.so with symbols, PC graph in resolve_next_node); evrcat for hashes; the scenario build's dispatch_event / fire actions for a live check; a screenshot per step.

🤖 Generated with Claude Code

Dominant language
C++
Stars
2
Forks
5
Avg merge
5h 9m
Merged PRs (30d)
949

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 EchoTools/nevr-runtime

All issues in EchoTools/nevr-runtime

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.