Contact

Send a correction

Use this page for code reports, source corrections, and changed game mechanics. The fastest useful report includes the code text, what the redeem box returned, whether you tried a fresh server, and a source link if one exists.

What makes a useful report

A good code report is narrow. Send the code spelling, the reward you expected, the exact message from the redeem box, the server age if you know it, and whether the code had already been claimed on that account. If you saw the code on a guide page, include the URL instead of a cropped screenshot.

A mechanics correction should say what changed in play. For example: the Shade reached the lane earlier than the guide says, a turret spot lost line of sight after a map update, or a weapon stopped killing Brutes in the same window. The best note connects the correction to a player decision: redeem timing, buy order, class choice, target priority, or map position.

Review path

I check corrections against public sources first, then against a fresh server when the claim affects code status or gameplay advice. If two sources disagree, the page keeps the narrower claim until the result is repeatable. That is why one verified code stays active while copied code names stay out of the table.

Corrections do not need to be polished. A short note with the page URL and a concrete observation beats a long message that tries to rewrite the whole guide. If the report changes a live decision, it goes into the next edit pass before lower-priority wording cleanup.

What not to send

Do not send passwords, Roblox account details, account recovery information, private Discord screenshots, exploit scripts, paid script links, or screenshots that identify another player without permission.

This contact route cannot grant rewards, recover Roblox accounts, reverse purchases, or speak for Nectarforge Studios. Use official Roblox support for account issues and the developer's official community channels for game support requests.