yes defenetly, thanks for stopping by 💪

aw man

That's actually how the creeper was originally made. Notch accidentally messed up the pig model which gave him the inspiration for the creeper

totally agreed but I'm lazy 😭😂💀

@@lowlevelgamedev9330 I mean, which programmer is not lazy 🤷‍♂️

@@lowlevelgamedev9330I mean, which programmer is not lazy? 🤷‍♂️

@@knitnatsnokprogramming true true. Dani,

​@@lowlevelgamedev9330 that's me with my current project with a database system I'm doing entirely from scratch, some days I'm lazy some days I'm productive as hell 😂😂

I'm too lazy to answer in detail in text to all of this so I will say that it compiles in like 2 secconds rn (I use glm that is already more heavily templated than what I will ever do) and adding a scripting language means that you need to make a binding for it, adding all sorts of problems, with no benefit except compile times, that already aren't a problem so

@@lowlevelgamedev9330 It's your game engine, so you are the boss. But inheritance is a design pattern that gets annoyingly complicated pretty quickly, which is why a lot of modern developers try to avoid it.

well I wouldn't say that yet but maybe in the future 💪

it would simply be more efficient to take all entities in a radius of the player, then calculate the fastest way to a player ONCE per x frames rather than do that every single time, maybe even limit that to hostile entities only, maybe the youtuber should also give a mob type to the entities, hostile, neutral, passive etc sort of like minecraft :) you could also interpolate those path findings so they look more linear rather than just giving it the new path (re-calculate) so then - a zombie following you to a block you were previously at then getting the update that you are actually on 5 x blocks away right when he's about to get to your old location, this way it looks more smooth and it'd be way more optimized than what you suggested, but then you have also other problems like mobs having different verticalities and so on, could always limit that as well in the y difference player vs mob, obviously not as easy when you actually go to implement it. i think minecraft did that pathfinding operation per frame solution because they're single-threaded, and on top of that they never thought about interpolating pathfindings so it'd look less weird if they dit pathfinding less often, so they just run it consistently every now and then per each entity but not all at once (because again we're single-threaded), simply doing it every 1/2 of total fps, should result in a very smooth experience regardless of what fps you have, and it'll always scale linearly with your pc's performance.

oh interesting, did't know that but why yes since I found a better way to do it 💪

@@lowlevelgamedev9330 isopaque and istransparent is also not ideal, do bit masking instead, istransparent takes too much to execute, isopaque will also become more annoying down the road when you have more stuff to care about.

@@depralexcrimson unless they have different goals :) then his solution simply doesn't work.

yes 💪💪

I was actually thinking of adding golems but ther's a lot of work unti than

start doing it then, lad. you will never do anything if you do not start.

yes, it actually will be even easier than a* probably

A* works the same way in 2d, 3d or even 4d. Doesn't require any special work. For zombies every solid block that has 2 air block above should be considered walkable. It's easy to get valid neighbours and find path.

@@vatyunga Yeah, you would just need to add some more conditions for where you could walk to. But that shouldn’t be too hard.

you need to compile the project, the github link is in the description, and you also have instructions there

you need to compile the project, the github link is in the description, and you also have instructions there

ok nvm you don't have instructions there but clone the repo, right click in the folder and select open with visual studio

directx 8 ⁉ god damn at that point port the whole engine to windows 95 💀

Why??