Hello, if you are reading this, its most likely due to CSL exploding in mid-load for no good reason. Updates usually break CSL when loading a map, but on the latest DLC, Snowfall, has created new and unexpected problems when starting CSL. This is due to apparently something that was changed in-game. With this in mind, we can expect something to go wrong.

To start off, you should recall what mods did you have installed at the last possible successful load. This is usually during post-DLC content has been installed. After you roughly remember them (or have an idea) separate mods using this basic idea:

• Mods
  
• Assets
  
• Assets with special qualities
  
• Flora
  
• Vehicles
  
• LUTs

Once you have an idea, start the next step.

--------------------------TL,DR Edition--------------------

Since I have gone with the trouble, I have discovered the issue with the lastest DLC, Snowfall.

• If you are looking for the quick and effective method to get rid of the issue, get rid of ALL flora/tree/tree props. Do this by unsubcribing, or manually getting rid of them.

I have discovered this by coincidence, but I understand why this happened. See, it would seem that Snowfall adds a new layer of textures or alters the tree behaviour, causing trees to have an entirely new file format. Due to this, CSL gets confused on load time and it suddenly explodes when it reaches a post-DLC tree. So for now, until trees are properly updated, the only suggestion is to leave them off the game.

Below is when this step doesn't iron out the issue.

--------------------------------------End TL,DR------------------------

So, trees were not the issue? No problem! This next step will be scary depending on how many mods you have installed. I have approximately 900 mods and assets installed, all from diffrent periods and qualities so browsing through the Steam workshop gets old, fast... So to solve the issue, you need to manually browse the mods. The exact place of this, however, is not obvious.

So, where is this file path? It's on steam, no joke.

C:\Program Files (x86)\Steam\steamapps\workshop\content\255710

This is where my mods from the workshop are "thrown". Your number folder may vary, so in order to find it, try to look for the folder with the largest number of folders or subscribe to a mod and find the latest folder on top. Please note that each number of the folders relates to a mod on the workshop. This is usually something like:

steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=######### (9 numbers)

Using this step, you can google the workshop page for the mod or use it to dig up information on the mod.

Should you have done the previous step, you will start debugging now. Start by dragging every single mod in the root workshop folder into a folder on the desktop for easy management.

The next steps would be fairly self-spoken. Basically start by dragging out a series of folder. For example, the folder management starts at 40###### and ends at 67#######. Start by shoveling out all the 40######## files first and then the next series and so on until the game runs successfully.



Do these steps:

1) As shown on the screenshot, you will PUSH files from the right to the left in accordance to folder number series (########).

2) Take note of the folders pushed out of the native folder.

3) Run CSL

If you do this for several series of folders, you should eventually reach the offending file. You will know when you have found the broken file when the game finally runs.





How to find the broken file amonst various series

This step involves many crashes, force closing CSL and general madness until you find the file. Take patience and allocate a time to do this (usually 1hr or so) because finding a broken file amongst thousands isn't easy.

Do these steps:

1) Look at your stored pushed files. (On screenshot 2, Hold window) Start pushing folders from series 20####### from your hold folder to the native folder. Once you move a series DO NOT MOVE ANYTHING ELSE. This will make windows forget the last folders you pushed and cause confusion.

2) Run CSL

3) Note what series does it crash, export it to a separate hold folder. I suggest finishing all the series that you have in your hold folder until your hold folder is empty.

Finding a broken file amongst a series.

This part is difficult and the one you will find that you need the most paticience. The steps are the same for the previous process, BUT you will find yourself swamped over 100+ files. I suggest divide and conquer.

Remember: Mods don't make CSL usually crash, assets do. Start finding the mods and then pushing them out to check if those run on the base game.

1) Push 50 or so mods from the held series folder to the native folder

2) Run CSL

3) Note what runs, what doesn't.

4) Push broken files back to a separate hold folder.

5) Repeat steps 1 - 4 until your series folder is emptied into the Native folder

6) Once you have found an offending file, do a steam workshop look up and report in the comments section of the file that it is broken. This will be a favor to everyone as it helps inform everyone of the broken file.

Hopefully this guide was useful to you, please spread around the word to understand how to debug mod problems. I have been in the bussiness since 2009 (SC4) so I have the experience to understand when something goes wrong. Comment below if you want a guide on debugging another game if you need such guide.

Comment and fav to help your fellow chirpies!