Paid mods, fan guidelines and EULA: when monetization is possible

The current dispute over a VR mod for a major AAA game is a good starting point because it highlights a pattern that recurs in almost every major modding complex: technically, something is added that many gamers want, economically it quickly becomes a subscription model or a paywall, and legally, three levels collide, which are often mixed up in discussions. The first level is copyright law, i.e. the question of whether the mod encroaches on protected positions and whether permission is required for this. The second level is contract law, in particular EULA/Terms of Use and other terms of use, which often extend very far in the case of games. The third level is enforcement practice, i.e. takedowns, platform mechanics, cease-and-desist letters, injunctions, the logic of the value in dispute and the question of when it is worth escalating or negotiating a solution.

This article deliberately does not focus on “news”, but on sound principles. The aim is a realistic classification: modding is not automatically “illegal”, but in practice monetization is almost always the point at which toleration becomes a conflict. If you want to generate revenue, you need a clean license chain or a business model that cannot legally or actually be read as the sale of an IP-related product.

Fan guidelines: What are they anyway?

At first glance, “fan content guidelines” or “fan policies” look like general terms and conditions. In fact, they are legally something separate: they are usually publicly communicated rules under which a rights holder tolerates or (partially) permits certain uses. Dogmatically, this can be described as a kind of unilateral permission with conditions. The essence is: without permission, the legal exclusive rights of the rights holder remain in force. Guidelines define an area in which the rights holder typically does not intervene – as long as the conditions are met. This is less a “contract” in the traditional sense than a licensing policy.

Whether guidelines are GTC depends on how they are incorporated into a contractual relationship. If they are part of an EULA or expressly included in a user relationship, the rules on general terms and conditions (Sections 305 et seq. BGB) and their effectiveness control apply. However, many publishers work on two tracks: the EULA regulates the use of the game and contains modding prohibitions or modding permissions, while guidelines are an additional document describing which forms of fan content are tolerated and how branding, disclaimers or monetization should be handled. In this constellation, guidelines are often less “terms and conditions clauses” than an external framework that explains when the rights holder makes use of their rights.

In practice, the distinction is important because GTCs only apply to persons who are contractual partners. A purely “public set of rules” does not bind anyone per se. It does not act like a law. The leverage arises differently: anyone who interferes with protected rights without a license is in copyright anyway. Anyone who wants to claim tolerance must comply with the conditions. Seen in this light, guidelines are less a “bond” than a “door sign”: Behind them is copyright; the sign only says when the door is open.

“What if the modder has not accepted the EULA at all?”

The question is central and is often answered incorrectly in practice. If no contract has actually been concluded, contractual prohibitions from the EULA do not apply directly. However, this does not mean that there is free rein. In this case, copyright law, trademark law and, if applicable, competition law must be considered. The rights holder does not have to prove that an EULA has been accepted in order to enforce copyrights.

Moreover, “non-acceptance” is less common than is claimed in discussions. Anyone who installs, launches or updates the game or uses online services regularly accepts conditions somewhere; this also applies if a key has been passed on, a family account is used or access is via cloud/subscription. Even if the mod developer has not purchased the game themselves, consent to acts of use may still exist. And even if this is not the case: as soon as a modding SDK, editor, API access or developer portal is used, separate contractual relationships often arise. In many ecosystems, this is the legal basis for modding: Access to tools or interfaces is only granted in return for agreement to developer terms.

In theory, however, it is still possible for a modder to dock onto a game using only technical means without being a contractual partner. Then the question is not “how does an EULA bind”, but “which copyright-relevant actions take place”. In this situation, the main issue is not contract law, but the copyright qualification of the modding process.

Copyright core: Modding between Section 69c UrhG and “intended use”

Computer games are legally mixed works. Copyright protection applies to software components (§§ 69a ff. UrhG) as well as graphics, music, texts and other components of the work. In practice, the software rules are particularly decisive for technical mods. § Section 69c UrhG assigns the exclusive rights to the computer program; this includes, in particular, reproduction and adaptation. § Section 69d UrhG permits actions that are necessary for the intended use, such as loading and running. § Section 69e UrhG allows decompilation for interoperability under strict conditions.

These standards form the framework within which technical mods operate. As soon as a mod interferes with program sequences, patches code, injects into memory structures, uses debug interfaces or bypasses protective measures, the question arises as to whether this constitutes an adaptation requiring consent or any other use relevant to copyright law. Anyone who argues that a mod contains “no assets” and “no code” of the game is regularly aiming to defend against the accusation that protected content is being reproduced or distributed. This can help in certain constellations, but does not automatically solve the problem of editing and certainly not the problem of a possible circumvention of technical protection measures.

For the practical risk analysis, the question of whether the mod “includes files” is therefore less important than what happens technically. A pure config layer that sets permissible parameters is to be treated differently from a binary patch in legal terms. An external tool that redirects input devices or renders an overlay is to be assessed differently to a hooking system that changes the render path. A VR implementation often involves deep interventions in rendering and camera handling. The deeper the intervention, the more likely it is that Section 69c UrhG will come into focus.

At the same time, modding in the PC sector has been a de facto part of the user culture for decades. Many types of use are tolerated by rights holders without every single technical action being legally clarified in detail. In practice, this tolerance often does not end with the technology, but with commercialization.

Trademark law and misrepresentation: The mod is not just “code”

Alongside copyright law, trademark law is often the second stumbling block. Even the term “Cyberpunk VR Mod” or a logo use can create points of contact under trademark law if the impression is created that the product is official, licensed or part of the publisher ecosystem. Even if a mod is technically “clean”, branding can be a risk in its own right. In addition, there are competition law issues if the product presentation, compatibility or “official” support is misleading. Those who pay expect quality; if conflicts then become public, a rights holder often reacts not only out of IP interest, but also to protect their brand and reputation.

Practical experience with clients shows that the legal attack surface rarely arises from a single standard. It is usually a bundle of copyright arguments, EULA infringements, trademark use and platform conditions. The more monetization is involved, the more likely this bundle is to be pulled.

Paywall, Subscription, Early Access

The difference between “donations” and “paywall” is not only morally, but also legally and factually relevant. A paywall links access to an IP-related product to payment. This turns fan use into a commercial offer. It is precisely at this point that toleration becomes politically and economically unattractive: a publisher must fear that a parallel market will emerge that creates support expectations, radiates quality problems onto the brand and also sets a precedent that is difficult to explain to other creators.

In contrast, “donations” are typically structured in such a way that the content remains free and the contribution is voluntary. Many guidelines tolerate donations because they have less of an economic effect like an exploitation of someone else’s IP value and more like a recognition of the development work. However, as soon as “only supporters get the build”, “early access exclusive”, “subscription for updates” or similar models are chosen, access is effectively for a fee. The risk then increases not only legally, but also in terms of enforcement: platforms react more quickly to paywalls because a “commercialized conflict of rights” is regularly classified as a higher risk.

Subscription models in particular are tricky. A subscription is not just a payment method, but a promise of ongoing service. This shifts the profile from a hobby project to a commercial software service. Although this can make economic sense, it requires a clearer legal basis. Anyone offering a subscription must expect that rights holders will take more consistent action because the continuation of the offer is directly affected and because sales can be used as a starting point for arguing for damages.

Is commerce even allowed?

Paid mods may be legally possible. In practice, however, certain conditions are necessary, because otherwise the classic question arises: “Is someone else’s IP being commercially exploited here?” Three ways are viable in reality.

The first way is the clean one: a license or cooperation with the rights holder. This can be negotiated individually, as a revenue share, as whitelisting of certain forms of monetization or via an official creator program. The decisive factor is not the name, but that the rights of use for the specific exploitation are granted, including distribution, update mechanics and, if applicable, brand use. If you choose this model, you can turn modding into a real business without permanently skating on the thin ice of toleration.

The second way is through official mod marketplaces or curated platforms. Where publishers themselves enable monetization, the licensing issue is typically resolved because the rules of the marketplace map the rights chain. This is attractive for creators because it creates legal certainty; it is attractive for publishers because quality and brand perception remain controllable.

The third way is the most difficult and at the same time the one that is often referred to in discussions: monetization of a tool that should not be qualified as an adaptation of the game. This can theoretically work if no protected content is actually used or distributed, no protective measures are circumvented and there is no contractual obligation to the contrary. In practice, this approach is fraught with conflict because publishers often argue that the economic value of the tool arises precisely from the use of the game and because technical details quickly lead into areas that are sensitive in terms of copyright or contract. If you want to go down this route, you need very precise technical documentation and very conservative distribution, otherwise the discussion quickly becomes a “question of faith”, which in the event of a conflict is no longer decided on social media, but via cease-and-desist declarations.

“Fan content” – what does that actually mean?

The term “fan content” is not a legal term, but a category of publisher communication. It usually refers to anything that is based on the game universe: Videos, streams, screenshots, artwork, cosplay, music covers, memes, but sometimes also mods. Legally, this category is heterogeneous. A stream can be treated differently under copyright law than a mod that changes program sequences. A meme can be treated differently from an asset bundle when it comes to copyright issues.

That is why it is regularly problematic when a modder says in debates: “This is not fan content”, and a publisher says: “Yes, it is fan content.” Both statements are often communicative, not dogmatic. In legal terms, the decisive factor is which actions are involved. A publisher can describe a mod as “fan content” in order to apply its own guidelines to it and at the same time argue under copyright law that editing/distribution requires consent. The modder can say “no fan content” to get out of this pigeonhole, but must then legally explain why no rights are affected and why no contractual obligation applies. This is possible, but rarely trivial.

Binding without a contract: Is copyright the only option?

If there is no contractual obligation, the legal assessment actually remains primarily in intellectual property law. However, this is not “less dangerous”, but often even more dangerous, because claims for injunctive relief do not depend on whether general terms and conditions have been effectively included. Injunctive relief under copyright law essentially presupposes an unlawful act of infringement; contract law is then only flanking.

In practice, the question “has the modder accepted the EULA” is therefore often secondary. The decisive factors are whether the product is based on another party’s protected position, whether it interferes with protected types of use and whether the exploitation is commercial. Commercial exploitation increases the probability that a court will consider an infringement to be significant, increases the amount in dispute and increases the willingness to not only communicate in a “friendly” manner, but also to take formal action.

Realistic design for creators: revenue without a paywall – and still professional

The economic pressure is understandable: A sophisticated mod costs time, knowledge and ongoing maintenance. Nevertheless, the “access only against payment” model is the classic trigger for conflicts in many ecosystems. A more realistic design separates the levels: The mod remains freely accessible; revenue is generated via voluntary support or services that do not sell access to the IP-related product. Support services, custom setups, compatibility work, advice for hardware setups, prioritization of certain bugs via bounty systems or training are examples where the economic performance is more based on one’s own work and less on the exclusivity of access.

Here, too, the boundary remains blurred. If you sell “support” but in fact only provide working builds to paying users, you are quickly back to a paywall. The difference is not in the headline, but in the actual structure: does the core functionality remain free or does it become commercially exclusive? This question is answered very soberly in the event of a conflict.

Realistic design for publishers: Why guidelines still make sense

The publisher side is often perceived as “arbitrary” in discussions. In fact, guidelines are a pragmatic instrument for controlling community practice without having to go through the legal process every time to determine whether a specific use would be permissible in detail. This is also in the interests of the community: without guidelines, there would only be tough legal enforcement or complete ambiguity. Guidelines are therefore often not an expression of “fan hostility”, but an attempt to enable creativity and at the same time control commercialization.

For publishers, a creator program or a defined license track can even be economically attractive. Those who generate sustainable quality from modding deliver innovation and customer loyalty. The conflict usually does not arise over “whether mods”, but over “who monetizes and who controls”. VR mods are a good example of this: they expand the market, but can also create support risks and brand risks if expectations of “official” VR functionality arise.

Commercial modding is not “wishful thinking”, but it is a licensing issue. As soon as a business model is to scale seriously, it is worthwhile not to operate on the edge of toleration, but to create a targeted rights basis. The legal leverage lies not only in copyright law, but in the overall package: rights of use to game components, distribution regulations, update obligations, liability, support delimitation, trademark use, communication rules, dealing with security vulnerabilities and, if necessary, compliance with platform rules. In the case of subscription models, there are additional consumer law and contract law issues relating to the company’s own product side, as an independent digital product is then offered, which in turn can trigger warranty, termination and transparency requirements.

From a mandate perspective, it is important that negotiations with publishers should not be conducted as a “request for permission”, but as a business case: which user groups are tapped into, how support is separated, how brand risks are minimized, which quality control is accepted, how security risks are handled, how revenue is shared, how conflicts are resolved. This is where the space is created in which a modder can change from a tolerated status to a reliable commercial position. For publishers, on the other hand, it is interesting to see how community innovation can be channeled without creating a proliferation of paywalls that are later difficult to regulate.

What to do in the event of a takedown or warning – without dramaturgy

In practice, the first escalation rarely leads straight to court. The first step is often removal, a change in the monetization model or subsequent licensing. It is crucial for creators not to react reflexively. Those who hastily issue cease-and-desist declarations are committing themselves in the long term. Those who escalate defiantly risk high amounts in dispute. The most sensible approach is usually to take stock of the situation: what technical actions have taken place, what distribution channels have been used, what revenue has been generated, what brands have been used, what disclaimers exist, what EULA or guideline texts were relevant at the time. This can be used to develop a realistic negotiating position: Switch to free distribution, clean up branding, request a license or partially dismantle problematic components.

The most common mistake is to conduct the debate purely about “no assets”. That is one point, but not the only one. The second misunderstanding is that “guidelines are not GTC” automatically means “guidelines don’t matter”. That is not true. If there is no contractual obligation, copyright and trademark law remain. If there is a contractual obligation, contract law applies. In both cases, a publisher can take action; the justification just shifts.

Conclusion: Monetization is possible – but not “just like that”

The current case shows one pattern in particular: technical arguments (“no asset, no code”) can be relevant in the matter, but do not automatically resolve the conflict if a business model is chosen that appears to be commercial exploitation from the publisher’s point of view. Fan guidelines are not a law and do not bind the world, but they do define what use is tolerated. Anyone acting outside of this framework ends up in formal enforcement mode more quickly, and then the talk is no longer about community culture, but about omission and chain of rights.

Commercial modding is realistic if a license basis is created or if the monetization is designed in such a way that access to IP-related functionality is not sold. Subscription models are particularly sensitive because they promise a permanent commercial service and thus structurally reinforce the conflict. In practice, the most sustainable approach is therefore either cooperation with the rights holder or a model that clearly separates free distribution and own services.

Creators and studios who want to be able to plan their activities in this field need fewer “hot takes” and more contract architecture. This is precisely where the value of the mandate arises: not in commenting on individual cases, but in setting up a robust monetization and licensing strategy that reflects both community interests and IP interests.

Author: Marian Härtel

Marian Härtel ist Rechtsanwalt und Fachanwalt für IT-Recht mit einer über 25-jährigen Erfahrung als Unternehmer und Berater in den Bereichen Games, E-Sport, Blockchain, SaaS und Künstliche Intelligenz. Seine Beratungsschwerpunkte umfassen neben dem IT-Recht insbesondere das Urheberrecht, Medienrecht sowie Wettbewerbsrecht. Er betreut schwerpunktmäßig Start-ups, Agenturen und Influencer, die er in strategischen Fragen, komplexen Vertragsangelegenheiten sowie bei Investitionsprojekten begleitet. Dabei zeichnet sich seine Beratung durch einen interdisziplinären Ansatz aus, der juristische Expertise und langjährige unternehmerische Erfahrung miteinander verbindet. Ziel seiner Tätigkeit ist stets, Mandanten praxisorientierte Lösungen anzubieten und rechtlich fundierte Unterstützung bei der Umsetzung innovativer Geschäftsmodelle zu gewährleisten.