DEBUG ROOM
JP KR VN EN
HomeGame QAGraphicsFieldNegative TestingChecklistBug ReportLINK
Back to TOP

Bug Report

🧩 Bug Report Format


Bug Example

Case where the player character falls through terrain
OK Image
NG Image

Simple Report

No. Location Details Remarks Reporter Date
101 Hero’s Town
In Hero’s Town, when moving the character to the part where the 「Weapon Shop」 and 「Stone Wall」 meet,
the character passes through the ground and falls.
Tenkawa Yota 2025-09-22



Abbreviated Report

No.101 ReporterTenkawa Yota Report Date2025-09-22
Bug RankA TypeTerrain Clipping Reproduction Count3/3 (100% reproduction)
LocationHero’s Town
Summary When moving the character to the area where the 「Weapon Shop」 and 「Stone Wall」 meet, the character passes through the ground and falls
Steps 1. Enter Hero’s Town
2. Move to the area where the 「Weapon Shop」 and 「Stone Wall」 meet
3. Character passes through the ground and falls
Environment SmartPhone A (iOS 17)
SmartPhone B (Android 14)



Detailed Report

No.101 ReporterTenkawa Yota Report Date/Time2025-09-22 14:30
Bug RankA TypeTerrain Clipping Reproduction Count3/3 (100% reproduction)
LocationHero’s Town
SummaryWhen moving the character to the area where the 「Weapon Shop」 and 「Stone Wall」 meet, the character passes through the ground and falls
Details In Hero’s Town,
when moving the character to the part where the 「Weapon Shop」 and 「Stone Wall」 meet,
the character passes through the ground and falls.
Steps 1. Enter Hero’s Town
2. Move to the area where the 「Weapon Shop」 and 「Stone Wall」 meet
3. Character passes through the ground and falls
Remarks In this state, the character keeps falling until the app is restarted.
It may also be reproducible in other locations where building objects are arranged in the same way.
ROM VerA20250922_12098
Environment SmartPhone A (iOS 17)
SmartPhone B (Android 14)
Reference DocumentHero’s Town Map Specification 20250824
Attachmentsbug/screenshot/101_a.png
bug/screenshot/101_b.png






🧩 Points to Note When Reporting Bugs


Use Correct Terminology

NG In the first town
Use official names according to the specification or in-game display. Do not use nicknames or arbitrary labels

If the official name is unclear, confirm with developers or the lead to unify expressions so reports are consistent
OK In Hero’s Town



Avoid Vague Expressions

NG When opening the window, the screen becomes strange
Avoid expressions like 「becomes weird」 or 「messed up」. Instead, describe the actual phenomenon specifically
OK When opening the window, the character name and icon image are not displayed



Do Not Include Emotional Expressions

NG For some reason, the item cannot be purchased
Only record the actual facts. Questions or personal impressions are unnecessary

Extra information may cause misunderstanding or discomfort to developers
OK The item cannot be purchased

NG Why is the reward not available after completing the mission?
In other games, rewards are always given
Never use wording that blames developers

Only describe the observed phenomenon. If not asked, do not write proposals or complaints

Even when giving feedback, avoid accusatory tone and use objective, neutral wording
OK After completing the mission, receiving a reward would likely make users happier



Do Not Omit Information

NG At Hero’s Town
Situations may vary greatly depending on game progress,
so environment, steps, results, and other info needed for reproduction must be clearly stated without omission
OK At Hero’s Town after the world collapse



Record Only Facts

NG Occurs at all save points
Record only facts that were definitively confirmed
Writing assumptions as “facts” may confuse the person fixing the issue

Especially the term all should only be used when everything has truly been verified
OK Confirmed to occur at the save point in Hero’s Town



One Report = One Phenomenon

NG In the shop screen, the item price is not displayed, and the item count does not increase after purchase
Do not combine multiple defects; create a separate report for each phenomenon

If combined into one, report management becomes complicated when only part of the issue is fixed
OK Report No.401: Item price not displayed
Report No.402: Item count does not increase after purchase



Ensure “Summary” and “Details” are consistent

NG 【Summary】
The motion of Skill A stops midway

【Details】
When using Skill A, the character sinks into the ground midway and becomes unresponsive
The content is similar, but the final phenomenon description is inconsistent

Developers judge severity based on the summary, so “motion stops midway” and “sinks into the ground and becomes unresponsive” can lead to different priorities
OK 【Summary】
When using Skill A, the character sinks into the ground and becomes unresponsive

【Details】
When using Skill A, the character sinks into the ground and becomes unresponsive midway through the motion



Do not include information unrelated to “Reproduction Steps” or “Phenomenon”

NG After visiting the weapon shop, wait for about 5 minutes, change equipment, then use Skill B — the character sinks into the ground midway through the motion and becomes unresponsive
The investigation of reproduction steps is insufficient, and unrelated actions or waiting times are included

Only list the shortest necessary steps, and separate any unclear or unrelated elements
OK When using Skill B, the character sinks into the ground midway through the motion and becomes unresponsive



Convey the accuracy of reproduction steps

NG No reward is received upon completing the mission
The reproduction rate is an indicator of report reliability

If reproduction using the written steps is uncertain, the rate should be clearly stated

It is necessary to inform developers of possible procedural errors or missing information
OK No reward is received upon completing the mission
(Reproduction rate: 0/3)

NG No reward is received upon completing the mission
If the phenomenon does not occur every time, use phrasing such as “may occur” and include the reproduction rate

Since the conditions are likely not yet fully identified, make sure developers understand the accuracy of the described content
OK A reward may not be received upon completing the mission









🧩 Bad Examples of Images Attached in Reports

Unclear where the defect is located

NG Image
NG
Not obvious at a glance where the error is
OK Image
OK
Red lines make it immediately clear where the error is

Key defect not captured

NG Image
NG
The defect moment is not captured
OK Image
OK
The defect moment is captured

Capture area too narrow to understand context

NG Image
NG
Only the defect area is cropped, making it unclear where it occurred
OK Image
OK
Image shows the surrounding context of the defect

Too many irrelevant parts captured

NG Image
NG
Entire monitor plus desk and wall unnecessarily captured
OK Image
OK
Only the part showing the defect is included

Multiple defects mixed in one image

NG Image
NG
Image shows both wrong “shop name” and “price”
OK Image
OK
Image shows only wrong “price”

Image quality too poor to identify defect

NG Image
NG
Poor image quality
OK Image
OK
Good image quality

Image different from reported environment

NG Image
NG
Smartphone screenshot used for PC bug report
OK Image
OK
PC version screenshot

File size too large

NG Image
NG
Unnecessarily high resolution
OK Image
OK
Quality sufficient to identify the defect





🧩 Bad examples ofvideos attached in reports

Only shows after the bug occurs, "cause" not recorded

NG Image
NG
Video only after the bug "character becomes semi-transparent"
OK Image
OK
Video starting from acquiring the "apple," the cause of the bug

Unrelated parts recorded too long

NG Image
NG
Video includes unrelated parts (before and after the phenomenon) recorded too long
OK Image
OK
Video only includes parts related to the bug

Unrelated actions included in reproduction steps

NG Image
NG
Obtaining a "banana" is not part of the reproduction steps
OK Image
OK
Only obtaining an "apple" is part of the reproduction steps