The game failed to load as the save file is corrupted. If this issue persists, please file a bug report.
Mafi.Serialization.CorruptedSaveException: Failed to finalize deserialization of 'FishFarm #304' (type 'FishFarm')
parent object '--' (type '--')
Previous deserialized in this finalize call: 'Mafi.Core.Vehicles.Trucks.Truck.ToString() threw NullReferenceException' (type 'Truck')
Last deserialized across all finalize calls: 'Mafi.Core.Vehicles.Trucks.Truck.ToString() threw NullReferenceException' (type 'Truck')
Last read object types: [AutoBufferLogisticsHelper, IProductBuffer[], ProductBuffer] ---> Mafi.Serialization.CorruptedSaveException: New deserialized type was expected to have ID 1317 but value 5422 was read.
at Mafi.Serialization.BlobReader.ReadType (System.Boolean allowNulls) [0x00084]
at Mafi.Serialization.DynamicDispatchClassSerializer`1[T].<.ctor>b__11_1 (Mafi.Serialization.BlobReader reader) [0x00000]
at Mafi.Serialization.BlobReader.ReadGenericAs[T] () [0x00032]
at LivestockAndAgricultureMOD.Buildings.FishFarm.FishFarm.DeserializeData (Mafi.Serialization.BlobReader reader) [0x000be]
at LivestockAndAgricultureMOD.Buildings.FishFarm.FishFarm+<>c.<.cctor>b__100_1 (System.Object entity, Mafi.Serialization.BlobReader reader) [0x00000]
at Mafi.Serialization.BlobReader+<FinalizeLoadingTimeSliced>d__37.MoveNext () [0x00054]
--- End of inner exception stack trace ---
at Mafi.Serialization.BlobReader+<FinalizeLoadingTimeSliced>d__37.MoveNext () [0x00202]
at Mafi.Core.SaveGame.GameLoader+<FinishGameLoadAndDisposeTimeSliced>d__12.MoveNext () [0x004ef]
at Mafi.Core.Game.GameBuilder+<BuildLoadedGameTimeSliced>d__1.MoveNext () [0x005a4]
at Mafi.Unity.GamePlayScene+<loadGame>d__28.MoveNext () [0x002ca]
at Mafi.Unity.GamePlayScene+<Initialize>d__25.MoveNext () [0x000ad]
at Mafi.Unity.Main+<unloadAndStartNewScene>d__112.MoveNext () [0x0013b]
at Mafi.Unity.Main.stepSceneInitialization () [0x000fd]
Game version: 0.8.5
Loaded mods: ..... (Animal husbandry and agricultural expansion 4.0.2), .....
Failed mods: none

hello

That's right, the corrupted file prevented me from entering the game. I had to revert to the previous version, which also doesn't work properly; the fish aren't visible on the dock.

关于4.0-4.02版本存在的问题.
根据社区网友反馈,检查出4.0版本存在BUG,重新读取存档后无法正确显示码头的鱼等信息,这个问题在于存档序列化的处理参数配置错误,属于bug,已经被4.0.1和4.02修复.
但是,问题在于原本的老存档,已经使用4.0的写入方式对存档写入了不存储指令,造成即使你加载新版本依然无法解决问题,甚至会引起存档损毁.
原因在于,这个升级是不兼容的,因为对存档序列进行了修改,任何对存档序列修改方案,都会引起不兼容性.因此会损伤存档

对于你的存档,本人表示遗憾,你可以在v4.0老版本模式下继续你的老存档到终结,而新开游戏时再根本最新版本即可.
或者使用新版本开启新的存档进行游戏.
另外,使用新的mod,建议使用沙盘进行测试,观察日志反馈.
非常感谢,提供完整的日志报错使得我精确定位这个问题.因为技术缘故,存档序列化已经写入无法再次变更,当然也是有方案可以解决,但是将会引起更多连锁反应,所以决定更新版本到5.0,做了兼容处理和全新的存档序列化,但4.0产生的序列化问题只存在这个版本.
Issues Existing in Versions 4.0–4.02
Based on feedback from community users, a bug has been identified in Version 4.0. After reloading save files, information such as fish at docks fails to display correctly. This bug stems from misconfigured processing parameters for save serialization and has been fixed in Versions 4.0.1 and 4.02.

However, legacy save files originally created under Version 4.0 have been written with non-storage instructions via the 4.0 writing mechanism. As a result, loading newer versions cannot resolve this issue and may even lead to save file corruption.

The root cause is that this update is incompatible due to modifications made to the save serialization sequence. Any alterations to the save serialization sequence will trigger compatibility issues and consequently damage save files.

I apologize for the trouble with your save files. You may continue playing with your legacy saves all the way through the game’s ending using the old v4.0 build, then switch to the latest version when starting a new playthrough.
Alternatively, you can start a brand-new save file using the latest version to play.

Additionally, it is recommended that you test new mods in a sandbox environment and monitor log outputs for feedback.

Thank you very much for providing complete error logs, which allowed me to pinpoint this issue accurately. For technical reasons, once save serialization data is written, it cannot be modified retroactively. While workarounds do exist to address this problem, they would trigger a cascade of additional side effects. Therefore, we have decided to release Version 5.0, which includes compatibility adjustments and a brand-new save serialization system. The serialization defects originating from Version 4.0 are exclusive to this release only.