Skip to content
Home · About
Independent · source-checked · fan-run

About slimerng.co.

An independent, source-checked wiki for Slime RNG players who want answers fast. Codes verified against IGN, Pocket Tactics and Beebom. Every stat shows when it was last checked.

What this site is

slimerng.co is a third-party fan reference for Slime RNG, a Roblox game by Stouts Studio. We track active codes, slime drop rates, tier ratings, crafting recipes, trading values, luck mechanics and zone progression. Everything is structured for one-handed lookup while you’re playing: large fonts, fast page loads, mobile-first layouts.

The site was built because existing community references made you scroll through long unsorted lists, hide data behind ads, or guess at when information was last checked. Each page on slimerng.co shows when its data was last verified and links back to the source so you can audit anything you don’t trust.

Where the data comes from

Three sources, in order of authority:

  1. In-game observation. Drop rates and stats are checked against the live game where possible. The game is the ground truth.
  2. The official Stouts Studio Discord. Codes and patch notes originate there. We cross-check active codes against the Discord before publishing.
  3. Community wikis (slime-rng.fandom.com and slimerng.org). Used for slime portraits (under CC-BY-SA 3.0) and as secondary cross-check for stats. See /credits for full attribution.

When a stat is contested or unverified, the page says so explicitly rather than picking a number and pretending. That is the deal: the cost of a fast wiki is honesty about what we have actually checked.

Verification workflow

We separate facts by how they were checked. Roblox public APIs cover public game stats such as visits, favorites, vote ratio and group size. Stouts Studio Discord is the source of truth for official code drops, patch language and event timing. In-game checks are used for route advice, menu labels, redemption steps and practical timing.

Community sources are used as secondary evidence, not as blind copy. When Fandom, IGN, Pocket Tactics, Beebom, PCGamesN or player reports disagree, the page keeps the uncertainty visible instead of forcing a fake final answer.

  • Codes: published only after cross-checking at least one current source and keeping expired codes visible for audit history.
  • Slime stats: indexed only when drop rate, HP, damage, tier and source data are complete.
  • Guides: written from player route decisions: what to redeem, what to chase, where to farm and when to rebirth.

Correction policy

Every important guide links to related source pages and shows a last verified date where the underlying data changes often. If a player reports a wrong code, outdated stat, broken image credit or bad route recommendation through the contact page, we check the claim against the strongest available source and update the page when the report is confirmed.

Corrections are intentionally boring: fix the claim, keep uncertainty visible, and avoid silently turning guesses into facts. For active-code mistakes, the target response is same day. For stat disputes, the target response is the next content refresh after the source is confirmed.

Who runs it

slimerng.co is operated by a single maintainer with help from the community Discord. It is not affiliated with, endorsed by, or sponsored by Stouts Studio or Roblox Corporation. All trademarks belong to their respective owners.

Editorial copy on this site is signed The Slime Desk. If you want to flag a wrong stat, suggest a feature, report a broken link, or contribute data, the fastest channels are listed on the contact page. Email reaches the maintainer directly at hello@slimerng.co; the community Discord is faster for quick questions.

The site is applying for AdSense so it can stay online without paywalls. If ads are approved, the plan is non-aggressive placement only: no popups, no autoplay, no interstitials and no ads that block the guide content. Editorial recommendations are not sold placements.

Editor’s note

Build a wiki you would actually use. Mark uncertainty instead of guessing. Cite sources per row. Update timestamps that aren’t lies. That’s the entire plan.

The Slime Desk · 2026-05-15