[b]Issue:[/b] Error Code AntEater, Delayed XP, Delayed Loot, Delayed mechanics related to XP, Unable to rally a rally flag. (This is all related to how XP is rewarded) [b]Background:[/b] For the general player base, this issue has been going on since the launch of Witch Queen, Most predominantly known within Wellspring. For those that may be unaware XP is awarded after each enemy killed in all content. This seems fine as it rewards you for killing enemies and allows you to level up your season pass and artifact level. But this has caused a ripple effect in all content with high enemy density. Which has caused all of the Issues shown above. [b]Content Affected (and how):[/b] - [u][i]Vault of Glass[/i][/u], Confluxes has very high enemy density. When killing the enemies quickly and efficiently you will then be error code "anteater" out of the raid simultaneously with your fireteam members. If you were to not get error coded, you would then be unable to rally the rally flag and your loot will not have dropped from that encounter for an extended period of time. - [u][i]Last Wish[/i][/u], Shuro Chi has very high enemy density. There are not enough enemies in comparison to Confluxes in Vault of Glass to be error coded, but you will receive a massive delay in loot being rewarded to you along with the portal to Morgoth not appearing. Without this portal to Morgoth, you are unable to enter the ascendant realm to make your way to the next encounter. - [u][i]Wellspring[/i][/u], as a whole has very high enemy density. This is incentivising players to clear the enemies as quickly as possible to progress and not die. Because of this when you are allowed to place a rally flag you will be unable to rally it. - [u][i]Ketchcrash[/i][/u], as a whole has very high enemy density. This is incentivising players to clear the enemies as quickly as possible to progress and not die. Because of this when you are allowed to place a rally flag you will be unable to rally it. - [u][i]Garden of Salvation[/i][/u], Clearing the starting portal enemies very quickly can cause a slight delay in being able to rally the rally flag at the first encounter. - [u][i]Vow of the Disciple [/i][/u], Third encounter "Exhibition" has very high enemy density. When clearing the enemies quickly and efficiently the prompt to place a rally flag at the final encounter is not available, and the "prism" (the thing ruhlk spawns out of) when you walk close to and start the encounter is not visible, there are no doors to the red chest rooms and there is no respawn zone so if you die you are stuck in finding spawn location. - [u][i]Deepstone Crypt[/i][/u], Third encounter "Rapture" has very high enemy density. When clearing the enemies quickly and efficiently you will be unable to rally the rally flag at the final encounter (boss encounter) for an extended period of time. - [u][i]Kings Fall[/i][/u], Totems encounter has very high enemy density. When clearing the enemies quickly and efficiently you will be unable to rally the rally flag at warpriest and loot/XP will be delayed for an extended period of time. [b]The Re-Occurring Variable:[/b] As you can probably tell if you have made it this far, the common variable would be high enemy density. When the game is calculating a base amount of XP to be given based on an enemy dying, and you are killing those enemies at a quick rate after a while for 6 players in a fireteam you end up with the game needing to catch up. It can only process so much data that when it reaches a point the game Anteaters you out of that content and if it does not anteater you than you will be waiting for an extended period of time without being able to rally a rally flag and wait for your loot from that encounter to drop if you are in a raid. Destiny's servers also play a factor as if the servers are not under as much pressure (so in a time with fewer players online), it can process that data quicker resulting in these issues being slightly less prevalent. [b]Closing Remarks:[/b] This issue is not a particularly easy one to solve, I have some ideas on what I think could be done to make this a nonissue, but I am not a game developer. I am looking to make sure this issue is noticed by Bungie and addressed as soon as possible. If this thread gains some traction I will give some ideas as others might as well. Something else that I am looking for is in future TWABS/HotFixes that they actually put all known issues in the known issues section so we know you are aware of it. Sometimes it feels like the player base has to bring it up way more than we should before it is addressed that you are aware of an issue.