Editorial Policy

I write each page for one question. A codes page does not also try to be a weapon database. When two sources disagree, I show both dates instead of averaging them into a cleaner story.

Source order

• First: a Roblox-hosted field. That includes the games API, the votes API, the passes API, the groups API, the badges API, and text rendered on the official experience page.
• Second: a named article or a second community site, quoted with the date I read it. Those claims stay labeled. They are not upgraded to “confirmed” because several blogs copied the same sentence.
• Third: a gameplay video. I use it as a view of the HUD, not as a stat table, unless the video shows the number on screen and I say so.
• Never: a guessed keybind, a guessed boss name, a version number the API does not return, or a damage cell copied from a single wiki and then stripped of its warning.

Corrections and freshness

The updated date on each page is the day I last checked the sources for that page, not the day the game itself patched. Email contact@surviveamillionmonkeys.com with the URL and the better source. I would rather delete a number than defend it. Who is responsible for the site is on about.

Correction record: 9 October 2026

Added Beebom’s new 5MVISITS report without claiming an independent redemption. Removed unsupported boss archetypes, corrected the source for enemy behavior categories and separated role recommendations from measured damage. Removed historical counters whose original API capture was not retained. Creation time remains labeled as a record timestamp, not a verified launch announcement.

I do not publish exploit scripts, and I do not accept payment to raise a weapon or a class on the tier list. The tier page says it is community opinion for that reason.