Jili777 PH Top editorial lens: read the source record, note any configuration gap, then compare the corresponding game profile before relying on a claim.
Start with the exact product
We match the title and product ID against the provider’s own listing, then record the layout, risk label, feature names, maximum-win field and publication date. A sequel or similarly named game does not inherit the original’s specifications. Source pages and media URLs are retained with the build.
A research score, not a win prediction
Our 100-point framework reserves 30 points for hands-on mobile usability, interface clarity and actual-play observations. Those points are not assigned without testing. The available 70-point research rubric covers mechanics documentation (20), bonus detail (15), RTP transparency (15), risk-label clarity (10), and identifiable official sources and media (10). Published research scores are the awarded research points divided by 70, then multiplied by 10.
How the research points are assigned
Mechanics receive 10 points for a named feature and 10 for an interpretable, non-conflicting layout. Bonus documentation receives 5 points for one named mechanism and 10 additional points when two or more distinct mechanisms are documented. RTP receives 15 only for an explicit sourced configuration; none is assigned in this launch set. A clear provider volatility label receives 10. An official product page and local source-attributed media receive 5 each. This score measures available documentation, not game quality or expected profit.
What a future play test must record
A hands-on record must name the device, browser, connection, date, exact game build and configuration. Screenshots must come from that session. Opening a product page or testing this website does not count as playing the game. We will update a review date only when its content or evidence is actually checked.