Windows XP users will now be able to see the custom chat, although it’ll use an installed typeface rather than the featured one. This bug is caused by Windows XP itself and there isn’t a suitable workaround (apart from getting a newer OS), although you’ll be able to select your own typeface at some point in the future.
Some maps could cause the game to crash after downloading. This was a regression (plain English: it worked, then I broke it) introduced in the January update.
Forgetting to use an option (0/1/true/false) with custom_chat will no longer cause a crash.
This update introduces a Lua scriptable medal system. To get the ball rolling, I’ve provided three example medal packs (click to download); Halo 3, Halo Reach and Halo 4. To install a medal pack, simply download it to your HAC folder under the ‘packs’ directory (create it if it doesn’t exist) but do not extract it. For example:
Just a minor update to fix a few issues introduced by the rushed 2.1.2 that was primarily intended as a 1.10 compatibility patch.
Joining 1.10 servers on Halo PC (CE unaffected) will now work as expected.
Map downloading is once again functional.
“Play ball” is no longer announced in the place of “double kill”, as amusing as it was.
As a peace offering, a console command that can be used to enable a test version of the new chat system has been added. If you’d like to give it a try, use ‘custom_chat 1‘. An example of what to expect below.
Aside from 1.10 compatibility, here’s the list of changes:
The sightjacker will no longer advance by two players at a time when using the keyboard controls.
HUD colour resets now save correctly.
Field of view preferences had a small chance to reset if the game didn’t exit correctly.
The sightjacker will now automatically continue to track your target after respawning.
The BSP upgrade is now available for all game versions rather than just CE 1.09.
The HUD colour shortcut key has been moved from F9 to F8.
New features overview:
The particle limit has been increased by 50%.
Active camouflage now renders correctly on Nvidia cards (not tied to 1.10).
Scope blur can be disabled via a console command without requiring the disablealpharendertargets config.txt mod.
Resolution selection is no longer limited to a maximum of 1600×1200 (not tied to 1.10).
Your resolution in windowed mode can now match your desktop resolution.
The game now has a windowed-fullscreen mode.
The full active camouflage effect will now display correctly on Nvidia cards by default. If you wish to revert to the old effect, you can use the console command camo_fix 0.
Scope blur can now be toggled with the command scope_blur 0/1. This removes the need to add the potential undesirable disablealpharendertargets option to your config.txt.
Resolutions & Windowed-Fullscreen mode:
The requirement to specify the -vidmode argument has been removed with a fix to Halo’s video options to allow for the selection of all supported resolutions.
Additionally, when running the game in windowed mode (-window), users can toggle between windowed and the new windowed-fullscreen mode by pressing alt + enter. As with other games that offer a windowed-fullscreen option, your game resolution must match your desktop resolution to be able to enter windowed-fullscreen. The reason for this limitation is simply that the window scaling used by Windows 7 and up makes the game look awful if it has to be stretched.