No Results Found Bug Report Mail Template

This page is the bug report template players can copy when they need to mail Zzangdol Games. The official inbox is zzangdolgames@gmail.com. The request was published on Steam news after the 14 August 2026 launch. The Bug Reports page mirrors that request and explains what not to send. This file is the actual template, with the lines that produce useful replies from a small studio’s inbox.\n\nIf you came here because your game crashed, your memo will not save, your Japanese build still shows wrong-language buttons, or your Mac build misbehaves on a current Patch 1.2 install, this is the file. If you came here looking for the community address, the wiki blanks, or Makor’s job title, the Hidden Community and IDs and Roles pages are the right doors. The developer asked for bugs, not for a second QA pass on the mystery.\n\nThe template below is intentionally short. A long mail to a small studio gets skimmed. A short mail with the right fields gets answered. The fields the developer needs are: OS, language, build number, fullscreen or windowed, the symptom in one sentence, and a screenshot. Optional: a save file if the bug is reproducible from a fresh load. Optional: a Steam client log if the crash left one. Skip: your opinion on Accuse versus Connive.\n\n## The template, ready to copy\n\nSubject: NRF bug - short symptom\n\nTo: zzangdolgames@gmail.com\nFrom: your mail\n\nBuild: No Results Found, version e.g. 1.2\nPlatform: Windows 10 64-bit / Windows 11 / macOS 14 / etc.\nStore language: Korean / English / Japanese / Simplified Chinese / Traditional Chinese\nDisplay: fullscreen / windowed\nGPU: model, optional but useful\n\nWhat I did:\none paragraph describing the steps that produce the bug\n\nWhat I expected:\none sentence\n\nWhat happened:\none sentence\n\nScreenshot: <attached>\nSave file: attached if relevant, location %USERPROFILE%/AppData/LocalLow/JJangdolGames/NoResultsFound\n\nNotes: anything else that helps - e.g. I updated past 1.0.2, Japanese client\n\nThat is the whole mail. Two paragraphs of symptoms. One screenshot. The OS line. The build line. The language line. The developer can read this in 30 seconds and reply with a useful answer.\n\n## Why these fields matter\n OS matters because the same bug looks different on Windows 10 and Windows 11. The Mac build only exists after Patch 1.2, so any Mac bug is implicitly a 1.2-plus bug. Linux is not a platform, so do not mail Linux bugs as platform bugs.\n\nLanguage matters because leftover untranslated UI after Patch 1.1 was a known issue. If the bug is a wrong-language button on a current build, naming the store language is the difference between a fix and a guess.\n\nBuild matters because the same bug can be fixed in 1.1, regressed in 1.2, or introduced in 1.2. The version number tells the developer which changelog to read before replying. The Steam client shows the build number under Properties > Updates > Installed version. The Mac build shows it under the app’s Get Info panel.\n\nFullscreen versus windowed matters because Patch 1.2 added windowed resize but kept the internal resolution fixed. Display bugs that only appear in windowed mode are a different class from display bugs that only appear in fullscreen.\n\nGPU is optional but useful. Intel UHD Graphics 620 is the Steam minimum. AMD and NVIDIA users sometimes hit different shaders. Naming the GPU shortens the back-and-forth.\n\n## What to attach\n Screenshot. The Steam overlay captures to a folder. The Windows Snipping Tool works too. Save the file as a PNG. Do not paste it into the body of the mail as a giant inline image; the developer is reading on a phone half the time.\n\nSave file, only if the bug reproduces from a fresh load. The save location on Windows is %USERPROFILE%/AppData/LocalLow/JJangdolGames/NoResultsFound. The Mac save location is similar under ~/Library. Send the JSON file, not the whole folder. Do not send saves that contain personal notes; the save file is JSON and is human-readable.\n\nSteam client log, only if the crash left one. The log lives in Steam > Help > System Information. Attach the text file, not a screenshot of the text file.\n\n## What not to send\n Puzzle answers. The community address. Makor’s username. Orca’s position. The true-nature blank. Pallidum, sealed slate, pretext, and the rest of the wiki fill-ins. Those are investigation tokens. They sit on Hidden Community, IDs and Roles, and Wiki Blanks. The developer asked for bugs, not for a second QA pass on the mystery.\n\nHint-mode requests framed as critical bugs. Players still want manual chat advance, a post-credits wiki, and more languages. Those are design asks. Log them as feedback if you want. Do not subject-line them as critical bugs unless the client actually throws.\n\nKeys for a free game. Anyone selling you a key for a free Steam title is wasting your time. Mail about those belongs in the trash.\n\nLong essays. The developer reads a two-paragraph mail. They do not read a four-page essay. The first paragraph is what you did. The second paragraph is what you saw. That is the whole mail.\n\n## When to mail at all\n Mail if your build is on the current version and the bug reproduces. Mail if the bug is on a Mac install after 1.2. Mail if you have a screenshot. Mail if your Known Issues page does not already name the bug.\n\nDo not mail if your build is older than 1.1 and your bug is in the 1.0.1 list of fixes. Update first. The 1.0.1 fixes are documented. Mail about them after a current build is noise.\n\nDo not mail if your bug is a Steam client issue. The Steam client has its own support. The Steam overlay, the Steam download, and the Steam library are not bugs in No Results Found.\n\nDo not mail if your bug is a translation complaint that the wiki can answer. The Languages page lists the five supported UI languages. If you wanted a sixth, the Known Issues page is the file. The developer has not promised a sixth.\n\n## What the developer actually answers\n The developer answers with one of four responses.\n\nFirst, a fix in the next patch. Steam news for app 4911390 is still Patch 1.2 as of the snapshot this wiki checked. New patches land when the developer ships them.\n\nSecond, a known-issue note. The Known Issues page is the wiki file that mirrors what the developer has acknowledged.\n\nThird, a request for more information. Reply with the additional file or screenshot. The developer is small. They triage by mail.\n\nFourth, no reply. Small studios do not always reply to bug mails. That does not mean the mail was wasted. It means the developer is busy. The wiki still mirrors the public Steam news items.\n\n## How this page sits next to Bug Reports\n The Bug Reports page is the policy file. It explains what to send and what not to send. This page is the template file. The two pages cross-link. A player who wants the policy reads the policy page. A player who wants the template reads this page. The wiki treats them as the policy-and-template pair.