About Slime RNG Guide
Who runs Slime RNG Guide, how guides are tested, and the independence and no-affiliation policy behind every page.
What this site is
Slime RNG Guide is an independent Roblox fan site about Slime RNG by Stouts Studio. I started it because every time I wanted a straight answer: what are the real odds on an Inverted, is this code still live, is rebirthing now actually worth it: I had to stitch it together from scattered Discord messages and YouTube comments. The site collects those answers in one place, one page per question, with the math left visible so you can check my work instead of trusting a number.
Who writes this
My name is Jim Liu. I build and maintain every page here: the calculators, the guides, and the methodology notes. I have been playing Slime RNG since early 2026 on a normal Roblox account, with no developer access and no early data, and most of what is on this site comes from sessions I actually sat through: rolling for rares, timing coin farms across biomes, and logging what hit and when. When a number is something I measured, I say so. When it is a community-reported estimate or a model, I label it that way too. I would rather tell you a figure is approximate than hand you false precision.
You can find me on GitHub as OOspurs. The site runs as a static site with no accounts and no data collection beyond anonymised analytics, which keeps the focus on the content rather than on harvesting visitors.
Why these guides are different
Most Slime RNG pages online repeat the same rate tables and code lists. I try to add something you cannot get from a copy-paste: a luck calculator that turns a 1-in-100,000,000 denominator into a realistic session time, a 10,000-trial simulator that shows the unlucky tail and also the average, coins-per-minute numbers from timed runs in each biome, and tier scores built on a formula I print on the page. The goal on every page is one real question answered well, with at least one thing: a worked example, a measured rate, a farming route: that you would not have found elsewhere.
How I test
Every guide is play-tested before it goes live. The routine:
- A dedicated verification account, so the numbers reflect normal play rather than an inflated setup.
- At least 30 minutes per topic spent confirming codes, strategies, or tier placements in-game before publishing.
- Re-testing after major patches, because Stouts Studio changes rates, zones, and codes, and a stale guide is worse than no guide.
- Measured versus modeled kept separate everywhere: see the methodology page for exactly how the simulator ranges and tier scores are computed.
- No paid placement. I take no money from Stouts Studio or Roblox, and nothing on a tier list or recommendation is sponsored.
What this site is not
This site is not affiliated with Roblox Corporation or Stouts Studio. It does not sell boosts, trades, accounts, Robux, or game access, and it never will. Anyone offering those in the name of this site is scamming you. I do not run a network of sibling sites that cross-link to inflate rankings, and there are no affiliate trades dressed up as recommendations. The tools run entirely in your browser; nothing you type into a calculator is sent anywhere.
Corrections welcome
Slime RNG changes constantly, and I get things wrong. If a code died, a rate looks off, or a recipe moved, email hello@slimerngguide.com with the page URL and what you saw. A screenshot or an official announcement is ideal. If a correction changes simulator math, I update the methodology note and the page date so you can see what moved. Full contact detail is on the contact page.
How I decide what deserves a page
I add a page when it answers a real Slime RNG decision that comes up during play. A code tracker is useful because boost timing changes a session. A map page is useful because players waste time farming the wrong zone. A calculator is useful because a nice rarity label can still mean a chase is too long for tonight.
I avoid pages that only repeat the same advice with a different slime name. If a target needs its own page, the page has to explain the route, the rough time cost, the account stage, and the mistake that would make the farm worse. Otherwise it belongs in the wiki, the finder, or a table.
Independence notes
This site does not sell accounts, boosts, Robux, trades, or paid placements. I do not take a developer feed from Stouts Studio. When a guide mentions Discord, YouTube, or another public source, I use it as a cross-check and keep the actual player decision on the page in plain text.
The site is intentionally practical. A player standing in Cave or Graveyard should be able to decide what to keep, what to roll for, and whether to spend a timed boost without reading five tabs of copied filler.
Now you know the site methodology - next steps
Codes are the fastest page to check before a live Slime RNG session.
Run the calculator before a long roll blockThe tool turns rough targets into visible timing ranges.
Use the tier list to choose a practical targetProgression value matters more than rarity labels when resources are limited.
What I Actually Check Before Publishing a Slime RNG Guide
A guide starts with a player decision, not a keyword. For the odds pages, I check whether a player can turn a denominator into a realistic roll block. For recipe pages, I verify the zone, the three ingredient names, the unlock condition, and whether the crafted result is confirmed or still disputed. For progression pages, I compare the time spent farming with the account value gained. A page does not ship just because I can fill a table.
My Slime RNG test account is deliberately ordinary. I do not use developer access or private Stouts Studio data. That limitation is useful because it exposes the same problems a normal player sees: timed boosts lost to menus, a slow server cutting actual rolls per second, ingredient slimes being deleted too early, and long dry runs that make a correct probability feel wrong. When a number comes from a community guide rather than my own session, I label it as community-reported.
How corrections change the site
A useful correction includes the exact page, the game screen or announcement that conflicts with it, and the date observed. I reproduce the claim where possible. If it changes a formula input, I update the example and rerun the output. If it is a single screenshot with no repeatable context, I keep it as an open lead rather than replacing a confirmed row. This is especially important for Graveyard crafting and rare-form odds, where confident guesses spread faster than reliable evidence.
Editorial boundaries
I do not sell rankings, accept payment from Slime RNG's developer, or present a community estimate as an official drop rate. The site may earn money from advertising, but an ad does not decide which slime ranks well or which strategy I recommend. The practical downside of this approach is that some rows stay marked unconfirmed longer than players would like. I would rather leave a visible gap than give someone a polished answer that fails at the crafting machine.
The current focus is narrow: Slime RNG tools and guides that help with codes, luck, odds, recipes, zones, rebirth timing, and collection planning. The methodology page documents the math and evidence rules in more detail.