Welcome to the Metruvia Content Creator mod.io publishing tool guide for our series on Transport Fever 2 mod distribution. If the first article was about the “bricks and mortar” of your mod’s file structure, this article is about the logistics network that delivers those bricks to the world.
In the year 2026, the gap between “hobbyist modder” and “content creator” has closed. With the Transport Fever franchise expanding its footprint across consoles and the upcoming Transport Fever 3 promising even tighter integration with unified modding platforms, understanding the Mod.io API and the Cloud Dashboard is no longer optional. It is the difference between a mod that gets 10 downloads and one that becomes a staple of the global “Must-Have” list.
This guide will walk you through every button, toggle, and API call involved in the publishing process. We will cover the in-game publishing interface, the advanced features of the Mod.io web dashboard, and how to use the API to manage your portfolio like a pro.
1. The Gateway: The In-Game Publishing Tool
Urban Games built a bridge directly into the Transport Fever 2 main menu. For 90% of your needs, the Publish Tab in the Mod Browser is your primary interface. However, it is not a “set it and forget it” tool. It is a synchronization engine.
1.1 The “Publish” Trigger
To see your mod in the Publish tab, it must reside in the staging_area (as discussed in Article 1). If your folder is named correctly—author_modname_1—the game will scan the mod.lua and present it to you.
The First-Time Sync:
When you click “Publish” for the first time, the game communicates with the Mod.io API to create a Unique Resource ID. Once this ID is generated, it is “baked” into your mod’s metadata in the cloud. This is why you should never manually copy-paste the mod.lua from one mod to another; if you copy an existing Resource ID, the API will attempt to overwrite your old mod with the new one.
1.2 Platform Selection: The Critical Fork in the Road
Within the publishing UI, you will see a dropdown for “Platform.”
Steam Workshop: The traditional route for PC-only players.
Mod.io: The cross-platform route.
Warning: You can publish to both, but they do not “talk” to each other. If you update your mod on Steam, it does not automatically update on Mod.io. You must treat them as two separate delivery pipelines. In 2026, many creators are moving to Mod.io-First workflows because it covers the Epic Games Store, GOG, Mac, and Consoles in a single click.
2. The Cloud Dashboard: Your Strategic Command Center
While the in-game tool is great for uploading files, the Mod.io Web Dashboard is where you actually manage your mod’s life. To access this, you must log in to the Mod.io website and navigate to your “Creator” profile.
2.1 The “Edit Mod” Interface
Once your mod is uploaded via the game, it will appear in your dashboard. Here, you have access to parameters the in-game tool doesn’t show:
Visibility Toggle: You can set a mod to “Hidden” while you fix a day-one bug. This allows you to keep the mod page active for existing subscribers while preventing new ones from downloading a broken version.
Maturity Rating: While Transport Fever 2 is generally family-friendly, if your mod includes “gritty” realistic graffiti or certain historical themes, you must tag this correctly to avoid being flagged by platform moderators.
The Homepage/URL: You can create a “vanity URL” (e.g., mod.io/g/tf2/m/my-super-train). This is vital for social media sharing and SEO.
2.2 Advanced Tagging: Beyond the Basics
The in-game tool only allows for basic tags like train or bus. The web dashboard allows for Custom Taxonomies.
Region: (e.g., North America, Europe, Asia)
Era: (e.g., Steam, Diesel, Electric, Future)
Technical: (e.g., Script-Heavy, High-Poly, Vanilla-Style)
Properly tagging your mod in the dashboard ensures that when a console player filters for “European Steam Locomotives,” your mod actually shows up.
3. The Art of Metadata: SEO for Modders
You’ve spent weeks on the 3D mesh, but if your metadata is poor, your mod will stay buried. Mod.io is a search engine, and you need to treat it like one.
3.1 The Summary vs. The Description
The Summary (250 Characters): This is what appears in the search results list. It should be a “hook.”
Bad: “A locomotive mod for my game.”
Good: “The definitive 1950s Heavy Freight Diesel. Optimized for console with 3 custom LODs and realistic engine sounds.”
The Description (Markdown Supported): Use the web dashboard to format this. You can use bolding, bullet points, and even embed YouTube videos of your mod in action. In 2026, a “Feature List” is the standard. Players want to know exactly what is in the box before they hit the 150MB download.
3.2 Thumbnail Optimization
The in-game tool grabs a square screenshot. Don’t use it. In the web dashboard, upload a dedicated 16:9 1080p hero image. Use a photo editing tool to add the mod’s name in a clear, readable font. Console players browse on TVs; tiny text on a screenshot will be unreadable.
4. Versioning and the “Reversioning” Trap
One of the most complex aspects of the Mod.io API is handling updates.
4.1 Push vs. Pull
When you upload a new version of your mod, Mod.io doesn’t instantly delete the old one. It keeps a File History.
The Current File: This is the one new users get.
The Archive: Older versions remain in the cloud. This is a lifesaver if you push a “hotfix” that accidentally breaks everything—you can “revert” to the previous version in the dashboard in seconds.
4.2 The minorVersion Logic
In your mod.lua, you have a minorVersion integer.
Vtotal=Major_Version.Minor_Version
Whenever you push a change to Mod.io, you should increment the minorVersion.
Incremental Updates (v1.1, v1.2): Used for bug fixes, new liveries, or sound tweaks. These generally don’t break save games.
Major Overhauls (v2.0): If you are changing the internal folder structure or renaming files, you are moving to a new Major Version. Warning: If you change a file name (e.g., train_old.mdl to train_new.mdl), the save game will look for the old file, fail to find it, and crash. Always use the severityRemove parameter (discussed in Article 1) to warn players.
5. The Mod.io API: For Power Users and Automation
If you are a member of a modding “team” or you manage 50+ mods, the web dashboard is too slow. This is where the REST API comes in.
5.1 Obtaining your API Key
In your Mod.io account settings, you can generate an API Access Token.
Security Note: Never share this token. It gives full read/write access to your entire mod library.
5.2 Automating the Workflow
Using a simple Python script or a tool like curl, you can push updates to multiple mods simultaneously. This is how the “Pro” teams in 2026 manage massive asset packs. Example API call (Conceptual):
POST https://api.mod.io/v1/games/1066780/mods/{mod_id}/files
Authorization: Bearer {your_token}
Content-Type: multipart/form-data
file=@my_updated_mod.zip
version=1.5
changelog=”Fixed wheel animation and lighting.”
5.3 Webhooks: The Community Connector
You can set up a Webhook in the dashboard. Whenever you update your mod, Mod.io can send an automated message to your Discord server or Twitter/X feed. This keeps your community engaged without you having to manually type out “Update is live!” every time.
6. Community Governance: Comments, Ratings, and Reports
Mod.io is a social platform. Managing your “Brand” as a modder is as important as the code.
6.1 The Rating System
Unlike Steam’s “Thumbs Up/Down,” Mod.io uses a percentage-based rating system.
Positive Sentiment: Drives your mod up the “Trending” list.
The “Report” Button: If a player reports your mod, it goes to Urban Games’ moderators. Most reports are “User Error” (e.g., the player forgot a dependency), but if you are flagged for “Copyright Infringement” (using a real-world logo without a disclaimer), your mod will be suspended.
6.2 Managing Comments
The Cloud Dashboard allows you to pin comments (e.g., an FAQ) and delete spam. In 2026, “Toxicity Filters” are more robust, but as a creator, you should be the primary moderator of your own page. Empathy goes a long way: if a player has a crash, ask for their stdout.txt log rather than being defensive.
7. Analytics: Who is playing your mod?
One of the greatest features of the Mod.io dashboard is the Analytics Tab. It provides data that the Steam Workshop simply doesn’t.
7.1 Platform Breakdown
You can see exactly how many people are playing your mod on:
PlayStation 5
Xbox Series X
PC (Epic/GOG/Microsoft Store)
7.2 Geographic Data
Are you making a Japanese locomotive? You might be surprised to see 40% of your downloads coming from Germany. This data is invaluable for deciding what to build next. If your “British Rail” pack is blowing up in the US, perhaps an “American Shortline” pack is a good next move.
7.3 Subscriber Retention
The dashboard shows you “New Subscribers” vs. “Unsubscribes.” If you see a massive spike in unsubscribes immediately after an update, you broke something. Check your logs immediately.
8. Troubleshooting the Upload Pipeline
Even with a perfect mod, the API can fail. Here are the 2026 “Common Fixes”:
Error 401 (Unauthorized): Your API token has expired or your in-game Mod.io login has timed out. Re-log in through the main menu.
Error 413 (Payload Too Large): You hit the 200MB limit. Go back to Article 1 and purge your junk files.
“Validation Pending”: This isn’t an error. It means your mod is in the queue for Console Certification. It will be available on PC immediately, but the PS5 version is waiting for a human to check your LODs and textures.
Thumbnail Not Updating: The Mod.io CDN (Content Delivery Network) can be slow. If you changed your image but still see the old one, clear your browser cache or wait 30 minutes.
9. Metruvia Content Creator: The Responsibility of the Cloud
Distributing through Mod.io is a professional-grade commitment. You aren’t just dumping a file on a forum; you are pushing code to thousands of living-room consoles.
By mastering the Cloud Dashboard, you ensure that your work is discoverable, your updates are stable, and your community is informed. The API is your friend—it handles the complex compression and distribution logic so you can focus on what you do best: building the future of transportation in Transport Fever 2.