Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.
Lord Zedd
Administrators-
Content count
1,614 -
Joined
-
Last visited
Recent Profile Visitors
.png.2c1a630588b18556e4a5ba66f9ce7d61.thumb.png.1bf7cd14829665035cc34a48c2026bf6.png)
-
Yeah Reach chdt is very ugly. If you pull up a weapon hud that keeps the crosshair, you can try and copy over all the "compiled states" for that crosshair element(s) in the "compiled widget data" (along with the starting value enums) to match.
-
That is a limitation of the forge map format itself. Roughly 650 objects total for forge.
-
Hi there. So the tooltips in the latest Assembly says that an AI char interpolates between the 1st and 2nd firing pattern block based on its 0-1 accuracy. However, most covenant weapons have 4 firing pattern blocks, so what are the 3rd and 4th firing patterns for? Through some in-game testing (in firefight), I think I have confirmed all of the following theories to be false:
- patterns 0-3 used sequentially between accuracy 0 and 1 (pattern 3 is not used on accuracy 1 ever)
- patterns 2-3 replace patterns 0-1 on heroic or legendary (legendary AI on accuracy 1 still uses pattern 1)
- patterns 2-3 are for USNC characters using covie weapons (I gave an ODST a needler and he used the same pattern as the grunt I took it from)
My only untested theory is that one pair is for campaign and the other is for firefight? But i doubt it.
-
Download this and replace the file in Formats\ReachMCC\ https://raw.githubusercontent.com/XboxChaos/Assembly/dev_mcc/src/Blamite/Formats/ReachMCC/ReachMCC_Poking.xml
-
You no longer need to compile. It is available at https://www.nexusmods.com/halothemasterchiefcollection/mods/1
-
Tags can share blocks to save on space, resulting in stuff like you guys are experiencing. A workaround would need to be added to Assembly to make a unique copy.
-
With Cheat Engine go to haloreach.dll+DC9DA and haloreach.dll+DC9E7, right click them and select "replace with code that does nothing" With Cheat Engine go to haloreach.dll+DCA8A and haloreach.dll+DCA97, right click them and select "replace with code that does nothing"
-
You can send plugins to me directly, or create a pull request on github.
-
It isn't quite finished or I would have uploaded it myself.
-
I'd rather you not upload.
-
hi. greetingts lord zedd. ive updated my halo 4 xex with default.xexp. (tu10) . do you have any patch to enable theater in campaign again for that TU? i´ve found this Halo 4 Checks Removed and Unlock All XEX PPFs for TU7. (not aplicable) . i will thank you if you give me some info about. (i got banned console so i dont have xbox live) . greetings
-
now with campaign and better stability thanks to more research
