Transport Fever 3 · PYT - Blueprint Exchange

Blueprint Pack Maker

Put your blueprints in a pack that anyone can subscribe to on mod.io. Once subscribed, the pack’s blueprints appear in their BPX Library — no files to move.

1. Add your blueprints

The blueprints you named in BPX are files in your myblueprints folder: C:\Program Files (x86)\Steam\userdata\your number\3493540\local\myblueprints

No blueprints yet.

    2. Name your pack

    It goes at the very top of the pack’s mod.io page, next to PYT - Blueprint Exchange, so nobody subscribes without them.

    The picture

    This shows on mod.io. We make one from your pack’s name, or use your own screenshot — it’s cropped to 16:9.

    3. Download, try it, upload it

    Add blueprints, a pack name and your name first.
    1. Unzip it and move the folder inside (it starts with bpxpack_) into your staging_area folder: C:\Program Files (x86)\Steam\userdata\your number\3493540\local\staging_area
    2. Try it. Start Transport Fever 3 and load a game with PYT - Blueprint Exchange and your pack switched on. In the BPX Library pick Show: Packs and paste one.
    3. Upload it from the game to mod.io as you would any mod — run its Validation Report first.
    4. Keep the folder. The game remembers your mod.io page in it: to update the pack, change the files there and upload again.

    Help

    Why make a pack?

    A blueprint file can be shared by hand, but only on a PC, and the other player has to find the right folder. A pack is a mod: players subscribe to it on mod.io like any other, and its blueprints show up in their BPX Library on their own.

    Is anything uploaded when I use this page?

    No. Your files are read, checked and zipped right here in your browser. Nothing is sent anywhere — you upload the pack yourself, from the game.

    Why was one of my files refused?

    The Pack Maker only takes BPX blueprint files, and only plain data: track, roads, stations, signals and their settings. Anything else in a file (like a piece of program code) is refused, so a pack can never carry something unexpected to the people who subscribe.

    My blueprint uses another mod’s track or roads

    Then players need that mod too. Say so in “More about it”, so it’s on the pack’s mod.io page.