Skip to content

Dragon Ball World - Official Server, 2026

Game Rules

Last updated Oct 28, 2026

Hover any badge, rank or punishment for its meaning.Hover a rule and press the quote to copy it.

0General information

This section explains who enforces the rules and what each punishment means.

0.1Server staff

0.2Punishment types

Punishments are listed from lightest to heaviest.

PunishmentScopeWhat it means
WarningPersonLogged notice with no other effect. Counts as the first offense for 0.3.
NamelockCharacter / guildThe character cannot play until the owner gives Higher Staff a new name.
SuspensionCharacterThe character cannot log in for N days.
Character DeletionCharacterThe character is permanently deleted.
Account SuspensionAccountEvery character on the account is suspended, for N days or permanently.
Full DeletionPersonEvery character and account the person owns or has ever owned is deleted, including houses and belongings.
Identity BanPersonFull Deletion, plus the person is permanently removed from the server. New accounts are blocked by device, or deleted when there is proof of identity.

Evading an Account Suspension is forbidden (see 4.11). Playing other characters while one character is suspended or deleted is allowed.

0.3Hard offenses and repeat offenses

  • 0.3.1
    Rules marked Hard give a hard suspension. A second hard suspension on the same character results in Character Deletion.
  • 0.3.2
    Repeating the same non-hard offense within 6 months of the last punishment for it:
  • 0.3.3
    Where a rule gives a range (e.g. 5–15 days), the base punishment is the value chosen by Higher Staff within that range.

0.4Warnings

  • 0.4.1
    A person's first offense of a rule marked Warnable may be handled with a warning instead of a punishment. This is decided by Higher Staff and is not a right.
  • 0.4.2
    Rules without Warnable are punished from the first offense.

0.5Persons, accounts and linked characters

  • 0.5.1
    Rules that say "person" apply to the human player across all their accounts and characters.
  • 0.5.2
    Higher Staff may link accounts to one person by IP, device, payment data, logs or other evidence.
  • 0.5.3
    Players who share an IP or device with another real player (family, roommates) should report it to Higher Staff in advance so an exception can be added. Without an exception, shared IPs may be treated as one person.

1Account, character and guild names

Rules 1.1–1.5 apply to account display names, character names and guild names.

  • 1.1
    A name must not be offensive or vulgar.
  • 1.2
    A name cannot contain the name of a real person.
  • 1.3
    A name cannot contain the name of another player, monster, NPC, item, guild, quest or staff member.
  • 1.4
    A name cannot contain a staff rank (e.g. BN, GM, SGM, Admin, Tutor).
  • 1.5
    A name must be pronounceable. Random letter strings (e.g. "Xkqzpw") are not allowed.
  • 1.6
    If a new name is very similar to an existing one, the owner of the original name may request a name change. If Higher Staff approves, the new name gets a namelock.
  • 1.7
    Intentionally or repeatedly creating characters with names that break 1.1–1.5 → Character Deletion of those characters, up to Account Suspension.

2Communication and trading

Rules 2.1–2.6 and 2.9–2.10 mostly cover in-game chat. Outside the game, the platform's own rules (Discord, forum) apply first, except in special cases. Rules 2.7 and 2.8 are fully enforced outside the game too (Discord, WhatsApp, Messenger etc.).

3Third-party software and client modifications

  • 3.1
    PvE automation – using taskers, macros, AutoHotkey or any other software that performs game actions without the player's participation → Suspension 20–40 days Hard Warnable Hidden proof
    • Includes keyboard and mouse software where one input triggers several actions (e.g. dash macros, auto-clickers).
    • Includes automatic healing in PvE (pixel color detection, client memory reading, any tool that turns the client state into input).
    • Does not include one-to-one key remapping (e.g. binding a function key to a mouse button). This is allowed.
    • Cavebots (fully automated leveling) fall under 3.3, not 3.1.
  • 3.2
    PvP support software – automatic healing, auto-targeting, spell dodging or similar tools used in PvP → Character Deletion Hidden proof
  • 3.3
    Client modification – any change to the game client: modules, game files, sprites, shaders, visual mods, fonts, runtime injection → Character Deletion Hidden proof No expiry
    • Purely cosmetic changes are also forbidden, because they require the same file decryption and tooling as a bot module.

4Abuse, exploitation and malicious behavior

5Checks, reports, evidence and appeals

Checks

  • 5.1
    A player must answer every Higher Staff member. Ignoring Higher Staff during a check breaks the rules.
  • 5.2
    A player must answer when checked by another player or Regular Staff with standard keywords such as "recording", "are you there", "<nick> answer".
  • 5.3
    A player must follow staff instructions during a check. Instructions beyond writing in chat can only be given by Higher Staff; other instructions can be ignored.
  • 5.4
    Staff must show the proof to the suspended player.
  • 5.5
    A checked player who keeps acting (moving, attacking, healing) but does not answer within about 30 seconds is considered to be using automation (3.1, 3.2, 3.3). This is a guideline; Higher Staff may use a shorter or longer time in unusual cases.
  • 5.6
    Escaping a check by logging out, closing the client or dying on purpose counts as an admission of guilt. A death that is clearly unintentional does not.
  • 5.7
    Checking a player so often that it disrupts their game, or spamming pointless or false reports → Suspension up to 15 days Warnable

Reports and evidence

  • 5.8
    Every player may record and report others, in moderation.
  • 5.9
    Serious situations (e.g. messages and photos from outside the game) are handled only by SGMs and Admins.
  • 5.10
    Appeals
    • A suspended player may appeal once, up to 7 days after the suspension.
    • The appeal is reviewed by a staff member of a higher rank than the one who issued the punishment (e.g. a Banner's decision is reviewed by a GM or above).
    • Appealing again after a denied appeal may extend the suspension.
    • Rules marked No appeal cannot be appealed: 2.7, 4.7, 4.8, 4.9, 4.10.
  • 5.11
    Recorded proof expires 48 hours after the offense. Rules marked No expiry are excluded: 2.7, 2.8, 3.3, 4.1, 4.7, 4.8, 4.9, 4.10, 4.11, 4.13.
  • 5.12
    Screenshots must:
    • show the entire screen, including the taskbar;
    • show the whole chat window when context matters (e.g. insults), in several screenshots if needed;
    • be unedited and uncropped;
    • be legible.
  • 5.13
    Recordings of a suspected cheater must:
    • be unedited;
    • show a chat message with the player's nickname and check keywords such as "recording", "answer me", "checked";
    • show that message readably;
    • show the ignore list during the video.
  • 5.14
    Evidence must stay available for at least 7 days after the suspension. SGMs and above may uphold a suspension even if the evidence disappears.
  • 5.15
    Reports are posted only on the forum (blacklist), unless they expose another player's private data, sensitive information, or information that could harm the server.
    • 5.15.1
      High-risk bugs and abuses are reported directly to Higher Staff or Technical Support.
    • 5.15.2
      Low-risk bugs may be reported on the dedicated Discord channel. This is encouraged.
  • 5.16
    Reports with no valid proof or describing no rule break are denied without further review. Repeating them falls under 5.7.

6Extraordinary cases

  • 6.1
    Admins may change the rules, suspend a player for any number of days, or lift a suspension without justification when they consider it necessary.
    • This is reserved for edge cases the rules do not handle well, e.g. a player actively harming the server or repeatedly evading suspensions.
  • 6.2
    Any player may report a Higher Staff member who breaks the rules or punishes against the rules. Such reports go directly to an Admin.
  • 6.3
    Rollbacks and compensation after bugs or server problems are decided case by case, after investigation and log review.