What Is Microsoft Freelancer and How Do You Join Its Modding Community?

Microsoft Freelancer is a 2003 space shooter published by Microsoft, and its modding community is still active today — The Starport is one of the hubs where that activity lives. You can join by playing the game as-is, installing a mod, or registering on a community forum to ask questions. The main thing to get right before you touch any mod is where the game stores your saves and settings, because that folder is the usual cause of crashes when you switch between modded and unmodded installs.

The game, the mods, and the community hub are three different things

It helps to separate them before you start:

• Microsoft Freelancer — the base game from 2003. A single-player campaign plus multiplayer, set in a space-trading and combat universe.
• Mods — community-made changes that add content: new ships, items, systems, internal names, and so on. Some mods are large total conversions; others are small fixes.
• The Starport — a modding-focused community site built around Freelancer. It is not the game and not a mod. It is where people post news, ask for help, showcase work, and share tools.

The Starport organises itself into a few clear areas, which map neatly onto what you might want to do:

If you are brand new, General Discussion and Modding are the two places worth reading first. If you want to build something rather than play something, Programming & Tools is where the technical work happens — including reverse-engineering threads such as crash offsets.

Why Vanilla installs crash after you use mods

This is the single most common trap, and it is worth understanding before you install anything.

Freelancer keeps a local user folder at:

Documents\My Games\Freelancer

That folder holds your performance settings (screen resolution, for example), your hotkey binds, and your save files.

The problem is how the game reads saves on launch. It reads the single-player save files in that folder, and any incompatible data in them makes it crash. So any mod that adds content which is not strictly Vanilla-compatible in terms of save files — new items, new internal names, and similar — will cause a Vanilla Freelancer installation to stop starting up. That can happen even after the mod has already been removed, until the save files are cleaned up or moved.

In other words: the mod may be gone, but the save file still remembers it.

How one mod sidesteps the issue

HD-Edition is described as completely Vanilla-compatible, but it still respects this problem and pre-emptively avoids it by storing your single-player save games in a new folder. That way, if you also play (or played) older mods that do not redirect their saves themselves, your HD-Edition saves stay separate.

The trade-off: if you want to use older save games, or you don't want to manually redo your hotkeys, you have to copy or move those files over yourself.

A worked example: carrying your hotkeys across

Say you changed your afterburner key bind away from the default (TAB) and you want that setting in the new setup. The approach shown in the community is:

1. Go to Documents\My Games\Freelancer.
2. Copy UserKeyMap.ini.
3. Paste it into Documents\My Games\FreelancerHDE, replacing the existing file.

Input: your existing key map file. Action: copy and replace. Expected result: your custom binds carry over instead of being reset to defaults.

What mods can go wrong beyond saves

Save-file incompatibility is the headline issue, but it is not the only one. In a reverse-engineering thread about crash offsets, a contributor describes a specific failure mode: if an "overloaded" character instead loads the client onto a base, the immediate crash does not occur — but all items, equipped or in cargo, fail to show up (fixed mounted ones appear to be an exception). The client has not successfully loaded that character.

The practical lesson is that a modded client can fail in ways that look like missing content rather than an obvious error. If your ship or inventory looks empty after loading a character, that is a client-side loading failure, not necessarily a save you deleted.

Choosing your starting point

Pick based on what you actually want:

• Just want to play the original — install Vanilla and leave the save folder alone. Don't mix in modded saves.
• Want to try a mod — check first whether it redirects saves to its own folder. If it does, you can keep Vanilla and the mod side by side. If it doesn't, back up or move Documents\My Games\Freelancer before you start.
• Want to build or fix things — head to Programming & Tools and the reverse-engineering threads. This is developer-facing work, not a casual install.
• Stuck and need help — register on The Starport and post in the relevant area. Note that the site places you in read-only mode if JavaScript is disabled or unsupported, so enable JavaScript (or allow it past NoScript) before you try to post.

One caveat worth stating plainly: The Starport's own pages don't list pricing or account requirements, so nothing here should be read as "free" or "no login needed" — check the site directly for how registration works.