# FreeSO reimplements The Sims Online as a Monogame engine > FreeSO is a C# Monogame re-implementation of The Sims Online that now serves as a technology base other servers build on, and it needs the original game files to run at all. Its most interesting parts for engineers are the SimAntics VM, the 3D mode reconstructed from sprite buffers, and the Volcanic live object editor. **riperiperi/FreeSO** — Re-implementation of The Sims Online. - Repository: https://github.com/riperiperi/FreeSO - Website: http://freeso.org - Stars: 988 · Forks: 155 - Language: C# - License: MPL-2.0 - Published: 2026-10-20 · Updated: 2026-10-20 · Language: en - Canonical page: https://hysenlabs.com/projects/riperiperi-freeso ## FreeSO is a base layer, not a running game service The scope of this project changed and the documentation is candid about it. FreeSO began as a full reimplementation of The Sims Online built on Monogame, and while it aims to be faithful to the original game it also carries quality of life changes such as hardware rendering, custom dynamic lighting, hi-res output and houses with more than two floors. What it is now is different, and this matters for anyone evaluating it. There used to be an official FreeSO server, but the project now exists as a technology base for other The Sims Online servers to build upon. The project site blog is the place to look for further information, and the README points out that a client built specifically for exploring the original FreeSO server alone or with friends will live in a different repository. So the artefact to judge is the engine and the tooling, not a service you can sign up for. The engine is described as shipping no copyrighted assets of its own, and it depends on the original game files for objects, avatars and UI in order to function. Those files are available for download from EA servers. This also means the contribution model is unusual. The README asks for testing new features in the latest releases, filing bugs, joining forum discussion, and points new contributors at issues tagged help wanted. There is a wiki with Getting Started, Project Structure and Coding Standards pages, a translation forum, a Discord server and an Azure Pipelines file at the repository root. ## The SimAntics VM and content system carry both game file sets The architectural fact that makes FreeSO more than a skin is that the content system, the HIT VM and the SimAntics VM all live in this repository and support both The Sims Online and The Sims 1 game files. The consequence is stated directly: The Sims 1 will still run in a limited sense under the Sims Online UI frontend inside FreeSO. The HIT VM and SimAntics VM are the simulation core, and the content system sits above them, resolving objects and assets from whichever game file set is loaded. The repository layout supports that reading. It separates the client into `TSOClient/`, keeps an `FSOInstaller/` for obtaining the required files, and carries a `Charvatia/` directory that is named after a distinct content area rather than the Sims Online object set. There is also an `Other/` directory and a `Documentation/` folder, alongside the pipeline definition in `azure-pipelines.yml`. The Sims 1 work continues in a separate project, Simitone, which is described as largely incomplete but of interest in itself. The division of labour is that FreeSO carries the shared engine and the Sims Online frontend, while Simitone ties the neighbourhood and game systems together with a suitable UI frontend to restore full Sims 1 gameplay. Both point at the same base. ## 3D mode rebuilds meshes from sprite z-buffers at runtime The most unusual feature is the 3D mode. Instead of shipping 3D models, FreeSO reconstructs them at runtime from the z-buffers included with the object sprites. It also generates 3D geometry for walls and floors at runtime, and switches to an alternate camera with different controls when the mode is turned on. That approach is worth understanding on its own terms. A sprite set that carries depth information already describes a 3D shape, so recovering geometry from it means the object art does not have to be remodelled. The cost is that the reconstruction happens every time, and the quality of the result is bounded by what the original sprite buffers contain. The mode is enabled with a launch parameter: ```sh -3d ``` The README refers readers to the blog post at freeso.org/the-impossible/ for more information. Since the reconstruction and the alternate camera are runtime behaviour of the engine, this is also a feature to test on the specific content you care about rather than assume from the description. ## Volcanic edits objects while the SimAntics VM is running Volcanic is an extension of FreeSO that lets users view, modify and save game objects alongside a live instance of the SimAntics VM. The description lists a wide array of resource editors for objects, with the script editor as the most prominent, and says it allows easy creation of new objects and debugging of existing ones. The live part is what distinguishes it. Editing a resource while the simulation is running, rather than editing a file and restarting, changes the loop for anyone developing content: you can watch the effect of a change in the running world instead of rebuilding between attempts. Volcanic also functions when the FreeSO engine has loaded The Sims 1 objects and other resources, which follows from the shared content and VM layers described earlier. Two practical notes apply. Volcanic is described as an extension of FreeSO rather than a standalone program, so it sits in the same build. And it is a development and debugging tool, which means it is aimed at people making content, not at players. Combined with the 3D mode, this is the part of the project that has the most value for an engineer reading the source: a virtual machine you can inspect and edit while it executes. ## Building from source needs Visual Studio 2019 and the original files The prerequisites section is short and points at a Windows toolchain. It lists Visual Studio 2019 and MonoGame, with the note that MonoGame 3.5 is needed for the iOS and Android VS2015 project types, marked as optional. The `FSOInstaller/` directory at the repository root is the visible counterpart to that. Since the engine depends on the original game files for objects, avatars and UI, and those files come from EA servers, the installer component is where the acquisition step lives. The `.gitmodules` file in the root indicates that the build pulls in submodules as well. Releases are named in a way that signals the current phase. The three most recent tags are v0.8.5-beta, v0.8.4-beta and v0.8.3-beta, and each carries the suffix FreeSO Archive Beta. All three landed in September 2026. The word Archive in the tag name, combined with the README's statement that the official server no longer runs, suggests the tagged builds target the historical server rather than a current one. For a developer building locally, the practical sequence is to have Visual Studio 2019 and MonoGame available, obtain the original game files through the installer, then compile the client and the tooling. ## The Simitone split shows what a shared VM buys you Simitone is the clearest available comparison for what FreeSO's architecture enables, because it is built on the same base and does something different with it. The Sims 1 engine reimplementation lives in its own repository, and the README is candid that it is largely incomplete. The reason is structural rather than incidental. The content system, the HIT VM and the SimAntics VM are all in the FreeSO repository, and they accept both game file sets. The Sims 1 therefore already runs in a limited form under the Sims Online frontend. What Simitone adds is a frontend that ties the neighbourhood and the game systems together properly, so the game works as a Sims 1 experience rather than as a shell running Sims 1 assets. That is the difference in approach worth taking from the pair. FreeSO provides the engine, the content resolution and the two virtual machines. Simitone provides the game-level systems and the interface for a different product built on them. One repository hosts shared machinery, the other hosts a specific game built on that machinery, and the Sims Online frontend is one such consumer of it. It also explains why other servers are described as building on FreeSO. A server author needs the simulation layer and the content system, and needs freedom over the frontend and the server protocol, which is precisely the split the project has made. ## Maintenance state and what MPL-2.0 covers The repository is not archived, and the last push was on 2026-10-19, with the beta tags following in September 2026. The licence is MPL-2.0, and the README reproduces the standard Mozilla Public License notice pointing at the MPL 2.0 text. The licence file sits at the repository root as `LICENSE.md`. MPL-2.0 is a file-level copyleft licence, and for the question a server developer is likely to be asking, the practical answer is that modifications to MPL-covered files carry an obligation to publish those changes while other files remain under their own terms. This is a description of the licence shape, not legal advice, and anyone building on the project should read the licence text itself. The obvious point of contact for a server developer is that the README describes FreeSO as the base for other servers to build upon, and the contribution routes are the forum, the blog, the Discord, the wiki pages on project structure and coding standards, and the pull request area with open and closed lists linked. The help wanted label is where a new contributor is directed. The one thing the documentation does not spell out is a roadmap. With the official server gone and the releases named as archive betas, the direction of the engine work is something a reader has to infer from the blog rather than from a document in the repository. ## Conclusion FreeSO suits a developer who wants to study or extend a SimAntics virtual machine, build a private server on top of its content and VM layers, or debug game objects live in Volcanic, and it suits a player who still has the original game files and wants a modernised build with hardware rendering and hi-res output. It is the wrong choice for anyone without those files, since the engine ships no assets of its own, and the wrong choice for someone expecting a finished standalone game rather than a foundation. Verify three things first: that you can obtain the original game files from EA servers, that the build works with the Visual Studio 2019 and Monogame prerequisites listed in the README, and that the client build you pick matches the server you intend to connect to, because the project's own role has shifted from running an official server to providing the base other servers build on. ## FAQ ### Do I need the original The Sims Online game files to run FreeSO? Yes. The README states that FreeSO depends on the original game files for objects, avatars and UI, and that these are available for download from EA servers. The engine itself is described as containing no copyrighted assets of its own. ### What is Volcanic in FreeSO? Volcanic is an extension of FreeSO for viewing, modifying and saving game objects alongside a live instance of the SimAntics VM. It provides resource editors for objects, most prominently a script editor, and also works when the engine has loaded The Sims 1 objects and resources. ### How do I enable 3D mode in FreeSO? The 3D mode is enabled with the `-3d` launch parameter. Meshes are reconstructed at runtime from the z-buffers included with the object sprites, and the engine also generates wall and floor geometry at runtime before switching to an alternate camera. ### What do I need to build FreeSO from source? The README lists Visual Studio 2019 and MonoGame as the prerequisites, with MonoGame 3.5 required for the iOS and Android VS2015 project types, marked optional. The `FSOInstaller/` directory in the repository handles obtaining the original game files. ### Is there still an official FreeSO server? No. The README states that there used to be an official FreeSO server, and that FreeSO is now a technology base for other The Sims Online servers to build upon. A client meant for exploring the original FreeSO server is planned for a different repository. ## Sources - [License: MPL-2.0](https://github.com/riperiperi/FreeSO/blob/master/LICENSE) - [Project website](http://freeso.org) - [README](https://github.com/riperiperi/FreeSO/blob/master/README.md) - [Releases](https://github.com/riperiperi/FreeSO/releases) - [riperiperi/FreeSO on GitHub](https://github.com/riperiperi/FreeSO) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/riperiperi-freeso