Théo Garnier, Instant Game Tester and Editor

About This Tester and the Byline

The byline is a role, not a resume. The tester byline on Chicken Plinko belongs to a narrow role. Open the title in the developer's own free demo, read every help screen and the rules document end to end, then report only figures that Onlyplay, the game server or a public register has put on record. Tests one instant game at a time and prints only what the game itself, its maker or a public register will back: opens the title through the studio's own launcher, reads every help screen and the full rules document inside the client so that the figure the marketing page leaves out can be named, pulls the configuration the game server actually sends for stakes, baskets and bonus prices, plays a session captured in screenshots and reads the bet and the balance off the frames afterwards, does the arithmetic behind a ceiling the maker quotes without saying which feature reaches it, and looks the supplier up in the public licence registers that publish one instead of taking a footer at its word.

Every page here is written, tested and signed by the same person. Corrections reach Théo Garnier directly at editor@chickenplinkoreview.com: send the sentence you dispute with the document that contradicts it, and the reply comes from whoever wrote the line rather than from a support queue. A page that changes keeps its update date, and the correction is named in it.

What sits behind the byline on this game is a record with dates, which is a different thing from a title. The studio's public launcher was opened on 2 November 2026, all nine HOW TO PLAY screens were read, and the full RULES document inside the client was read from the first line to the last and saved to disk. The server's init response was pulled for the stakes, and the configuration the server sends over its websocket connection was decoded for the basket values, the bumper cap, the wheel sectors and the shop prices. Then 83 eggs were dropped at the default 0.50 stake: the demo balance moved from 10,000.00 to 10,007.20, the best single payout was 10.00, and no bonus feature triggered once. The supplier was looked up in two public licence registers downloaded in full on 2 November 2026: neither carries an entry for it, and the same search was first run on Pragmatic Play, Evolution and Playtech, which are in the files, so that an empty result could be read as an empty result.

What this byline does not claim is as short as what it does. No degree, no certification, no employer in the gambling industry: the qualification on offer is the record above, and a reader who doubts it can repeat every step in an afternoon. No real-money play stands behind any page here, because none happened - the one recorded session ran on demo credits, and no bonus was bought. No relationship exists with Onlyplay or with any casino, paid or otherwise. And no laboratory certificate for this title was read, because none was published where we looked.

In Short, What the Tester Signs

Here's the deal on this profile: it's a method, not a resume. Every figure on the 9 pages is printed beside the document it came from, and the schema names a role because a role is what can be verified today.

If a number isn't printed by the studio, its game server or a regulator, the page says not confirmed and moves on. That's the whole promise, so the sections below simply show it working.

Role

Instant-Game Tester

Focus

One plinko game, its maths and the screens its maker prints them on

Method

Demo first, rules document read end to end, server config decoded, sourced numbers

Scoring

1 to 10, across 5 named criteria for a game verdict

Writing since

2 Nov 2026

Contact

Editorial contact page

What Should You Check Before You Start?

Four checks are worth making before you start, and the free demo makes every one of them available for nothing. Open the RULES document first, then compare what it prints against what the maker publishes on its own game page.

1. Open the free demo, go to the menu and read the RULES document to the end, where the return figure sits.
2. Open the studio's own game page and compare its return with the one in the rules: one says 96.14%, the other 96.00%.
3. Read the basket row along the bottom of the board, and count how many of its values return less than the bet.
4. Open the shop and note what each bonus costs in bets before anything tempts you to buy one.

The same client is what an operator embeds, so the check above works on any copy of the game a reader meets, and all 9 pages here are dated. Doing this in advance turns the rest of this profile into a cross-check instead of a claim.

How This Tester Tests a Game

The tester starts every test in the free demo client, because a demo is the one place where a plinko game runs without a stake and without an operator account. Théo captures each session in screenshots and reads the bet and the balance off those frames afterwards; where the frames cannot separate two results, the page gives a count as “at least” instead of inventing one.

One recorded session stands behind every first-hand sentence here. Eighty-three eggs went down at the 0.50 stake the client opens on, 41.50 staked and 48.70 returned, and the balance closed at 10,007.20 — a run that finished ahead, which is exactly why it is labelled an illustration wherever it appears rather than a measurement.

Only then does the tester read the maker's current game page, its rules document and the configuration its own server sends the client. Testing happens in demo credits, so nothing here describes a deposit, a withdrawal or anything a casino account does. That limitation is printed on every page it touches.

There is no seed-and-hash panel to re-check here, and no page pretends otherwise. The rules say only that outcomes come from a random number generator, so a single drop cannot be recomputed by anyone, and the tester records what the client prints and looks the studio up in every register that publishes one instead. The full procedure sits on the testing method page, which every review links from its byline.

5 Types of Check, Compared in a Table

No criterion outweighs another. Five criteria carry the same weight in every game verdict, and each one measures a separate thing, so a page states them instead of blending them into a mood. The return figure, licensing, the features, the stakes and ceiling, and disclosure all count the same, which makes the headline figure their plain average.

What Does a Score Mean?

A score grades the record, not the urge to replay. It is the plain average of the five criteria above, so it rises when the maker prints its numbers and falls when a figure is missing or contradicted. Whether the game is worth a look, and in which mode, is said in words in the verdict rather than read off a threshold.

The score appears in the first 100 words of a review and again in the verdict. A reader who stops early still leaves with the answer, which is the point of printing it twice.

What This Tester Covers, and Its Limits

This tester covers one game, and nothing else. Coverage stays deliberately narrow, and compared to a multi-game portal that is the whole point. The subject is this title and what surrounds it: the two return figures its maker prints on two of its own surfaces, the 1,000x ceiling published without saying which feature reaches it, the bumpers, the wheel and the Jackpot Game, the three bonuses the shop sells, the plain plinko games it gets confused with, and the licence record its studio leaves blank. Since 2026 that has produced 9 pages: 2 sections plus the front page.

The list of pages below runs in reading order. Start with the Chicken Plinko review for the verdict, then move to the return reference page for the two figures behind it. Onlyplay supplies the game, and it also supplies every figure this site checks, which is why the pages are built around the places where one of its surfaces disagrees with the next.

• Mechanics and controls, learned and recorded in the free demo.
• The stakes, the basket values and the shop prices, read from the server's own configuration rather than copied from a catalogue.
• The supplier claim, checked in the registers that publish a file, and found in none of them.
• The studio's own game page and its rules document, saved to disk so any figure can be re-read rather than recalled.
• The limits a reader sets before play, self-exclusion, and help services that answer anyone, anywhere.

The gaps in the public record are worth naming out loud, and several of them are real, so they are printed as problems instead of hidden.

Here is the shortlist a reader should carry anywhere this game is offered. No laboratory certificate names this title, the studio names no legal entity, no licence number and no licensing body on its own site, and neither of the two public licence registers we downloaded in full carries it. Each of those gaps is printed where it applies.

What Is Verified, and What Is Not?

The verified list starts with the stakes. They were read out of the server's own configuration rather than copied from a catalogue: seven of them, from 0.50 to 40.00, with 0.50 as the default. Catalogues print a range up to 50 for the same game, which is an operator setting rather than the demo we played.

The ceiling was checked by arithmetic the maker leaves undone. It is published as 1,000x with no feature named, and the rules give one route to it: a Jackpot Game door worth up to x100 multiplied by a beak worth up to x10. The rules themselves name no ceiling, and the server caps each bumper at 500, so how the 1,000x applies to a golden egg that collects both bumpers and a basket is not explained anywhere.

The limits are just as real. A drop cannot be recomputed, no laboratory publishes a certificate naming this title, and no surface publishes the odds of any basket, bumper, wheel sector or jackpot door, so each of those stays an absence rather than an estimate. You will see each gap stated instead of smoothed over.

Pages This Tester Has Signed

The index below is generated from the database instead of typed by hand, so every one of the 9 content pages appears in it, each with its section and the date of its last edit. A page therefore cannot quietly drop out of the list.

A page that was merely rebuilt keeps its old date, because a build is not an edit. However, a page re-checked against a changed studio page or rules document gets a fresh date the same day, so you can tell one page from another at a glance.

Each page in the index carries its section beside it, and each links straight through to the work itself. A page edited this morning shows that date; a page merely rebuilt keeps the older one.

Every page above is a page the tester has read end to end, and no page enters the list until its sources are checked. The date shown on each page is the one of its own last edit.

Terms This Profile Uses

Return to player

The share of all stakes a game hands back over a modelled long run; this title carries two figures from its own maker, 96.00% in the rules document and 96.14% on the game page.

Basket

One of the eleven landing spots along the bottom of the board; ten multiply the bet by a fixed value from 0.2 to 20, and the eleventh is a mystery basket worth 2, 5 or 20.

Bumper

One of two pegs marked x25 and x50 that collect value from ordinary eggs and pay it out when a golden egg touches them once they are active.

Not confirmed

The label printed whenever no studio page, server response or public register states a figure the reader asked about.

Where the Maker Disagrees with Itself

On the return the maker is not consistent: its game page and the rules document inside the client print two different figures, and both are its own. The table sets the surfaces beside one another instead of picking a winner, because the studio's own website terms say that, where website information differs from the certified or operator-specific version of a game, the certified documentation or the operator configuration takes precedence.

The Session on Record

One recorded session stands behind every first-hand sentence on this site, and it ran on demo credits alone. Splitting it below separates what the run staked from what it returned.

What the Client and Its Server Print

The board, the shop and the server configuration print their own figures, and the tester copies them as they appear, with the surface each one was read on. Every row in the table below comes off a screen or a server response we read ourselves.

Corrections, Contact and the Reply Rule

Corrections travel one way only. One page, one sentence and one document settle most of them. They go through the contact page: name the page, quote your sentence, attach the source you believe is right. If your source holds up, the page changes and its update date moves. Where two sources disagree, they are printed side by side, each with the surface that printed it, and where the maker does not say which one applies, the page says that too.

1. Send the page URL and the exact sentence you dispute.
2. Attach the document that shows the correct value.
3. Give the date you read that document, because a studio page can be redrawn without notice.
4. Say whether you want to be credited by name.

Readers who want the whole procedure should read how we test it and the terms of use. Before playing anywhere, read the responsible gambling page, which sets out the limits worth fixing and where free help is available; every page here is written for adults aged 18 or over.

Does a Demo Score Mean Anything?

A demo score means something narrow, and the page says so: it measures mechanics, licensing and sourcing, and it never measures how a bankroll behaves under real pressure.

Readers who want the wider answer should read the limits above before the verdict below. A score summarises a pile of documents and one recorded session, and nothing beyond that.

Recap: What These Tester Pages Promise

Two promises close this profile. If you want the short answer on any return figure, the rules document is the one a player can actually open inside the running client, and the page names the game page beside it whenever the two disagree, without ruling which of them applies. Nothing reaches a reader that a document does not already carry. Coverage runs to 9 pages across 2 sections and the front page, and every one of them carries a byline and two dates.

The weaknesses stay on the page beside the strengths, because a profile nobody could argue with is worth nothing. The about page explains where the money comes from, and why a commission leaves a score untouched.