**Mastery Loadouts**
Due to issues related to the release of Mastery Loadouts, the "free swap" period will be extended.
The new end date will be May 1st.
Due to issues related to the release of Mastery Loadouts, the "free swap" period will be extended.
The new end date will be May 1st.
Options
Comments
Beside Mike said "...We don't want to fix this..." in his comment, and you still act like it not exist
1) Gaming company will test many thing, asking them to announce what they are testing and then test is plain nonsense. They will test it, and then make a post about it. Then you get outraged. This was a mistake that happened while testing. Move on
2) Asking for RDT and awakening gems back is again plain nonsense.This was a exploit. If you have problems with the nodes, complain about the node. Fixing something in the game is what they are supposed to do. Saying that you awakened corvus to play map 7 i imagine is unbelievable. I would ask you to pull the other one because it has bells on them.
3) 13 sheets of complaints for something that is not even live in game is amazing. Atleast with general feedback thread, people were complaining about the problems in act 6 which is legitimately a problem. In this case, we are not even live with the change. So, people need to cool down
If Kabam is developing new content or champions, fine. They can keep that under lock and key and release it when they feel the time is right.
However, bugs that are discovered should be shared with the community once they've been confirmed. This would save a TON of heartache and anger. There is a "Known Issues' thread on this very forum for this specific reason.
For example, if Kabam thinks that Archangel's neurotoxin stun is acting in an unintentional way, they should
1) Confirm the bug
2) Let the community know the bug has been discovered
3) Develop a fix for the bug
4) Roll out the fix
In that order.
The impending Morningstar Life Steal "fix" that's coming was still a mess due to how long the bug existed in the public eye before Kabam addressed it, but at least they followed these steps. With this Timeout "Bug", the issue was confirmed, but never shared with the community. The practice was well-known, so it's not like Kabam was trying to downplay a seldom-used exploit. Instead, they skipped the transparency step and went right into bungling a fix for the "bug".
If there's a bug in the game you're working to fix, there is no downside to letting the players know that you're working on the fix. It let's us know what to expect and shows us that you're actually committed to a culture of open communication.