Contact

Reaching the editorial team behind Video Game Development Authority — whether to flag a factual error, suggest a topic gap, or ask about the reference content — works best when the message arrives with enough context to act on. This page explains how contact works, what the coverage scope includes, and what kind of response to expect.

How to reach this office

The primary channel for editorial correspondence is email. The address verified in the site footer routes directly to the editorial desk, not a ticketing queue. For corrections to specific pages — say, a sourcing error in the Unity vs Unreal Engine comparison or an outdated figure in Game Development Budgeting and Funding — email is the fastest path to a real review.

There is no phone line, no live chat widget, and no social media direct-message channel monitored for editorial purposes. That is not an oversight. Reference publishing runs on careful review cycles, not real-time response windows, and pretending otherwise would just create a queue nobody was actually watching.

Service area covered

Video Game Development Authority covers the US game development landscape at a national scope. The reference content addresses topics that apply across all 50 states — career pathways, engine choices, production pipelines, funding structures, publishing platforms, and legal considerations like Intellectual Property and Game Law. The US Game Development Industry Landscape section maps the broader context.

What falls outside the editorial scope:

1. Jurisdiction-specific legal advice — content about contracts, IP filings, or employment law describes general frameworks, not state-specific counsel.
2. Studio-specific development support — the site is a reference authority, not a development consultancy or job placement service.
3. Platform holder inquiries — questions about Sony, Microsoft, or Nintendo certification processes are addressed in Console Certification and Submission as reference material, but the editorial team has no relationship with those platforms.
4. Academic program enrollment or admissions — Game Development Education and Degrees covers the landscape of programs; the editorial team cannot assist with applications.
5. Commercial partnerships or sponsored placement — editorial content is independent; advertising inquiries go to the business address in the site footer, separate from the editorial desk.

What to include in your message

A well-formed message takes less than 2 minutes to write and dramatically shortens the review cycle. The editorial desk handles corrections, content suggestions, and accessibility feedback — and each type benefits from slightly different information.

For factual corrections:
- The exact page URL
- The specific sentence or figure in question
- The source that contradicts it (named publication, statute, or database — not a general URL)

For content suggestions:
- The topic as a plain descriptive phrase
- Why it belongs in a game development reference context
- Whether a related page already exists (checking the full topic index first saves time for both sides)

For accessibility issues:
- The page and the specific element (heading, image, table, embedded list)
- The assistive technology or browser involved, if relevant
- A brief description of what broke

Messages without a page reference or a specific claim take longer to route. "I think something is wrong about Unity" does not give the editorial team a starting point. "The shader compilation benchmark on Shader and Visual Effects Development cites a 2019 figure that Unity has since revised" does.

Response expectations

The editorial desk reviews correspondence on a rolling basis, not a fixed daily schedule. Corrections to factual errors — especially sourcing issues or broken citations — are treated as the highest priority and typically acknowledged within 5 business days. Content suggestions enter an editorial review queue that operates on a longer horizon; not every suggestion results in a new page, but all submissions are read.

Two things to set expectations clearly:

What generates a response: Factual corrections with a named source, accessibility reports with a specific element identified, and content gap suggestions that identify a genuinely missing topic in the reference network.

What does not generate a response: General praise or criticism without a specific page reference, commercial inquiries sent to the editorial address, and requests for the editorial team to review or evaluate third-party content, tools, or portfolios.

The Game Development Frequently Asked Questions page covers the most common reference questions about how the content is structured and sourced — worth checking before drafting a message, because the answer may already be there.