Games and Interactive Entertainment IP Toolkit: Mechanics, Assets, User Content, and Live Operations

By Casey Scott McKay · 2025-05-28

A game is two things at once - a set of rules, which copyright does not protect, and an audiovisual work, which it protects well. This toolkit collects both sides. It covers the idea-expression line from Baker v Selden through the modern game cases, what Tetris Holding actually held, and why the filtered comparison strips away everything that made a clone feel like a clone. It then works what does protect a game: the audiovisual registration, the art and audio assets, the characters, the title as a mark, and the terms of service that do more daily work than any of them. It covers the asset register that decides publishing deals, user content licences drafted against real use cases, mod and streaming policies published rather than improvised, and a clone response that starts with the store.

IP and Technology > Copyright | Toolkit | Published 28 May 2025 - Updated 10 November 2025 | Casey Scott McKay - marksy.us

Summary. A game is two things at once — a set of rules, which copyright does not protect, and an audiovisual work, which it protects well. This toolkit collects both sides. It covers the idea-expression line from Baker v. Selden through the modern game cases, what Tetris Holding actually held, and why the filtered comparison strips away everything that made a clone feel like a clone. It then works what does protect a game: the audiovisual registration, the art and audio assets, the characters, the title as a mark, and the terms of service that do more daily work than any of them. It covers the asset register that decides publishing deals, user content licences drafted against real use cases, mod and streaming policies published rather than improvised, and a clone response that starts with the store.

Keywords: games IP toolkit · idea expression dichotomy · Baker v Selden · scenes a faire · Tetris Holding · clone response · audiovisual registration · asset register · contractor assignment · open source in builds · title clearance · user content licence · safe harbour housekeeping · mod policy · streaming policy · stream-safe audio · live operations terms · virtual items · publishing agreement carve-outs · generative tooling provenance

Start Here

A studio ships a game. Three months later a near-identical product appears on the same store — same core loop, same progression, same economy, different art.

The founders describe the copying in detail and ask what can be done. The answer depends almost entirely on a distinction they have never had reason to think about: whether what was taken is the rules or the expression.

Copyright does not protect the rules of a game. Not the mechanics, the systems, the progression curve, the economy, the win condition, or the idea. 17 U.S.C. § 102 excludes any idea, procedure, process, system, or method of operation, regardless of the form in which it is described, and Baker v. Selden settled the principle before games existed.

What copyright protects is the expression — the art, the audio, the specific audiovisual sequences, the text, the code, the characters. Which is a great deal, and it is why the clone with different art is a hard case and the clone with copied art is an easy one.

The uncomfortable fact at the centre of the practice is that the thing a designer works hardest on is the thing the law protects least. Say it early, say it once, and redirect immediately to what can be done.

Because almost everything useful happens before the clone appears. The asset register that decides whether a publishing deal closes. The registrations filed within three months of publication that decide whether a clone is worth pursuing. The marks filed before announcement. The policies published at launch. The terms of service with an owner.

This toolkit answers four questions. Where exactly does the idea-expression line fall in a game? What actually protects one? What do the characteristic agreements and policies need to contain? And what does a clone response look like when it starts with the store rather than the courthouse?

The Idea-Expression Line

Codified. 17 U.S.C. § 102 at subsection (b) excludes ideas, procedures, processes, systems, methods of operation, concepts, principles, and discoveries. A game's rules are a system.

Merger. Where an idea can be expressed in only a small number of ways, expression merges with idea and receives no protection — a scoring display, a health bar, a countdown timer.

Scenes a faire. Elements standard to a genre or dictated by subject matter are unprotectable. Zombies in a survival game, mana in a fantasy game, a minimap, wave-based enemies.

Why this combination is so destructive to clone claims. Courts filter out the rules, then the merged elements, then the genre conventions, then material dictated by platform or hardware — and compare what remains. Frequently very little remains, and the similarity that felt overwhelming to the developer was similarity in the unprotectable layer.

Tetris Holding v. Xio Interactive is cited for the proposition that games are protectable, and it is worth reading for what it actually held. The defendant copied not merely the rules but the specific visual expression — piece shapes and colours, board dimensions, the display of the next piece, row behaviour. Those choices were not dictated by the rules, and the defendant had copied them precisely rather than implementing the rules independently.

The lesson. A developer who copies rules and builds its own look is generally safe. One who copies the look while claiming it only took the rules is not.

Google v. Oracle America matters for the code layer, treating declaring code and interface specifications as further from the core of copyright than implementing code, and holding reimplementation for a new platform to be fair use.

Where a claim does exist. Art assets copied or traced. Audio taken. Text lifted, including item descriptions and tutorial copy. Character designs reproduced. Code copied, provable by artefacts. The overall audiovisual presentation reproduced in arbitrary detail. Store listing assets, screenshots, and trailers reused. And the title or a confusingly similar mark used, which is a trademark claim rather than a copyright one.

What Actually Protects a Game

The audiovisual work. A game as played is an audiovisual work, and the specific sequences of images and sounds it produces are protected. This is the strongest copyright claim available and it is the one Tetris Holding v. Xio Interactive vindicated.

Art assets. Character models, environments, textures, interface elements, icons, and concept art — each protectable and each registrable.

Audio. Music, sound effects, and voice performances, each with its own rights chain and each frequently licensed rather than owned.

Text. Dialogue, item descriptions, lore, and quest writing.

Code, as a literary work, though Google v. Oracle America limits how far protection reaches into functional interfaces.

Characters, where sufficiently delineated — consistent appearance, personality, and traits across appearances. One of the most durable assets a studio builds.

Titles and marks. A title is not protected by copyright but is registrable as a mark where it functions as a source indicator. Series titles register more readily than single-game titles, which frequently attract descriptiveness or failure-to-function refusals — a practical argument for naming the franchise rather than the instalment.

Trade dress in a distinctive interface or store presence, on a showing of secondary meaning and non-functionality.

Patents. Available for genuinely novel technical implementations — matchmaking methods, rendering techniques, input mechanisms, network architectures — subject to 35 U.S.C. § 101 and the Alice v. CLS Bank International framework, which is hostile to gameplay concepts recited on a generic computer. File during development, not after a clone appears, because by then the disclosure has occurred.

Design patents under 35 U.S.C. § 171 for physical products, controllers, and tabletop components, where the term under 35 U.S.C. § 173 matches the product life.

Trade secrets. Server-side logic, matchmaking parameters, monetisation models, and anti-cheat methods, protected by secrecy rather than disclosure.

Contract. The terms of service, which do more practical work than any of the above.

Registration timing. 17 U.S.C. § 412 conditions statutory damages and fees on registration before the infringement or within three months of publication — and a clone appearing at month three or four is entirely typical. Register the audiovisual work, the code with trade secret portions redacted, key art and character designs, the trailer and store assets, and substantial text. Confirm ownership before registering, because naming the studio as author of contractor art with no assignment makes the registration inaccurate. And confirm registration has issued before suit under 17 U.S.C. § 411.

Assets and Provenance

The most common finding in game diligence is that nobody can say where the assets came from.

Marketplace asset packs. Limits by seat, project, and platform. Some prohibit use in products competing with the marketplace. Some prohibit shipping assets in a form users can extract, which conflicts directly with mod support and is discovered after mod tools are promised.

Fonts. Licensed by workstation, installation, or embedding. A font embedded in a shipped executable is frequently outside a desktop licence, is trivially detectable in the binary, and font licensors enforce.

Engine and middleware. Royalty triggers, branding requirements, and use restrictions. Read them before the revenue threshold.

Open source. Composition analysis over the shipped build including any editor tooling that ships. Copyleft components linked into proprietary code create source obligations a studio may be unable to meet, and remediation takes engineering quarters rather than weeks.

Contractor deliverables. The single most damaging finding, because the assets are already in the shipped product and the contractor has moved on.

Music. Composition and recording are separate rights, and a licence to one is not a licence to the other. Streaming rights, trailer rights, and soundtrack rights are further separate grants.

Voice. Union or non-union terms, usage limits, and express terms on synthetic reproduction of the performance.

Motion capture. Performer releases and likeness rights where the performance is identifiable.

Real-world references. Trademarks in the world assessed against Rogers v. Grimaldi and its limit in Jack Daniel's Properties v. VIP Products; buildings, where 17 U.S.C. § 120 permits pictorial representations of architectural works visible from public places; vehicles and firearms; and identifiable people requiring releases.

Generative tooling. Record which assets were tool-assisted and to what degree. Material generated without human creative contribution may not be copyrightable, which means a shipped asset the studio believes it owns can be copied freely — and vendor terms on output rights, training use of inputs, and indemnity vary enormously.

User Content

Every game with a creation tool, a chat channel, a screenshot button, or a replay system hosts user content, and the framework is the same as any platform's.

Ownership. Players own what they create absent assignment. Terms purporting to assign all player creations to the studio are increasingly disfavoured, unenforceable in some jurisdictions, and reputationally costly. Do not rely on them.

The licence that works. Worldwide, royalty-free, non-exclusive, sublicensable, irrevocable, and perpetual, to use, reproduce, modify, adapt, publish, translate, display, perform, and distribute content in connection with the game and its promotion.

Draft against the actual use cases, because a narrow licence fails at the moment it matters. Moderation requires reproduction and modification. Marketing requires public display and distribution, including on third-party platforms. Incorporating a player creation into the base game requires derivative work rights and sublicensing. Player-to-player use requires an explicit sublicence chain, or players cannot lawfully use each other's creations — which is the entire point of a creation tool. And survival after account termination matters, or a banned player's creation must be stripped from a shipped update.

Have marketing and community read it before it ships. They will identify uses the draft does not cover.

Safe harbour housekeeping. 17 U.S.C. § 512 requires a designated agent registered and kept current, published contact details, a notice-and-takedown policy, a counter-notice process, and a repeat infringer termination policy that is actually applied and recorded. Application, not publication, is what the safe harbour requires, and agent registrations lapse quietly.

When sending notices, consider fair use first, per Lenz v. Universal Music.

47 U.S.C. § 230 covers non-intellectual-property claims from player conduct — harassment, defamation, fraud — requires no registration, and neither covers intellectual property claims nor displaces platform or statutory moderation duties.

Mods and Streaming

These are where legal analysis and community management collide, and where getting the law right while getting the tone wrong causes more damage than the reverse.

Mods. A modification incorporating the game's assets, or built to run within it, is frequently a derivative work under 17 U.S.C. § 106. Every mod scene exists on the studio's forbearance whether or not anyone has said so.

Publish a policy at launch anyway, because silence reads as permission and later enforcement reads as betrayal — a reputational cost that has affected sales more than the modding ever did.

What the policy states. Whether non-commercial mods are permitted and on what conditions. Whether commercial mods are permitted and on what terms. What may be used — assets, tools, formats, extraction. What may not — circumventing protection measures, multiplayer cheating, offensive content. Whether the studio may incorporate a mod, which requires a licence back. Revocation grounds, stated narrowly.

The third-party asset problem. A studio frequently cannot authorise redistribution of middleware, fonts, or licensed music inside a mod, because it does not hold those rights. Say so explicitly rather than granting permission it cannot give.

Anti-circumvention. Where modding requires defeating technical protection measures, 17 U.S.C. § 1201 is engaged independently of infringement, and the exemptions are narrow and periodic.

Streaming. A stream reproduces and publicly performs the audiovisual work, within the studio's exclusive rights. Fair use is genuinely uncertain — commentary and transformation help, wholesale reproduction of a narrative game may substitute for the purchase, and Andy Warhol Foundation v. Goldsmith narrowed the transformative purpose analysis.

Which is why almost every studio publishes a licence rather than litigating. Cover monetisation, sponsorship, spoiler windows with dates, use of the title and key art in thumbnails, what the studio may do with clips, and narrow prohibitions.

The licensed music problem, which recurs constantly. A studio licensed music for the game and not for third-party streams, so streamers receive claims on the studio's own audio. Fix it by licensing streaming rights, shipping a stream-safe audio mode, or publishing which tracks to mute — the third costs nothing and is better than silence.

Tournaments. Organised competition using the game requires a licence. Publish community competition guidelines with thresholds for prize pools, sponsorship, and mark use, so small events proceed without asking and large ones know to.

Amend prospectively only, with notice. Retroactive restriction is the failure mode.

Live Operations

A shipped game used to be finished. A live game is a service, and the legal questions continue for its whole life.

Terms of service. The operative document, formed properly — clickwrap at account creation with a retained record, because a term nobody agreed to binds nobody. Amendment by notice plus continued use with records of both, since posting alone is weak.

Virtual items. Sold as licences rather than property, said plainly, with the point-of-sale description aligned to the terms — because consumer regulators have taken an interest in the gap.

Randomised rewards. Regulated as gambling in some jurisdictions, subject to disclosure requirements in others, and subject to platform odds-disclosure policies regardless of law. Confirm the position in every market where the game ships.

Minors. Age gating, parental consent for data collection, and refund practices for purchases by children — an area of active enforcement with real penalties.

Data. Accounts, telemetry, chat, and voice are personal data, with retention limits, access rights, and deletion obligations that must be operationally supported rather than merely promised.

Conduct and moderation. 47 U.S.C. § 230 protects against liability for player conduct and does not remove platform-imposed or statutory moderation duties.

Anti-cheat. Enforced through contract and technical measures, with the 17 U.S.C. § 1201 claim available against circumvention tools and their distributors.

Real money trading. Prohibited by most terms, enforced by account action, and occasionally litigated against commercial operations.

Sunset. Addressed at launch rather than improvised: notice period, refund treatment for recently purchased items, whether an offline mode will be provided, data deletion, and what happens to player-created content. Several markets now treat service shutdown as a consumer protection question.

Name an owner for the terms. A terms of service without one drifts out of alignment with the business model within two updates.

Publishing and Platform Agreements

Read the intellectual property provisions first. The financial terms decide one game's revenue; the intellectual property terms decide whether there is a studio afterwards.

Ownership of the game. Retention by the studio with an exclusive licence to the publisher is the better structure and is negotiable more often than studios assume. Assignment should be priced as the sale it is.

Sequel and derivative rights. Frequently swept into broad grants. A studio that assigns them has assigned the franchise, including adaptations and merchandising it has not thought about.

Reusable technology. Carve out the studio's own engine, tools, libraries, and pipeline for the next project. This is the single most valuable carve-out in a first publishing deal and it is routinely omitted.

Trademarks. Who owns the title, and what happens on termination. A studio whose title is owned by a former publisher cannot ship a sequel under it.

Term and reversion. What comes back, when, and in what condition — source, assets, marks, live service accounts, and player data.

Approval rights, and whether they extend to the studio's other projects.

Platform terms. Certification requirements, revenue share, content and monetisation policies, and the platform's rights over store assets. Largely non-negotiable; read as constraints and design around them.

Development kits. Confidentiality obligations reaching marketing statements about performance.

Middleware and services. Analytics, matchmaking, anti-cheat, advertising, and payments, each with its own data and liability terms and each a dependency at sunset.

Insolvency. What happens to the licence if the publisher or a critical service provider fails, and whether the studio can continue operating the game.

Produce a one-page rights summary per agreement, filed with the asset register, so the position is knowable without rereading the contract.

Responding to a Clone

Sequence matters, and the fast remedy is not the courthouse.

One. Run the filtered comparison honestly. Strip out rules and systems under 17 U.S.C. § 102, merged expression, genre conventions, and elements dictated by platform or hardware. Compare what remains.

Two. Check the store listing before anything else. Copied screenshots, key art, trailers, descriptions, and confusingly similar titles are the fastest wins, and store copycat policies reach conduct copyright does not. Report there first — it resolves in days and costs nothing.

Three. Look for artefacts. Identical asset filenames, embedded metadata, shared string tables, the same typo, the same bug. Lazy copying leaves fingerprints in text and metadata, and artefact evidence moves a case faster than expert similarity analysis.

Four. Assess the trademark position. A clone using a similar title, similar iconography, or the studio's marks in store keywords is attackable under 15 U.S.C. § 1114 and 15 U.S.C. § 1125 even where copyright fails, with stronger remedies.

Five. Confirm registrations are in place, since 17 U.S.C. § 412 determines whether statutory damages and fees are available.

Six. Decide whether to send anything. If what was taken is the rules and the art is original, say so internally and stop. A letter asserting rights in mechanics is answerable in one paragraph and damages the studio's position in the next dispute.

Seven. Where a claim exists, be specific. Identify the registered work, the copied elements, and the evidence. Do not add the mechanics claim to a good asset claim, because the recipient answers the weak assertion and characterises the whole demand as overreaching.

Eight. Consider the community dimension. Public identification works in this industry and costs nothing, and it carries defamation exposure if overstated. Apply the same triage.

What to tell founders at the outset. That the mechanics were taken lawfully, that this is the ordinary condition of the industry, and that the response is the store report, the artefact search, the trademark position, and the registration programme that makes the next clone a shorter conversation.

Clearance

Most studio legal work is clearance rather than enforcement, and the framework read from the defensive side is largely permissive.

Mechanics are free. A studio building in an established genre uses that genre's systems and should be told so plainly.

What clearance covers. Assets verified against the register. Open source via composition analysis over the shipped build. Music, both composition and recording, plus streaming and trailer rights. Voice and performance, including synthetic reproduction terms. Real-world trademarks. Buildings and architecture. Identifiable people. Character, place, and item names cleared against marks. And the title, cleared before announcement.

Interoperability work. Sega Enterprises v. Accolade and Sony Computer Entertainment v. Connectix support intermediate copying to achieve interoperability as fair use — relevant to tooling, emulation, and platform work — subject to the separate 17 U.S.C. § 1201 question where protection measures are involved.

Responding to a demand received. A claim that the studio copied mechanics is answerable with a short letter citing 17 U.S.C. § 102. A claim that an asset was used outside its licence is a factual question the register answers in minutes — which is the practical argument for the register.

Tabletop and Adjacent Products

The same framework, weighted differently, and worth stating because studios frequently ship both.

Rules remain unprotectable. A rulebook's specific text and layout carry copyright; the rules it recites do not, and competing rulebooks expressing the same system are lawful.

Component art is the asset. Board art, card art, iconography, miniatures, and box design are what tabletop disputes are actually about.

Card text. Individual abilities are frequently too short and too functional to protect; a compiled set of hundreds carries compilation copyright in selection and arrangement, subject to the originality standard in Feist Publications v. Rural Telephone Service.

Design patents matter more here. Tabletop products have long commercial lives, so the term under 35 U.S.C. § 173 matches the product in a way it does not for a mobile release. File on distinctive component shapes and miniatures before any public showing.

Trade dress in box and component presentation under 15 U.S.C. § 1125, on the usual secondary meaning showing.

Marks on the title and the line, which is where the durable value sits.

Adaptation licences should specify platform, territory, term, exclusivity, and whether mechanics-only implementations by third parties remain possible — because they will be.

Fan content. Print-and-play variants, custom cards, and unofficial expansions occupy the same forbearance position as digital mods. Publish the policy.

The Programme by Stage

Pre-production. Asset register started on the first commit. Contractor templates with present-tense assignments. Engine and middleware terms read. Title candidates cleared.

Production. Register maintained at acquisition. Composition analysis running in the build pipeline. Music and voice rights secured, including streaming. Marks filed on intent to use before announcement.

Announcement. Title and studio marks filed. Store metadata monitored.

Pre-launch. Terms of service, privacy notice, user content licence, mod policy, and streaming policy drafted and reviewed by the community and marketing teams. Safe harbour agent registered. Age gating and regional compliance confirmed.

Launch. Copyright registrations filed within the three-month window. Store presence monitored for clones.

Live. Terms reviewed on every business model change. Repeat infringer terminations recorded. Registrations updated for major versions. Community policies amended prospectively only.

Sunset. Executed against the terms promised at launch.

Annually. Asset register audit against build contents. Composition analysis. Mark renewals and watch results. Safe harbour agent registration confirmed. Policy review.

Almost every item is trivial at its stage and expensive or impossible afterwards.

Scaling to the Studio

The solo developer or small team. The register is a spreadsheet and it is still the most valuable thing on the list. Add present-tense assignments for anyone who contributes, a cleared and filed title, a copyright registration for the audiovisual work at launch, and a terms of service that was written rather than copied. Skip patents, trade dress, and the mod policy until there are mods.

The mid-size studio with a live game. Add the full policy set, safe harbour housekeeping, a named terms of service owner, composition analysis in the pipeline, character and studio marks, and store monitoring.

The studio with a franchise. Add merchandising class coverage, character marks, a trade dress position where the interface or store presence is distinctive, technical patents filed during development, and a rights summary per agreement.

The publisher. The exposure inverts: diligence on incoming studios' registers and contractor assignments, flow-down of platform obligations, and consistent policy templates across titles with different communities.

The work-for-hire developer. Almost pure clearance. Confirm what the client owns and what the studio keeps, carve out reusable technology in every contract, and maintain a per-project register so deliverables can be certified.

Where to spend first, at any size. The register, then the assignments, then the title, then the registrations.

Common Errors

No asset register, which cannot be reconstructed after three years of development.

Contractor art with no signed assignment.

Fonts embedded under desktop licences.

Copyleft components discovered at acquisition rather than at ship.

Announcing the title before clearing or filing it.

Registering late, losing statutory damages on exactly the clone the studio cares about.

A user content licence written for "operating the service", which does not cover the trailer, the showcase, or incorporating a player creation.

Purporting to assign all player creations to the studio.

Safe harbour agent registration lapsed, or a repeat infringer policy published but never applied.

Silence on mods, followed by enforcement when the studio launches competing paid content.

Silence on streaming, followed by claims on the studio's own licensed audio landing on its community.

Terms of service with no owner.

Assigning derivative and sequel rights in a publishing agreement without noticing.

No reusable-technology carve-out.

Sending a demand letter about mechanics.

Litigating a clone before reporting it to the store.

A Closing Note

The work that protects a game happens years before anyone needs it.

The asset register, started on the first commit and maintained at acquisition, is worth more than any enforcement strategy — it decides whether a publishing deal closes and whether a demand letter is a crisis or a database query.

The registrations, filed within three months of publication, decide whether a clone is worth pursuing. The marks, filed before announcement, decide whether the studio owns its own name. The policies, published at launch, decide whether the community is an asset or an adversary. And the terms of service, owned by somebody and reviewed when the business model changes, decide almost everything else about a live game.

None of that helps with the mechanics, which will be copied and lawfully so. That is the industry's operating condition rather than a failure of the studio or its counsel — and the sooner a founder hears it plainly, the sooner the effort goes where it produces something.

Three Situations

The clone with original art. A studio's core loop, progression, and economy were reproduced almost exactly by a competitor with entirely new art, audio, and text. The filtered comparison left almost nothing. There was no copyright claim. What did work was the store: the clone's listing used a confusingly similar title and had copied two screenshots, and a platform report resolved both in nine days. The mechanics remained copied and lawfully so, and telling the founders that plainly at the outset saved a year of expectation management.

The clone that copied the string table. A different clone, superficially more distant, shipped with the original's tutorial text — including a typo the original studio had never fixed. That artefact did more work than any similarity analysis, and the case settled in six weeks. Lazy copying leaves fingerprints in text, filenames, and metadata, and looking for them first is faster than expert comparison.

The mod policy that came too late. A studio tolerated a monetised mod scene for four years, then attempted to prohibit commercial mods when it launched its own paid content. The legal position was sound — mods incorporating game assets are derivative works — and the community reaction was severe enough to affect sales of the paid content it was protecting. A policy published at launch, permitting non-commercial mods and reserving commercial rights, would have produced the same legal outcome with none of the damage.

Metrics

Assets in the register with a licence reference attached. Missing entries should block a build.
Contractor engagements with a present-tense assignment executed before work began.
Copyleft components in the shipped build, and days to remediation.
Copyright registrations filed within the three-month window, by title.
Marks filed before announcement, as a percentage of titles announced.
Safe harbour agent registration currency, checked annually.
Repeat infringer terminations recorded, against notices received.
Community policies amended prospectively only. Any retroactive restriction is an incident.
Clones identified, and the proportion against which a right existed.
Store reports filed and resolved, with median days to resolution.
Terms of service reviews triggered by business model changes.
The one that matters. Whether a publishing deal, acquisition, or platform certification was ever delayed by an asset provenance question. That is what the register exists to prevent, and it is the only measure the business will recognise.

Who Does This Work

Almost none of it requires a lawyer day to day. The register is maintained by whoever acquires assets. The composition analysis runs in the pipeline. The policies are drafted once. The marks and registrations sit on a docket.

Counsel's role is to set the templates, define what blocks a build, and be available for the handful of genuine questions.

The failure mode of over-lawyering. A studio that routes every asset purchase through legal review will stop maintaining the register within a month. One given a rule it can apply itself will keep it for years.

The failure mode of under-lawyering. Nobody reads the engine licence before the revenue threshold, nobody notices the derivative rights grant in the publishing agreement, and nobody registers within the window.

The emotional dimension. Clone disputes are unusually hard on founders, because the thing copied is the thing they spent years designing and the law's answer is that it was never theirs. The temptation is to soften it, and that produces a demand letter that cannot be backed, a year of expectation, and a portfolio still built in the wrong place.

A note on international variation. Some systems reach game imitation through unfair competition doctrines requiring no copyrightable expression, and others protect a coherent look and feel more readily than US law does. A studio with meaningful revenue in those markets may have claims that do not exist at home, and the analysis should not stop at the US answer.

A note on the store as first resort. Platform takedown processes resolve more clone disputes than courts do, they are free, and their policies against copycat products reach conduct copyright does not. Studios reach for litigation because the injury feels large and skip the remedy that works within days.

A Suggested Reading Path

For the doctrine:

For the platform and user content layer:

For the assets and code layer:

For the brand and character layer:

Primary Authorities

| Authority | Proposition | |---|---| | 17 U.S.C. § 101 | Work made for hire; audiovisual works | | 17 U.S.C. § 102 | Ideas and systems excluded | | 17 U.S.C. § 103 | Compilations and derivative works | | 17 U.S.C. § 106 | Exclusive rights | | 17 U.S.C. § 107 | Fair use | | 17 U.S.C. § 120 | Representations of buildings | | 17 U.S.C. § 204 | Signed writing for transfers | | 17 U.S.C. § 411 | Registration before suit | | 17 U.S.C. § 412 | Statutory damages and fees | | 17 U.S.C. § 512 | Safe harbour | | 17 U.S.C. § 1201 | Anti-circumvention | | 35 U.S.C. § 101 | Patent eligibility | | 35 U.S.C. § 171 | Design patents | | 35 U.S.C. § 173 | Design patent term | | 15 U.S.C. § 1051 | Intent-to-use applications | | 15 U.S.C. § 1114 | Trademark infringement | | 15 U.S.C. § 1125 | False designation; trade dress | | 47 U.S.C. § 230 | Platform liability for user conduct | | Baker v. Selden | System versus explanation | | Tetris Holding v. Xio Interactive | Visual expression protected | | Google v. Oracle America | Interface reimplementation | | Sega Enterprises v. Accolade | Intermediate copying for interoperability | | Sony Computer Entertainment v. Connectix | Reverse engineering an emulator | | Andy Warhol Foundation v. Goldsmith | Transformative purpose narrowed | | Feist Publications v. Rural Telephone Service | Originality | | Lenz v. Universal Music | Fair use before takedown | | Rogers v. Grimaldi | Expressive works and marks | | Jack Daniel's Properties v. VIP Products | Source use limits the defence | | Alice v. CLS Bank International | Abstract idea framework |

Forms and Templates

The single most valuable artefact in a game studio's legal file is not an agreement — it is the asset register, started on the first commit and maintained at acquisition. One row per asset or asset source, with the item and version, the source type, the date acquired, the licence document reference stored alongside rather than linked to a vendor page that will change, the seat or project or platform limits, the redistribution and modification permissions, the attribution requirements, whether it ships in the build, where it is used, and whether generative tooling contributed. The Portfolio Inventory Template adapts to it directly, and the operating rule is that a missing licence reference blocks a build. Provenance is the finding that most often derails a publishing deal or an acquisition, and retrofitting it across three years of development is a project rather than a task.

The Assignment Agreement Template is the ownership instrument. Contractor art and code are not works made for hire in most categories, 17 U.S.C. § 204 requires a signed writing, and without one the contractor owns assets already in the shipped product — the worst finding in game diligence. Present-tense assignment language, executed before work begins, covering preliminary materials and source files as well as delivered work, and extended to outsourced studios flowing the obligation to their own personnel.

The License Agreement Template covers the inbound side — engine terms with royalty triggers and branding requirements, middleware, music with composition and recording rights treated separately, voice talent with synthetic reproduction terms, and core library licences — and the outbound side where a studio licenses its own technology. The terms of service, the user content licence, the mod policy, and the streaming policy are the studio's own instruments, and they are drafted once and reviewed whenever the business model changes.

Related Toolkits and Checklists

The Game Development Legal Checklist runs the programme from first commit to sunset with gates before a build ships and before a demand letter goes out. The Software, Data, and Open Source Toolkit covers the composition analysis and copyleft obligations that shipped firmware and tooling carry. The Data Licensing and Rights Toolkit covers the telemetry and player data layer that a live service generates. The AI Content and IP Toolkit covers the generative tooling questions that now touch concept art, placeholder assets, dialogue, and runtime content. And the IP Audit and Portfolio Governance Toolkit covers the register discipline the asset inventory depends on.