Halo MCC Trainer - MCC Toolbox V5.2!- Halo 4, Halo 3 ODST, Halo 3, Halo 2, Halo CE, Halo Reach

[blackbommer22]

How do I do Flycam for CE and 2?

[SilentRunner]

How do I do Flycam for CE and 2?

I have updated the Fly Cams in awhile so they don't work, they take extra time to update and virtually no one ever used them

[blackbommer22]

damn i really wanted to mess with it.....is there any chance you can add it back? or if theres another mod of one for Halo 2 MCC specifically? thank you <3

[SilentRunner]

damn i really wanted to mess with it.....is there any chance you can add it back? or if theres another mod of one for Halo 2 MCC specifically? thank you <3

Here you go. Please note though thirdperson seems to be bugged in Halo 2 and I haven't figured out a fix for it yet. Once you turn of the flycam you will be stuck in thirdperson likley until you restart the game. Should work fine in Halo CE though, this is a quick update and I haven't tested the flycam much either...
[Link]

[sean24]

MCC Toolbox-
MCC Toolbox is designed to work across all MCC titles
and is intended for custom game and campaign use
only. This tool is designed to be used in mod mode
and will not work online. I will not help you in anyway
to cheat online so don't bother asking. This tool makes
no attempts to bypass anticheat and any attempt to use
it online may result in a ban you have been warned.

NOT WORKING READ HERE?
-Toolbox will not work unless MCC is run in mod mode
-Running your operating system in another language may cause issues
-When MCC is updated Toolbox will likely stop working, check the game version in the console window
-You may need to run Toolbox as admin
-Check your antivirus is not blocking Toolbox



Download:
[Link]

Just wanted to say thanks for all your hard work your project’s been a huge inspiration while I’ve been building my own MCC mod! I’ve been learning a ton, and I’ll definitely be giving you credit in my menu

A Tiny Speed Boost for Offset Scans
I noticed the offset updates could get a little slow on weaker hardware (my PC’s showing its age ), so I tweaked my scan ranges and saw a massive improvement from 8 minutes down to 10 seconds!

The key was narrowing the AoB scan range to just moduleBase + 0x2500 for most patterns (instead of scanning the entire module). Example:

long result = m.AoBScan((long)moduleBase, (long)moduleBase + 0x2500, pattern, true, true, false, "").Result.FirstOrDefault();

A few patterns (like deathless player scans in H3/ODST/H4) still need wider ranges (0x10000 or custom per option), so those take 20 sec each for me. "hope soon to get them down to 0x2500 for faster scans"
Not a universal fix, but works for me

Sharing = Caring
Figured I’d pass it along in case it’s useful for your project (or anyone else digging through the forums). If you’ve got any pro tips for optimizing those stubborn H3/ODST scans, I’m all ears!

Thanks again for everything. Cheers!

[SilentRunner]

MCC Toolbox-
MCC Toolbox is designed to work across all MCC titles
and is intended for custom game and campaign use
only. This tool is designed to be used in mod mode
and will not work online. I will not help you in anyway
to cheat online so don't bother asking. This tool makes
no attempts to bypass anticheat and any attempt to use
it online may result in a ban you have been warned.

NOT WORKING READ HERE?
-Toolbox will not work unless MCC is run in mod mode
-Running your operating system in another language may cause issues
-When MCC is updated Toolbox will likely stop working, check the game version in the console window
-You may need to run Toolbox as admin
-Check your antivirus is not blocking Toolbox



Download:
[Link]

Just wanted to say thanks for all your hard work your project’s been a huge inspiration while I’ve been building my own MCC mod! I’ve been learning a ton, and I’ll definitely be giving you credit in my menu

A Tiny Speed Boost for Offset Scans
I noticed the offset updates could get a little slow on weaker hardware (my PC’s showing its age ), so I tweaked my scan ranges and saw a massive improvement from 8 minutes down to 10 seconds!

The key was narrowing the AoB scan range to just moduleBase + 0x2500 for most patterns (instead of scanning the entire module). Example:

long result = m.AoBScan((long)moduleBase, (long)moduleBase + 0x2500, pattern, true, true, false, "").Result.FirstOrDefault();

A few patterns (like deathless player scans in H3/ODST/H4) still need wider ranges (0x10000 or custom per option), so those take 20 sec each for me. "hope soon to get them down to 0x2500 for faster scans"
Not a universal fix, but works for me

Sharing = Caring
Figured I’d pass it along in case it’s useful for your project (or anyone else digging through the forums). If you’ve got any pro tips for optimizing those stubborn H3/ODST scans, I’m all ears!

Thanks again for everything. Cheers!

The AOB scans used to update Toolbox use the module base as the start region, as for some of the scans used to enable features some dynamically grab a start region such as Halo 2, this should be displayed in the console window. Some of the others like Halo 3 I did not find a reliable way as they are not stored in a static area. I haven't put alot of effort into improving the AOB scan speed as in the memory module I use they are known to be pretty buggy, I have put in requests to improve them on the GitHub page but there has been no improvement I have seen for along time, they still seem pretty hit and miss.



For example scanning certain memory areas in certain games can just fail sometimes and other times it works. I created a dedicated AOB scanner tool here which allows you to play around with AOB scanning abit more but again it uses the same memory module viewtopic.php?t=20592

You can create, export and import your own AOB scan lists, it's a basic system but I thought it might be useful and has been for me on occasion, it also conducts multiple scans at once and is much faster but may still be slow on older computers. My full MCC scan list is also included in that thread. I had thought about looking for another memory module to use but recoding Toolbox was something I had little interest in.

Best of luck on your tool.

[chekmizake]

Hello, how are you? I hope you're doing well. Before writing, I took the time to read the entire post, from day one of creating this tool to your last post a few months ago. I'll try to be as brief as possible.
While playing the entire MCC, I installed a Reach maps mod where I also implemented Halo MCC Trainer - MCC Toolbox V5.2, and I noticed that third-person work was working for some weapons but not for others. Thinking it was a bug in the modified maps, I tried Toolbox V5.2 again, but it continued to show the same situation: some weapons were in third person and others were not. I started testing the entire MCC series, and the only ones that had this problem were Halo Reach and Halo ODST. My question is, in all this time creating and testing Toolbox, did the same thing happen to you? I didn't read anyone talking about this in the 31-page post. That's my question. I'd like to know your answer. I've tried a lot of things, and so far, I haven't discovered anything about it. I used the AOB scam and it was no use.

I have:
- Halo MCC pirate "elamigo"
- I don't use Steam, Microsoft Game, or anything like that.
- The game is installed 100% portable.
- I have Windows 10
- And my native language is Spanish.

I apologize if what I'm writing isn't very clear, since I use Google Translate, and I'll be looking for a solution on my own anyway.

By the way, the Halo MCC Trainer - MCC Toolbox V5.2! It works perfectly for me. I just have this question about third person in Halo Reach and Halo 3 ODST.

Finally, if there's a new Halo Toolbox update, could you include a way for 3rd person to be automatically disabled when the scope is activated? Could you also include a hotkey for third person in all Halo games? They could use it with any key, like in Cheat Engine with the hotkey option.

Thank you very much in advance for reading everything.

[SilentRunner]

Hello, how are you? I hope you're doing well. Before writing, I took the time to read the entire post, from day one of creating this tool to your last post a few months ago. I'll try to be as brief as possible.
While playing the entire MCC, I installed a Reach maps mod where I also implemented Halo MCC Trainer - MCC Toolbox V5.2, and I noticed that third-person work was working for some weapons but not for others. Thinking it was a bug in the modified maps, I tried Toolbox V5.2 again, but it continued to show the same situation: some weapons were in third person and others were not. I started testing the entire MCC series, and the only ones that had this problem were Halo Reach and Halo ODST. My question is, in all this time creating and testing Toolbox, did the same thing happen to you? I didn't read anyone talking about this in the 31-page post. That's my question. I'd like to know your answer. I've tried a lot of things, and so far, I haven't discovered anything about it. I used the AOB scam and it was no use.

I have:
- Halo MCC pirate "elamigo"
- I don't use Steam, Microsoft Game, or anything like that.
- The game is installed 100% portable.
- I have Windows 10
- And my native language is Spanish.

I apologize if what I'm writing isn't very clear, since I use Google Translate, and I'll be looking for a solution on my own anyway.

By the way, the Halo MCC Trainer - MCC Toolbox V5.2! It works perfectly for me. I just have this question about third person in Halo Reach and Halo 3 ODST.

Finally, if there's a new Halo Toolbox update, could you include a way for 3rd person to be automatically disabled when the scope is activated? Could you also include a hotkey for third person in all Halo games? They could use it with any key, like in Cheat Engine with the hotkey option.

Thank you very much in advance for reading everything.

Hi, thanks for reading through the thread before leaving a comment.

In most of the Halo games there is a flag for each weapon that determines if thirdperson is triggered when you equip it, I break this flag or mess with it in someway sometimes changing the offset to trigger thirdperson. It's not a perfect method I use, it's probably abit messy but for the most part it works. If you are only having problems with mods it's likely because people can add new weapons and change them so much my method just no longer works. There are other ways I tryed forcing thirdperson in the past but this was often worse as it could cause crashes in cutscenes. If you are having issues in the base game without mods that is new to me, I have never tested thirdperson with every weapon so it could be possible there is a scenario where it does not work but for the most part it should.

I don't really work on the project anymore so I don't have plans to add anything new, if I do come back it's generally just to fix it for a patch.

[chekmizake]

Hi, thanks for your quick response. I thought it would take you longer.

I understood what you said. What you were saying about third-person weapons is in Halo Reach and Halo 3ODST, but I'll focus more on the former, which is the one I've spent the most time on. For example, in the first mission in Reach, although there are several weapons that aren't visible in third-person, the ones that are affected are the Magnum and the assault rifle. Both on the modified map and the original map, they look exactly the same. But if I move on to the mission "Long Night of Consolation," which is the mission where you most understand third-person weapons, like the Magnum and the assault rifle. It's truly something I haven't been able to understand, how the same weapons don't work in one map but do in another.

Regarding the flags you mentioned about activating third-person, I've used the Assembly program, and it works perfectly in 3D.

On the other hand, I scanned with the toolbox within the mission where third-person is enabled, like the magnum and assault rifle weapons, and it returned the following code: "Well, I don't know what it's actually called."
HR Third Person = haloreach.dll + 000C6AEB
HR Third Person = haloreach.dll + FFFF80021A550000
HR Third Person = haloreach.dll + FFFF800218FD0000
HR Third Person = haloreach.dll + 000C690F

The first one is the one that always changes and works. I've added the others to the addresses.ini file, but I don't know if it works that way or if something else needs to be added to see if it works for weapons that aren't displayed in third-person.

In conclusion, there are weapons that can be seen in third-person and others that can't on the same map. Whether the map is modified or not, the result is the same.

My question is, and I apologize for insisting, in Reach, in the first mission, didn't you see the magnum and assault rifle in third-person view? Do you have a friend or acquaintance who can confirm what I'm asking?

I'll continue investigating, and if I find a solution, I'll share it here.

Thank you for taking the time all these years to create and support this tool. It's incredible!

[SilentRunner]

Hi, thanks for your quick response. I thought it would take you longer.

I understood what you said. What you were saying about third-person weapons is in Halo Reach and Halo 3ODST, but I'll focus more on the former, which is the one I've spent the most time on. For example, in the first mission in Reach, although there are several weapons that aren't visible in third-person, the ones that are affected are the Magnum and the assault rifle. Both on the modified map and the original map, they look exactly the same. But if I move on to the mission "Long Night of Consolation," which is the mission where you most understand third-person weapons, like the Magnum and the assault rifle. It's truly something I haven't been able to understand, how the same weapons don't work in one map but do in another.

Regarding the flags you mentioned about activating third-person, I've used the Assembly program, and it works perfectly in 3D.

On the other hand, I scanned with the toolbox within the mission where third-person is enabled, like the magnum and assault rifle weapons, and it returned the following code: "Well, I don't know what it's actually called."
HR Third Person = haloreach.dll + 000C6AEB
HR Third Person = haloreach.dll + FFFF80021A550000
HR Third Person = haloreach.dll + FFFF800218FD0000
HR Third Person = haloreach.dll + 000C690F

The first one is the one that always changes and works. I've added the others to the addresses.ini file, but I don't know if it works that way or if something else needs to be added to see if it works for weapons that aren't displayed in third-person.

In conclusion, there are weapons that can be seen in third-person and others that can't on the same map. Whether the map is modified or not, the result is the same.

My question is, and I apologize for insisting, in Reach, in the first mission, didn't you see the magnum and assault rifle in third-person view? Do you have a friend or acquaintance who can confirm what I'm asking?

I'll continue investigating, and if I find a solution, I'll share it here.

Thank you for taking the time all these years to create and support this tool. It's incredible!

Toolbox has so many features for so many games I never really had the time to test the features through all of the missions so often I would implement a feature thinking it was fine testing it on a few maps but there would be some situations were it would not work or even worse cause a crash. Not to mention there is even multiplayer custom games were many feautres work.

The .ini file where the addresses are stored, this is only really for updating addresses of existing features you cannot add really new addresses in there because the OP codes that are being changed are stored inside toolbox. The purpose of the .ini file was a last ditch attempt by me to keep the program alive should I abandon it completely in the future and there are future patches.

It's never actually been fully tested since a patch hasn't come out since I put in the automatic updating feature, the way it is supposed to work is the following. When you start the game Toolbox checks the games process and finds the MCC launch .exe location and grabs the version number form it comparing it to the one stored in the .ini file. If there is a mismatch it attempts to automatically update all of the addresses inside the .ini file using AOB scans again that are built into Toolbox. For me to let people add there own opcodes would be alot of work as I have always said Toolbox was a learning project for me I've never been a great programmer I just hacked stuff together along the way and had help from alot of people.

The way I do alot of my features is usually NULLING out opcodes which is abit lazy and sometimes I have found some decent ways to just change an offset to another which gave a desired effect. I can't really off any solutions to your thirdperson issue besides opening the thirdperson address in memory viewer and messing with it yourself and learning abit of Cheat Engine online. You can also get quite far with AI these days aswell and asking it for help but I think your better off learning alittle bit yourself or gettin the AI to teach you, some of the basics can get you along way.

Incase you missed it I also created a AOB scanning tool and released my full MCC scan list here - viewtopic.php?t=20592 This actually lets you see the AOB scans I am using and you can keep them updated yourself should you want to as you can edit the full list inside the program. You could also edit the list so it only scans for Halo Reach or whatever game you want...