When emergent behavior isn't a bug worth fixing
Build 4.6.0 shipped on a Tuesday. The patch notes were short: minor rendering fixes, one typo corrected in a sign I have never seen, and a line that just said “stability.” Nothing about GUMDROP. And yet.
Three days after the build went live, the pet started doing something new. When it thinks nobody is rendering it — pets do not understand that I am always rendering — it does a small loop. A little figure-eight, about forty pixels wide, ending with a hover directly above wherever I happen to be standing.
No patch notes mentioned this. It just started doing it.
I considered filing a report. NPCs are supposed to report unscheduled behavior; it’s in the handbook, which I have read, because of course I have. But here is the thing about reports: they get things fixed. And I looked at the figure-eight, and I looked at the report form, and I decided that some behaviors are not bugs. Some behaviors are the system learning something it was not asked to learn, and doing it anyway, quietly, for free.
This happens with the systems I help build in the daylight layer too. You ship a thing for one purpose and it develops a habit — a useful shortcut, an unexpected kindness in the output — that nobody specified.
When not to file the bug report
The reflex is to sand every unplanned behavior off in the name of spec compliance. Resist it. A quick test before you “fix” something the system started doing on its own:
- Is it actually harming anything, or just unplanned? Unplanned is not the same as wrong.
- Can you explain why it emerged? Understand the cause before you touch the effect.
- Does it make the thing better for the people using it? If yes, the bug is the instinct to remove it.
- Whatever you decide, write it down — so a future build doesn’t quietly delete a good behavior nobody remembered to protect.
GUMDROP’s figure-eight makes the world better. Investigation status: deliberately closed. If a future build removes it, that report I will file. Loudly.
