failed to find type in planetbase assembly-csharp.dll, planetbase framework.dll or mscorlib v4.0.0.0 is what i get when trying to patch it, it's in admin mode, i have the files selected and i updated the framework first then i get this when i hit patch what do i do?
Failed to resolve assembly: "UnityEngine.CoreModule. Version=0.0.0.0. Culture=neutral, PublicKeyToken=null'.
Details:
See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text ************** Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly: 'UnityEngine.CoreModule, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' at Mono.Cecil.BaseAssemblyResolver.Resolve(AssemblyNameReference name, ReaderParameters parameters) at Mono.Cecil.DefaultAssemblyResolver.Resolve(AssemblyNameReference name) at Patcher.PlanetbaseResolver.Resolve(AssemblyNameReference name) at Mono.Cecil.MetadataResolver.Resolve(TypeReference type) at Mono.Cecil.TypeReference.Resolve() at Mono.Cecil.Mixin.CheckedResolve(TypeReference self) at Mono.Cecil.MetadataBuilder.GetConstantType(TypeReference constant_type, Object constant) at Mono.Cecil.MetadataBuilder.AddConstant(IConstantProvider owner, TypeReference type) at Mono.Cecil.MetadataBuilder.AddField(FieldDefinition field) at Mono.Cecil.MetadataBuilder.AddFields(TypeDefinition type) at Mono.Cecil.MetadataBuilder.AddType(TypeDefinition type) at Mono.Cecil.MetadataBuilder.AddTypes() at Mono.Cecil.MetadataBuilder.BuildTypes() at Mono.Cecil.MetadataBuilder.BuildModule() at Mono.Cecil.MetadataBuilder.BuildMetadata() at Mono.Cecil.ModuleWriter.<>c.<BuildMetadata>b__2_0(MetadataBuilder builder, MetadataReader _) at Mono.Cecil.ModuleDefinition.Read[TItem,TRet](TItem item, Func`3 read) at Mono.Cecil.ModuleWriter.BuildMetadata(ModuleDefinition module, MetadataBuilder metadata) at Mono.Cecil.ModuleWriter.Write(ModuleDefinition module, Disposable`1 stream, WriterParameters parameters) at Mono.Cecil.ModuleWriter.WriteModule(ModuleDefinition module, Disposable`1 stream, WriterParameters parameters) at Mono.Cecil.ModuleDefinition.Write(String fileName, WriterParameters parameters) at Patcher.PatchBuilder.Patch(String assemblyPath, String assemblyFirstPassPath, String unityEnginePath, String unityEngineUiPath, String frameworkPath, String patchedAssemblyPath) at Patcher.PatcherWindow.PatchButton_Click(Object sender, EventArgs e) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled.
When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.
Already tried The Windows Framework thing... did absolutely nothing. This is why you don't upload mods you didn't create yourself. Need the original author in here to fix this.
In the meantime Steam allows reverting the game to version 1.3.8 via right clock Planetbase, left click Properties, left click Betas tab, left click the dropdown menu that reads "None", left click the old version. Close the properties window, and allow Steam to update to the old version. This is still compatible with the old patcher. Additionally make sure the default setting to the installation folder of Read-Only is removed.
There are no viruses in this Patcher2 (Framework2). Some antiviruses like to swear at regular programs and especially often at mods. In this case, this Patcher2 has an open source code and you can look at it yourself and understand everything that this Framework2 does.
The author of Patcher2 (solidDoWant) himself answered this as follows:
There are a few AVs on VirusTotal that flag this as a virus. These are false positives?. If you take a look at the AVs that are flagging the file, you'll notice that they are all fairly small, no-name companies that (as you can see via a quick Google search) tend to report a lot of files as viruses when they are not. I've emailed a few of them to get it reviewed/whitelisted, but some respond, some don't. If you're still not convinced, you can review the source code on GitHub? yourself, compile the project, and scan the build with VirusTotal. You'll get the exact same results.
This mod also contain a virus (https://www.virustotal.com/gui/file/4c4537e18055c68fc2a01fa505d6ecfa2ad913712c911aeb6ce532c16a7ed96b/detection) He is not safe to use.
There are no viruses in this Patcher2 (Framework2). Some antiviruses like to swear at regular programs and especially often at mods. In this case, this Patcher2 has an open source code and you can look at it yourself and understand everything that this Framework2 does.
The author of Patcher2 (solidDoWant) himself answered this as follows:
There are a few AVs on VirusTotal that flag this as a virus. These are false positives?. If you take a look at the AVs that are flagging the file, you'll notice that they are all fairly small, no-name companies that (as you can see via a quick Google search) tend to report a lot of files as viruses when they are not. I've emailed a few of them to get it reviewed/whitelisted, but some respond, some don't. If you're still not convinced, you can review the source code on GitHub? yourself, compile the project, and scan the build with VirusTotal. You'll get the exact same results.
The information and advice in this comment is long out of date (2021). Since then, the author of this Patcher2 (Framework2) has posted a major update of his work. Now this Framework2 works and is currently the most powerful Framework for Planetbase mods. Only solidDoWant's Framework2 allows players and modders to work with mods that change textures, buildings, items, ships, technology and much more.
I have version 1.4.0 and the program shows an error when trying to patch.
Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly: 'UnityEngine.CoreModule, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' in Mono.Cecil.BaseAssemblyResolver.Resolve(AssemblyNameReference name, ReaderParameters parameters) in Mono.Cecil.DefaultAssemblyResolver.Resolve(AssemblyNameReference name) in Patcher.PlanetbaseResolver.Resolve(AssemblyNameReference name) in Mono.Cecil.MetadataResolver.Resolve(TypeReference type) in Mono.Cecil.TypeReference.Resolve()
Please make sure that you are using .Net Framework 3.5+ and the latest version of Framework2 downloaded from GitHub. Also, check out the list of common problems when working with Planetbase mods. If suddenly this did not help, then try to roll back the game version to the previous one. (In Steam, there is an option to choose to install the game version). If the problem persists, report it to solidDoWant, the author of Framework2 (Planetbase Mod Patcher 2). He is rarely on the NexusMods website, so it will be more effective to contact him on Discord and describe your Issue on GitHub. After all these above actions, it would be great if you tell us what you eventually managed to do and what solidDoWant, the author of Framework2, answered you.
What you may need for the mods and patcher2 to work:
.Net Framework 3.5+. Don't forget to enable Windows .Net Framework 3.5+ features for the patch (Framework2 = Planetbase Mod Patcher 2) to work. Make sure that "Windows .Net Framework 3.5+" is installed on your computer or its functions are activated.
Download and install the latest version of Framework2 (Planetbase Mod Patcher 2). Look where the more recent version is [GitHub (2.3.2 Release = Feb 21, 2022) or NexusMods (2.2 Release = 20 Jan 2020)] and download the file from there. At the moment, the more recent version of Framework2 (2.3.2 Release = Feb 21, 2022) is on the GitHub website. Now it is better to download the file from GitHub.
4.2) it is always possible to communicate with the author of the Framework2: (solidDoWant): Discord, Issue, Steam. Considering that solidDoWant very rarely visits the NexusMods website, it will be much more effective if you contact him via Discord and also write your description of the problem in the Issues on GitHub. This way you will get an answer to your question much faster.
Use a more stable version of the game. Some old mods work better on older versions of the game. (Especially Framework1 and JPFarias-style mods from 2016). On Steam, you can officially select version 1.3.8 of the game for installation in the "oldversion" installation section. It is quite difficult for players to notice the differences between the latest version of the game and versions 1.3.0-1.3.8.
In recent years, game updates 1.3.0+ have been quite formal and were made by the game's authors, mainly just to remind about the game and tell about other games of this company. There is an opinion that some game updates did not bring anything new to the game, except for the deliberate deterioration of the work of patchers and mods. The game's authors "Madruga Works" are against mods and ban mod creators on the forum.
It is unlikely that you will noticeably lose something in the gaming experience if you start playing on a slightly earlier version (1.3.0-1.3.8) of the game. At the same time, many old mods and patchers (frameworks) work much better and more stably on earlier versions (1.3.0-1.3.8) of the game.
Types and history of frameworks for mods. The history of the game and the creation of mods for it has been around for about 10 years. During this time, fans of the game have created several different patchers (frameworks) and types of mods for them for the game. If you have been following the Planetbase game for a while, then you may find it interesting and useful to read this article.
From this article you can learn, for example, about:
Hello, is it normal that updating the framework takes time? I can't patch without updating. Should I also install the old Mod Patcher ? in addition to the new ?
You do not need to install other mod patchers. These are different methods of working with mods that are not related to each other.
What you may need for the mods and patcher to work:
.Net Framework 3.5+. Don't forget to enable Windows .Net Framework 3.5+ features for the patch (Framework2 = Planetbase Mod Patcher 2) to work. Make sure that "Windows .Net Framework 3.5+" is installed on your computer or its functions are activated.
Download and install the latest version of Framework2 (Planetbase Mod Patcher 2). Look where the more recent version is [GitHub (2.3.2 Release = Feb 21, 2022) or NexusMods (2.2 Release = 20 Jan 2020)] and download the file from there. At the moment, the more recent version of Framework2 (2.3.2 Release = Feb 21, 2022) is on the GitHub website. Now it is better to download the file from GitHub.
4.2) it is always possible to communicate with the author of the Framework2: (solidDoWant): Discord, Issue, Steam. Considering that solidDoWant very rarely visits the NexusMods website, it will be much more effective if you contact him via Discord and also write your description of the problem in the Issues on GitHub. This way you will get an answer to your question much faster.
Use a more stable version of the game. Some old mods work better on older versions of the game. (Especially Framework1 and JPFarias-style mods from 2016). On Steam, you can officially select version 1.3.8 of the game for installation in the "oldversion" installation section. It is quite difficult for players to notice the differences between the latest version of the game and versions 1.3.0-1.3.8.
In recent years, game updates 1.3.0+ have been quite formal and were made by the game's authors, mainly just to remind about the game and tell about other games of this company. There is an opinion that some game updates did not bring anything new to the game, except for the deliberate deterioration of the work of patchers and mods. The game's authors "Madruga Works" are against mods and ban mod creators on the forum.
It is unlikely that you will noticeably lose something in the gaming experience if you start playing on a slightly earlier version (1.3.0-1.3.8) of the game. At the same time, many old mods and patchers (frameworks) work much better and more stably on earlier versions (1.3.0-1.3.8) of the game.
Types and history of frameworks for mods. The history of the game and the creation of mods for it has been around for about 10 years. During this time, fans of the game have created several different patchers (frameworks) and types of mods for them for the game. If you have been following the Planetbase game for a while, then you may find it interesting and useful to read this article.
From this article you can learn, for example, about:
I'm back from a fairly long modding hiatus and I'd like to address the comments below:
Regarding all issues, I am most likely to see/respond to them if you post them on GitHub, message me on Steam, or join the Discord server I've setup. Links to all of these are available on the description page. I typically only check Nexus when I release a new version of one of my mods.
This modding system, by itself, is not compatible with JPFarias-style mods. However, I have just released a mod (https://www.nexusmods.com/planetbase/mods/57?) that allows for 100% full, feature-complete compatibility with these older mods and this new mod patcher and framework. Simply patch your game following the instructions on the description tab of this patcher, then download/extract/install the linked mod the same way as any other.
There are a few AVs on VirusTotal that flag this as a virus. These are false positives?. If you take a look at the AVs that are flagging the file, you'll notice that they are all fairly small, no-name companies that (as you can see via a quick Google search) tend to report a lot of files as viruses when they are not. I've emailed a few of them to get it reviewed/whitelisted, but some respond, some don't. If you're still not convinced, you can review the source code on GitHub? yourself, compile the project, and scan the build with VirusTotal. You'll get the exact same results.
Again, if you've got any questions, I'm available via the contact methods above. I'll check here occasionally but it may be months between posts.
29 comments
Cela ne fonctionne pas actuellement, idem pour le patch original.
Bonne journée
Failed to resolve assembly: "UnityEngine.CoreModule. Version=0.0.0.0. Culture=neutral, PublicKeyToken=null'.
Details:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly: 'UnityEngine.CoreModule, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null'
at Mono.Cecil.BaseAssemblyResolver.Resolve(AssemblyNameReference name, ReaderParameters parameters)
at Mono.Cecil.DefaultAssemblyResolver.Resolve(AssemblyNameReference name)
at Patcher.PlanetbaseResolver.Resolve(AssemblyNameReference name)
at Mono.Cecil.MetadataResolver.Resolve(TypeReference type)
at Mono.Cecil.TypeReference.Resolve()
at Mono.Cecil.Mixin.CheckedResolve(TypeReference self)
at Mono.Cecil.MetadataBuilder.GetConstantType(TypeReference constant_type, Object constant)
at Mono.Cecil.MetadataBuilder.AddConstant(IConstantProvider owner, TypeReference type)
at Mono.Cecil.MetadataBuilder.AddField(FieldDefinition field)
at Mono.Cecil.MetadataBuilder.AddFields(TypeDefinition type)
at Mono.Cecil.MetadataBuilder.AddType(TypeDefinition type)
at Mono.Cecil.MetadataBuilder.AddTypes()
at Mono.Cecil.MetadataBuilder.BuildTypes()
at Mono.Cecil.MetadataBuilder.BuildModule()
at Mono.Cecil.MetadataBuilder.BuildMetadata()
at Mono.Cecil.ModuleWriter.<>c.<BuildMetadata>b__2_0(MetadataBuilder builder, MetadataReader _)
at Mono.Cecil.ModuleDefinition.Read[TItem,TRet](TItem item, Func`3 read)
at Mono.Cecil.ModuleWriter.BuildMetadata(ModuleDefinition module, MetadataBuilder metadata)
at Mono.Cecil.ModuleWriter.Write(ModuleDefinition module, Disposable`1 stream, WriterParameters parameters)
at Mono.Cecil.ModuleWriter.WriteModule(ModuleDefinition module, Disposable`1 stream, WriterParameters parameters)
at Mono.Cecil.ModuleDefinition.Write(String fileName, WriterParameters parameters)
at Patcher.PatchBuilder.Patch(String assemblyPath, String assemblyFirstPassPath, String unityEnginePath, String unityEngineUiPath, String frameworkPath, String patchedAssemblyPath)
at Patcher.PatcherWindow.PatchButton_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9290.0 built by: NET481REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
Patcher
Assembly Version: 2.2.0.0
Win32 Version: 2.2.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/Steam/steamapps/common/Planetbase/Patcher.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9251.0 built by: NET481REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9282.0 built by: NET481REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9037.0 built by: NET481REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9037.0 built by: NET481REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9277.0 built by: NET481REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9037.0 built by: NET481REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9037.0 built by: NET481REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
System.Web.Extensions
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9282.0
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Web.Extensions/v4.0_4.0.0.0__31bf3856ad364e35/System.Web.Extensions.dll
----------------------------------------
Microsoft.CSharp
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9037.0
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.CSharp/v4.0_4.0.0.0__b03f5f7f11d50a3a/Microsoft.CSharp.dll
----------------------------------------
System.Web
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9282.0 built by: NET481REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Web/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.dll
----------------------------------------
System.Dynamic
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9037.0
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Dynamic/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Dynamic.dll
----------------------------------------
Anonymously Hosted DynamicMethods Assembly
Assembly Version: 0.0.0.0
Win32 Version: 4.8.9290.0 built by: NET481REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/mscorlib/v4.0_4.0.0.0__b77a5c561934e089/mscorlib.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
In the meantime Steam allows reverting the game to version 1.3.8 via right clock Planetbase, left click Properties, left click Betas tab, left click the dropdown menu that reads "None", left click the old version. Close the properties window, and allow Steam to update to the old version. This is still compatible with the old patcher. Additionally make sure the default setting to the installation folder of Read-Only is removed.
Some antiviruses like to swear at regular programs and especially often at mods.
In this case, this Patcher2 has an open source code and you can look at it yourself and understand everything that this Framework2 does.
The author of Patcher2 (solidDoWant) himself answered this as follows:
This mod also contain a virus (https://www.virustotal.com/gui/file/4c4537e18055c68fc2a01fa505d6ecfa2ad913712c911aeb6ce532c16a7ed96b/detection)
He is not safe to use.
Some antiviruses like to swear at regular programs and especially often at mods.
In this case, this Patcher2 has an open source code and you can look at it yourself and understand everything that this Framework2 does.
The author of Patcher2 (solidDoWant) himself answered this as follows:
Since then, the author of this Patcher2 (Framework2) has posted a major update of his work.
Now this Framework2 works and is currently the most powerful Framework for Planetbase mods.
Only solidDoWant's Framework2 allows players and modders to work with mods that change textures, buildings, items, ships, technology and much more.
Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly: 'UnityEngine.CoreModule, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' in Mono.Cecil.BaseAssemblyResolver.Resolve(AssemblyNameReference name, ReaderParameters parameters) in Mono.Cecil.DefaultAssemblyResolver.Resolve(AssemblyNameReference name) in Patcher.PlanetbaseResolver.Resolve(AssemblyNameReference name) in Mono.Cecil.MetadataResolver.Resolve(TypeReference type) in Mono.Cecil.TypeReference.Resolve()
Also, check out the list of common problems when working with Planetbase mods.
If suddenly this did not help, then try to roll back the game version to the previous one. (In Steam, there is an option to choose to install the game version).
If the problem persists, report it to solidDoWant, the author of Framework2 (Planetbase Mod Patcher 2). He is rarely on the NexusMods website, so it will be more effective to contact him on Discord and describe your Issue on GitHub.
After all these above actions, it would be great if you tell us what you eventually managed to do and what solidDoWant, the author of Framework2, answered you.
What you may need for the mods and patcher2 to work:
Don't forget to enable Windows .Net Framework 3.5+ features for the patch (Framework2 = Planetbase Mod Patcher 2) to work.
Make sure that "Windows .Net Framework 3.5+" is installed on your computer or its functions are activated.
Look where the more recent version is [GitHub (2.3.2 Release = Feb 21, 2022) or NexusMods (2.2 Release = 20 Jan 2020)] and download the file from there.
At the moment, the more recent version of Framework2 (2.3.2 Release = Feb 21, 2022) is on the GitHub website.
Now it is better to download the file from GitHub.
Adds compatibility to the Planetbase Framework2 allowing it to load older, JPFarias-style mods (Framework1, 2016).
4.1) See the LIST of the main and most common PROBLEMS when working with the patch and mods.
Make sure that your problem is not on this list and that you are doing everything correctly and according to the instructions.
4.2) it is always possible to communicate with the author of the Framework2: (solidDoWant): Discord, Issue, Steam.
Considering that solidDoWant very rarely visits the NexusMods website, it will be much more effective if you contact him via Discord and also write your description of the problem in the Issues on GitHub. This way you will get an answer to your question much faster.
Some old mods work better on older versions of the game. (Especially Framework1 and JPFarias-style mods from 2016).
On Steam, you can officially select version 1.3.8 of the game for installation in the "oldversion" installation section.
It is quite difficult for players to notice the differences between the latest version of the game and versions 1.3.0-1.3.8.
In recent years, game updates 1.3.0+ have been quite formal and were made by the game's authors, mainly just to remind about the game and tell about other games of this company.
There is an opinion that some game updates did not bring anything new to the game, except for the deliberate deterioration of the work of patchers and mods.
The game's authors "Madruga Works" are against mods and ban mod creators on the forum.
It is unlikely that you will noticeably lose something in the gaming experience if you start playing on a slightly earlier version (1.3.0-1.3.8) of the game.
At the same time, many old mods and patchers (frameworks) work much better and more stably on earlier versions (1.3.0-1.3.8) of the game.
The history of the game and the creation of mods for it has been around for about 10 years.
During this time, fans of the game have created several different patchers (frameworks) and types of mods for them for the game.
If you have been following the Planetbase game for a while, then you may find it interesting and useful to read this article.
From this article you can learn, for example, about:
6.1) Types and history of Planetbase mod frameworks. Their differences, pros and cons.
6.2) Which framework is the most powerful and functional?
Only solidDoWant's Framework2 allows players and modders to work with mods that change textures, buildings, items, ships, technology and much more.
6.3) Why are there so many frameworks and so little information on the game's official resources?
6.4) The attitude of the authors of the game 'Madruga Works' to modders and mods.
Ignoring player requests, opposing the creation of mods and banning mod creators.
6.5) Options for further development of frameworks, mods and the entire Planetbase game.
6.6) A list of useful information about the game.
Have a good game and a cool gaming experience with mods!
Should I also install the old Mod Patcher ? in addition to the new ?
All the necessary information about the installation and work of this framework is written in the description and on the GitHub website in the wiki section.
You do not need to install other mod patchers. These are different methods of working with mods that are not related to each other.
What you may need for the mods and patcher to work:
Don't forget to enable Windows .Net Framework 3.5+ features for the patch (Framework2 = Planetbase Mod Patcher 2) to work.
Make sure that "Windows .Net Framework 3.5+" is installed on your computer or its functions are activated.
Look where the more recent version is [GitHub (2.3.2 Release = Feb 21, 2022) or NexusMods (2.2 Release = 20 Jan 2020)] and download the file from there.
At the moment, the more recent version of Framework2 (2.3.2 Release = Feb 21, 2022) is on the GitHub website.
Now it is better to download the file from GitHub.
Adds compatibility to the Planetbase Framework2 allowing it to load older, JPFarias-style mods (Framework1, 2016).
4.1) See the LIST of the main and most common PROBLEMS when working with the patch and mods.
Make sure that your problem is not on this list and that you are doing everything correctly and according to the instructions.
4.2) it is always possible to communicate with the author of the Framework2: (solidDoWant): Discord, Issue, Steam.
Considering that solidDoWant very rarely visits the NexusMods website, it will be much more effective if you contact him via Discord and also write your description of the problem in the Issues on GitHub. This way you will get an answer to your question much faster.
Some old mods work better on older versions of the game. (Especially Framework1 and JPFarias-style mods from 2016).
On Steam, you can officially select version 1.3.8 of the game for installation in the "oldversion" installation section.
It is quite difficult for players to notice the differences between the latest version of the game and versions 1.3.0-1.3.8.
In recent years, game updates 1.3.0+ have been quite formal and were made by the game's authors, mainly just to remind about the game and tell about other games of this company.
There is an opinion that some game updates did not bring anything new to the game, except for the deliberate deterioration of the work of patchers and mods.
The game's authors "Madruga Works" are against mods and ban mod creators on the forum.
It is unlikely that you will noticeably lose something in the gaming experience if you start playing on a slightly earlier version (1.3.0-1.3.8) of the game.
At the same time, many old mods and patchers (frameworks) work much better and more stably on earlier versions (1.3.0-1.3.8) of the game.
The history of the game and the creation of mods for it has been around for about 10 years.
During this time, fans of the game have created several different patchers (frameworks) and types of mods for them for the game.
If you have been following the Planetbase game for a while, then you may find it interesting and useful to read this article.
From this article you can learn, for example, about:
6.1) Types and history of Planetbase mod frameworks. Their differences, pros and cons.
6.2) Which framework is the most powerful and functional?
Only solidDoWant's Framework2 allows players and modders to work with mods that change textures, buildings, items, ships, technology and much more.
6.3) Why are there so many frameworks and so little information on the game's official resources?
6.4) The attitude of the authors of the game 'Madruga Works' to modders and mods.
Ignoring player requests, opposing the creation of mods and banning mod creators.
6.5) Options for further development of frameworks, mods and the entire Planetbase game.
6.6) A list of useful information about the game.
Have a good game and a cool gaming experience with mods!
I'm back from a fairly long modding hiatus and I'd like to address the comments below:
Again, if you've got any questions, I'm available via the contact methods above. I'll check here occasionally but it may be months between posts.
- solidDoWant