Here’s the thing with roadmaps. Developers can set all the goals they want, but they rarely account for bugs, feedback, balancing, and other disruptions. This is less of a case that the roadmap said what it said, and more that it was left up/unmodified after disruptions occurred.
It’s all too common for developers of anything to not admit that things aren’t going as planned, probably because whenever you see news about delays or change of plans people take dumps all over them. Damned if you do, damned if you don’t.
2 Likes
Yep, those are inconsistent. But it was also pretty clear I was commenting on the stuff you shared above that, since . . . you were sharing it as an example.
These are literally the same quotes cut in half.
Oh, haha. Yeah, I’m pretty sleepy. I realize you added the (Early March) part, just indicating when they said that, it wasn’t them saying that.
I guess what I said is all still true, then. And just goes to show; if you selectively use partial quotes, you can change the meaning of a sentence.
Anyway; it’s not like I’d not want content sooner. But a careful reading of what they did say, you can tell they left themselves loopholes. Still sucks, but issues have cropped up since then that put the roadmap - which showed what they would like/hope to do - off. This isn’t about letting anyone “off the hook”. Just reading comprehension.
I think it’s pretty discouraging to work on fixing your mistakes and then get called out for the mistakes you haven’t yet fixed.
I believe 1.08 was a huge step, fixing a lot of map problems and (at least on average) slightly improving performance, and 1.081 was better received despite being some rather easy balancing changes and minor fixes;
Goes to show that communication would actually help here, as I still don’t know of all the changes 1.08 brought.
1 Like
No one is trying to discourage the devs. We’re just pointing out their mistakes, to make sure they notice them, fix them and will not repeat them again. That’s what called FEEDBACK.
2 Likes