Mojang has changed combat forever lol (Snapshot bug) 

​@@Tiger10002 skill issue

​@@Tiger10002L don't care kid

@@Tiger10002womp womp

​@@Prismitten.?

​@@melonguy90 nah that's wild 😂😂😂

hey, you.. wake up

@@Tiger10002what is bro yapping about

​@@Tiger10002know your place, go back to the colbalt mines and work until you collapse from exhaustion.

@@Tiger10002womp womp

@@Tiger10002 womp womp

Lol, i feel that one.

@@Tiger10002don’t care😊

Meh, what a [not sharp] quote. When someone break you well enough you get totalled.

​@@Tiger10002 maybe a scam somewhere else kid?

@@Tiger10002Who cares? Go spam this shit somewhere else.

Mojang cooked and we got food poisoning.

that's Ohio fr ​@@DominusQuadra

They didn't cook they burned

I am pretty sure thats a bug, they only meant to change pickaxes, shovels and hoes as indicated in the changelog where they used the word "tools" And not "weapons"

​@@Tiger10002 😴

@@Tiger10002 That's such a sad story, bro...

​@@Tiger10002skill issue

Maybe cuz your content is trash and no one would click on it. Begging for views wont get you a real audience, you gotta put some effort into the content@@Tiger10002

on top of that, you have fake subscribers... Ain't no way your content is gonna get pushed to someone's recommendations. @@Tiger10002

@@christophsiebert1213don’t believe it prob either a bot or some guy cos they’re just copy and pasting it on every thread

Is that a jojo reference

bites the gunpowder

Is the wolf's name Kira Yoshikage?

@@landocalrissian. nah, his name is Hayato

Killer Queen Daisen no Bakudan Bites Za Dusto!

Combat’s about the get FAR more hilarious. I honestly wouldn’t be opposed to making tools of a similar tier do similar kinds of damage, because you could in theory use all of these things as weapons. It is pretty baffling that they would make tools of completely different materials do the same amount of damage.

@@foxpokemonforever4775 I'm pretty sure its a bug, no way they actually think this is a good idea

lethal company

Wooden Hoe

yes

Fr *Moyang* should definitely make up their mind

yea, if not gold swords (the worst tipe) are going to be meta in pvp because the have the highest echantability

they have terrible durability though, I wonder if the meta will evolve to include an inventory full @@user-ws9lg4ir6h

Me Yahng

yes dogs

Okie Dokie

WOOF WOOF

NO YOU DONT

dogz

oh hey, it's Ethyriel

Terrarian: defeats literal moon lord Also terrarian: dies of chest

@@UnknownZYX_4085Hello! o/

THEY NEED TO COOK MOREE I wanna be full

They are actually making important changes instead of making a bunch of small unimportant ones

@@Nuclear_energy_enjoyer Despite how much I love them, mob variants are honestly small and unimportant changes/additions imo

Hell yeah, now there's more colors of wolf for me to completely ignore.

Wtf is Mojang? I only know Moyang.

it just works! :)

One, Java doesn't have unsigned data types built-in (well they added a way to treat an int as unsigned in Java 8, but it's hard to use and requires using the Integer class, which entails extra overhead), so that's a non-option for Minecraft. Two, even for languages which have built-in unsigned integer datatypes, such as C, C++, or C#, we still prefer to use signed ints unless there is a good reason not to (and preventing negative numbers is not considered a good reason). The core language features are generally implemented with 32-bit integers in mind, and it tends to be more work to try to use unsigned integers with very little gain. Beyond that, the problem with negative numbers is usually in the process that creates them, and you'd need to guard against such a situation regardless of data type. E.g., if you have two values A and B, you could compute (A-B) to get some value. If you are working with signed integers, that value may be negative, if you are working with unsigned integers, that value may be very large due to an underflow. In both cases, it could cause unintended behavior, so regardless of the data type, you'd need to guard against performing this operation. It's not very often that using an unsigned integer actually protects you any better than a signed integer.

@@NellyHumanthe first sentence is a fun fact. The rest I wholeheartedly disagree but you're entitled to your opinion. Never heard of such an opinion before in 21 years of computer science, and you're acting like it's normal, but you're definitely entitled to it. First time I've ever heard of it being more work to use unsigned integers lmao.

​@@TRDiscordian I don't think that I can leave links here, but you can find a lot of discussion online about why people prefer against unsigned integers, and this reasoning is not found only in my RU-vid comment. A prominent example would be in Google's style guide for development which advises against using unsigned integers except in situations where the extra positive range is needed or you intend to twiddle bits. One thing that I will say is that it is more work to use unsigned ints, but not arduously so. It's more of a case of, "why add the extra effort?" It may be that my career has been spent primarily in C# and .NET, and the standard library is exclusively signed (unless you're dealing with externs), so using unsigned ints tends to cause a lot of typecasting when working with the standard library. When the data type is changing, you should be ensuring that it won't be introducing new errors. The other aspect of "more work" is that the same logical error can be harder to spot with unsigned integers. Regardless of whether your variables are signed or unsigned, it will always be possible to write code that subtracts a large number from a small number. For signed integers, a negative value is returned. For unsigned, a very large value is returned. It's much easier to implement a guard that checks for negative numbers and throws an error when one is encountered than it is for checking for very large numbers. The boundary between negative and nonnegative is always 0. The boundary between expected and unexpectedly large is somewhere in the positive end of the range, to be determined by the developer.

@@NellyHuman Where the fuck have you been working where uints are not the default? Also, under and overflows are a problem SPECIFICALLY on signed integers. For unsigned integers, it's simply a buffer overflow.

Likely forgot to change the values of the damage and attack speed when migrating every tool to the new system

In real life getting hit by a hoe, showel or axe is lethal in way way, so props to moYang for being realistic

They fixed it they just released 24w10a and it fixes the damage

@@dashybois I really hope that that is the reason, and not a bad combat update.

@@StinginShadow thanks for the info!

Damn 💀

Its just a bug why is everyone acting like they changed combat forever lol (the thumbnail and title are kinda clickbait) they would def have said something like "oh btw all your swords are useless now"

Dude it's a bug not the end of the world And that update was an april fools

​@@LineOfThy Upd isnt an "april fools", it's a bug It's not even April fools either

@@mudafucca4420 You completely misinterpreted my comment

​@@daniiii888 the OP said that it has to be something gone wrong with the snapshot

People are dumb sometimes

people want to find reasons to complain about mojang

​@@PenguingotPeople are dumb MOST of the time

i am slightly stupid

They are young

​@@Tiger10002well ain't that such a sad story because now I'm dying of laughter

@@Tiger10002you play pretty bad lmao

@@Tiger10002 L bozo

@@Tiger10002 My mother left us My father tried to unalive himself 2 times infront of me We have a really high problem financially and more XD

@@Tiger10002skill issue

@@Tiger10002 That's such a sad story, bro...

why don't you stop using dominant weapons and come here to dominate me by yourself?

@@christophsiebert1213 it's also such a fake story

@@Tiger10002 get ur money up

because I needed the shovel to do the same amount of damage as the sword lol

Same

Bites the dust

It's like paying 10000 dollars for a skin You spend time finding resources to obtain something worthless

And its ugly too so now completely useless 🙃

@@MDE_never_dies Stop being netheritist, if anything the turqoise hue of Diamond is ugly

@@cataclysmi Blue Power 💎✊🏻

@@MDE_never_dies That's it. I'm going to say the diamond slur.

But why

@@atorik1076 Reference to a film called Shaun of the Dead. Good film, would recommend. It is a comedy-zombie movie.

y/lostyoutubers yes, its an r/lostredditors parody.

Maybe we could have underground heart crystals too? When you break them and use them your maximum health goes up by 2, permanently in the world, even after death - but you can only use them 15 times, capping out at 50 health

what the Terraria

No

Bedrock has actually been deleted and today it has been replaced with diamond edition for the ps2.

i’d assume so.

​@@Prawn-fish I'd prefer that tbh

bedrock and java are completely seperate games

Crit spam be like:

1.9:

No? Minecraft autosaves every few minutes, or when the game is paused. The autosave fails when it reaches the negative damage tag, so it fails to save and crashes. The game then loads the most recent successful save, which is the one before the failed save. That's why rollbacks happen, there is no "memory eater" or whatever you're talking about in this bug.

@@kingacrisius by "memory eater" i mean as for example like tnt. Tons of it, that blow up, they need a lot of computing, so the game crashes, same here i presume. Auto saves can be disabled and also, it appeared as if almost instantly after the "memory leak bug" the game crashed, and multiple times, meaning it couldn't be everytime autosave.

@@alexdefoc6919 Bro it's when the autosave happens after you have performed the bug. I.e. when there exists an item with negative damage. Once such an item exists, the next autosave fails and the game crashes.

@@kingacrisius Sry then. I am mostly a C/C++ dev. Not a java one, which has a garbage collector for memory leaks.

​@@alexdefoc6919why would a signed integer underflow lead to a memory leak?

Now it only has to work as good as NBT's did before. Then it can start being better.

I am so scared... I made an entire map with nbt and stuff (not finished) and now they're gonna remove it? Hopefully it doesnt delete my custom items.

@@daniiii888 just don't update it then.

Oh you sweet summer child You could do all of this with NBT already, and quite painlessly to boot

@@GreyMaria (custom recipes go brrrr)

spam m1

nukes in minecraft

You can't do it in survival, yes, but 1) you can do it without cheating, so this is a real problem 2) the problem is just the fact that there exists a way to make an item with such contents that it crashes the game wich is a problem in itself, but also shows that the contents part of the game is still very undercooked and need further development

​@@user-tc4hi7dn1qWithout commanding* Remember, cheating was removed from the game. :P

@@DarkonFullPower yes, it was removed, wich means you can get this wolf armor without cheats Tis da joke

Reducing crashes and potential for crashes in software is probably a good thing, especially when if this bug just goes through, it means map makers can easily create mobs that will crash your game when you interact with them.

​@user-tc4hi7dn1q but its a snapshot, the whole point is to find bugs and test things. They can probably easily fix this

ur so funny 😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂 please kill me

bark

bc he needed content for today and was grasping at straws

Instead they're making unnecessary changes to fundamental systems and breaking even more things! I love new minecraft!

It's a snapshot, it doesn't even matter if the game launches or not. And bugs are fun to explore.

the game is crashing? that's the whole POINT of a snapshot bro

It's like you people just forgot that it's a snapshot two minutes after learning it's a snapshot.

yall saying this shit are very dumb lmao

There's probably a better pun for it

Nah, the crash occurs when the game tries to save. When you open the pause menu the world immediately autosaves, which causes the crash. Hitting save and quit would just cause the game to try and save again, causing the crash.

Even if it somehow bypassed the crash, which it wouldn't, it still wouldn't save and would rollback your world just like it did here.

that's the intention. the snapshots are there practically just so these bugs can get fixed

minecraft fans when the test updates are in unfinished 😦

@@jojomicheldu59: Considering I complained about someone gatekeeping older versions of Minecraft, I might edit my original comment to sound more civil.

(Another reason is also because of the lack of Optifine.)

Didn't they just fix it in 24w10a

?