Mine Rush field guide
Alex Spencer & Editorial Standards
MineRushGame.com is an independent editorial project focused on one VeliPlay title. We publish source-backed game mechanics, visual walkthroughs, comparisons and safety notes. We do not run Mine Rush, accept wagers or represent VeliPlay.
Page summary
Editorial process
Four passes before publication
Source capture
Preserve the provider page, public metadata and dated media.
Interface check
Match copy with controls, counters, bonus states and results.
Claim labels
Separate published facts, arithmetic, observations and unknowns.
Safety review
Check age language, risk framing, links, schema and accessibility.
Source hierarchy
Which evidence carries the most weight
| Priority | Source | Use | Limit |
|---|---|---|---|
| 1 | Current game rules and provider product page | RTP, mechanics, feature names | Still provider-published |
| 2 | Regulator registers and lab certificates | Licence status and tested versions | Must match entity and date |
| 3 | Original interface images and video | Control labels and visible states | Cannot reveal hidden probabilities |
| 4 | Operator terms and account help | Stake, bonus, payment and dispute rules | Can vary by operator and region |
| 5 | Independent reviews | Comparison ideas and reported issues | Claims need primary confirmation |
Our Mine Rush fact sheet records 96% RTP, a 21,661.6× maximum, Low/Medium/High settings, persistent keys, a 50-key trigger and 50×/100× purchase routes. Universal stake limits, exact step odds and a title verifier remain marked unknown.
Visual evidence
Why the site uses more than decorative screenshots
Each image has a job. The instruction screen maps the controls. The main interface explains the decision. Statistics separate multiplier and key fields. Bonus screens distinguish direct entry, lives and reward states. Video is clipped and compressed to show motion where a still frame cannot.
Competitor screenshots are used for criticism, comparison and visual analysis. They remain attributed to the site shown, and our pages link to the source. Screenshots do not imply endorsement, ownership or partnership. Rights holders can use the contact page for a removal or correction request.
We preserve aspect ratios, descriptive alt text, width and height to reduce layout shift. WebP delivery reduces mobile weight. Motion respects reduced-motion preferences, and contextual autoplay clips remain muted and pause outside the viewport.
Rating method
How the 4.1/5 homepage score is formed
| Category | Weight | Reading |
|---|---|---|
| Mechanic clarity | 25% | GO, CASH OUT and route progression read clearly |
| Feature depth | 20% | Persistent keys and Treasure Hook add structure |
| Mathematical value | 20% | 96% RTP is ordinary for the category |
| Transparency | 20% | Exact odds and title verifier are absent publicly |
| Mobile and visual UX | 15% | Responsive media and simple controls are positive |
The rating is an editorial assessment, not an aggregate of invented player reviews. Providers and casinos cannot purchase a higher score. A major rules update can change it, and the visible changelog will state why.
Commercial policy
Affiliate links do not own the conclusion
Some play buttons use an internal redirect and may produce compensation. The editorial desk decides page structure, comparison criteria, fact labels, pros, cons and ratings before commercial placement. A partner cannot remove the 4% edge explanation, missing-odds note or responsible-gambling links.
We do not claim every referred operator is suitable for every reader. Age, jurisdiction, licence status, game availability and current terms must be checked at the time of use. Commercial links use nofollow attributes and the redirect page is excluded from indexing.
Read the full affiliate disclosure and send a conflict concern to [email protected].
Corrections
What to send and what happens next
Send the URL, disputed sentence, a primary source or redacted screenshot, operator name, game version and observation date. We compare it with the saved evidence, update the page if needed and add a dated history entry for material changes.
Do not send passwords, identity documents, full payment numbers, unredacted account history or wallet seed phrases. The editorial desk cannot investigate private casino balances. Rights requests should identify the media and the requested remedy.
Planned review frequency is monthly for homepage facts and operator-sensitive pages, quarterly for mechanics and strategy, and yearly or after a legal change for policy pages. A current date means the stated checks were performed; it does not mean every external operator term is frozen.
Publication standards
What we refuse to fabricate
We do not create player testimonials, casino withdrawal histories, personal gameplay hours, regulator approvals, promo codes or independent audit claims without evidence. Alex Spencer is identified through the public profiles and Mine Rush article linked in his profile; we do not add unsupported employment history, private operator access or guaranteed-results claims.
Calculated fields show the formula. The 4% edge is 100 minus the provider-published 96% RTP. Example payouts multiply stake by a displayed factor. Neither calculation becomes independent certification simply because it is mathematically correct.
Comparison winners are conditional. A higher RTP may suit a value comparison, while a clearer interface or preferred interaction can decide product fit. We state the criterion beside the result and do not convert taste into a universal ranking.
Automation helps validate HTML, metadata, links, schema and content thresholds. A passing script does not prove factual truth or visual quality, so pages also receive source, mobile and screenshot review. Test defects are corrected in the testing tool and documented rather than hidden by changing valid site architecture.
Governance
How a material update is approved
Fact changes
A new RTP, maximum, feature cost or rule requires a current primary source or a dated in-game capture. The editor updates visible copy, structured data, comparison tables and the change history together so search metadata does not preserve an obsolete claim.
Corrections and conflicts
Commercial compensation cannot veto a correction. When sources conflict, the page identifies the source, operator, version and date rather than silently choosing the more attractive value. A rights request is assessed separately from whether the screenshot is favourable to the reviewed product.
Technical releases run HTML, metadata, schema, accessibility, internal-link and runtime checks. Desktop and mobile screenshots are reviewed for clipping and overlap. Automated counts are useful gates, but publication still requires a human-readable conclusion and an explicit boundary around unknown facts.
Content update history
Content update history
- — facts, internal links, structured data and mobile layout checked.
- — initial evidence map and page outline prepared.