What the game's live diagnostics sends

Everything the game's crash and usage reporting does, in plain words: when it sends, every field, what is never sent, who can see it, how long it is kept, and how to turn it off.

Last changed 13 November 2026. The short version is in Privacy.

Contents
  1. In short
  2. When it sends
  3. Every field
  4. Two example reports
  5. What is never sent
  6. Where it goes
  7. Who can see it
  8. How long it is kept
  9. What we use it for
  10. Files on your PC
  11. How to turn it off
  12. See and delete your own reports
  13. Changes to this page

In short

With the new client patch (hvmods.dll 24 or later), the game sends two kinds of report to Hunsterverse: a small health report every few minutes (frame rate, where you are, errors the game noticed) and, after a crash, a crash report. We use them to find and fix bugs in the patch, the mods and the server.

It is on by default, and you can turn it off at any time (see How to turn it off). Every line a report can hold is listed in Every field. A test on our side fails when the game sends a line this page does not list.

In the owner's words: "We aren't stealing your data, we just need to know what your client is doing in order to identify issues."

When it sends

Every field

A health report holds the lines in the first two tables. A crash report holds the first table and then the crash file the game wrote on your PC, which holds the lines in the third table. The server also keeps the time it received the report.

Both reports start with

LineWhat it is
HVTELEM 1The first line, "HVTELEM 1": the report format and its version.
kind:"health" (the regular report) or "crash".
session:A random number made new at every game start (from the clock and a tick count). It is not tied to your PC and changes every time.
seq:The report's number in this game session: 0, 1, 2 ...
time:Your PC's clock (UTC) when the report was made; for a crash, when the crash happened.
edition:HD or SD: which game client you run.
patch:The Hunsterverse client patch version (v1.24 = 124, v1.24-pre3 = 12403, 0 = an old patch without a version).
hvmods:The version of hvmods.dll (our mods and diagnostics).
character:The id number of the character you logged in with (0 before you log in). Never the name.
running:Seconds since the game started (since hvmods.dll loaded).

Health report

LineWhat it is
fps:Game steps per second over the last 5 seconds (the game's logic runs at about 30).
drawn:Pictures drawn per second over the last 5 seconds (lower than fps when the PC cannot keep up).
frames:Game steps since the game started.
flags:The mod switches the server sent (a number).
mods:The same switches as names (for example "damage numbers, damage meter").
scene:none, town or quest.
stage:The id number of the area you are in (0 when none).
quest:The id number of the quest you are on (0 when none).
connection:"open", or "closed" and the code the game gave when the connection to the server closed.
requests:Since the last report: how many requests the game sent to the game server, how many failed and how many got no answer in 30 seconds. Counts only, never their contents.
dropped:Reports thrown away while your PC was offline (the queue was full).
[problems] linesKnown problems seen this session, one per line, for example a map file the game refused (with the file's name inside the game folder, never a full path).
[errors] linesErrors since the last report (at most 16), one per line: the time, stage, quest and what failed: a game file refused, a map that fell back to Mezeporta, a server request that failed or got no answer, a disconnect.

Crash report

LineWhat it is
HVCRASH 1The crash file's first line, "HVCRASH 1": its format and version.
time:When the crash happened (your PC's clock, UTC).
exception:The Windows error code and its name (for example "0xc0000005 access violation (read of 0x00000010)").
at:Where in the game's code it crashed: the module's file name and an offset (for example "mhfo-hd.dll+0x0089f165").
hvmods running:Which of our mods was running at that moment, if any.
registers:The processor's registers at the crash (ten numbers, needed to read the crash).
frames:Up to 16 code addresses of the calls that led to the crash (module file name + offset).
stack:Up to 24 code addresses found on the game's stack (module file name + offset).
client sections:The game DLL's section names, addresses and sizes (to see whether it is our patched DLL).
[client] edition:HD (mhfo-hd.dll) or SD (mhfo.dll).
[client] patch:The client patch version, as text and as a number.
[client] hvmods:The version of hvmods.dll.
[client] client base:The address the game DLL was loaded at.
[environment] game exe:The game program's file name (for example mhf.exe).
[environment] launcher:The file name of the program that started the game (for example Mezeporta.exe), or that it has ended.
[environment] game folder modules:The file names of the DLLs loaded from the game folder (for example mhf.exe, mhfo-hd.dll, hvmods.dll, d3d9.dll). File names only, never the folder.
[files] linesThe game's own files (mhfo-hd.dll, mhfo.dll, dat/mhfdat.bin, dat/mhfpac.bin, dat/mhfinf.bin, hvmods.dll and the game program): size and SHA-256 checksum, to see whether the patch installed fully. Never their contents.
[server] flags:The mod switches the server sent, their names, and when they arrived.
[server] keys:The key-binding settings the server sent for our mods (numbers).
[server] last login:When you last logged in this session.
[mods] started:Which of our mods started.
[mods] refused:Which of our mods refused to start.
[mods] meter:The damage meter's state (in a quest or not, how many monsters and hits, where it was drawn on screen), when the meter is on.
[mods] move hits:How many hits had their move recorded, only when you switched on "Show move id" for damage numbers.
[state] scene:Title screen, town or quest (with the game's state number), whether a menu was open, and whether you were disconnected.
[state] stage:The area and map number you were in.
[state] weapon:The weapon type you had (for example long sword).
[state] quest:The quest's id, its file, class, the time left and carts left, and how long ago it started.
[state] character:Your character's id, HR and GR points. The name is removed before sending.
[state] connection:Which of the game's server connections was in use and whether it was open or closed (with the code).
[problems] linesKnown problems seen this session (as in the health report).
[events] linesThe last 50 things that happened, each with a time: logging in, area and quest changes, a menu opening, the connection closing, the mod switches arriving, server requests that failed or got no answer, game files refused, what our mods did. Messages from the server's own "Erupe" account read "server: (not sent)". Chat is never recorded.
[requests] linesThe last 30 requests the game sent to the game server: the time, the request type number, an internal handle number, and whether it was answered, failed (error code) or was still waiting. Never their contents.
[moves] linesThe last 200 moves you hit with (weapon, move id, damage), only when you switched on "Show move id" for damage numbers.
[system] windows:The Windows version number (and the Wine version on Linux or Mac).
[system] locale:Your Windows language setting and code page as numbers (for example 0x00000409, code page 1252), to explain text shown wrong.
[system] memory:Total and free memory on the PC and how much the game used.
[system] game running:How long the game had been running.
[system] hvmods running:How long hvmods.dll had been running and since when.
[system] fps:Game steps and pictures drawn per second in the last 5 seconds, and steps since the start.

The crash part is the crash file the game wrote on your PC (hvcrash-<time>.txt) with two changes: the character line has no name, and messages from the server's own "Erupe" account read server: (not sent).

Two example reports

These are made up: the shape is real, the values are not anyone's. A real crash report is longer (up to 64 KB).

A health report

HVTELEM 1
kind: health
session: 1a2b3c4d5e6f7081
seq: 3
time: 2026-11-13 12:00:00Z
edition: HD
patch: 124
hvmods: 24
character: 4321
running: 3723
fps: 30.0
drawn: 29.8
frames: 111690
flags: 0x00008240
mods: damage numbers, damage meter
scene: quest
stage: 394
quest: 21751
connection: open
requests: 120 sent, 1 failed, 0 no reply
dropped: 0
[problems]
quest-file-failed file=21751d0 error=0x01
[errors]
11:58:12Z stage 394 quest 21751: request 0x01c failed: error 0x01 (quest file 21751d0)

A crash report

HVTELEM 1
kind: crash
session: 9f8e7d6c5b4a3921
seq: 0
time: 2026-11-13 11:40:05Z
edition: HD
patch: 124
hvmods: 24
character: 4321
running: 2405
[report]
HVCRASH 1
time: 2026-11-13 11:40:05Z
exception: 0xc0000005 access violation (read of 0x00000010)
at: mhfo-hd.dll+0x0089f165
hvmods running: none (the game's own code)
registers: eax=00000000 ebx=1e77dccc ecx=00000010 edx=00000001 esi=0a3f1200 edi=00000000 ebp=0019fa40 esp=0019fa10 eip=1089f165 eflags=00010246
frames:
  mhfo-hd.dll+0x00a8ba10
  mhfo-hd.dll+0x00a8c2f4
stack:
  [esp+0x0004] mhfo-hd.dll+0x014ecee4
  [esp+0x0010] mhf.exe+0x00012a30
client sections: .text 0x00001000+0x015d12a8 .rdata 0x015d3000+0x0031a000 .data 0x018ed000+0x0d2f1000 .hvqol 0x0f2e4000+0x00000c40
[client]
edition: HD (mhfo-hd.dll)
patch: v1.24 (124)
hvmods: 24
client base: 0x10000000
[environment]
game exe: mhf.exe
launcher: started by Mezeporta.exe
game folder modules: mhf.exe, mhfo-hd.dll, hvmods.dll, d3d9.dll
[files]
mhf.exe: 1630208 bytes, sha256 3f1c0d9a5b7e2c4d6f8a0b1c2d3e4f5061728394a5b6c7d8e9f0a1b2c3d4e5f6
mhfo-hd.dll: 29667328 bytes, sha256 0a1b2c3d4e5f60718293a4b5c6d7e8f90a1b2c3d4e5f60718293a4b5c6d7e8f9
mhfo.dll: missing
dat/mhfdat.bin: 4870144 bytes, sha256 b5c6d7e8f90a1b2c3d4e5f60718293a40a1b2c3d4e5f60718293a4b5c6d7e8f9
dat/mhfpac.bin: 2316288 bytes, sha256 c6d7e8f90a1b2c3d4e5f60718293a4b50a1b2c3d4e5f60718293a4b5c6d7e8f9
dat/mhfinf.bin: 3407872 bytes, sha256 d7e8f90a1b2c3d4e5f60718293a4b5c60a1b2c3d4e5f60718293a4b5c6d7e8f9
hvmods.dll: 412160 bytes, sha256 e8f90a1b2c3d4e5f60718293a4b5c6d70a1b2c3d4e5f60718293a4b5c6d7e8f9
[server]
flags: 0x00008240 (damage numbers, damage meter), received 2026-11-13 11:00:12Z
keys: 1003=0x0152 1004=- 1005=- 1006=0x4000 1007=- 1008=- 1009=-
last login: 2026-11-13 11:00:10Z
[mods]
started: damage, meter
refused: none
meter: in a quest, 1 monster, 3 hits; drawn 812 frames, the last at 14,504 468x166 on 1280x720, 2 px dots, alpha 255
[state]
scene: quest (player state 2)
stage: 394, map 75
weapon: long sword (7)
quest: 21751 (file 21751d0), class 3, time left 60000 of 90000 (30 per second: 0:33:20 of 0:50:00), carts left 3, started 0:12:00 ago
character: id 4321, HR 999, GR points 1234
connection: lobby terminal 0, open
[problems]
[events]
11:00:10Z in town: character 4321, stage 200
11:00:12Z QoL flags 0x00008240 (from the server)
11:27:58Z stage 200 -> 394 (map 75)
11:28:01Z quest running: quest 21751 (file 21751d0)
11:30:00Z server: (not sent)
11:39:50Z mod: meter: top right, normal
[requests]
11:39:58Z op 0x01c handle 0x00010002 ok 0x00 in 40 ms
[system]
windows: 10.0.19045
locale: 0x00000409, code page 1252
memory: PC 16384 MB, free 8192 MB; game address space used 1500 of 4096 MB; game working set 900 MB (peak 950 MB), committed 1200 MB
game running: 0 h 40 min 10 s
hvmods running: 0:40:05, since 2026-11-13 11:00:00Z
fps: 30.0 (last 5 s), drawn 30.0, frames 72150

What is never sent

Where it goes

Only to our own API, https://api.hvmhfz.eclipseforge.xyz/api/public/telemetry, over HTTPS (encrypted). There is no third party, and no advertising or analytics service. No sign-in is sent with it: on our side, the character id in the report links it to your account.

Who can see it

Hunsterverse staff with the Diagnostics permission: admins, moderators and helpers (helpers have Diagnostics by default; an admin can change staff permissions). And you, for your own characters, on the Account page (see below). It is never shown publicly.

How long it is kept

30 days, then it is deleted automatically (a daily job). You can delete your own reports earlier on the Account page.

What we use it for

Then we fix the patch, the mods and the server. We do not use it for bans, advertising or selling anything, and it is never shared outside staff.

Files on your PC

The game always writes these files, whatever the setting. They never leave your PC unless you upload them yourself. They are in the game folder (the folder with mhf.exe).

FileWhat it is
hvdiag.txtThe game's own report. Rewritten while the game runs: at the start, a few seconds after something worth knowing, every minute when anything changed, and at exit. It has your character name.
hvmods.logWhat the mods did.
hvcrash-YYYYMMDD-HHMMSS.txtOne per crash. The time in the name is UTC.
hvsend-crash.txtA crash waiting to be sent. Empty when there is none.
hvmods-telemetry.datYour choice: on or off.

You can upload these files yourself on the Account page (Diagnostics) to get a plain answer about what went wrong.

How to turn it off

When it is off, sending stops at once, anything waiting is dropped before the next send, and a crash waiting to be sent is deleted. Nothing is built while it is off. The local files above are still written.

Your choice is kept on your PC, in hvmods-telemetry.dat, so the notice shows only once. Deleting that file brings the notice back.

Turning it off does not delete what was already sent. Delete that on the Account page.

See and delete your own reports

Sign in, open the Account page, "Live reports from your game". It lists every report of your characters and shows the full text of each one exactly as we stored it. The button "Delete my reports" deletes them all.

Changes to this page

When this page changes, the date at the top changes too.