Playtest LivePlan a playtest

FOR PLAYERS

Become a game playtester

Playtest Live recruits PC players in Oceania and Asia Pacific for live multiplayer research sessions. This page is the honest version: what registering does, what it does not do, and what is actually running today.

Start here: what this is not

Searching for game testing work turns up a lot of pages promising steady income. This is not one of them. Before anything else:

  • Registering does not guarantee selection, invitations, work or income.
  • There is no reward until you accept a specific written offer for a specific session.
  • This is occasional session work, not a job and not a side income you can plan on.
  • You are never charged anything, and you are never asked for payment details to join.
  • No paid study has run yet. The panel is being built ahead of the first ones. If that makes registering not worth your time right now, that is a reasonable conclusion.

How registration works

You fill in one guided form. It asks for the things a study actually selects on, and nothing else. There is no interview, no test to pass to get in, and no fee.

Where and when you play
Your region and time zone, and the weekly windows you are realistically free. Sessions are scheduled, so availability is the single most useful thing you can be accurate about. Twelve cities across Australia, New Zealand and Asia are covered by the standard region list.
What you play and how
Genres, titles you know well, the roles you actually play (entry, anchor, support, shot-caller, flexible), and your language. There is also a first-time-player cohort, which is a real and frequently requested role, not a consolation prize.
Your PC
The machine you would play a session on. This matters because studios test on hardware spreads, and a mid-tier rig is often the seat that is hardest to fill.
Your agreement
That you meet the age requirement, and that you have read what applying does and does not commit you to. Ordinary qualification never requires government ID.

Self-reported versus measured evidence

Everything in your profile is labelled with where it came from, and the label changes how much weight it carries:

Self-reported
What you typed. Enough to be considered for most seats. It is never presented to a studio as though it were verified.
Browser-measured
An optional check you run yourself in your browser: it reads your GPU string, core count, approximate memory, display, and times a short render loop and the round-trip to a named Playtest Live route. It does not read your files, your other applications, your processes, serial numbers or product keys.
Operator-verified
Something a researcher confirmed directly.
Session-observed
What actually happened in a session you attended.

Measured evidence expires on purpose. Route measurements go stale after 30 days, driver and OS evidence after 30 and 90 days, GPU, CPU, memory and display evidence after 180. An expired capture is shown as expired rather than quietly reused, because a twelve-month-old speed test is not evidence about tonight’s session.

Running the browser check is optional. It is also the single thing most likely to get you selected for a technically specific seat, because a studio filtering on measured hardware cannot see a profile that only has typed values.

Consent, and what studios can see

Your profile is private by default. Studios do not browse a directory of players. A studio building a cohort sees the shape of the supply, meaning how many profiles match a set of requirements. Specific profiles only enter that view through an operator-reviewed request tied to a real study.

Hardware and route evidence is collected under a stated purpose: matching a named rig to a study’s technical conditions. It is kept until you delete it, and you can delete it. Rejected applications and private notes are never shown to a studio. Linking Discord, Steam or Twitch is optional, never affects qualification, and linking Twitch never grants anyone permission to stream a build.

How project fit and eligibility actually work

Seats are filled in a fixed order: the session shape the study requires first, then verified regional and hardware coverage, then experience and reliability history. Reward rate is never a ranking input. Nobody undercuts anyone for a seat, and there is no bidding.

Practically, this means the things that get you selected are: being available in the window a study needs, being in the region it is played from, having the hardware tier it calls for, having evidence that is current rather than stale, and turning up when you said you would.

There is optional certification covering confidentiality and conduct, session protocol, honest hardware reporting, and how to give feedback that is useful. It exists because those are the four things that make a participant valuable, and none of them are about how good you are at the game.

Being good at games is not the same as being useful in research

This is the part that surprises people. A cohort is usually specified as a mix across four experience bands (new to the genre, genre-familiar, experienced, and competitive expert) with a target count in each. Studies frequently need more players in the first two bands than the last, because the questions that matter commercially are usually about players who are still deciding whether to keep playing.

Studies also reserve exploration seats and first-time-player cells on purpose. If you have never played the genre, you are not a weaker candidate for those seats. You are the candidate.

What actually makes someone valuable in a session: turning up on time and ready, playing the protocol as briefed rather than optimising for a win, noticing what confused you and being able to say why afterwards, and reporting a problem plainly. Critical feedback never reduces a reward. A researcher who wanted to hear only good news would not need participants.

If a study does match

You receive a written offer for one seat in one session. It states the session time in your local time zone, the total time you are committing, the fixed reward with any premium itemised, and the confidentiality and recording terms. You accept or decline; there is no penalty for declining and no minimum availability to maintain.

If you accept, there is a readiness checklist before the session: confidentiality accepted, build installed, build launched, connection checked, voice checked. All five are required. Standby seats are paid whether or not you are called in, and if you are promoted from standby the reward never goes down.

You can update or withdraw your profile at any time. There is no exclusivity.

Available now versus planned

Pre-launch status

Playtest Live is a pilot release candidate. No paid study has been delivered yet, so nothing on this page is a customer result, a reliability record or a turnaround promise. The workflow described here is built and inspectable; its performance is not yet evidenced.

Working today: registration, a private profile, the optional browser hardware and route check with its consent record, the certification modules, and account connections for Steam and Discord.

Not yet running: paid studies. No participant has been paid, because the payout path has not been through legal, accounting and provider review and is deliberately gated until it has. There is no wallet, no balance and no points system, and there will not be one.

Community sessions are free, coordinated multiplayer games with a scheduled time, a named host, teams and standbys. They are not paid research, and participation evidence from them stays labelled as coming from a community session.