Read moreWe understand that much, it’s just the obstinace that comes with how, imo, particularly YaW responded to criticism. Everyone’s reaction, when you unveiled the feature a month ago, was “ew no I hate that” and you guys got criticism then on it beinf too jarring, too quick, affecting battle.
You seem to have made no changes to the feature in response to THAT feedback. Why should we have faith you will now it’s released? You were told it would make people motionsick a month ago, made no changes, and then were shocked in the discord when people told you they LITERALLY have to QUIT the game because it makes them too sick now to play it.
When you were told how bad it was a month ago, you should have either: - Delayed the feature until it was improves - Added an option to disable it until it was improved, or just give us that option anyway.
Instead you shipped it as is, having already ignored the feedback. Surely you can understand why people are, matter of factly,...
We can't make any changes to features until we publish a patch. Patch 1.2.1 was sent to platform holder for review two weeks ago, but they're still on it, and with the holiday period in-between, they'll take more time than usual.
We can't delay a feature that's already been shipped and in the patch, and the feedback came after it had been shipped and was in the patch. Any change, even adding an option to disable them, requires a new patch, and a patch requires certification.
Like I said, we've already made a lot of changes to them internally following your feedback, now it's only a matter of us being able to launch the patch and have it reach you folks.