Store Page
Halo: The Master Chief Collection
All Discussions Screenshots Artwork Broadcasts Videos Workshop News Guides Reviews

Halo: The Master Chief Collection

Store Page
Halo: The Master Chief Collection >  Workshop > III AVIATOR III's Workshop > Diamondback AI Battlefield | Endless AI War > Discussions
Diamondback AI Battlefield | Endless AI War
Description Discussions5 Comments107 Change Notes
This topic has been locked
III AVIATOR III  [developer] 13 Mar, 2024 @ 9:00pm
Version 1.2 Update is Now Released!
Well its that time again! I have just released an update to this map, which includes a number of fixes and improvements to the mod overall. Some of the implemented changes came directly from you the fans! Read below for whats changed/new and I'll see you out there on the battlefield!


1.2 Changes:

  • After disabling an AI squad control switch, the corresponding AI squad will no longer arrive an additional time.

  • When an AI switch is disabled, the corresponding AI squad will immediately be despawned.

  • Cooldown times reduced for a number of the AI squads.

  • The AI Spartans have been upgraded. They now come in assorted H3 classic armors, and sport a desert colored armor coating.

  • Drones will no longer sometimes refuse to descend into the map after being dropped from their Phantom.

  • Player spawns fixed to be way more consistent. Green Team (UNSC) players will always respawn near the UNSC base, Purple Team (Covenant) will always respawn near the Covenant base, and Gold Team (Flood) will respawn in the central cave network, or map center. Please read the section that has been added to the map's description to see how to get your spawns working consistently. It will not work out of the box.

  • UNSC Marines/ODST’s are now far less likely to camp their high ground near the UNSC man cannons. They are now somewhat more likely to attempt a takeover of the Covenant’s high ground on the opposite side. This decision is up to each and every AI, and randomized on each spawn.

  • Code side rewrites and optimizations.
Last edited by III AVIATOR III; 26 Oct, 2024 @ 10:36pm
< >
Showing 1-2 of 2 comments
Vrishnak92™ 16 Mar, 2024 @ 1:48am 
Got a bug report for ya, when one of the odst's were infected by the flood their AI bugs out and they end up on a separate team to the flood itself, resulting in them being hostile to both the flood spawned by the button and gold team: https://youtu.be/I-jIWHLISK8
#1
III AVIATOR III  [developer] 16 Mar, 2024 @ 12:50pm 
Originally posted by Vrishnak92™:
Got a bug report for ya, when one of the odst's were infected by the flood their AI bugs out and they end up on a separate team to the flood itself, resulting in them being hostile to both the flood spawned by the button and gold team: https://youtu.be/I-jIWHLISK8
That's a known issue to me actually. I noticed it during testing and thought it was too minor of a bug to address. I'll explain:

This happens due to the AI default team settings in H3's engine. Players wanted the Covenant's team color to be purple, as it matches their color theme the best. In Halo 3's engine, the purple team actually equals the "flood" team. Orange team is the team that equals the "covenant" faction in the game engine. So what I did was force all Covenant forces onto the flood faction which comes to equal the purple team in MP, and forced all flood onto the "forerunner" team which happens to be gold in multiplayer. The forerunner team was going unused with no sentinels or other units in the map, so I felt that this move was a good idea.

When the flood infection forms resurrect a dead flood or UNSC/Covenant corpse, the game automatically places the new AI on the internal "flood" faction - which in my mod is being used by the covenant to make their MP team alliance purple. Hence this is why you'll sometimes see these flood attempting to betray each other. Funny, I know. However I never saw this as that much of an issue so I left it un-addressed. Now, I could go ahead and fix this as I definitely know what is wrong and how to remedy it, but it will take potentially a decent amount of time and effort which I never felt was actually that worthwhile as the bug is so minor. Maybe in the next update if I can set aside some time I'll eliminate this bug once and for all.

Thanks for the question and bug report. It means a lot!
#2
< >
Showing 1-2 of 2 comments
Per page: 1530 50