The challenge says “Defeat light infantry enemies in PvE modes.” It says Firefight counts, but when I played Firefight matchmaking, I got no progress towards the challenge despite killing a lot of infantry (grunts, jackals, etc.).
You’re better off just playing a Campaign mission, finding a spot with lots of infantry, kill all enemies, reload checkpoint, lather-rinse-repeat.
Yes while it says firefight what they mean is campaign… Sadly these challenges need some fine tuning on what counts and what doesn’t.
I didn’t have trouble doing it. I use a custom mode that makes every enemy 1shot kill grunts and makes yourself invincible with infinite ammo.
> 2533274981422006;4:
> I didn’t have trouble doing it. I use a custom mode that makes every enemy 1shot kill grunts and makes yourself invincible with infinite ammo.
Yes I know that counts. My point is that matchmaking games should also count, as they are very much PvE.
I’m currently playing ODST Arcade FF in matchmaking and the enemies are counting towards the challenge and now they are in Heroic as well.
> 2533274823473367;5:
> > 2533274981422006;4:
> > I didn’t have trouble doing it. I use a custom mode that makes every enemy 1shot kill grunts and makes yourself invincible with infinite ammo.
>
> Yes I know that counts. My point is that matchmaking games should also count, as they are very much PvE.
I still get kills for that.
> 2727626560040591;6:
> I’m currently playing ODST Arcade FF in matchmaking and the enemies are counting towards the challenge and now they are in Heroic as well.
I guess it works for some people then and I’m just unlucky.
It’s been a year or more and halo is still having issues with these challenges being bugged or completely broken. Why say firefight if it’s not gonna count?!
> 2535423203175874;9:
> It’s been a year or more and halo is still having issues with these challenges being bugged or completely broken. Why say firefight if it’s not gonna count?!
I agree it’s ridiculous. Luckily however, you can still gain progress towards it in custom Firefight.
This is still an issue… This is the second time MCC has launched and it is still pretty disappointing. Between this and the mess of a ‘file share’ system they have that doesn’t at all resemble what it was back in the day, MCC is just kinda blegh. Still hyped for Infinite though, hopefully things like this can be ruled out quickly and efficiently in Infinite.
As this appears to be an issue with your game, we recommend heading over to https://aka.ms/HaloSupport for further assistance. Please review the latest known issues and submit a ticket if your issue is not listed.
Thanks!
> 2533274823473367;1:
> The challenge says “Defeat light infantry enemies in PvE modes.” It says Firefight counts, but when I played Firefight matchmaking, I got no progress towards the challenge despite killing a lot of infantry (grunts, jackals, etc.).
> 2533274823473367;8:
> > 2727626560040591;6:
> > I’m currently playing ODST Arcade FF in matchmaking and the enemies are counting towards the challenge and now they are in Heroic as well.
>
> I guess it works for some people then and I’m just unlucky.
I want to assure you this is not an issue specifically with your game. This is a widespread, long standing issue with MCC and has been for as long as challenges have been out. What is the issue? Challenge progess for PvE kills does NOT track in Halo Reach firefight if you are NOT the host of the session. These challenges work perfectly in Halo 3 ODST firefight regardless- that’s why LUKEPOWA is able to get progress towards those challenges in ODST FF. In firefight matchmaking, the session is hosted on a dedicated server and noone is the host. It will work perfectly in Custom Firefight in Halo Reach only if you’re the host.
I’ve had a ticket in for a year about this and with every update it keeps getting blindly closed out. A year ago I created a thread in the then MCC PC forums about this, giving specific instructions on how to consistently reproduce this bug and encouraging players to submit tickets for this issue. Maybe if we hammer the support site this time around we can get them to act on this. If you’re going to submit a ticket on this matter I would ask that you add the following instructions to your ticket:
Side note: if you’re reading this and have some free time (and a friend) I kindly ask you to try these steps yourself and if you can reproduce the bug please submit a ticket at the support site with these steps:
ISSUE: Challenges for PvE kills do not track in Halo Reach Firefight if you are not the host of the session. Since FF matchmaking is hosted on dedicated servers, it is impossible to get these challenges when you play Reach FF in matchmaking. It is, however, possible to get progress when you are the host of a the Firefight session. These challenges seem to track just fine in the Halo Reach campaign- the issue appears to be isolated to firefight. Halo 3 ODST’s firefight is completely unaffected by this bug.
STEPS TO REPRODUCE THIS ISSUE: - Get two players together (we’ll call them players A and B) who still need to unlock a PvE challenge that deals with killing enemies (such as the “Cannon Fodder” challenge). Have both of them record their progress towards the challenge. - Have player A create a Halo Reach custom firefight and have player B join player A. - Start the custom firefight and kill some enemies. How long you play is up to you, although don’t kill enough to unlock the challenge just yet. - At some point during the firefight, have each player record their progress towards the challenge. What you should notice is that the host player (player A) should have progress getting tracked. The off host player (player B) should have had no kills count for this challenge. - End the game and have A and B switch roles. B now hosts the session and A joins. Before starting, have A and B once again record their progress towards the challenge. - Repeat the test again. At some point in the match, have A and B record their progress. What you should notice now is that A’s kills are no longer tracking but B’s now are.This could just be a simple bug or oversight say from when Reach’s firefight networking model got converted to asynchronous. If we could get them to acknowledge/ fix this issue that would be great.
> 2533274916415091;13:
> > 2533274823473367;1:
> > The challenge says “Defeat light infantry enemies in PvE modes.” It says Firefight counts, but when I played Firefight matchmaking, I got no progress towards the challenge despite killing a lot of infantry (grunts, jackals, etc.).
>
>
>
> > 2533274823473367;8:
> > > 2727626560040591;6:
> > > I’m currently playing ODST Arcade FF in matchmaking and the enemies are counting towards the challenge and now they are in Heroic as well.
> >
> > I guess it works for some people then and I’m just unlucky.
>
> I want to assure you this is not an issue specifically with your game. This is a widespread, long standing issue with MCC and has been for as long as challenges have been out. What is the issue? Challenge progess for PvE kills does NOT track in Halo Reach firefight if you are NOT the host of the session. These challenges work perfectly in Halo 3 ODST firefight regardless- that’s why LUKEPOWA is able to get progress towards those challenges in ODST FF. In firefight matchmaking, the session is hosted on a dedicated server and noone is the host. It will work perfectly in Custom Firefight in Halo Reach only if you’re the host.
>
> I’ve had a ticket in for a year about this and with every update it keeps getting blindly closed out. A year ago I created a thread in the then MCC PC forums about this, giving specific instructions on how to consistently reproduce this bug and encouraging players to submit tickets for this issue. Maybe if we hammer the support site this time around we can get them to act on this. If you’re going to submit a ticket on this matter I would ask that you add the following instructions to your ticket:
>
> Side note: if you’re reading this and have some free time (and a friend) I kindly ask you to try these steps yourself and if you can reproduce the bug please submit a ticket at the support site with these steps:
>
> ISSUE: Challenges for PvE kills do not track in Halo Reach Firefight if you are not the host of the session. Since FF matchmaking is hosted on dedicated servers, it is impossible to get these challenges when you play Reach FF in matchmaking. It is, however, possible to get progress when you are the host of a the Firefight session. These challenges seem to track just fine in the Halo Reach campaign- the issue appears to be isolated to firefight. Halo 3 ODST’s firefight is completely unaffected by this bug.
>
> STEPS TO REPRODUCE THIS ISSUE: - Get two players together (we’ll call them players A and B) who still need to unlock a PvE challenge that deals with killing enemies (such as the “Cannon Fodder” challenge). Have both of them record their progress towards the challenge. - Have player A create a Halo Reach custom firefight and have player B join player A. - Start the custom firefight and kill some enemies. How long you play is up to you, although don’t kill enough to unlock the challenge just yet. - At some point during the firefight, have each player record their progress towards the challenge. What you should notice is that the host player (player A) should have progress getting tracked. The off host player (player B) should have had no kills count for this challenge. - End the game and have A and B switch roles. B now hosts the session and A joins. Before starting, have A and B once again record their progress towards the challenge. - Repeat the test again. At some point in the match, have A and B record their progress. What you should notice now is that A’s kills are no longer tracking but B’s now are.This could just be a simple bug or oversight say from when Reach’s firefight networking model got converted to asynchronous. If we could get them to acknowledge/ fix this issue that would be great.
I was host of multiple firefight sessions in Reach and they still did not count.