Steam 社区 :: 指南 :: MCC Mod Versioning Fix

商店页面

Halo: The Master Chief Collection

全部讨论截图艺术作品实况直播视频创意工坊新闻指南评测

Halo: The Master Chief Collection > 指南 > Gard Hater 的指南

评价数不足

MCC Mod Versioning Fix

由 Gard Hater 制作

This is a guide to getting mods that have not been updated to work after MCC releases a new version.
You have to do this every time the campaign or map you're wanting to play does not appear as a selectable option.
No, I don't understand why MCC's versioning is the way it is, you'll have to take that up with the incompetents at Halo Studios.

奖励

创建者

Gard Hater
在线

类型: 创意工坊

发表于

9 月 22 日下午 7:19

117	不重复访客数
4	当前收藏人数

指南索引

总览

Step 1: Checking the current Game Version

Step 2: Finding the ID of the Mod You Need to Change

Step 3: Finding the Game's ID

Step 4: Finding your mod's Install Folder

Step 5: Editing your ModInfo.json

Conclusion

留言

Step 1: Checking the current Game Version

The Easiest Method

Navigate to your steam library.
Open the search bar.
Search for Halo MCC Mod Uploader.
Download it.
Open It.

Click Create.

Take note of the game version numbers. They will not always be the same as the ones listed here.

Step 2: Finding the ID of the Mod You Need to Change

Pay Attention

Open the mod's page on the workshop.
Grab the url of the mod.
The mod's id will be listed at the end of that url.

https://psteamcommunity.yuanyoumao.com/sharedfiles/filedetails/?id=3559858278
Here is my vanilla rebalance mod as an example.
The id is: 3559858278

Step 3: Finding the Game's ID

Store Page

Select Halo the Master Chief Collection in your Steam Library.
Move your mouse to the right.
Click store page.
Grab the url.
The id will be in that url.

https://psteamproxy.yuanyoumao.com/app/976730/Halo_The_Master_Chief_Collection/
For MCC this is: 976730

Step 4: Finding your mod's Install Folder

Here's the fun part.

Go to your Steam Library.
Right click Halo the Master Chief Collection.
Manage.
Browse Local Files.

On the top bar, navigate to "/SteamLibrary/steamapps/workshop/content/976730/"

For this example, there is only one file, but you'll notice that the name is the same as the mod ID collected earlier.

Step 5: Editing your ModInfo.json

Almost Done

Open your mod folder.
Open ModInfo.json in a text editor.

{ "ModIdentifier": { "ModGuid": "adb1a75e-8412-4010-b4ec-9a61ab2a4d4f", "HostedModIds": { "SteamWorkshopId": 3559858278 } }, "ModVersion": { "Major": 0, "Minor": 0, "Patch": 0 }, "MinAppVersion": { "Major": 1, "Minor": 3385, "Patch": 0 }, "MaxAppVersion": { "Major": 1, "Minor": 3495, "Patch": 0 }, "Engine": "Halo1", "Title": { "Neutral": "Halo CE: Vanilla Rebalance" }, "InheritSharedFiles": "FromMCC", "ModContents": { "HasBackgroundVideos": false, "HasNameplates": false }, "GameModContents": { "HasSharedFiles": true, "HasCampaign": true, "HasSpartanOps": false, "HasController": false } }

Here is the code for the example mod.

"MinAppVersion": { "Major": 1, "Minor": 3385, "Patch": 0 }, "MaxAppVersion": { "Major": 1, "Minor": 3495, "Patch": 0 },

These are the lines we must change. Use the game version numbers collected earlier.

"MinAppVersion": { "Major": 1, "Minor": 3385, "Patch": 0 }, "MaxAppVersion": { "Major": 1, "Minor": 3528, "Patch": 0 },

This example didn't require much editing, there's no guarantee that will always be the case.

Conclusion

Save that File

The mod you've edited will now appear in game and can be played. If you experience further issues, it's because the mod is so old that it actually was affected by an update, not just the game's versioning system being bad. You'll have to contact the mod author at that point or do some experimentation on your own.