Sample interface with demo data

A review report, from start to finish.

This report uses demo data to show how a review team reads one. Filter the findings, pick one to see its context, and note your decision.

Review the findings Nine sample findings Go to the decision Your choice isn’t saved

People, device and file names are made up. Nothing you choose on this page is saved anywhere.

  • One report Every finding in one document
  • Signed result For every completed scan
  • Consent first Agreement shown before the scan
  • 0 automatic sanctions Your team decides sanctions

01 Overview

Sample interface with demo data

Player
demo-player-01
Date
14 Oct 2026, 21:40
Scan
–

Highest severity

Warning

A real report opens with the signed result and score.

Scan started

demo-player-01 accepted the agreement

Scan duration

This duration comes from the sample report and isn’t a promise.

By status 9 findings

  • Warning 4

    Something your team should look at, though it is not evidence of cheating on its own.

  • Info 3

    Recorded for context, and it doesn’t point to a problem on its own.

  • No issue seen 2

    This check showed no issue, but that doesn’t mean the result is “Clean”.

The report gives a result. Your team decides what happens next.

02 Findings, one by one.

The first five findings are in this list, and the other four are in the deck below. Pick a row to open its details straight away.

Sample interface with demo data

F-01 Warning

Modified file in the game folder

Category
File integrity
Time
26 min before the scan
Location
C:\Users\demo-user\AppData\Local\DemoGame\plugins\
Hash
sha256 3f9a…c21e

Why it was flagged

The file’s contents differ from the expected value for this version. This finding can’t tell why it changed.

Note

Doesn’t show who changed the file, or with what tool. An update or a repair can leave the same trace.

Related findings

Team notes

  1. demo-yetkili-2

    The system clock changed at 18:05. Let’s keep that in mind when comparing times.

  2. demo-yetkili-1

    There are 14 minutes between the changed file and the deleted file. Before deciding, let’s ask the player for their install history.

F-02 Warning

Trace of a recently deleted executable

Category
Execution history
Time
40 min before the scan
Location
C:\Users\demo-user\Downloads\
Hash
sha256 81b0…4d07

Why it was flagged

The file is no longer on disk, but system records still show a trace of it being run.

Note

Doesn’t show what the file did or why it was deleted.

Related findings

F-03 Info

Screen recording software was running

Category
Running applications
Time
during the scan
Location
System processes
Hash
None for this finding

Explanation

This is for information only and doesn’t indicate a problem on its own.

Note

Doesn’t show when recording started or what was recorded.

F-04 Info

System clock changed in the last 24 hours

Category
System settings
Time
3 h 33 min before the scan
Location
System settings
Hash
None for this finding

Explanation

Keep this in mind when reading the timestamps.

Note

Doesn’t show whether the clock was changed by hand or by automatic sync.

Related findings

F-05 No issue seen

Remaining game files match expected values

Category
File integrity
Time
during the scan
Location
C:\Users\demo-user\AppData\Local\DemoGame\
Hash
None for this finding

Explanation

This check showed no problem, but that doesn’t mean the whole report is clean.

Note

Covers only the files in this folder. It doesn’t cancel out other findings.

Related findings

A cheating result comes from the whole scan, never from a single warning.

03 The evening’s events, on one timeline.

Findings, scan steps and team notes appear in time order. To jump to a finding, pick the ID next to it.

Sample interface with demo data

Because the system clock changed at 18:05, read the times after it with that in mind. Open finding F-04

  • Warning
  • Info
  • No issue seen
  • Scan

Pick a star to open its finding.

Before the scan

  1. System clock changed in the last 24 hours

    InfoSystem settings

  2. Game files refreshed in bulk

    InfoFile integrity

  3. Trace of a recently deleted executable

    WarningExecution history

  4. Unexpected file in the plugins folder

    WarningFile integrity

  5. Modified file in the game folder

    WarningFile integrity

  6. App closed shortly before the scan

    WarningRunning applications

The scan and after

  1. Player accepted the agreement, scan started

    demo-player-01

  2. Screen recording software was running

    InfoRunning applications

  3. Remaining game files match expected values

    No issue seenFile integrity

  4. No other changes seen in system settings

    No issue seenSystem settings

  5. Scan completed

  6. Team note added

    demo-yetkili-2

  7. Team note added

    demo-yetkili-1

  8. now

    Waiting for the team’s decision

    Note the decision

04 Four more findings, from the same evening.

F-06–F-09: four more findings from the same evening. The order of the cards changes on this page only.

Sample interface with demo data

F-06 Warning

Unexpected file in the plugins folder

Category
File integrity
Time
33 min before the scan
Location
C:\Users\demo-user\AppData\Local\DemoGame\plugins\demo-dosya-02.dat
Hash
sha256 c47e…09ab

Why it was flagged

This file isn’t among the files expected for this version of the game. It’s in the same folder as the modified file and appeared 7 minutes before it.

Note

Doesn’t show the file’s contents or what it does. Some plugins write their own files to this folder.

Related findings

F-07 Warning

App closed shortly before the scan

Category
Running applications
Time
2 min before the scan
Location
System processes · demo-uygulama-03
Hash
None for this finding

Why it was flagged

The app closed about two minutes before the consent screen opened. This finding can’t tell what it was.

Note

Doesn’t show who closed the app or why. It may have closed for an ordinary reason.

Related findings

F-08 Info

Game files refreshed in bulk

Category
File integrity
Time
2 h 18 min before the scan
Location
C:\Users\demo-user\AppData\Local\DemoGame\
Hash
None for this finding

Explanation

Most of the files were refreshed together at this time. This may be an ordinary update, but it’s the starting point for reviewing later changes.

Note

Doesn’t show which tool did the refresh.

Related findings

F-09 No issue seen

No other changes seen in system settings

Category
System settings
Time
during the scan
Location
System settings
Hash
None for this finding

Explanation

Apart from the clock change, this check showed no problem.

Note

Covers only the settings that were checked.

Related findings

05 Your team decides the sanction. MYTHOS applies no sanction.

Team notes and the decision field are planned dashboard features. This section shows how they would work, and the decision covers the whole report.

Team notes Sample interface with demo data

F-01 Modified file in the game folder

  1. demo-yetkili-2

    The system clock changed at 18:05. Let’s keep that in mind when comparing times.

  2. demo-yetkili-1

    There are 14 minutes between the changed file and the deleted file. Before deciding, let’s ask the player for their install history.

Select an underlined phrase to open its finding.

Related findings

RPT-DEMO-7F3A-0412 Sample interface with demo data

Team decision

Status
Not made yet
Decision

MYTHOS doesn’t fill in this field for you.

MYTHOS applies no sanction on its own, and your team decides what happens.

Next step

Let’s talk about your team’s review process.

Let’s look at how MYTHOS could be used on your server, together with your questions.

Get in touch About your review process How does it work? PIN, consent, report

Player consent is required, and your team decides on any sanction.

Frequently asked questions