The bulk of our messaging between the AH and WS is incident data, which is one-direction and doesn’t require a response. While the discrepancy between those two numbers throws up some red flags, we don’t need a matching number of callback handlers. Based on these constants, BAP can queue up to 2048 messages, but it is limited to 16 responses. K_server_message_default_callback_handler_count= 16 īAP reserves callback handlers for BAP messages that expect a response. k_investment_bap_message_queue_element_count= 2048 Back in the code, I noticed these two constants. Players were frequently loading into activities without completing the full peer validation process! Now I just needed to figure out why we were dropping the query. I checked logs from a random retail AH, and sure enough I found signs that peer validation was waiting indefinitely after sending the query to the WS. Perhaps peer validator was blocking indefinitely while waiting for a response from the WS? Suspiciously, I couldn't find a timeout mechanism in peer validator. In other words, a player is free to join any activity, but is kicked out whenever the AH receives a negative response from the WS. I learned that peer validation happens asynchronously and in parallel with the normal flow of joining an activity. I couldn't reproduce the bug with my onebox, so I began to look through code to see if I could spot the bug, starting with the peer validator. How could the player get into the activity without the flag getting set? Clearly the player loaded into the correct activity. While this was an interesting theory, was it plausible? At the time, I had no idea how this could happen. But if a player could get into an IB match without the IB intrinsic flag set on their account, none of their kills would count towards their IB bounties because those bounties require the IB flag. In those cases, the game is only looking for if/how you killed an enemy, not where you killed an enemy. Some rewards are not tied to activity intrinsic flags, such as world drops or Gunsmith bounties. Our rewards system uses those flags to determine the eligible rewards. When a player starts a new activity, the activity intrinsic flags are marked on the player's account. Within those higher-level categories, there are more specific flags, like Nightfall or Iron Banner. For example, there are flags for strikes, pvp, and raids. This was a compelling theory because it could also explain the IB bug.Įach activity in Destiny is associated with various activity intrinsic flags. It was almost like the game didn't know the type of activity (raid). You can check out the now-disabled exotic helmet, breaking Iron Banner matches below.Interestingly, affected players continued to earn world drops (engrams from enemy kills) even though the raid chests didn't spawn loot. However, players are reporting that if you still have the exotic helmet equipped on your Titan and do not change characters, the bug still works. UPDATE: Bungie has now changed the featured game mode in Iron Banner from Control to Eruption. So, for those who don’t have the helmet already equipped on their Titans, they are out of luck. Shortly after the bug was shared online, Bungie officially announced on its Bungie Help Twitter account that it has disabled the Khepri’s Horn exotic helmet in the game. It was first shared yesterday by none other than Cheese Forever on YouTube. So, if all six players capture a point, it will result in +70 points, activating the Mercy Rule instantly. When used on a capture point in Iron Banner, it gives out +12 points for one player. This glitch involves players using the Titan’s Barricade ability combined with the Khepri’s Horn exotic helmet and Drengr’s Lash Strand Aspect. Image: Bungie via TheGamePost Destiny 2 Bug Ruins Iron Banner, Results in Instant Mercy Rules This bug was extremely disruptive and ruined the entire activity for players who just want to enjoy and score some kills. Recently, there was a new bug discovered that instantly activated the Mercy Rule in Iron Banner matches, resulting in either of the teams winning the match. Related: Nathan Fillion Announces His Destiny Return As Cayde-6 in a New Video Message The emblem is called “Brazen Wolf” and can be unlocked by leveling up Lord Saladin at the Tower to level 16-which brings us to the current state of Iron Banner in Destiny 2. But, that’s not the only new thing added this season for those who love Iron Banner.īungie has also created one of the best-looking emblems Destiny 2 has to offer, specifically for Iron Banner. This season, Iron Banner has received a new weapon called “Pressurized Precision”, which is an Adaptive Frame Strand Fusion Rifle. Season of the Deep is going in full flow with the first Iron Banner currently active in Destiny 2.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |