Lots of Glitches In The Flood! NEEDS FIXING!

Games Other Halo
1

There seems to be quite a few issues with this gametype which I’m sure has been brought into the light already. But, for some reason has yet to be resolved. So, I’m asking anyone who has witnessed these glitches or others to please make a post so we can get them resolved!

The Flood Gametype appears to be the most glitchy game you have at the moment. About 40% of all games that I have played have had at least one human rendered a different color which is the least of the problems.
However, there is also a high chance within any given game of viewing or being viewed as an enemy (through a red name instead of a friendly white name) which is a bit sketchy considering the third possible glitch.
Which would be a friendly player being rendered as an actual enemy even though their character is a human (or if you’re a flood then a flood character). They have the ability to kill or be killed without any consequences and getting kill points for it, almost as if they are on a third team. Mostly after they die they seem to revert back to one of the standard flood or human teams.
Finally the most severe glitch which has a person join a game (usually once it has already been started) and is permanently on a type of ‘third team’ (starting out as a human) with a weapon that is usually associated with their own custom loadout such as a DMR and they are able to kill both the humans and the flood without any consequences, and even when they die they respawn as a human - still on that ‘third team’.

Just a friendly heads up to 343 to help resolve these issues.

Once again, if anyone has witnessed these glitches or has seen others within this gametype please post anything just so we can get this game cleaned up a bit!

2

I had these glitches happen to me every game for the first 20 odd I played. After that I just gave up on the game-type. I mean how can they test the game and not see these things happening.

I sincerely hope they fix these glitches which are so blatant and in your face, I can’t fathom how they missed them.

3

I’ve seen all these glitches and more. And they have all happened from in-game joining. Unfortunately, the testers wouldn’t know that because, apparently, no one joined in with them at the time. Hopefully, now that the game’s out, it will be fixed soon.

4

These glitches exist in both Reach and Halo 4, though the new Flood model adds a new dimension to them, and Matchmaking JIP makes them more frequent.

Basically, the gametypes cannot rely on the normal team system that is built into the core game engine, because that team system does not allow gametype script to force a team change mid-game. (Glitches in Halo: Reach prove this; I’d be happy to go into more detail on them.) So Infection/Flood basically had to reinvent the wheel and use their own, script-based team system: they start with an FFA gametype, they manually add all players to lists that serve as teams, and they manually assign alliance status and traits on a per-player basis.

Unfortunately, this reinvention of the wheel is imperfect; it’s especially hosed by mid-game joins. Traits are assigned incompletely or not at all, and alliance status is assigned incorrectly off-host.

First glitch permutation noted in OP: Trait assignment failure. Appearance traits are especially prone to this; player waypoints were very sketchy in Reach.

Second glitch permutation noted in OP: Alliance status assignment failure, off-host. Host correctly tracks team status, which is why you can boot for the relevant betrayals.

Third glitch permutation noted in OP: Alliance status assignment failure, on-host. The player is put on one of the proper team lists, but the actual switching of alliance status between them and others doesn’t happen for some reason. Alliance status is properly assigned on respawn.

Fourth glitch permutation noted in OP: Pseudo-team tracking failure. Seems that for some reason, the gametype fails to add the new player to any of the team lists. Since they’re not on a list, they’re never set to allied with any other players, and their alliance status is never corrected on respawn.

Fifth glitch permutation, not noted in OP: Player model assignment failure. Flood can appear with Survivor models and vice versa. Common sense would dictate that an “enemy” with the same player model as you is simply suffering from an alliance status bug, but thanks to this bug, common sense is occasionally wrong. Notably, this permutation appears to result from lag as well as join-related bugs.