Editorial Policy

This site publishes at most one original article per day. That limit lives in the code, not in a goal.

Who answers for what is here

Every article is bylined by Gustavo Cantino (Guga028), and the editorial responsibility for what this site publishes is his. There are no anonymous articles here and no invented authors.

Signing is not the same as writing every sentence. What each text claims, and on what basis, is described below — no fine print.

How an article is made

1. Topic. It comes from a question somebody actually asked — a video comment, a forum thread — and priority is how many times it was asked. We do not invent topics to fill a calendar.
2. Sources. Before the text, the pages that support the subject are actually fetched and recorded with the URL and the date they were fetched. Only first-hand sources count: Roblox itself, the game page, the official forum, the developer's official profile. A site that merely repeats the information is not a source.
3. Text. Since 28 September 2026 the text is written in an editing session, from those sources, with AI assistance. Before that it was generated automatically; articles published until then stay marked as such, each carrying the type of approval it received. The mark appears in the article itself, at the end, with a link to the sources used.
4. Checking the claims. Every factual claim is checked against the recorded excerpt from the source — and, in the current format, a person does the checking, while writing. Until 28/09/2026 that was a separate automated second pass. In neither format does the check fetch anything or fill gaps: if it is not in the source, it is not supported.
5. Checks that block publication. The article is also blocked if it claims experience that did not happen ("I tested", "we played"); cites a game code without the date its source was checked; repeats content already published here or on the sister site; has a link that does not resolve; or has no image with a description.
6. Publication. Passing everything, the article joins the queue and is published automatically, one a day. The text passes through a person's hands as it is written; there is no separate editorial review after that, which is precisely why the checks above exist and are described here.
7. Sampling and correction. The editor reads a sample of what was published and corrects what needs correcting. Any correction is recorded on the Corrections page, with the date and what changed.
8. Record. For every article, and forever, we keep who approved it and what kind of approval it was — human, automatic or editing session. The three mean different things and are never swapped: automatic states that a machine compared every claim against the source; editing session states that the text was written from the sources cited and passed the form checks; human carries the seals only the author can give, about his own data, code he ran and images he made. Automatic and editing-session approvals are never recorded in a person's name, and never carry those seals.

What this site never does

• Promise free Robux, generators, giveaways or "methods". They do not exist, they are scams, and trying one risks your account.
• Write addressed to children. These texts are for teenagers and adults.
• Claim we tested, played or checked something that was not tested, played or checked.
• Publish a game code without saying which source it came from and on what date that source was checked. A code without a date expires while still claiming to work.

Corrections

An error found is corrected in the article itself and recorded on the Corrections page, with the date and what changed. We do not erase history.

If you found an error, it is welcome: the correction is worth more to this site than a silent save.