SnowRunner Integration Has Officially Started
SnowRunner development is underway, and the first exports already have terrain, textures, trees, and buildings. The difficult part now is learning everything the editor does not explain.
Hey everyone. As I mentioned earlier on Discord, I’ll be focusing on bringing SnowRunner to MapToPlay.
You may reasonably ask: why SnowRunner? The answer is pretty simple — I personally love this game. I’ve spent an unreasonable number of hours in it, and since MapToPlay is a solo project, I occasionally get to use the highly scientific planning method of “I want this.” I want to make a SnowRunner map for myself, so here we are.
The FS25 Pain Is Finally Paying Off
My first estimate was honestly scary. I was preparing myself for this integration to take months. But once I started digging, it turned out that all the pain and struggle with Farming Simulator 25 is finally paying me back.
The basic pipeline came together much faster than I expected. It already has terrain generation, textures, trees, and buildings. That does not mean SnowRunner support is almost finished — absolutely not — but it means the foundation works, which is a very good place to start.
A First Look
These are very early exports inside the SnowRunner Editor. They are rough, but seeing MapToPlay data turn into an actual SnowRunner map this quickly was a pretty good moment.
The Goal Is Much Bigger Than A Basic Export
As usual, my goal is much more ambitious than getting a basic map to open. I want to automate everything that can be meaningfully automated: water, mud, and whatever else I discover after another few days buried in the editor. I still need to understand what a genuinely complete SnowRunner map needs.
And, as usual, I am not here to replace modders. I want to automate the boring and repetitive parts so creators can spend their time on the decisions that actually make a map interesting. That also means I have no intention of generating missions or pretending creativity is just another export checkbox.
The Hard Part Is Not Really The Code
It is difficult to give a real estimate right now because I can hit a concrete wall at almost any step. At the moment I am drowning in guides, manuals, and the SnowRunner Editor, trying to understand how everything fits together. It brings back strong memories of the early Maps4FS days: “Okay, how do I place a tree through code? Fine, make a map before and after placing one tree, then compare the files. Great. Now how does the base game do it?” You know the routine.
The real struggle is rarely writing the code. It is understanding how the game stores things, connects them, and expects them to be packaged. I would honestly say that this consumes around 90% of the development time. That is not a joke.
MapToPlay already provides the rails. Terrain data, imagery, OpenStreetMap features, model placement, textures, and the rest of the shared workflow are already there. I do not need to build those systems again. I “just” need to learn how SnowRunner wants everything packed. It is not some impossible technical challenge; it is more like slow digital archaeology, with occasional trees.
So, stay tuned. There is a lot left to learn, but SnowRunner integration has officially started, and the first results are already real.
Thank you for your ongoing support. I will not pretend that this is just a polite closing line: you are the reason I keep pushing. Every message, test, shared screenshot, and encouraging word matters more than I can properly explain. On a solo project, that support is often the difference between “this is too much” and “all right, one more impossible thing.”
Stan, Developer of MapToPlay