Contact

Corrections

For corrections, include the page URL, the exact claim, and a public source or screenshot context. Unit stat changes are especially useful after patches.

What not to send

Do not send exploit tools, code generators, account credentials, or private server sales pitches. They will not be published or linked.

Contact channels and what happens next

Send general UTDX corrections, code reports, and source-attribution questions to hello@universaltowerdefensex.org. Send privacy requests to privacy@universaltowerdefensex.org. These addresses are for this independent guide site; they cannot restore a Roblox account, reverse a UTDX ban, grant a unit, or provide support on behalf of the game developer.

A useful correction message identifies the exact page and claim before explaining what changed. For example: name the unit, its visible level, the map or mode, the patch date, and whether a displayed number came from the in-game panel or from damage observed during a run. For code reports, include the code exactly as entered, the approximate test time, and the result shown by UTDX. That detail lets one narrow claim be checked without guessing which server version or game mode produced it.

Evidence is reviewed against the site's published UTDX methodology. A public developer announcement, a clear in-game screenshot, or a reproducible sequence is stronger than an unsourced tier-list image. Screenshots may be cropped to the relevant stat or message before use. Player names, chat messages, and unrelated account details should be removed before sending.

How submitted UTDX information is reviewed

Code status is checked separately from unit and strategy data. A reported code is tested for spelling, punctuation, expiry behavior, and reward text before the codes tracker changes. A unit-stat report is compared with the current visible roster and calculator assumptions. Strategy claims need a practical condition: the map, approximate wave range, team role mix, and the failure the change solved. A build that reaches Wave 100 on one long-loop map is not automatically presented as the best answer for every UTDX run.

Not every submission becomes a page edit. Conflicting screenshots, private-server modifiers, old patch footage, and claims that cannot be reproduced remain unverified. When evidence is useful but incomplete, the site may label the number as a planning baseline instead of presenting it as an official stat. Material corrections are folded into the affected guide during the next review pass; small spelling fixes may be handled sooner.

Messages are read for editorial purposes only. Do not attach executables, scripts, account exports, or files containing personal information. A concise plain-text explanation and one or two relevant images are enough for almost every UTDX correction. Privacy and copyright requests should identify the affected URL and the specific material at issue so the request can be evaluated directly.