Virginia skill games remain a subject for careful statutory reading after Governor Abigail Spanberger's April 10, 2026 veto of Senate Bill 661. Operators comparing proposals, vendor materials and news reports should begin with the current code, then trace the status of any proposed change. An attractive licensing plan printed in a bill is not itself an operating license.
This guide separates the governor's documented action from the language in Virginia's published law as checked September 9, 2026. The April veto is background, not a new development this week.
What the governor vetoed
The governor's April 10 announcement identifies SB 661 among the bills she vetoed. In explaining her decision, Spanberger raised concerns about fragmented gaming oversight and impacts on communities. Those are the governor's stated reasons; this article does not present them as independent findings about a particular business or machine.
The release documents the executive action. The official SB 661 record is the place to examine legislative versions and subsequent actions. We could verify the veto announcement and current code but could not inspect the full interactive bill history for this report. We therefore do not report an override vote count or a complete legislative chronology.
What the current statute says
Virginia Code section 18.2-325 expressly includes playing or offering to play skill games within its definition of illegal gambling. Its gambling-device definition also includes skill games. The presence of player skill therefore does not, by itself, resolve how the statute treats the equipment.
The same section defines a skill game using several characteristics, including an insertion requirement and the possibility of cash or cash-equivalent awards. Its language covers payment of awards automatically or manually. It also excludes an amusement device as separately defined in the section. Those details belong together: selecting one phrase while ignoring another can change the apparent meaning.
For an actual installation, the necessary factual questions include how play is purchased, how the game functions, what can be awarded and how awards are redeemed. This is not a determination that every device called a skill game has identical features or that a particular product satisfies every part of a definition.
Do not turn a bill into an authorization
Legislative websites retain introduced bills, substitutes, amendments and other versions so readers can follow what lawmakers considered. A document may describe license classes, fees or a future effective date without that framework having become operative law.
When someone relies on a bill, request its number, session, version and action history. Ask which provisions actually became law and where they appear in the current code. A screenshot of proposed language cannot answer those questions. Nor does a court decision involving another state's statute automatically answer a Virginia question.
Our primary-source reading guide illustrates the distinction between statutes, proposals, tax records and court decisions using Texas examples. The reading method travels; the legal conclusions do not.
Build a record around the actual equipment
Before relying on a supplier's compliance explanation, identify the manufacturer, cabinet, game title, software version and proposed location. Request a written description of payment and redemption, along with the complete documents supporting the supplier's position. Date the record so a later software update or legal development can be recognized.
The vendor diligence guide offers questions for organizing that file. Take the actual equipment facts and current Virginia materials to qualified counsel. A product label, a pending proposal or a workaround described in a sales conversation is not a substitute for that review.
Sources checked September 9, 2026. Produced with AI assistance and checked against the cited materials. This is editorial information, not a legal opinion on a particular machine or business.