Contact

How to reach Slime RNG Guide for corrections, code updates, and methodology evidence: plus response times and what we can and cannot help with.

Contact

The fastest way to reach me is email: hello@slimerngguide.com. I read everything sent there, and corrections jump the queue. For anything about privacy or your data specifically, use privacy@slimerngguide.com so it lands in the right place.

What to include in a correction

To fix something fast, three things help: the page URL, the specific number or claim you think is wrong, and where you saw the correct version. A screenshot, an official Stouts Studio announcement, or a repeatable in-game observation beats "I'm pretty sure it's different." Codes change constantly, so a quick "GIVEMELUCKNOW stopped working today" with a screenshot is genuinely useful, and I will update the codes page the same day where I can.

How corrections get handled

I prioritise dead codes and broken rates because those waste the most player time. If a correction affects simulator math, I update the methodology note and bump the page's "last updated" date so the change is visible rather than silent. Smaller fixes (a typo, a moved recipe) get folded into the next update pass for that page.

Response time

This is a one-person site, not a company, so expect a few days rather than minutes. I batch replies and updates instead of sitting on the inbox. If something is time-sensitive, like a code that just expired, send it anyway. Even if I do not reply, I will likely act on it.

What I can't help with

A few things land in my inbox that I cannot do anything about, and it is fairer to say so up front. I cannot recover Roblox accounts, reverse bans, or retrieve lost items. Those are Roblox's, not mine. I do not run trades, give away Robux, or sell boosts, and anyone claiming to do so "via this site" is a scam. I also cannot share unreleased rates or developer information, because I do not have any; this is a normal-account fan site.

Business and press

For partnership questions or press, the same address works: hello@slimerngguide.com. Note that tier lists and recommendations are never for sale. Independence is the whole point of the site, and a paid placement would defeat it.

What makes a correction useful

The fastest correction email includes the page URL, the sentence or number that looks wrong, and one piece of evidence. For codes, send the exact code spelling and where you saw it announced. For odds, send a screenshot or a repeatable test setup. For recipes, name the biome, machine, ingredients, and crafted result.

A message that says "this is wrong" still helps, but it takes longer to verify. A message that says "on the Graveyard recipe page, Waxie is listed as an ingredient, but this screenshot from the June 15 patch shows the third slot changed to Germy" can be checked in one pass.

Response expectations

I prioritize corrections that affect active play: broken codes, changed recipe ingredients, wrong calculator assumptions, and broken internal links. Styling issues and wording suggestions are still welcome, but they usually wait until the next content batch.

Do not send Roblox passwords, account recovery details, private Discord logs, or payment information. This site cannot help recover accounts or reverse trades. It can fix guide text when the game changes.

Now you know the site methodology - next steps

Start with the current code list

Codes are the fastest page to check before a live Slime RNG session.

Run the calculator before a long roll block

The tool turns rough targets into visible timing ranges.

Use the tier list to choose a practical target

Progression value matters more than rarity labels when resources are limited.

What to Send for a Useful Slime RNG Correction

The fastest corrections are specific. Include the URL you were reading, the exact sentence or table row that looks wrong, what you saw in Slime RNG, and when you saw it. A screenshot that includes the slime name, zone, or upgrade panel is more useful than a cropped rarity badge. For code reports, include whether the code redeemed successfully, the reward shown, and the approximate time tested because active codes can change without a game patch.

Odds, luck, and calculator reports

For an odds discrepancy, send the target rarity, visible luck multiplier, total rolls, roll speed, and whether a timed boost was active for the whole sample. A dry run is valid feedback, but it does not by itself prove the listed rate is wrong. I compare the report with the geometric probability model and look for repeated evidence before changing a denominator. Calculator bugs should include the inputs used and the output that appeared so I can reproduce the same case.

Recipe and zone reports

For a crafting correction, show the machine, zone, ingredient slots, and result screen if available. The Graveyard result has been difficult to verify consistently, so a clear result screenshot carries much more weight than a copied list. For zone changes, include the unlock requirement shown in-game and the preceding zone. This prevents a late-game observation from being mistaken for the route a new account sees.

What not to send

Do not send a Roblox password, cookie, account recovery code, private server credential, or payment information. I cannot restore deleted slimes, reverse a rebirth, grant Robux, activate a code, or moderate the official game or Discord. Slime RNG Guide is an independent fan site, not Stouts Studio or Roblox support.

I normally review well-documented corrections before broad suggestions. For details about how evidence is evaluated, see the methodology page. General and correction mail goes to hello@slimerngguide.com; privacy requests go to privacy@slimerngguide.com.