How we test StudyOutlaws tools and write these guides
The StudyOutlaws team, the people who build the tools, writes and maintains every guide. Each tool has automated tests, changes to how a tool joins live games are tried against real games we host, and the reasons real runs fail feed straight back into the tools, their messages and these guides.
- Written by
- The StudyOutlaws team
- Published date
- First publication
- Updated date
- Last real content change
- Usage numbers
- Rounded, last 7 days, on one page
How it works
- Build and test the tool
Automated tests run before every release.
- Try it on real games
Live-game changes are run against games we host.
- Write from the product
Inputs, messages and limits come from the tool itself.
- Learn from failed runs
Failure reasons become fixes and troubleshooting guides.
Who writes StudyOutlaws guides
Every guide is written and maintained by the StudyOutlaws team, the same people who build and run the tools. That's why each guide is credited to the team rather than to a named author. The guides live next to the tools' code, so a change to a tool and the matching guide update can ship together.
The guides are also published in German, Spanish and Portuguese, and the translations are kept in step with the English text.
What goes into a guide
A guide states only what the tool does today. Each fact is taken from the product itself: the plans and task credits a tool needs, the inputs it accepts, the defaults and limits in its settings, and the exact messages it shows when something goes wrong. If a tool can't do something, the guide says so as plainly as it describes what works.
Results in the dashboard say which answers are verified and which came from AI, and the guides use the same distinction. A guide never promises that a teacher or platform can't see something; it describes what appears in the game or the account when the tool knows it, such as a bot's name in a Kahoot lobby.
How StudyOutlaws testing works
- Automated tests: the dashboard tools have automated tests, including tests for the inputs they accept and the messages they show when a run fails. The complete test suite runs on every proposed change, and a change can't be merged until it passes.
- Real games: when we change how a tool joins or reads a live game, we run it against real games we host for the test. For example, the October 2026 fixes for Kahoot's nickname generator, taken names and lobby links were checked this way.
- Inputs people actually enter: when runs fail because of what was pasted, we look at those inputs and teach the tool to read them or to say at once what to enter instead.
- Chrome extension: guides for a new extension version appear only once the Chrome Web Store serves that version, so a guide never describes a release you can't install yet.
How failure reasons improve the tools and guides
Every failed dashboard run records a short code and a plain reason, such as a game that wasn't found or a login the platform refused. We review those failure reasons to find bugs, to rewrite messages that didn't help, and to decide which problems need their own guide. The troubleshooting guides for Kahoot PINs, Kahoot lobby settings, private Kahoot links, Blooket set IDs and Membean session lengths were written from these reasons.
A failed answer lookup never uses task credits, so a problem on the platform's side or ours doesn't cost you. Bots and flooders charge when the run starts, and their guides say so.
How pages are dated
- Published is the date the guide first appeared on the site, taken from the project's history. It never changes later.
- Updated is the date of the last real change to the guide's content. Fixing a typo in another page or rebuilding the site doesn't move it, so a recent date means the content itself changed.
- Guide updates usually follow a change to the tool or a new failure reason from real runs.
How usage numbers are published
Usage numbers appear on one page only, the StudyOutlaws stats page at studyoutlaws.com/stats, never in the guides or on the homepage. It covers the last 7 days for each platform: answers served, dashboard runs completed and the run success rate.
Counts are rounded down, and any count under 100 isn't shown. The success rate leaves out runs that failed because of what was entered, such as a wrong or ended game or a rejected login, and is rounded down too. The numbers refresh at most once an hour.
How to report a wrong guide
If a guide doesn't match what you see, tell us. It's the fastest way to get it fixed for everyone.
- Open Support
Use the Support link on this page or in the site menu. You can reach us through support chat, Discord or email.
- Name the guide
Give its title or address and the part that's wrong.
- Say what you saw
Copy the exact message or result and roughly when the run happened.
- Leave out passwords
Never send a school or platform password. We don't need it to check a guide.
Common questions
Why don't the guides name an author?
The tools and guides come from one team, so the byline credits the StudyOutlaws team and links to this page, which explains how that team works.
Why does a guide show an older Updated date than another?
The Updated date only moves when that guide's content changes. An older date means nothing in it needed to change since then.
Why aren't usage numbers shown on platform pages?
So every number has one source that refreshes itself. The stats page explains what is counted and how it's rounded.
How quickly is a wrong guide fixed?
We don't promise a time. Reports that include the exact message and the time of the run are the easiest to check and correct.
Ready to try it?
Questions along the way? Ask support and include this guide's link.
