Terms

Every mod, map and file on this site downloads for nothing. You do not need an account or a key. You need to own OPERATOR, and that is it.

The Patreon runs several tiers, priced monthly. None of them buys a mod, a map or a fix that free players never get. What the higher ones buy is time and a voice: a build about a week before everyone else, a vote on what gets built next, and a seat in the channels where that gets decided. The top tier gets a direct say in which projects we take on at all. A week's head start and a vote are not a file, and every mod, map, mission and fix still reaches every player, free, once it ships. That part does not move tier to tier, and if it ever did, it would change on this page before it changed anywhere else.

A couple of tiers also earn you personal credit for what you contributed: your name in the patch notes for a bug you found, or a patch for your own kit if the fix you flagged ships. That is a thank-you for what you did, not a piece of the pack.

Current tiers, prices and what each one includes live on the Patreon page, because that is the page we actually keep up to date.

What the money covers is the domain and the file server, plus the hours. Nothing in the pack is for sale, there or here.

Patreon runs the billing and we don't. They charge the card and set the date, and they sit on the money for about a week before any of it moves. The amount on your statement can come out higher than the tier price, because Patreon adds the tax your country requires, and an app store adds its own cut if you joined from inside an app. We never see a card number.

Cancelling is on their side too. You do it from your own Patreon account before the next billing date. Refunds go through Patreon's billing history within 60 days of a payment, and through Patreon support after that. Ask us if you like, but we can't return money we never held.

We're a creator on somebody else's platform, so Patreon's rules apply to us. One of them is that a creator can only offer what they have the right to offer, and Patreon can pull the page if that stops being true. Their rule and ours point the same way. The Patreon is funding. The pack is free. Nothing built on another studio's assets is being sold to anyone.

Most of the pack is built on OPERATOR's own art. The rifles use weapons, meshes and parts the game already ships, and three of the five missions are the game's own scenes with the competitive machinery switched off. All of it runs on a copy of the game you already own.

THE WORLD'S WORST AIR BNB and THE OFFSHORE ACCOUNT are built with assets from Ground Branch by BlackFoot Studios. We also put a lot of our own work into both of them, including the sky scenes.

Some of the textures and work in the closet come from DegenerateXL, SevenStudios, MarseloGogob0y, Mscabecinha, your401kplanreturns and .ScottSauce. [UES], whose originals are on Nexus Mods. We networked them, so what one player is wearing shows up on everyone else's screen. If any of them wants a credit worded differently, or wants their work out of the pack, section 04 applies to them the same as to anyone else.

Some insignia is military or belongs to serving units. Where an asset carries a Creative Commons licence, the credit ships in a PROVENANCE file inside the bundle and travels with it.

Trademarks belong to their owners. Weapon names, camo patterns, brands and insignia are used to identify the thing you are looking at. No endorsement is implied and none has been given.

If you hold rights to something in this pack and you want it gone, write to us and it is gone. We will not argue and we will not make you file a formal notice first. We may ask you which files you mean, so that we remove the right thing and not the wrong one.

What happens: we pull the file from distribution, take the page down, and stop the launcher handing it out. We aim to do that within 48 hours of reading your message, and faster in practice. If you want a change instead of a removal, say so and we will do that instead.

This applies to any rights holder, including BlackFoot Studios, the developers of OPERATOR, marketplace asset authors, and anyone whose insignia or artwork is in the closet.

Everything here is provided as is, with no warranty of any kind. We do not promise that a mod works, that it keeps working after a game update, or that it does what the page says on your machine.

Mods change how a game runs. This one loads code into OPERATOR and writes files into its folder. It can crash the game, corrupt a save, break a session for whoever you're playing with, or stop working the day the game updates. We test what we ship and we fix what gets reported, and neither of those is a guarantee.

You install it because you want to. To the fullest extent the law allows, we are not liable for damage, lost data, lost time or anything else that follows from using it. Some places do not allow that exclusion, and where yours does not, your local law wins and this paragraph gives way to it. If you are not comfortable with any of that, don't install it.

Installing mods may also breach the game's own terms of service. That's between you and the game's developers, and you should know it before you start.

Free players can skip this section. The public pack needs no account, no key and no sign-in, and that is not going to change.

What a key is. A subscriber launcher holds one: thirty-two random bytes, issued by our server, kept in a file on your own PC. We store only a one-way hash of it, the same way a password is stored. It is not a password and there is nothing to remember. It identifies your launcher so the server can answer one question: is this person's subscription live.

Two ways to get one. An invite code, which is eight characters you type once. Or sign in with Patreon, where the launcher opens your browser, you sign in to the account you already have, and the launcher picks the key up on its own. Both end in the same place. The code works whether or not you use Patreon.

What the launcher asks. When it starts, and about once an hour while it is open, it asks our server who it is. The answer is small: active or ended, which tier, and the name on the account. The server writes down when your launcher last asked and which version it is running, and that is what tells us whether a bug report is about a current build.

The developer distro. Two tiers reach the private repository where the work happens. That is a GitHub collaborator invite on a real repository, so it needs your GitHub username, and we check the name exists before it goes anywhere. Nothing is sent automatically. A person reads the request and presses confirm, because a payment can clear and reverse within the hour and a repository invitation cannot. Once you are in, GitHub's own terms and privacy policy cover what happens there.

How access ends. Cancel on Patreon and it ends when Patreon says so, usually at the end of the period you already paid for. We can also end it ourselves: for a payment that never arrived, for sharing your key or the private repository with people who did not pay, or for conduct that makes the channels worse for everyone. We will tell you why.

What ending it does. Your launcher stops starting the game and stops treating the subscriber pack as installed. It offers you three things: resubscribe, remove the pack, or download the free launcher and carry on with the public release. Nothing is deleted from your PC unless you press the delete button yourself. The files stay exactly where they are. If you come back, the launcher downloads the current pack from scratch. A folder that has sat outside the update path for a month is not worth trusting.

What we will not do. We will not reach into your game folder to delete anything because a payment stopped. We will not disable a mod you already had. The free release stays free and stays available, and it carries everything the paid one does, a little later.

No advertising, no analytics, no tracking across the site, and nothing about you is sold, because there is nothing to sell. Free players still have no account of any kind. What changed is that subscribers now do, so this section says exactly what that holds.

Server logs. Like any web server, this one sees your IP address and the pages you ask for. Those logs exist to keep the site up and to stop abuse.

Download counts. Two numbers per file: how many times it was downloaded, and how many separate people downloaded it. The second one has to tell one visitor from another, so the server keeps a keyed one-way hash of your address beside the file name. The key lives on the server and never leaves it. A hash can't be turned back into an address; all it can do is match another hash of the same one, which is what stops six clicks from one person reading as six people. The figure on the downloads page is that count.

Bug reports. If you file one, we keep what you typed, the pack version, the machine description, and the log file you attached. Name and contact are optional and blank is fine. Your IP is stored as a one-way hash for rate limiting, so we can tell two reports came from the same place without knowing where that is.

Open a log file before you send it. A game log usually contains your Windows username, folder paths and your hardware. Have a look first if that concerns you. We use it to work out what broke and for nothing else.

Subscriber accounts. If you connect a launcher, our server keeps one row about you. It holds the name to call you, your tier, whether access is live, a one-way hash of your launcher key, your Patreon member id if you signed in that way, the pledge amount Patreon reports, when your launcher last checked in, which launcher version it was running, which version of these terms you accepted and when, your GitHub username if you asked for the developer distro, and a short note field we use for things like "paid by bank transfer". That is the whole row. There is no email address in it, no payment details, and nothing about your PC.

What the launcher sends. Your key, and the launcher version, to our server only. It does not send your game files, your saves, your logs, your hardware, your Windows account or anything you play. There is no telemetry in it. Downloads come from GitHub, so GitHub sees the download the way it sees any download.

Signing in with Patreon. This is a change from how it used to work, and it is worth being blunt about. If you use that button, Patreon tells us your member id, the name on your account, whether you are an active patron, the amount you are entitled to, and whether your last charge went through. We keep those in the row above, The last two are how the launcher knows the money actually arrived. We do not ask Patreon for your email, your address or your card, and Patreon does not give us your card at any point. Patreon also sends us a signed message when a pledge starts, changes or ends, so the row stays current without us reading anything extra. If you would rather none of that reach us, use an invite code instead: that route tells us nothing except the name you are given and the tier on the code.

Patreon itself. Clicking the link takes you to their site, under their privacy policy, with your account and your card held by them. As a creator we can see what every creator sees about their own patrons, including the email on the account. We use that to know who is supporting the work and to reply if you write to us. It is not put on a mailing list and it is not passed to anyone. Patreon's record is theirs, so corrections and deletions there go through Patreon.

GitHub. If you take the developer distro, we send your username to GitHub to invite you to a private repository, and we remove it the same way when access ends. GitHub then holds whatever GitHub normally holds about an account of theirs, and we have no part in it.

Fonts. Pages load two typefaces from Google Fonts, so Google's servers see your IP when a page loads. Nothing else on the site calls out anywhere. The launcher loads nothing from anyone but our server and GitHub.

Cookies. None for visitors. The developer portal sets one session cookie for whoever signs in, and that page is not for players. The launcher uses no cookies at all.

How long we keep it. A subscriber row lives while the account exists and for a while after. Somebody who resubscribes then comes back to the account they had. Bug reports are kept while the bug is open and cleared out afterwards. Logs rotate.

Getting it deleted. Ask, and we will delete your subscriber row, your GitHub username and any bug reports you name. Send the ticket number for a report. Deleting the row ends the access it carried, so ask when you mean to leave. Your Patreon record is Patreon's, and that one you ask them for.

Who can see all this. The server is ours and the database sits on it. The portal behind it needs a named account with a password and a second factor. The launcher key on your PC is yours; we hold only a hash, so nobody here can read it back out and pretend to be you.

Don't use the report form to send abuse, spam or anything illegal. Don't hammer the server. We can block an address that does either.

Our own work in the pack is yours to share: pass it on, mirror it, put it on a server for your friends. A link back here means they get updates. Do not sell it, do not put it behind a paywall or a link shortener that pays you, and do not present it as your own.

We cannot licence the parts that came from somewhere else, and we are not pretending to. Sharing the pack is not permission to lift the assets inside it and use them in your own project. That permission is the original author's to give, not ours.

These terms can change. The date at the top says when they last did. If a change affects you, the release notes will say so.