Our Testing Method for a Plinko Game in Full
Every verdict on Chicken Plinko comes out of this testing method. We open the studio's own free demo, read every help screen and the RULES document end to end, decode what the game server sends the client, and quote only figures that Onlyplay, its server or a public register has printed. The rules document prints 96.00% and the studio's game page prints 96.14%, our recorded run covers 83 drops, and scores run from 1 to 10. This page walks through the process, including its four limits.
- Where testing happens
- The developer's own free demo, every time
- Scoring scale
- 1 to 10, across 5 named criteria for a game verdict
- Evidence accepted
- Recorded session, the game's own rules document, the server's config, a downloadable register
- Sessions on record
- 1, of 83 drops at the 0.50 stake
- Known limits
- 4, each printed on the page it affects
- Audience
- Adults aged 18 or over
Table of contents
- Demo Play Comes First in Our Testing
- What Demo Testing Cannot Show
- Why a Single Drop Cannot Be Checked
- Sourced Numbers Quoted as Printed
- Honest Cons from the Recorded Session
- Scoring: 5 Named Criteria, and What a Score Cannot Mean
- Why There Are No Casino Pages Here
- Recap: The 4 Limits of This Testing Method
Demo Play Comes First in Our Testing
Demo play comes before every other step, so testing starts in the current official client instead of on a marketing page. We open the studio's public launcher, note the demo balance of 10,000.00 it grants, then run a recorded session at a stake held fixed throughout.
Nothing is kept from memory. Every session is captured in screenshots while it runs. The balance is read off those frames afterwards, and where two results fall between frames the page says “at least” rather than inventing a count.
That record of frames is what later turns into a score. The demo runs the same client an operator embeds, while the stake stays imaginary; in the demo it carries seven stakes and the shop, and an operator can change the stake list and switch the shop and autoplay off. Adults aged 18 years or over can open it without an account.
In Short, Before You Trust a Testing Score
Here's what a score on this site is worth: it's the product of one recorded demo run plus a pile of documents, and nothing else. We've never deposited at a casino for this site at all, and you'll see that limit repeated wherever it matters.
That limit is deliberate, and it is stated on every page. A demo can't measure the psychology of real money, so the score speaks to mechanics, licensing and sourcing, while the return figure stays the maker's own claim rather than something we measured.
A session record holds the stake, the opening and closing balance read off the frames, the best payout and every bonus that did or did not trigger. It is the only evidence that stands behind a sentence beginning with “in our testing”. The Chicken Plinko free demo page shows how a reader can repeat the same run without an account.





What Should a Reader Check First?
Four checks are worth making before you weigh a score, and each one is available without an account. Page through the nine HOW TO PLAY screens first, then compare the RULES document against what the maker publishes on its game page.
- Open the demo, find RULES in the menu and read it to the end, where the return figure sits.
- Read the maker's own page for the game and check its return and its ceiling line, which names no feature.
- Open the shop and read the three prices in bets, which settles what a bought bonus costs at your stake.
- Look for a licence on the studio's own site: it names no licence number, no licensing body and no legal entity, so any licence claim you meet has to be checked in the issuing regulator's own register.
That is the same client an operator embeds, so a reader needs a few minutes and no money at all for the check. Doing the four in advance is the fastest way to test this method instead of trusting it, and every page here carries the date of its own last check.
What Demo Testing Cannot Show
Demo testing has a ceiling, and this is the honest shape of it. A run of 83 drops is far too few to say anything about a long-run return, so the published figure does that job instead.
Our run closed 7.20 ahead across 83 drops at a 0.50 stake, and its best single payout was 10.00, the x20 basket, which arrived twice. Against a published return below 100% the run should have finished a little behind, and instead it finished in front — which is the clearest argument on this site for not trusting any short run, including ours. Those are observations, not statistics, and the page says so wherever they appear.
One number from that run is worth printing on its own, and it is a zero. Across all 83 drops no bonus feature arrived: no golden egg, no bomb, no battery and no lightning, so the two bumpers were never cashed. The bonus pages here are therefore built from the rules document and the server's configuration, and they say so.
Why a Single Drop Cannot Be Checked
This is where the method runs out of road, and saying so is more useful than dressing it up. This game exposes no server seed, no player seed and no published hash, so there is nothing a reader could hash together and compare. A drop is a result you take on trust or walk away from.
Randomness and a title-level certificate are two different assurances, and neither is documented here. The rules document says outcomes come from a random number generator and stops there: no laboratory certificate, number or audit date is published for this title, and the studio's own RNG page does not resolve. Nothing here is offered as provably fair either, and no page claims otherwise. Catalogues that describe a provably fair plinko with a risk setting are describing a different game.
What a Reader Is Left With
What is left is randomness a reader has to take on trust, which is weaker than a proof they could run themselves. The gap gets printed as a gap rather than smoothed over.
So the missing assurances are named instead of implied, and the checks we can actually run take their place. The rules text, the server's configuration, the basket row and the public registers are all open to anyone, and every one of them is repeatable in an afternoon.
Sourced Numbers Quoted as Printed
The method below is written for an adult reader anywhere, so it treats no single country's regulator as the one that answers. Every number is sourced before it is printed, and the date of its check travels with it. Returns, stakes and licence details come only from the client, the studio rules document, the server's configuration or a regulator's own page, and each figure keeps the shape they gave it.
The game carries two returns from one maker: 96.00% in the rules document and 96.14% on the game page. The studio's website terms add that a certified or operator-specific configuration takes precedence over website information, so the figure belongs to the deployment rather than to the title. Those statements describe different things, so the pages keep them apart rather than blending them into one average.
The same sourcing rule governs the win side. The game page prints a maximum win of 1,000x and names no feature; the rules name no ceiling at all and say the Jackpot Game has no maximum limit; and the server caps each bumper at 500. Each figure travels with the surface that printed it instead of being merged. We invent no payment methods, bonuses, licences or multipliers, and the return reference page is the model for this rule.
Honest Cons from the Recorded Session
Every page names its downsides. Cons are mandatory on every page that carries a verdict. A testing round that comes back with only good news was never a test, so the drawbacks are written before the verdict.
Every page carrying a verdict includes a real downsides section and a named anti-recommendation: what the editors would not do with this game, said in so many words.
The drawbacks stay specific: two return figures from one maker, a ceiling published without saying which feature reaches it, a basket row in which five of the ten fixed baskets, carrying x0.8, x0.4 and x0.2, return less than the bet, no odds published for any basket or bonus, a shop that sells a bonus for up to 200x the bet, autoplay that opens on the infinity setting in the demo, and a studio that names no licence of its own. We also name who should avoid the game: the verdict says it before the sponsored button appears, and the sponsored card repeats it.
Scoring: 5 Named Criteria, and What a Score Cannot Mean
A game verdict rests on 5 named criteria and runs from 1 to 10: the return figure, licence and certification, the features, the stakes and ceiling, and the disclosure behind every number. The score is their plain average, and what it recommends is said in words in the verdict rather than read off a threshold.
What a score here cannot mean is that a casino is good or bad. A second scale exists for that, 16 criteria across trust, the game and money, computed from a casino dossier rather than from an opinion, and on this site it grades nothing, because no casino dossier was built. A reader therefore gets a graded game and an ungraded market, which is the honest shape of what was actually read.
| Criterion | What is tested | Evidence accepted |
|---|---|---|
| Return figure | Which return each surface of the maker prints, and which one the running client shows | The game's own rules document, the studio game page |
| Licence and certification | Whether a regulator publishes a register the supplier can be looked up in | A register file a reader can download |
| The features | What triggers the bumpers, the bomb, the wheel, the Jackpot Game and the Free Eggs, and what each costs to buy | Rules document, help screens, server configuration |
| Stakes and ceiling | Every stake the panel offers, and whether the published ceiling names the feature that reaches it | Stake panel in the client, server configuration |
| Disclosure | Whether every number traces to an open source | Named source beside each figure on the page |
What the Client and the Registers Provide
The studio provides the demo client, and its RULES document carries the return figure, the basket values and the bonus rules in plain text. Demo mode runs on demo credits only, so nothing you hold is ever at stake.
The registers supply the licence half of the same picture, and on this game every one we could download returned nothing. Two public licence registers, downloaded in full on , carry no entry for Onlyplay — a result we only trusted after the same search in the same files found Pragmatic Play, Evolution and Playtech. The studio itself names no legal entity, no licence number and no licensing body on its own site, and the licence catalogues attribute to it appears only in second-hand descriptions.
Volatility the studio does settle, after a fashion: its game page prints Medium. What it never explains is the scale, so the figure is quoted as the maker's own rating rather than repeated as a fact about the game. The hit rate appears only in its launch press release, and nowhere a player can see it.
Which Criteria Decide a Score?
Our criteria are fixed before a game is opened, and they stay fixed whatever the result turns out to be. To verify a claim, the editors go back to the document that carries it, then quote the wording they find there rather than their impression of it.
Every page includes the source beside the figure it carries. Readers can follow the same trail, so they can open a document themselves, and you can disagree with a score while still trusting the numbers under it.
Which Lines the Player Never Sees
Some figures this game publishes, and some it keeps. The table keeps the two apart, because on this title the gap between them is much of the story: the return reaches a player only through a menu, and the odds behind every basket and bonus are named nowhere at all.
| Figure | Where it is printed | What the player sees on the main screen |
|---|---|---|
| The return | 96.00% in the RULES document, 96.14% on the studio game page | Nothing: the demo's server config sends no display figure, so the board shows no return |
| The maximum win | 1,000x on the studio game page only | Nothing; the rules name no ceiling and say the Jackpot Game has no maximum limit |
| The odds of any basket or bonus | Not printed anywhere we could read | Nothing: the game page, the rules and the server all leave them out |
| The stakes | 0.50 to 40.00, seven steps, in the server's own config | The stake panel, with 0.50 selected when the game opens |
What Else the Client and Its Server State
Four more fields, each with the surface it was read on: the board, the rules document, the shop screen or the configuration the server sends. Nothing in the table is inferred from a third party.
| Field | Value, and where it is read |
|---|---|
| Baskets | Ten fixed values from 0.2 to 20 in a symmetric row on the board, plus a mystery basket the rules say awards x2, x5 or x20 |
| Bumpers | Two, marked x25 and x50 on the board; the rules say a golden egg or a bomb pays them out, and the cap of 500 each comes from the server configuration, not from any screen |
| Bonus buy | The BUY NOW screen shows 15.00, 25.00 and 100.00 at the 0.50 stake for Free Eggs, the Wheel of Fortune and the Jackpot Game; the multiples behind them, 30x, 50x and 200x the bet, come from the server configuration |
| Jackpot Game | Per the rules, a door worth x5 to x100 multiplied by a beak worth x2 to x10, times the bet of the egg that triggered it; the rules add that no pooled funds are involved, which is why we read it as not a progressive |
Why There Are No Casino Pages Here
No casino is written up on this site, and that is a decision rather than an omission. A casino page under this method needs its own dossier: the licence number read out of its footer, looked up in a register, then every figure it publishes about this title recorded as found. No such dossier was built for this game. So no page here reports what any particular casino shows, charges or allows.
The checklist below is what such a dossier would have to carry. It is printed here so a reader can see the bar, and so the absence of casino pages reads as a standard we did not meet rather than a gap we hid.
How Licence Regulation Is Confirmed
Regulation is confirmed by register instead of by badge, and on this game every register we could download came back empty. Two public licence registers, downloaded in full on , carry no entry for Onlyplay; the same search in the same files finds Pragmatic Play, Evolution and Playtech, so the search works and the absence is an absence. The studio's own site names no legal entity and no licence number, so there is nothing of its own to look up.
A casino licence answers a different question from a supplier licence, and it has to be read where it was issued. A badge in a casino footer is a claim; the account number behind it, looked up in the issuing regulator's own register on the day you read it, is the evidence. Any page claiming a verified licence for this game without naming that register and that number is describing a document it has not shown.
- Account number and holder, read in the regulator's register on the test date.
- Presence of this title in the lobby, proved by a catalogue sitemap, a lobby record or an indexed game page.
- The wagering contribution for this game, read in the operator's own bonus terms rather than in a banner.
- Demo availability, where the operator states it in a form a reader can check.
- Payment methods and identity-check rules, taken from the operator help pages.
Every page here says not confirmed wherever a figure resisted verification, and not published wherever nobody prints it at all. That wording is deliberate, because a gap a reader can see beats a number nobody can trace.
Terms This Method Uses
- Recorded session
- A demo run captured in screenshots, with the stake and the balance read off the frames, and a count given as “at least” wherever the frames cannot separate two results.
- Random number generator
- The mechanism the rules name as deciding every drop; no laboratory certificate for it was published where we looked, and no drop here can be recomputed.
- Server configuration
- The settings the game server sends the client at launch: the stakes, the basket values, the bumper cap, the wheel sectors and the shop prices, which an operator can set differently.
- Account number
- The number a regulator files a licensed business under, and the key a supplier claim is looked up in a published register; this game's supplier has none in either register we downloaded.
What the Record Actually Holds
The record is one run in the developer's own demo, written down as it happened, never a deposit. The closing figure only means something beside the press count, which is exactly why the page prints both.
| Part of the record | Date | What it holds |
|---|---|---|
| Recorded run | 83 drops at 0.50, closing 7.20 ahead, with a best single payout of 10.00 and no bonus feature | |
| Help screens and rules | All nine HOW TO PLAY screens and the full RULES document, saved to disk | |
| Server configuration | Stakes from the init response; basket values, bumper cap, wheel sectors and shop prices decoded from the configuration the server sends over its websocket |
4 Types of Testing Limit, Compared
The complete list of testing limits runs to four entries, and each one shapes every score here. Readers who weigh a verdict should read them before the verdict itself.
| Limit | Why it exists | What happens instead |
|---|---|---|
| No real-money play | Testing runs in the free demo, with no deposit at any casino | Nothing here describes a deposit, a withdrawal or an account |
| A short session | 83 drops cannot measure a long-run average, and ours finished ahead | The return figure is quoted from the maker, never computed here |
| No drop-level proof | This title exposes no seed or hash a player could re-check | The randomness is reported as the maker's claim, not as something we verified |
| No casino was read | No dossier was built for any operator carrying this game | No figure from any casino is quoted anywhere here |
Does a Demo Drop Prove Anything?
A demo drop proves the mechanics and stops there; a long-run average comes out of the maker's model instead. That is why the return figure is quoted from the maker instead of measured here.
Readers can repeat any of it themselves in a few minutes. They will meet the same board, the same basket row and the same shop our session recorded.
Recap: The 4 Limits of This Testing Method
Four limits shape this testing method, and the page names each out loud. Testing happens in the demo instead of with real money, so nothing here describes a deposit or a withdrawal. Eighty-three drops say nothing reliable about a long run, which is why the return figure stays the maker's claim rather than our measurement. A drop cannot be recomputed by anyone, so randomness is reported rather than proved. And no casino was read at all for this game, so nothing here describes what one shows, charges or allows.
Everything else on this page recaps in a sentence or two. Demo play comes first, the fairness gap is named rather than papered over, sourced numbers are quoted as printed, cons sit beside the verdict, a game verdict rests on 5 named criteria while the operator instrument weighs 16 and runs on nothing here, and a supplier is looked up in a register file rather than taken off a footer. All testing is done by the tester who signs each page, and every page here is written for adults aged 18 or over.
This site takes no deposits and runs no identity checks; both stay off it entirely.