anonymous2342
- Telinc1
- telinc1
- Europe/Stockholm
- Yes
- No
In my opinion, auto-jump should make you jump if you can manually do it. In this case, I think it should work with both carpets and snow because you can make that jump yourself.
So just because it doesn't make sense (Minecraft in general doesn't make sense), you fixed one of the most useful "features" ever. It made so many more things possible and everything it broke could be adjusted for it.
Instead of letting us have incredibly fast transportation, you'd rather make players AFK in minecarts for 10 minutes.
Instead of keeping in easy to make elevators, you leave us with slower slime block elevators or manual elevators.
By getting rid of translocation, you're not going to fix clever mob farm designs. They'll just become laggier.
And besides, this ticket talks about mobs in front of or on the side of block 36 getting pulled through, which is even in my opinion weird. By keeping translocation for mobs which are inside of block 36 (in the piston arm), you'd fix crushers and practically everything else translocation broke while still leaving in useful gadgets like elevators. Or even better, make a separate translocation piston block.
Quasi-connectivity turned out useful and you kept it. Translocation is arguably even more useful, especially now that observers are in the game.
If the Minecraft community ever dies, the game will die along with it. In this case, it wouldn't be hard to give us the best of both worlds, just like Jeb did with fixing hopper item duplication (hopper timers are really consistent in the newest snapshot).
anonymous2342 You didn't understand that, "making sense or not" is not the main issue here, it is that it was a BUG.
All bugs will be removed some day, intentional via bugfixing them, or unintentional, by fixing other bugs or implementing new code which might automatically fix bugs such as this one.
I "love" how guys like you list some accusations first and then are like "but hey pls add a block which does the same, kthxbye".
If you want to have something from someone, package your arguments why it is a loss for the tech community in words which are not accusatory but explanatory.
| Quasi-connectivity turned out useful and you kept it. |
Wrong. I was one of the people who tried to convince Microsoft/Mojang to give the JAVA-MCPC-community a replacement for Quasi-Connectivity if they'd fix that bug.
YES it is a BUG.
And from how I see how they "tick", it seems rather that they couldn't find a way to give us a proper replacement for QC yet, so they left it in currently.
Whole Redstone system needs a lot of fixing, it works different from PE/WIN10 and will need some time until it is fixed and some sort of "feature parity" will be achieved.
Until then QC might still be in the game, but I would make bets anytime that it'll be fixed one day, one way or another, intentional fix, or automatically when the code is squeaky-clean.
Or maybe everyone will have gone to the PE/WIN10-version then so MS can simply shut down JAVA, who knows?
The Minecraft community will never die, as you overdramatizingly say it. At the very least not PE and anything educational-related.
The Java-tech-community might be more "tamed" or not as "innovative", and thin out/we might become less in number, yes, but let's face it:
We are only a comparably small group which Microsoft does not need to take care of really, no matter how many influencable YTers are out there with their creations.
In order to survive as YTers they will just follow what MS lays as a path and go with it.
So, maybe we Java-techies will die out one day, yes, but do you really think it's a concern for them if we're not their target group after all?
But I don't really think we will "die out", it's just that the contraptions will change. Not as mind-blowing and breathtaking anymore maybe, but still very useful and "clean", surely.
The majority of players are fine with comparably mediocre tech stuff or just want to play a minigame, and, being a business, MS will surely rather please its target audience, which we are surely not, I'd say.
We have to see MS as business company and act accordingly.
So all we can do is to try to make them understand that we are a crazy but lovable bunch who wants to show innovation and make this game more fun.
We have to convince them to give us additions into the game via clean code (not via bugs) that can also be implemented into the other platforms for feature parity.
But we surely cannot get there by making accusations.
We need arguments that are mature and appeal to their business sense.
As much as I understand you and everyone else (and yes, I do, or I wouldn't care as much about QC and everything related to MC Tech etc. and also talk against some Devs' decisions), it is not as you were not being warned since this bug was occurring, that it might vanish one day again.
Confirmed in 14w32d.
I'm 99.9% sure that's intended.
In my opinion, auto-jump should make you jump if you can manually do it. In this case, I think it should work with both carpets and snow because you can make that jump yourself.