The hard part of a map bug is that the cause sits far from the symptom - a boss misbehaving because of something in the skill system, saving failing because of a player-count check. Sweeping the whole file is where a model is genuinely strong.
What you hand over decides the result, though. “Sometimes it breaks” gets nowhere.
| 언제 일어나는가 | “Only with two or more players”, “only past level 400”, “on the second boss kill” - narrow it to conditions. |
|---|---|
| 무엇을 기대했는가 | What it should do when it is working. |
| 무엇이 실제로 일어나는가 | What you actually observed - not what you think caused it. |
| 언제부터인가 | If you remember which change it started after, that is the strongest clue there is. |
And do not hand over a conclusion. “The spawn trigger is probably the problem, fix it there” gets taken at face value and something innocent gets edited. Give the symptom and let the cause be found.
보스가 특정 스킬에 맞으면 공격을 멈추고 도망가는 문제가 있어. - 다른 스킬로 때릴 때는 정상이야 - 보스가 완전히 멈추는 건 아니고, 엉뚱한 방향으로 이동해 - 언제부터인지는 확실하지 않아 원인을 짐작해서 고치지 말고, 먼저 관련될 수 있는 트리거를 전부 찾아서 보여줘. 그다음에 가능한 원인을 순서대로 정리해줘.
Do not take the proposed cause on trust. When an explanation sounds convincing, ask for the evidence and have the actual code shown to you. Long-standing triggers are usually right; the thing you added last week usually is not.
After a fix, write one line about why it happened. Bugs of the same shape always come back.