Article 526: Describe Observable Phenomena First
Reports should give the time, affected actions, area, whether multiple people experienced the issue together, and the reporter's device status. Players and administrators should separate observation from guesses about root causes. Lag near someone does not automatically prove their equipment caused it. Improvement after a device stops should still be checked against maintenance observations, rather than let neighborhood conflicts replace technical investigation.
Article 527: Necessary Temporary Damage Prevention
During a persistent, clear anomaly, authorized suspected devices may be stopped first or their running capabilities limited. Focus measures on actual risks instead of demolishing unrelated buildings or confiscating all materials. Players should safely stop their own devices where possible. Leave others' devices to maintainers when knowledge is lacking, rather than damage them to demonstrate responsibility.
Article 528: Keep Investigation and Testing Within Boundaries
A review may record conditions before and after shutdown and participants' feedback. Tests require clear permission for their scale, duration, and scope. Do not repeatedly enlarge devices, pile up entities, or crash the server to prove a point. Maintainers must not punish established normal projects using untested universal numbers. Announce actual grounds, scope, and a reasonable transition when adding restrictions.
Article 529: Adjust the Plan While Preserving Normal Uses
Feasible options include reducing scale, cutting pointless operation, improving shutdown methods, and changing actual usage arrangements, depending on configuration and equipment. Consider normal creative needs rather than declare every complex structure a violation. Knowingly increasing harmful load, threatening further faults, or bypassing clear restrictions requires separate investigation as malicious conduct.
Article 530: Follow-Up Checks and Explanations
Review temporary restrictions when risk changes. Adequately adjusted normal uses may resume under current decisions. Explain conditions and reasons for parts that remain disabled rather than substitute endless waiting for judgment. Public conclusions should contain only necessary operating information, not unrelated private data. Correct mistaken original judgments promptly rather than preserve unsupported blame through maintenance status.