Protected assets

Sell protected mods on Neighborly servers – what the protection covers and how to use it.

Protected assets are Neighborly's version of asset escrow. Creators sell custom content (.package) and script mods (.ts4script), grant them to the servers that bought them, and every player on those servers gets them automatically – without the server owner or the players ever getting a clean, shareable copy from Neighborly.

What protection covers – honestly

The Sims 4 can only load mods that sit as normal files in its Mods folder while it runs. Nobody can change that, so no system can make a mod uncopyable while the game is open. What Neighborly does is keep the files out of reach everywhere else, and make every copy traceable:

Encrypted everywhere elseYour files are encrypted in your browser before upload, stored encrypted on Neighborly with a key for each asset, sent to each player encrypted for that player, and kept encrypted in the launcher's cache.
Server owners never hold themA server only knows the asset ID and version it's allowed to use. The files never touch the server, so its owner has nothing to extract.
Only for the sessionThe launcher unlocks the files into the game's Mods folder when you press Play, under random file names, and deletes them as soon as the game closes. After a crash, they're deleted the next time the launcher starts.
A watermark in every copyEach delivered copy carries a signed, encrypted mark naming the player account and the server it was sent to. The leak checker reads it back.
Access you controlGrant an asset to one server or many, and revoke it at any time. Revoking blocks the next Play – cached copies can't be unlocked anymore.
Sources stay homeFor script mods, Neighborly can ship only the compiled Python files and strip your .py sources.

What it can't do: someone who copies the files out of the Mods folder while the game is running has a working copy, compiled Python can be decompiled, and a skilled person can strip a watermark. Protection makes casual sharing impossible and leaks traceable to an account and a server – it's a strong lock on the door, not a vault the game can't open.

For creators

  1. Get creator accessThe studio is invite-only while it's new. Ask the Neighborly team on Discord to unlock it for your account.
  2. UploadOpen the Creator studio, press New asset, give it a name and a version and drop your .package and .ts4script files. One asset can hold several files.
  3. Grant serversSearch servers by name or paste a server ID and press Grant access. The server lists the asset within a few seconds – the owner doesn't install anything.
  4. UpdateUpload a new version whenever you like. It goes live right away; you can make an older version live again or delete it.
  5. Watch and traceSee how many players and servers use each asset. Found a copy where it shouldn't be? Drop it into the Leak checker to see which player and server it was delivered to.

Script mods and Python 3.7

The Sims 4 runs Python 3.7, so compiled files must be Python 3.7 bytecode. With Ship compiled files only turned on (the default), Neighborly removes every .py source from your .ts4script and ships only the .pyc files.

  • Every module needs its .pyc right next to it, for example mymod/main.pyc beside mymod/main.py. Build them with python3.7 -m compileall -b. Files in __pycache__ folders aren't used by the game.
  • Uploads with .py files but no matching .pyc are refused with a list of the missing modules. Neighborly doesn't compile for you: only a real Python 3.7 produces bytecode the game is guaranteed to run, and guessing would break your mod for players.
  • .pyc files made with another Python version are refused, because the game can't load them.
  • If you turn the option off, your sources ship as they are and are only protected by the encryption and watermark.

How watermarks work

  • .package – Neighborly adds one small extra resource of its own type to the package index. It holds the player and server IDs, encrypted and signed so it can't be forged or read by anyone else. A second short tag sits in an unused part of the package header. Both sit where The Sims 4 doesn't look, and every one of your resources stays byte-for-byte the same.
  • .ts4script – a small extra file inside the zip carries the same signed mark, plus a short tag in the zip directory. Python ignores it.

The leak checker reads the marks in your browser and sends only the marks to Neighborly, never the whole file. You only see results for your own assets.

For server owners

Nothing to set up. Once a creator grants an asset to your server key, your server lists it and players get it when they join. Your server needs a valid server key, and players must be signed in to the launcher – protected mods can't be delivered to players without a Neighborly account. Normal mods in your mods folder keep working exactly as before.

For players

Nothing to do. Press Play as usual – the launcher downloads protected mods, unlocks them for your session and removes them when you close the game. Your copy is marked with your account, so please don't share it.

Limits

WhatLimit
One .package512 MB
One .ts4script64 MB, a normal zip (no ZIP64, no password)
Files in one version40
Storage per creator5 GB across all versions
Servers per asset500