**UPDATES TO ENLISTMENT GIFTING EVENT:**
To prevent exploitation, we will prevent new Accounts from being able to Gift enlistment crystals. We will also be taking action on those who are using 3rd Party Sellers, Bots and other farms to gift themselves mass amounts of Enlistment Crystals. Lastly, we will be adding an expiration timer to Enlistment Crystals. All unopened Enlistment Crystals will expire on Oct 18 @ 17:00 UTC. For more information, please see this post: https://forums.playcontestofchampions.com/en/discussion/346104/updates-to-enlistment-gifting-event
**KNOWN ISSUE**
We have adjusted the node placement of the new AW maps to better allow path traversal. As a result, defender placements have been reset. Please, take a moment to re-place your defender setup. We will be pushing out a message in-game shortly.

Thing Nerf - really?

MadcatMadcat Posts: 385 ★★★
in Bugs and Known Issues
Just casually slipping in a nerf to Thing that requires certain synergies and some skill to use properly... while leaving long standing bugs that cost the player base units in place... Really?



Why was this not mentioned at all until it is in the patch notes? It is clearly a nerf to people using Thing + The Champion + a cheat death synergy and an L3 to be able to ramp his damage up.

Comments

  • ZeezoosZeezoos Posts: 178 ★★
    Another thread on this topic got closed, referencing this thread:
    https://forums.playcontestofchampions.com/en/discussion/comment/1079174/#Comment_1079174

    The thread mentioned and the change being made don’t correlate. There was no change to Thing needed to fix the query in that thread, other than perhaps to the SP3 description. Is this a text change only Kabam?
  • Patchie93Patchie93 Posts: 1,898 ★★★★
    They had this in the known bugs sections since before Christmas
  • Kabam ZibiitKabam Zibiit Posts: 7,033
    Hey there, as others have mentioned, this issue has been known and communicated about for awhile now. The threads about the issue were updated with the status and details of this issue as soon as possible, as were the known issues threads for each update since the issue was found, as can be seen here and here. Since this is not a a bug report and this particular issue has already been addressed numerous times, this thread will now be closed.
This discussion has been closed.