Lobby

@lobbylc.bsky.social

39 Followers 30 Following

he/him • profile picture by Mastereloading • https://lobbylc.com

A screenshot of a document that reads: While I don’t necessarily believe you’re wrong, there is a difference between “someone’s” (one person’s) workflow, and a lot of people’s workflow. Let’s be clear, this is not a me-thing - any players interested in bridging, parkour, or even PVP, will be drastically affected by these changes. One of the main issues for me personally isn’t that the bug is being fixed, but that it’ll create even more of a divide in the multiplayer space. Similarly to how 1.8.9 is still a primary version for PVP, 1.21.1 will very likely now become another persistent version for players who are affected by these changes, which really sucks. If the bug had been discovered maybe a few months ago, I could understand, but years have passed. Players have learned to utilise it, coming up with so many unique mechanics, which even Mojang won’t be able to undo now. After this amount of time, you simply have to find a middle ground, because sure, while a bug is a bug at the end of the day, it should have been resolved before it became a key mechanic in so many different aspects of the game. It really doesn’t matter now whether they intended it or not, because as far as the affected players are concerned, it’s a part of the game, and over 7000 people already agree. Your perspective on the matter is that bugs can never become features, and every bug must eventually be fixed, even if fixing said bug will have an overall negative impact. My perspective is that bugs can shape features, and while some things may not originally be intended, they end up making for a much more enjoyable experience. Anyhow, to be clear, I haven’t once called Mojang lazy, but I can’t say I’m too shocked when people do. If you were to ask me, I’d say the issue lies in their frequent refusal to take player feedback into consideration. If you want the community to be pleased, you gotta be prepared to please the community, and, well, Mojang aren’t.
A screenshot of a document that reads: If your opinion is that any bug fix is a good bug fix, I suppose that's fair enough, but I would have to respectfully disagree. I do agree that the fact it didn’t get fixed for so long is more of a problem than the fact it’s getting fixed at all, but that doesn’t change how it feels as though such little thought went into the decision. Even if the original movement wasn’t intended, because it’s been a part of the game for such a long time, players have learned to like it. That doesn’t necessarily mean it should absolutely never be changed, but it does mean a little more care and effort needs to go into ensuring that any changes won’t have a negative impact. What I’m saying is if Mojang fixed movement in such a way that didn’t cause even more issues than we started with, I wouldn’t particularly mind, in fact, that would be great, but in my opinion, breaking so many other (debatably more important) mechanics to resolve one small issue isn't really fixing anything.