GroundedWisdom wrote: » They listened to feedback. That doesn't mean they could stop everything. They had to gather data to make adjustments. Once things are set in place, you wouldn't really find a total rollback. History shows this. They take the feedback as the data as apply it to the template implemented.
mostlyharmlessn wrote: » GroundedWisdom wrote: » They listened to feedback. That doesn't mean they could stop everything. They had to gather data to make adjustments. Once things are set in place, you wouldn't really find a total rollback. History shows this. They take the feedback as the data as apply it to the template implemented. Had they listened they would never have pushed the server side update for AQ. Had it been a client side update that would be a different story, there's a lot more moving parts and dealing with the play/app stores. It makes me cring that there's no roll back plan for any software updates or a way to block a push to production. That's just dangerous development practices, but I digress.
GroundedWisdom wrote: » mostlyharmlessn wrote: » GroundedWisdom wrote: » They listened to feedback. That doesn't mean they could stop everything. They had to gather data to make adjustments. Once things are set in place, you wouldn't really find a total rollback. History shows this. They take the feedback as the data as apply it to the template implemented. Had they listened they would never have pushed the server side update for AQ. Had it been a client side update that would be a different story, there's a lot more moving parts and dealing with the play/app stores. It makes me cring that there's no roll back plan for any software updates or a way to block a push to production. That's just dangerous development practices, but I digress. Their intentions weren't to have it as difficult. There was no way for us to gauge that until it went live.
Snizzbar wrote: » Lol no I'm not. I'm validating what we all said BEFORE the AQ. We said they'd be harder. The mods said they wouldn't. They were harder. Now they're not. Is English not your native tongue?
GroundedWisdom wrote: » You're asserting they planned it and you have no basis for that.
Snizzbar wrote: » GroundedWisdom wrote: » You're asserting they planned it and you have no basis for that. Who said that? All we're saying is that we knew the sentinels would be harder to fight. No one mentioned a plan except you. From my point of view, what the devs did was the very worst sort of unplanned changes with very predictable consequences. Predictable to everyone except the devs themselves. How hard is that to understand?
SomeoneElse wrote: » Wrong. You can read the descriptions and easily determine that the challenge will be more difficult. They are designed to adapt to repetitive actions, something no other character in the game has done so far. Each type has countermeasures built in that must taken into account. It is much more difficult than the simple symboids. Anyone should be able to figure that out without any data collection. They fully intended the make AQ more difficult for us without increasing the rewards. It was a bad decision, and they went way too far. The backlash is completely warranted.
GroundedWisdom wrote: » "They fully intended to make AQ more difficult for us without increasing the rewards." Care to point out how I misrepresented that? You made the comment. I'm sure you're fully aware of what you were implying.
Kromestone wrote: » GroundedWisdom wrote: » "They fully intended to make AQ more difficult for us without increasing the rewards." Care to point out how I misrepresented that? You made the comment. I'm sure you're fully aware of what you were implying. The reason kabam listened and changed their stance was because, the backlash was massive and people weren't interested in playing AQ any more and their intended game plan of milking the player base was failing, simple.
GroundedWisdom wrote: » mostlyharmlessn wrote: » GroundedWisdom wrote: » They listened to feedback. That doesn't mean they could stop everything. They had to gather data to make adjustments. Once things are set in place, you wouldn't really find a total rollback. History shows this. They take the feedback as the data as apply it to the template implemented. Had they listened they would never have pushed the server side update for AQ. Had it been a client side update that would be a different story, there's a lot more moving parts and dealing with the play/app stores. It makes me cring that there's no roll back plan for any software updates or a way to block a push to production. That's just dangerous development practices, but I digress. There's a difference between taking in feedback and obeying orders. They haven't removed Sentinels. They're adjusting them. Their intentions weren't to have it as difficult. There was no way for us to gauge that until it went live. They're making adjustments to be closer to what they wanted.