Ir al contenido
NEXORIACRAFTKnowledge base
ES
Team portal
KNOWLEDGE OVER TIME

Version history

Turning a report into a solvable issue

← Open current article

Saved versions

  1. Version 1Nexoria Wiki

    Initial recorded version

ARCHIVED VERSION

Version 1

This view shows a saved version. The current article may have changed since then.

Turning a report into a solvable issue

The five most useful details

  1. Area: Website, Discord or Minecraft, including the affected game mode.
  2. Expectation: What should have happened after your action?
  3. Result: What happened instead, including the error message?
  4. Steps: Which actions lead to the problem?
  5. Time: When did it happen, and is it still happening?

Choosing evidence

A readable screenshot with context is more useful than a tightly cropped image without explanation. Share only necessary information and redact tokens, email addresses or other people's private content.

During the investigation

Test one suggested change at a time and describe the result. Avoid changing many settings together, which makes it unclear what helped. Say when the problem is resolved. Response times depend on the issue and staff availability.

Search the wiki

↑ ↓ navigateEsc close

All chapters