Raycasting Through Slabs, Stairs, and More! 

i tried to do this too but gave up on the stairs bc of the many variants. your system is also way more efficient so thank you for that :D

You're a life-saver! Luckily I did all the blocks that can't use your system either way first 👀 Would've been painful otherwise

THANK YOU SO MUCH FOR THIS!!! Was super hesitant to even start a bunch of packs I wanted to make that required being able to detect *exactly* what block a player was looking at (same result as F3's "looking at:") when they used an item - since I knew it meant having to account for every possible orientation and state of every non-full-block model to make exceptions for, which I thought would be way too involved for what's only meant to be a simple function... but the transformation matrices solution and how you've ordered the checks to minimize the total number of block checks is a stroke of genius.

Oh I remember really wanting to know this!

Using the rotation matrixes is a GENIUS idea!

When you said doors, I thought you were gonna do something interesting, like fire through the holes on an oak door, or an acacia door. I never even realised if the door was open or not!

This is absolutely amazing! Never thought I'd see transformation matrices outside school! I don't know wheather this makes sense, but I've just had an idea how to make this even more percise. If you could dynamically adjust the step size somehow, you'd be able to do your normal raycast at a stepsize of like .5, but as soon as it enters one of your partial blocks, it steps back by .5 and then continues with a stepsize of .1 for the next one block. This way, you could reduce the load (because the small step size is not really needed when just figuring out what block the ray is in) but keep all the percision (because it knows exactly where it is inside the block if it really matters). Because everything is happening in one tick anyways, the different speeds wouldn't matter. But I don't know if the additional logic for such a system would maybe produce more load than is saved by the larger average stepsize... Anyway, great video and a really creative solution!

Thank you! I have been trying to figure this out for a while!

I used a very similar method when I made my video a couple years ago on this. However, instead of storing the decimal version of the block, I just used 16 as the multiplier and modulus operations. That way the values were pixel perfect and super easy for me to mentally map and figure out. Of course that's assuming you stayed with 16x16 models and weren't doing something fancy with custom models. I also set my step size to be 1/16th of a block as well, which might not be efficient, but it got really nice feeling hitboxes for my maps.

I love your videos so much bc theyre (at least somewhat) easy to understand, you dont seem to leave anything out and I always get a million more ideas of wha to code after watching them (and you also just seem to be a rly nice guy) thats why I come to you with my dilemma: I have so many ideas for stuff, its only ever increasing and I think its getting to a point where modding would just make more sense. but I already sank months into learning the datapack stuff and working on one and I feel like switching to modding now would waste that (I know that all the textures and ideas wont go to waste, but still) what should I do

This is just beautiful

very nice

There's one kind of raycasting that doesn't require you to account for weirdly shaped blocks, looking_at predicates already account for line of site through the blocks actual hitbox, so you can iteratively tp a hitbox (i use a tagged invisible nogravity arrow) away from the player until predicate looking_at is false, idk why its not a more common method bcs its almost as simple, its best for short distances since it requires the player to keep looking during the milliseconds that it takes to find a block that'll obstruct line of sight, but still very underated

Is it just me or are you slowly getting more and more blue

I just realized that I actually understood the contents of this video I just realized that I actually spoke way too soon

wait so, can you explain this to me for the stairs, why would you set the #bool score to 0 if the stair type is top? wouldnt it just completely erase all the previous checks? Like if it is top it won't set the .itt to 0 right? or does it do something else which makes it remember the previous stuff?

Amazing work, good job ! I am myself making a minecraft Zelda like, I guess you’re pretty busy with all your plans. In case you’re willing to work on a project or do you know anyone who’s available to work on a new project? I really need some help 😅 Thank you !

Now try doing bamboo

First XD

why am i watching this?