About
About Sell Fries Wiki
Sell Fries Wiki is a one-person reference for the Roblox experience Sell Fries! [Anomaly]. It exists because the details that decide a run ā roll odds, anomaly counters, upgrade payback ā were scattered across posts of different ages and partly wrong. Below is who publishes it, how each number is checked before it reaches a page, and what happens when something turns out to be incorrect.
Last checked 2026-10-18
The site is not a news outlet and not a community wiki with open editing. It is a maintained reference: every table has a date on it, and that date means someone opened the game or re-read the relevant source that day.
If you only want the practical part, start with the class odds and tier ranking or the full shift walkthrough. The rest of this page explains the editorial standard behind them.
Who
One operator, no newsroom
This site is written, built and maintained by one person. There is no editorial team, no contributor programme, no advertising department and no community moderators. That is a deliberate constraint rather than a stage of growth: a table of roll odds can only be kept honest if a single person is accountable for the last check, and every page shows the date of that check so you can judge it yourself.
The project is independent in the plain sense. It was not commissioned by the developer, it is not part of any Roblox creator programme, and it has no official data feed. Nothing on this site was supplied by Pharting or by Roblox Corporation, and nothing here has been reviewed or approved by either of them. The game name, the place ID and the developer name are used to identify what is being described.
The scope is narrow on purpose: one game, one reference. Pages cover the seven classes and their odds, the anomalies that begin after 8 PM, the kitchen upgrade order, a complete shift walkthrough, a planner for spins and income, and dated changes since launch. A question that falls outside that scope gets a short answer by email, not a new page.
There is no revenue model. No advertising network is installed, no affiliate link is placed, no rank or placement is sold, and no account is created. Hosting is on a free tier. If that changes, it will be stated on this page before it happens, not discovered by a reader through a cookie banner.
Method
How a number earns a place on a page
Every field is traced before it is written. The same four rules apply to odds, prices, anomaly behaviour, dates and statistics, and they are applied in order: a higher tier always overrides a lower one.
| Tier | What it covers | How it is used |
|---|---|---|
| Roblox public endpoints | Place and universe identity, creator, badge award counts, live player count | Treated as authoritative on its own. A value that comes from here does not need a second opinion. |
| In-game text and developer posts | Mechanics as the game states them, patch notes, badge names | Quoted with a date. Used to confirm that a change is real and to date it. |
| Two or more independent guides | Roll odds, upgrade prices, anomaly counters, spawn behaviour | The minimum for anything the API cannot answer. Agreement must be on the exact value, not on the general idea. |
| A single source | Anything reported once | Held as provisional in our own notes. It can inform a sentence, but it does not drive a recommendation or a table row. |
When two sources of the same tier disagree, the more recent one wins, and if the disagreement matters we go into the game and check. If it still cannot be resolved, the field is marked unverified in our internal data and left off the page. A dash in a table means no source listed a value, never that the game has none.
This is also why some obvious-looking numbers are missing. Visits and favourites are not exposed by any endpoint reachable from here, so they are not printed. The event currency name differs between sources, so it is described rather than named. The launch date is only known from the earliest official badge, which is why it is labelled approximate.
What gets removed, not softened. Unverified codes, guessed gem prices, invented item stats and model-recalled patch dates never reach a page. A shorter page is always preferred to a confident one that is partly fiction.
Corrections
Corrections start within 48 hours
If a number here is wrong, email [email protected] with the page address and what you saw in the game. The target is to have the page re-checked and, where needed, changed, with work starting within 48 hours of the message being read. That clock starts at reading, not at publication, and it applies to corrections rather than to feature requests.
A correction changes three things at once: the table or paragraph itself, the last-checked date printed on that page, and ā when it alters a recommendation ā an entry in the dated change log. The log entry states what was wrong, so a reader who acted on the old number can see it.
If a report turns out to be mistaken, the page stays as it is and you get a reply explaining which source was used and why. Reports are not silently discarded, and a disagreement is not treated as an argument to be won.
Requests to remove an image or a passage are treated as time-sensitive and handled before ordinary corrections. The full route for those, and what to include, is on the contact page.
Limits
What this site will not do
A guide for a game with a large young audience attracts requests that have nothing to do with guides. These are the ones that are refused outright, at any price.
- No boosting, carries or service runs. Nobody plays the game on your behalf, and no page sells a guaranteed win.
- No account or item trading.Account sales break Roblox's own terms and put the buyer's account at risk.
- No cheat, exploit or script distribution. That includes auto-farm tools and anything that manipulates the client.
- No gem or currency selling. No link to a reseller is placed, sponsored or traded.
- No invented codes. If the game has no working codes, the codes page says so and explains how that was checked.
- No paid placement. Rank order is an argument about the game, not inventory.
Build
How the site is put together
The site is a static Next.js export served from Cloudflare Pages. There is no database, no login, no comment system and no form, so a visit produces exactly one kind of record: the request log at the edge. That is also why a wrong number cannot be fixed by a comment ā it has to arrive by email.
Because every page is generated at build time, pages load without a round trip to a server and work on a slow connection. The only third-party embed is YouTube, and it is loaded only after a click. Details of what is and is not recorded are in the privacy policy, and the rules for reusing this material are in the terms of use.