Відео

Can you explain this in tf2 terms

*Int8 is a data type that represents an 8-bit signed integer, with a range of -128 to 127

what the -128 is happening with the captions?

Are you a model?

why is 128 read as -128?

If the results are 128 or greater it glitches out because 128 or 128< its double its more than 255 which is a limit that appears in killscreens like Pac-Man,any level higher than 255 has the left of the maze glitchy

999д39

hi. I heard you made a crash table. can you please explain it, otherwise I don't understand-at what level is there a chance of getting a crash?

No Video (1440p)

MY MAN DISCOVERED C TYPE!

All i hear was "beep boop beep beep boop". 🤖

1:00 Wait, so it's comparing Decimal 15 to Hex 10? Because Hex 10 is 16, and 15<16. And then in Level 16, 16 is *not* less than 16, so you go to "Hex" 11, or 17. 16<17, so it takes Decimal 110 lines. Because the left 2 digits of the line count are written in Decimal (11), but read as if it's in Hex (Hex 11 is Decimal 17, so it compares *17* to 16, rather than 11). On 19 start, when you reach 140 lines, it takes 14, thinks it's in Hex, so assumes the number is Decimal 20, and 19<20.

I've been curious about this for little while

hes legit i think

The back to back pentris okayyy 😍😍😍

I don’t even know what is this ????

"who" "who what" "who asked" LMFAOOOOOOOOOO

HydrantDude, that's not true cause Scuti crashed the game on level 157.

It's funny how back then tetris's best players made alt accounts and got world records, like Joseph Saelee's 1975TylerP account

these pieces are cursed

“Mom can i play tetris” “No! Go study for your maths” Him:

0:07 How it feels to chew 5 gum:

This does nothing to explain why a single line crashes the game at 155 but not a double. Or why on later levels, a single line does NOT crash the game.

One must imagine Sisyphus happy.

Pentris makes me feel uncomfortable

why does the rebirth screen happen at 255

Why he kinda

Get a jo*cough" ...i mean...good job

Hhhh, h'hhh hh hhĥhh hh hhhhhhh hhhh h'hhhhhhhh ! :'H Hh hhhhhh hĥhh : H >>> Hhhhhh, hhhhhh hh hhhh. 😤 Hh hhhhh hh hh hhhh́h hh HhhhhhhhhHhhh, hh hh hh́hhhhhh hh hhhĥhh ~ :H ✨ Hhhhhhhhhhh hh Hhhhhh !! 🍷🙋‍♀️🥖

What about a Lvl 0 start? Does the 810 line thing also happens ay Lvl 235?

Could you explain the "summoning Satan" glitch in Alex T's first crash?

Watched this at normal speed. Got nothing. Watched it at 0.75x, paused several times, went back 5 seconds a few times to try and understand a few words that I could not understand the first time, got it and loved it. Maybe talk a little bit slower next time? 😁 Thanks a lot for the video!

Was MOD not available to just do Level# MOD 10?

You're smart and you have an insane jawline, hopefully you'll procreate :)

I know this video is 1 year old, but I'm often confused in this video and want to help explain. It's the lack of base conversion or notation. I sometimes don't know when a number is written in base 10 (decimal) or 16 (hexadecimal). There are also not enough examples to explain new concepts. We have to have keen ears to understand what is said word-by-word. For example, when he says "The level written in hex is compared to the top 2 digits of the line count" there are not enough examples. I could provide 2 or 3 examples of converting between "line number as displayed" to "line number as represented in hex" and "line number as converted to decimal": as displayed: "123" as represented: 0x123 as converted to decimal: 1*16^2 + 2*16 + 3 = 291 adding quotes and the 0x notation are important for readability. as displayed: "999" as represented: 0x999 as decimal: 2457 In hexadecimal, numbers go from 0, 1, 2, 3, 4, 5, 6, 7 8, 9, A, B, C, D, E, F, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 1A, 1B, 1C, 1D, 1E, 1F, 20, 21, 22, and so on. Let's see what the game does to keep the numbers in decimal. *[The following might not actually be what happens. There is at least 1 other way to implement this.]* 0x89 is actually 137 in base 10. Adding 1 gives us 138, or 0x8A. But that's now how decimal works! So it pretends to add in decimal. When it sees an A, it zeroes that digit, making 0x80, then tries to add to the next digit: 0x80 + 0x10 is 0x90. That is how it goes from "89" to "90". What about hundreds? 0x399 is actually 921 in base 10. Adding 1 gives us 922, or 0x39A. That's an A! It zeroes that digit, making 0x390, then tries to add to the next digit: 0x390 + 0x10 is 0x3A0. That's another A! It zeroes that digit, making 0x300, then tries to add to the next digit: 0x300 + 0x100 is 0x400. That's how it can go from "399" to "400". What about thousands? 0x999. I won't convert to base 10. Just know that adding 1 makes it 0x99A. Zero the first, 0x990. Add 0x10. 0x9A0. Zero the second, 0x900. Add 0x100. 0xA00. That's another A, right? But the game only displays 3 digits. It doesn't expect the player to reach past 999 and doesn't bother to check the third. So it counts A00, A01, A02, and the first 2 digits continue on in decimal as normal, until it hits A99, at which point adding 1 gives B00. When deciding to level up, the line counter is divided by 0x10 in *hexadecimal*, which basically just takes out the first digit the same way dividing by 10 in base 10 does. Say you were at "120" lines. It's stored as 0x120 hex. 0x120 / 0x10 = 0x12 written in decimal, that would be: 288 / 16 = 18 The math checks out. All three numbers map to each other perfectly. More importantly, 120 lines doesn't give us 12 in decimal. It gives us 0x12, which is 18. To level up from 29, you're supposed to reach 290 lines. But you need not 190, not 290, but 200 lines. At 1:17, he says this is because "1D ... is greater than 19 but less than 20." But this is never illustrated. The best way to illustrate would be to start counting in hexadecimal and decimal at the same time: 0x16 = 22 in decimal. 0x17 = 23 0x18 = 24 0x19 = 25 (This is what happens after the line counter converts "190 lines" to hex and divides by 0x10; it results in 0x19 and is actually the number 25 in memory.) 0x1A = 26 (The line counter never reaches this number as it pretends to be decimal. It would never allow any of the letter digits ABCDEF.) 0x1B = 27 0x1C = 28 0x1D = 29 (This is our level, which the counter just stores directly as 29.) 0x1E = 30 0x1F = 31 0x20 = 32 (This is the result of converting "200 lines" to hex and dividing by 0x10. As you can see, 32 > 29. Therefore 0x20 > 0x1D. Therefore 0x20 > 29 decimal.) 0x21 = 33 0x22 = 34 0x23 = 35 0x24 = 36 0x25 = 37 0x26 = 38 0x27 = 39 0x28 = 40 0x29 = 41 (The result of converting "290 lines" to hex and dividing by 0x10. 41 is Way past the mark.) Furthermore, at 1:45, you say "The top digit of the line count is stored in normal binary" but we can't actually see the binary representation nor can we see how 2300 maps to 1700 or vice versa. Turns out it's really every digit after the smallest 2. So hundreds and thousands and beyond are in hex. He uses 0x1700 as an example. This is the raw number from the line count. Remember: the right 2 digits are pretending to be decimal, while the left ones stay hex. Basically, think of 1700 as (0x17 * 100 decimal) + (00 decimal). 0x17 is 23 decimal, times 100 is 2300, + 00 is still 2300. At 2:07 he says that 0x00-0x7F are positive, 0x80-0xFF are negative. going from 0x00 to 0xFF, you count in binary from 0b00000000 to 0b11111111. 0x7F in binary is exactly 0b01111111, the largest number that starts with a 0 in 8 bit binary. This is 127 decimal. 0x80 is exactly 0b10000000. The top bit is 1, so it's considered negative. Anything larger than that will still have a 1 for its top bit all the way to 0xFF, or 0b11111111, or 255 decimal, or negative one. Basically, if the second hex digit is 8 or larger, like 0x80 or 0x92 or 0xA3 or whatever, it's negative. 0 - 1 gives you 255 because of wraparound. 255 + 1 gives you 0. So, 255 must equal -1. 254 is -2, 253 is -3, all the way to 128 which is -128. I don't understand why he used 0xEA - 0x69 = 0x81 as an example. I could also say 0xEA - 0x68 = 0x82, which is also negative. Maybe it's because he'd been levelling every 10 lines for the past couple levels? As for 0xEB - 0xF0 = 0xFB, the smallest number that would result in a negative would actually be 0xEB - 0xEC = 0xFF, but you'd need a line counter of 0x1EC0, and the second digit skips over ABCDEF, so that's why you use the next best, which is 0x1F00. The previous possible line count is 0x1E99. 0xEB - 0xE9 = 0x02, positive. These stuff could be visualized better, but unfortunately just like the original video, it takes time to plan out how to explain these concepts to the layman.

Can you do the glitch from Thatches' crash? The one called "summoning"?

Your little drawings are so cute🥺

and now its reached HUMANLY!

Nice. 👌

this guy started trying gg

He can't just explain very well, he can also play very well :)

gg!

Is this a new world record ? I'm confused

GG! Those tetrises on 29 showed a lot of confidence.

Bro the next box💀

There’s a B on the rocket screen. Blasphemy

Pretty good job with your notes despite one error! I too think the carry flag could've been used instead because the code is dealing with unsigned bytes.

Not to mention, level 235 on an 18 start is CHARCOAL.

Alternative title: Tetris in Ohio be like: