As Requested by a Dev: A Thread about Devs' Actions/Inactions

While it may come as a surprise to some players, especially the newest among us, this is not a new stance when it comes to how this Company communicates and/or treats its customers: a perfectly usable weapon that wasn’t breaking anything and was fun (and useful) particularly for newer players to try to extend their reach, gets messed with for no justifiable reason.

Customers who have been around long enough did see some of it coming, since it’s not a new pattern:

While the final implementation remains to be seen once they are done revisiting their flawed Lycanthropy code, it is important to remember how much of this could have (once again) been avoided if anyone was actually listening to the customers that warned about the bug (and narrowed it down) days before the Green GvG day was upon us (queue “it’s not our fault if it happens during weekend/holiday” tirade), and duly prioritized customer satisfaction.

It is well documented in this forum how there’s often a claim that they’re overworked/have other priorities and therefore can’t always be on top of things…

…and yet among all the Lycanthropy feedback and discontent, we get this:

While it is a common stance to blame solely the Publisher and sometimes the Developer, each customer can evaluate the above facts to determine Responsibility (and lack thereof) accordingly.
:blush: :vulcan_salute:

6 Likes