Stand Out Wiki
Who runs this wiki and how it is checked

About Stand Out Wiki

About Stand Out Wiki: who runs this fan site, how every code and Stand entry is checked before it goes up, and what this site refuses to publish.

Last checked 18 November 2026 · how we check

This site is a fan reference for STAND OUT, the JoJo-inspired Roblox experience by Studio Umbra: Europa that opened to everyone on 14 November 2026. It is run by players who started on launch weekend and got tired of pages that answered a search query without answering the question.

What this site is for

Search results for a new Roblox game fill up fast with pages that copy each other. Most of them list twenty codes when one works, or publish a Stand tier list that nobody could have verified in a game that launched four days earlier. This reference is built the other way round.

Who writes it

A small group of players, writing in English, on their own time. Nobody here works for Studio Umbra: Europa or Roblox Corporation, nothing on the site is approved by them, and there is no contact, no payment and no early access. It is a reference written from the outside, by people playing the same build you are, which is also why the site does not pretend to know what the next patch will change.

How a code is checked before it goes up

A code does not reach the working table because it appears on another fan site. It gets there when all three of these are true:

  1. It is attributable. We can point to the developer's own post, the game description or the developer community, not just a screenshot somebody forwarded.
  2. It is still listed elsewhere. At least two independent code trackers still carry it with a date at the top of their page, so one stale list cannot push a dead code onto our table.
  3. We can say what it pays. An arrow count, a Dala amount, or both, as published by the developer. A code with no stated reward cannot be cross-checked at all.

What that means in practice: we do not redeem codes inside the game ourselves. Nobody on this site sits in a fresh server testing every code before it is published, and no page here claims a code was tested that way. What is published is what the developer said and what several public sources still agree on, both stamped with the date we compared them.

Anything that fails the second test but passes the first is listed as unconfirmed rather than deleted. That distinction is the whole point: a code that died and a code that never existed look identical on most pages.

What a code list usually gets wrong

Four failures show up again and again on pages about a game this young, and each one is avoidable:

How a Stand entry will be checked

No Stand statistics are published yet, and that is deliberate. There are no official odds, the sample of players who have rolled enough Stands to rank them is tiny, and a tier list compiled from other tier lists carries no information at all.

The standard for the table when it exists is the same as for codes: a name, what the ability does, a cooldown if it has one, and a note saying whether it was corroborated by more than one public report or rests on a single player's report. Two independent reports get a Stand listed; one gets it listed as unconfirmed.

What this site will not do

Ten minutes on this site, in order

If you have just started the game and none of the above matters yet, this is the route most new players take.

  1. The control table on the home page. Nine keys, taken from the game's own Roblox description, plus the two mistakes new players make in the first hour: never pressing the Stand key to see what the arrow gave you, and never opening the Phone to check whether a code is redeemable before hunting for more arrows.
  2. The codes page. Try the code that is listed as working in a server you have just joined. A code that fails in an old server is not a dead code, and knowing that difference saves most players a wasted evening.
  3. The Stands page. This one explains what arrows and awakening are and where they come from. It does not invent damage numbers, because the game has not published any.
  4. The comment box at the bottom of any page. If something on the site does not match what you see in the game, saying so is the single most useful thing a reader can do here.

How these pages are written

One page answers one question. The title is the phrase a player would actually type into Google, not a phrase invented for a keyword tool. The answer sits in the first two sentences, because a reader who has to scroll three hundred words to find out whether a code works has already left.

Every page carries the date it was last checked, and that date only moves when the facts were re-checked. A page that says 18 November 2026 is saying something specific about the state of the code list, the control table or the arrow system on that day; refreshing the date without doing the work would make it a lie.

How often it is updated

Codes are cross-checked against the developer's posts and public code trackers most days while the game is this young, and the check date is printed on the codes page and under the title of every guide. When the developer patches, the control table and the arrow pages get re-read against the official description the same day. If a page has not been touched since 17 November 2026 it will say 17 November 2026: the date is never refreshed without re-reading the sources.

Corrections

If something is wrong, the fastest route is the comment box at the bottom of the page you are on, or the contact page. Corrections that come with a source, a link or a screenshot get applied before anything else, and a correction from someone who works on the game beats our reading of the sources automatically.

The wider point: a fan reference about a five-day-old game is only useful if it is honest about how little is settled. That is why half of these pages spend as much space on what is not known as on what is.

Stand Out Wiki: questions about this site

Is Stand Out Wiki official?

It is a fan site. Nobody here works for Studio Umbra: Europa or Roblox Corporation, nothing is approved by them, and the game itself is only ever played on roblox.com.

How do you decide a code is working?

By cross-checking public sources, not by redeeming it ourselves. A code is listed as working when its source can be traced to the developer's own post, the game description or the developer community, and at least two independent code trackers still carry it with a current date. We do not sit in a fresh server testing codes before publishing them, so working here means the sources still agree, and the date we compared them is printed on the page.

Why is there no Stand tier list?

No, and that is deliberate. There are no published odds and no reliable sample yet, so the Stand pages explain the system and mark everything else as unconfirmed.

How do I report a mistake?

The comment box on each page, or the contact page. Corrections that come with a source or a screenshot get applied first, and a correction from someone who works on the game overrides our reading of it.

Who pays for this site?

Nothing. There is no sponsorship, no affiliate link and no paid placement on any page, and the only outbound link on the guide pages goes to the official Roblox game page.