Fire now has a knockback effect that is always in a TOTALLY RANDOM direction. Because the direction is completely random, there is no way to predict which way it sends you when you need to hit someone, so you are unable to hit someone while on fire. This will probably turn high level pvp (where everyone has fire aspect) into a random crapshoot that is dependant on who gets more luck with the fire knockback.
I was under the impression this was a bug, but maybe it is intentional. When I a bunch of burning mobs hopping up and down frantically like they on a pogo-stick, it looks so stupid it must be bug. If it is intentional, what were the developers thinking?
Rollback Post to RevisionRollBack
Let me know if my posts are helpful or if you like them. That's what I'm here for.
I am currently lurking more than I am posting. I haven't gone anywhere.
I'd imagine that if this isn't a bug, that its most likely going to be tweaked back to what it was. It might have been just a "lets see how this works" type of change, just to experiment with something new.
No mincing words from me. Seriously. None. This god forsaken "change" is either a bug, or simply the dumbest decision Mojang has ever made. All it does is turn damage into the most annoying and unfair thing ever. It's literally worse than getting stunned in Spelunky. I just watched a video of a let's player trying to drop onto a Nether Fortress to get her stuff back, and she landed high enough to not take a lethal amount of fall damage, where normally she could just stand there and then climb down a bit. One tiny little problem with that, though. The game seemed to think she didn't deserve to live, so it made her hop slightly, sent her flying off the edge, and made her die in the lava.
All because literally EVERYTHING that damages you in this snapshot will make you do a small bunny hop. Apparently because getting hurt by some purely non-physical force is exactly the same as being hit by a knockback sword.
This better be a bug. This BETTER be a bug. Because if they keep this god forsaken feature in, I will straight up not play 1.9 until the knockback is gone.
Rollback Post to RevisionRollBack
So I was working on this really cool resource pack a while ago, but bad progress nonwithstanding, I think I found something much better... I'm probably gonna never release another custom Minecraft map.Until we meet again...
No mincing words from me. Seriously. None. This god forsaken "change" is either a bug, or simply the dumbest decision Mojang has ever made. All it does is turn damage into the most annoying and unfair thing ever. It's literally worse than getting stunned in Spelunky. I just watched a video of a let's player trying to drop onto a Nether Fortress to get her stuff back, and she landed high enough to not take a lethal amount of fall damage, where normally she could just stand there and then climb down a bit. One tiny little problem with that, though. The game seemed to think she didn't deserve to live, so it made her hop slightly, sent her flying off the edge, and made her die in the lava.
All because literally EVERYTHING that damages you in this snapshot will make you do a small bunny hop. Apparently because getting hurt by some purely non-physical force is exactly the same as being hit by a knockback sword.
This better be a bug. This BETTER be a bug. Because if they keep this god forsaken feature in, I will straight up not play 1.9 until the knockback is gone.
Of course I'm going to move on, I was angry because there was a bug, not because there always will be. Do you think I'm still retroactively angry about every temporary bad thing that showed up and showed itself out?
Rollback Post to RevisionRollBack
So I was working on this really cool resource pack a while ago, but bad progress nonwithstanding, I think I found something much better... I'm probably gonna never release another custom Minecraft map.Until we meet again...
What don't people like you get? The team at Mojang stated before releasing the Snapshots "Features in snapshots are not final, and may seem a bit op, they will be changed in the full release of Minecraft 1.9" (Not the exact words) So this will most likely be changed in either future 1.9 Snapshots or in the full release of 1.9.
Listen, people.. LISTEN!
I'm pretty sure more than 90% of this thread is already acutely aware of the fact that it's a bug and it's going to be removed.
Rollback Post to RevisionRollBack
So I was working on this really cool resource pack a while ago, but bad progress nonwithstanding, I think I found something much better... I'm probably gonna never release another custom Minecraft map.Until we meet again...
So I was working on this really cool resource pack a while ago, but bad progress nonwithstanding, I think I found something much better... I'm probably gonna never release another custom Minecraft map.Until we meet again...
Fire now has a knockback effect that is always in a TOTALLY RANDOM direction. Because the direction is completely random, there is no way to predict which way it sends you when you need to hit someone, so you are unable to hit someone while on fire. This will probably turn high level pvp (where everyone has fire aspect) into a random crapshoot that is dependant on who gets more luck with the fire knockback.
I was under the impression this was a bug, but maybe it is intentional. When I a bunch of burning mobs hopping up and down frantically like they on a pogo-stick, it looks so stupid it must be bug. If it is intentional, what were the developers thinking?
I'd imagine that if this isn't a bug, that its most likely going to be tweaked back to what it was. It might have been just a "lets see how this works" type of change, just to experiment with something new.
It's been reported as a bug and is fixed for the next snapshot (an attempted bugfix that was reverted).
No mincing words from me. Seriously. None. This god forsaken "change" is either a bug, or simply the dumbest decision Mojang has ever made. All it does is turn damage into the most annoying and unfair thing ever. It's literally worse than getting stunned in Spelunky. I just watched a video of a let's player trying to drop onto a Nether Fortress to get her stuff back, and she landed high enough to not take a lethal amount of fall damage, where normally she could just stand there and then climb down a bit. One tiny little problem with that, though. The game seemed to think she didn't deserve to live, so it made her hop slightly, sent her flying off the edge, and made her die in the lava.
All because literally EVERYTHING that damages you in this snapshot will make you do a small bunny hop. Apparently because getting hurt by some purely non-physical force is exactly the same as being hit by a knockback sword.
This better be a bug. This BETTER be a bug. Because if they keep this god forsaken feature in, I will straight up not play 1.9 until the knockback is gone.
So I was working on this really cool resource pack a while ago, but bad progress nonwithstanding, I think I found something much better... I'm probably gonna never release another custom Minecraft map. Until we meet again...
That's part of the fun of the snapshots - trying to figure out if you've stumbled upon a feature or a bug....
Either way if it seems negative enough it'll get fixed.
All damages will now have knockback.
It's a bug. It was fixed. Move on.
Of course I'm going to move on, I was angry because there was a bug, not because there always will be. Do you think I'm still retroactively angry about every temporary bad thing that showed up and showed itself out?
So I was working on this really cool resource pack a while ago, but bad progress nonwithstanding, I think I found something much better... I'm probably gonna never release another custom Minecraft map. Until we meet again...
Guys it's not intentional, downgrade to 15w51b and then re upgrade to 16w02a and it won't be there, I tested it.
I'm pretty sure more than 90% of this thread is already acutely aware of the fact that it's a bug and it's going to be removed.
So I was working on this really cool resource pack a while ago, but bad progress nonwithstanding, I think I found something much better... I'm probably gonna never release another custom Minecraft map. Until we meet again...
Must be a bug...
Aspiring Youtuber and mod creator!!!
It's going to be fixed soon.
Alright then.
So I was working on this really cool resource pack a while ago, but bad progress nonwithstanding, I think I found something much better... I'm probably gonna never release another custom Minecraft map. Until we meet again...