Haswell

The missions are rolled randomly for everybody, people can also choose to reroll them using the tokens. I'm likely not even going to bother with the Raid, the skins and freebie rewards don't interest me.

OS: Windows 10 Home, version 1809, 64 bit Game Version: 0.33.7410--2020-10-16_03:16 Brief Description: Customization toggle in gameplay settings do not match description of setting. Steps to Reproduce: Equip some sort of camo/skin on your vehicle of choice Ask another tester to do step 1 Ensure you have customization toggled to "off" in gameplay settings Ensure partner tester have customization toggled "on" Go into a match together Check appearances against each other Result: Tester with customization "off" will not see any skin/camo on either players. Tester with customization "on" will see skin/camo on both players. Expected Behavior: Description of setting should properly reflect result, stating all customization will be disabled if toggled off . OR; Customization toggle should only affect the appearance of the user's own vehicle and nothing else. Fixes/Workarounds: None. Other Notes: Issue is applicable in all gameplay modes. Disabling customization will also remove skins or camos on PvE bots that may use them. Test with camos (Haswell has customization toggled off): Test with skins (Haswell has customization off):

https://aw.my.games/en/news/general/community-highlight-heroics-spg-team-only

https://aw.my.games/en/news/general/second-spirithaven-raid-now-available FAQ: List of possible missions restrictions: 3-6 AFV/LT/TD/MBT (pick one class) 7-10 AFV/LT/TD/MBT Chang MBT (any tiers) Chang non-MBT Francine all Shishkin TD/AFV Shishkin LT Shishkin MBT Wolfi AFV Wolfi MBT Wolfi TD Schreiber all List of possible normal missions (can accompany any restrictions listed above): General: Earn 20,000 points of net XP. Only the matches in which you are amongst the 3 best XP earners (PvP) or the best XP earner (PvE) of your team count towards this objective. In a single battle, eliminate 3 (Random Battles), 10 (GLOPS) or 20 (PvE) enemy vehicles. PvE: Deal 250,000 damage. Only the matches in which you deal the most damage of all players count towards this objective.\n\nAlternatively deal 40,000 damage in a single match while obtaining the Teamwork medal. Destroy or help destroy 250 enemies. Only the matches with 20+ kills or assists count towards this objective.\n\nAlternatively destroy or help destroy 35 enemies in a single match while obtaining the Teamwork medal. Win 10 matches while achieving 70% performance (the percentage of your shells that hit and do hitpoint damage) in each match and dealing the most damage of all players.\n\nAlternatively deal 30,000 damage while achieving 80% performance in a single match. Collect 10 Destroyer medals.\n\nAlternatively destroy or help destroy 30 enemies in a single match while achieving 80% performance (the percentage of your shells that hit and do hitpoint damage). PvP Deal 50,000 damage. Only the matches in which you are amongst the 3 best damage dealers of your team count towards this objective.\n\nAlternatively survive a match while dealing the most damage of both teams. Destroy or help destroy 50 enemies. Only battles with 3+ (Random Battles) or 10+ (GLOPS) kills or assists count towards this objective.\n\nAlternatively destroy or help destroy 5 (Random Battles) or 15 (GLOPS) enemies in a single match without dying yourself. In 10 matches, be amongst the top three damage dealers of your team.\n\nAlternatively, in a single match, deal 5,000 damage (Random Battles) or 20,000 damage (GLOPS). In 10 matches, destroy or help destroy 3+ (Random Battles) or 10+ (GLOPS) enemies.\n\nAlternatively, in a single match, destroy or help destroy 3+ (Random Battles) or 10+ (GLOPS) enemies while having the highest number of kills/assists from both teams. List of possible hard missions: PvE: AFV: Deal 350,000 damage. Each death of yours removes 50,000 points from this mission's progress. LT: Deal 350,000 damage. Received damage is multiplied by 3 and then deducted from the mission's progress. MBT: Deal 350,000 damage. Damage dealt from the distance of 150m or more is multiplied by 10 and then deducted from the mission's progress. TD: Deal 350,000 damage. Each hit without damage deducts 10,000 points from the mission's progress. PvP: AFV: Provide allies with spotting info worth 20,000 damage. Each death deducts 2,000 points from the mission's progress.\n\nAlternatively, in a single match, be the player with the most assist damage from both teams while not receiving any damage yourself. LT: Deal 30,000 damage. Each death deducts 6,000 points from the mission's progress.\n\nAlternatively, in a single match, be the top Experience earner of both teams while not being hit more than 2 (Random Battles) or 5 (GLOPS) times. MBT: Deal 50,000 damage. Received damage is multiplied by 2 and then deducted from the mission's progress.\n\nAlternatively, in a single match, deal the most damage from both teams while not losing more than 800 (Random Battles) or 4,000 (GLOPS) hit points. TD: Deal 30,000 damage. Your each hit without damage deducts 2,000 points from the mission's progress.\n\nAlternatively, in a single match, destroy or help destroy the most enemies from both teams (3 at least) while missing no more than 2 (Random Battles) or 5 (GLOPS) shots. List of freebies (probably non-repeating):

Last update buffed the Stalker missile reload considerably, down to 18s base and 3s burst. My criticism of the dakka still stands, but at least the missiles are more potent now. Doesn't make enough of a difference to improve the Stalker from meh to good though.

Arty OP please nerf. This is nothing short of amazing.

https://aw.my.games/en/news/general/maintenance-october-19-0 Removed formatting because the font shadow is god awful. Seriously, why is this a thing?

Still present as of 0.33.7403--2020-10-14_04:15 Related issue: https://armoredlabs.net/index.php?/topic/3343-ztq-15-incorrect-listed-top-speed/

OS: Windows 10 Home, build 10240 (yes) Game Version: 0.33.7403--2020-10-14_04:15 Brief Description: ZTQ-15 has incorrect top speed of 85km/h listed in garage, or it has a hidden speed cap of 80km/h. The listed top speed will never be reached, the vehicle will not go faster than 80km/h. Steps to Reproduce: Be ZTQ-15 Go into battle Drive straight and try to reach 85km/h Result: Acceleration continues until reaching 80km/h, then stops. 85km/h is never reached. Expected Behavior: Vehicle should continue accelerating until reaching 85km/h, or listed top speed should be amended to 80km/h. Fixes/Workarounds: None. Other Notes: Commanders, consumables and retrofits that increase top speed have no effect. Listed top speed in garage will update correctly, but actual speed cap of 80km/h remains. Related issue: https://armoredlabs.net/index.php?/topic/374-seongun-915-has-lower-top-speed-than-listed/

Context: Not sure why this isn't in the news feed.

If you know where the hole is, you can bully M1A2s.

OS: Windows 10 Home, version 1809, 64 bit Game Version: 0.33.7403--2020-10-14_04:15 Brief Description: M60-2000 hitbox do not match up with visual model. Steps to Reproduce: Be M60-2000 Check armor viewer Compare model with armor map Result: M60-2000 hitbox do not match up with visual model. Expected Behavior: M60-2000 hitbox should match up with visual model. Fixes/Workarounds: None. Other Notes: See mantlet, turret floor, overall turret height, geometry.

In case anyone thinks the mismatching hitbox isn't a big deal, allow me to show why it matters.

Yes, the update compensated people with an extra day to the event.

OS: Windows 10 Home, version 1809, 64 bit Game Version: 0.33.7403--2020-10-14_04:15 Brief Description: XM1 hitbox do not match up with visual model. Steps to Reproduce: Be XM1 Check armor viewer Compare model with armor map Result: XM1 hitbox do not match up with visual model. Expected Behavior: XM1 hitbox should match up with visual model. Fixes/Workarounds: None. Other Notes: See mantlet, turret floor, overall turret height, geometry.

OS: Windows 10 Home, version 1809, 64 bit Game Version: 0.33.7403--2020-10-14_04:15 Brief Description: M1 Abrams hitbox do not match up with visual model. Steps to Reproduce: Be M1 Abrams Check armor viewer Compare model with armor map Result: M1 Abrams hitbox do not match up with visual model. Expected Behavior: M1 Abrams hitbox should match up with visual model. Fixes/Workarounds: None. Other Notes: See mantlet, turret floor, overall turret height, geometry.

OS: Windows 10 Home, version 1809, 64 bit Game Version: 0.33.7403--2020-10-14_04:15 Brief Description: M1A1 Storm hitbox do not match up with visual model. Steps to Reproduce: Be M1A1 Storm Check armor viewer Compare model with armor map Result: M1A1 Storm hitbox do not match up with visual model. Expected Behavior: M1A1 Storm hitbox should match up with visual model. Fixes/Workarounds: None. Other Notes: See mantlet, turret floor, overall turret height, geometry.

OS: Windows 10 Home, version 1809, 64 bit Game Version: 0.33.7403--2020-10-14_04:15 Brief Description: M1A1 AIM hitbox do not match up with visual model. Steps to Reproduce: Be M1A1 AIM Check armor viewer Compare model with armor map Result: M1A1 AIM hitbox do not match up with visual model. Expected Behavior: M1A1 AIM hitbox should match up with visual model. Fixes/Workarounds: None. Other Notes: See mantlet, turret floor, overall turret height, geometry.

OS: Windows 10 Home, version 1809, 64 bit Game Version: 0.33.7403--2020-10-14_04:15 Brief Description: M1A1 hitbox do not match up with visual model. Steps to Reproduce: Be M1A1 Check armor viewer Compare model with armor map Result: M1A1 hitbox do not match up with visual model. Expected Behavior: M1A1 hitbox should match up with visual model. Fixes/Workarounds: None. Other Notes: See mantlet, turret floor, overall turret height, geometry.

OS: Windows 10 Home, version 1809, 64 bit Game Version: 0.33.7403--2020-10-14_04:15 Brief Description: M1A2 hitbox do not match up with visual model. Steps to Reproduce: Be M1A2 Check armor viewer Compare model with armor map Result: M1A2 hitbox do not match up with visual model. Expected Behavior: M1A2 hitbox should match up with visual model. Fixes/Workarounds: None. Other Notes: See mantlet, turret floor, overall turret height, geometry.

OS: Windows 10 Home, version 1809, 64 bit Game Version: 0.33.7403--2020-10-14_04:15 Brief Description: M1A2C hitbox do not match up with visual model. Steps to Reproduce: Be M1A2C Check armor viewer Compare model with armor map Result: M1A2C hitbox do not match up with visual model. Expected Behavior: M1A2C hitbox should match up with visual model. Fixes/Workarounds: None. Other Notes: See mantlet, turret floor, overall turret height, geometry.

OS: Windows 10 Home, version 1809, 64 bit Game Version: 0.33.7403--2020-10-14_04:15 Brief Description: XM1A3 hitbox do not match up with visual model. Steps to Reproduce: Be XM1A3 Check armor viewer Compare model with armor map Result: XM1A3 hitbox do not match up with visual model. Expected Behavior: XM1A3 hitbox should match up with visual model. Fixes/Workarounds: None. Other Notes: See mantlet, turret floor, overall turret height, geometry.

You know it's a quality game when your hitboxes don't match the visual model.

OS: Windows 10 Home, version 1809, 64 bit Game Version: 0.33.7365 (30/09/2020) Brief Description: MMP and MMP-1 missiles on CRAB have missing bonus module damage stat. Tooltip description indicates bonus module damage should be present, but there are no corresponding stats. Unknown if this is cosmetic or actual mechanic. Steps to Reproduce: Be CRAB Check missile stats Result: CRAB missiles have missing bonus module damage stat. Expected Behavior: Bonus module damage stat should be present, or the tooltip description requires correction. Fixes/Workarounds: None. Other Notes: Comparison of CRAB missiles and other missiles. Note that other missiles have bonus module damage.

https://aw.my.games/en/news/general/maintenance-october-15 Stalker buffs look very nice, might make it a more stealthy alternative to the Bradley that sacrifices dakka firepower for vision control. Chinese MBTs get buffs. RIP ATDU. Model changes here: https://aw.my.games/en/news/general/development-model-improvements-update-033-part-2 I personally can't see any difference between the old and new models, nor do I care that much about them when I play on potato graphics. All the MBTs are basically reskins of each other now anyway.