There needs to be 3 new tools/features added to Halo editing Kits and MCC that would make modding much easier and more fun.
-
There needs to be a tag extractor for H1, H2, H3 and future halo maps for people that want to mess with/use other people’s content derived from custom Halo maps. For example, I want to be able to extract weapon and character tags from Ruby’s Rebalanced H3 campaign, because I want to place them in my own custom maps and play around with them. The first Halo Editing Kit had a tag extractor for this specific purpose, so the new editing kits should also have one. If you do consider making a tag extractor for the modding community, don’t add a protector option for tag files (a protection method for your tag files with a purpose to prevent your tag files from being “stolen”). Adding this will ruin modding for everyone trying to have fun playing with other people’s creations. Back then in the good 'ol Halo Custom Edition days, there were many toxic people in the modding community who abused this “protective” feature making the modding community playground way less fun such as Zteam. HEK added this feature and it sapped the modding community playground for everyone, hence why people made numerous deprotector programs to combat this meaningless feature. Skyrim has a massive modding community and that community has no issues with modding protection, nor do modding programs have a “protective” feature. If someone truly wants to “protect” their creations, they can simply make their own custom directory within a tag directory and route all dependent tag files within that custom directory with custom named folders. That in itself will make it harder for someone to claim someone else content as their own.
-
There needs to be a developer mode for MCC, aside from Anti-Cheat disabled mode. This developer mode should have a command console ready for offline (disabled for multiplayer) use for testing and simply having fun. A command console is already included in Sapien, but it shouldn’t just be restricted for scenario testing. Users should be able to use a command console within their custom Halo maps in-game like in Halo Custom Edition. So have 3 modes upon start up for MCC, standard with Anti-Cheat, Anti-cheat disabled (offline for multiplayer) or Anti-cheat disabled Dev mode (offline multiplayer).
-
Now support for modding is up, there needs to be a browser for custom made Halo maps within MCC.
1 last thing: There needs to be audio within Sapien game editor. If anyone doesn’t want audio they can switch it off within Sapien. Adding audio within Sapien will make it easier for people trying to add audio scenery.
> There needs to be 3 new tools/features added to Halo editing Kits and MCC that would make modding much easier and more fun.
>
> - There needs to be a tag extractor for H1, H2, H3 and future halo maps for people that want to mess with/use other people’s content derived from custom Halo maps. For example, I want to be able to extract weapon and character tags from Ruby’s Rebalanced H3 campaign, because I want to place them in my own custom maps and play around with them. The first Halo Editing Kit had a tag extractor for this specific purpose, so the new editing kits should also have one. If you do consider making a tag extractor for the modding community, don’t add a protector option for tag files (a protection method for your tag files with a purpose to prevent your tag files from being “stolen”). Adding this will ruin modding for everyone trying to have fun playing with other people’s creations. Back then in the good 'ol Halo Custom Edition days, there were many toxic people in the modding community who abused this “protective” feature making the modding community playground way less fun such as Zteam. HEK added this feature and it sapped the modding community playground for everyone, hence why people made numerous deprotector programs to combat this meaningless feature. Skyrim has a massive modding community and that community has no issues with modding protection, nor do modding programs have a “protective” feature. If someone truly wants to “protect” their creations, they can simply make their own custom directory within a tag directory and route all dependent tag files within that custom directory with custom named folders. That in itself will make it harder for someone to claim someone else content as their own.
>
> - There needs to be a developer mode for MCC, aside from Anti-Cheat disabled mode. This developer mode should have a command console ready for offline (disabled for multiplayer) use for testing and simply having fun. A command console is already included in Sapien, but it shouldn’t just be restricted for scenario testing. Users should be able to use a command console within their custom Halo maps in-game like in Halo Custom Edition. So have 3 modes upon start up for MCC, standard with Anti-Cheat, Anti-cheat disabled (offline for multiplayer) or Anti-cheat disabled Dev mode (offline multiplayer).
>
> - Now support for modding is up, there needs to be a browser for custom made Halo maps within MCC.
There also needs to be audio enabled within Sapien. Audio disabled makes it hard for anyone trying to implement audio scenery into their maps