I just finished day 4 the Tile System, have been following along via raylib instead as I daily drive a Mac and my PC's not always available to me (hey we make do with the cards we have right?). General feel is that RayLib feels mostly the same to what I see on Ooga Booga. So definitely no issues following along. Has been a great exercise for me so far! Anyways, just wanted to point out that because RayLib uses source and destination Rectangles to draw the sprites, the destRect itself is already kinda like a range in itself. So you don't actually need to write range.c, and can just use the CheckCollision functions (https://www.raylib.com/cheatsheet/cheatsheet.html). The bounding range data itself is kinda encapsulated in the destRect already. Also GetMousePosition defaults to (0,0) even if the mouse isn't even active yet. So I did a 0,0 check (since it'll 99.999% not be 0,0 again once you start moving it cause floats) and cached that as a bool to check against for all the range or collision checks with the mouse. That way you don't have things highlighted in the top left corner of the window everytime you launch. Also, say hi if you're working on a Mac! So we can connect and help each other troubleshoot as we follow along! Esp if you're using raylib to follow along.

I'm on day 8 of the course now, As seen in the community, some of us are following along using RayLib (for variety of reasons, mine is I daily drive a mac) As far as I know RayLib doesn't have any built in z-sorting support. So whatever order you render things is what you get. Am wondering for those using or have used RayLib, what methods or systems do you use to handle z-sorting? More of a discussion than a question.

If you're using Raylib instead of Ooga Booga, and want to get the world position from your cursor for example, this may be of use: Vector2 screen_position_to_world_position(Vector2 screen_position, Camera2D camera) { Vector2 world_position = (Vector2){ .x = (screen_position.x / camera.zoom) + camera.target.x - (camera.offset.x / camera.zoom), .y = (screen_position.y / camera.zoom) + camera.target.y - (camera.offset.y / camera.zoom), }; return world_position; } Edit: As @Alperen Yilmaz pointed out, you could also use the function GetScreenToWorld2D that comes with Raylib.

Hi, as the title kind of suggests, i might have stepped into something way bigger than me (or specifically my programming knowledge), im no way near an intermediate-advanced programmer. I have done a bunch of C++ programming back in highschool mixed with a little bit of Java, then it progressed into a Junior Java backend developer (with very little experience) and then finally here i am trying to learn and figure out graphics/game programming. I'll just say that my progress so far was just being able to setup a project, make it work and being able to create a window with a background color and a nice orange triangle, which is basically nothing compared to what this group "requires" and provides considering i'm trying to use C++ (eventho im probably learning it as if it was C). What do you guys think? Is it fine for me to just hang around and learn new stuff? Or should i just step off and focus on something less challenging?

Just started looking at the Ooga Booga engine, and it reminded me a bit of RayLib (If you aren't familiar, RayLib is pretty similar, a C Framework for making games) Has anyone here used both? I'm curious what the differences are in terms of features/goals for the engine.