By
@Landen_A
Get in. Get out. p.s., don't let the Blood Axolotl find you... --- Image sourced from Ruben Undheim, wikimedia commons: https://commons.wikimedia.org/wiki/File:Ambystoma_mexicanum_(6337857516).jpg The image was edited by removing the green and blue channels.
2h 10m 57s logged
I made a house in the game! + I made the camera fallow the player! Oh yeah, I also changed the depth system a little bit! (All very thrilling)
I took the ramps stairs and physics AABB and put them together to make a house. It might look a little questionable at the moment, but it will (probably) look better when I add sprites and texture stuff.
I also updated the camera to follow the player. It’s a very small system but it works well 
.
I updated the depth system so that objects can fit in a specific range of depths instead of the old “all or one” depth style. So, now the depth component is an enumeration with Single, Range, and All states. This is useful for cases like when I want the base floor of a house to persist when going up stairs to the next floor or when going around a stair case (see the video).
Another exiting thing is that I made a macro for creating Depth components. It works like this: depth!() -> Depth::All, depth!(1) -> Depth::Single(1), depth!(1, 3) -> Depth::Range(1, 3). It’s simple, but it’s the first time I have ever made a macro 
!
That’s it for now, next I will be working on a collectables system. I wonder, because it shouldn’t be very complex, if I could could post two devlogs in one day…
2h 21m 7s logged
Today, I go over how I added a third dimension to my 2D game.
When running away from the blood axolotl, you may want to run inside a house or around a house. The game’s current setup doesn’t allow for this! So, by adding depth I can give the player more hiding spots, making them feel safe for longer, there for, making them play longer 
.
What I did was make a new component: Depth (how clever of a name). And in the collision reaction code, if two objects have different depth, than have them not collide. If one of the objects doesn’t have the Depth component, make the objects collide anyway. This makes Depth-less objects collide with everything, so I don’t need a bunch of different floor objects for each depth !
Than I also made a simple system so that the player can move depths. I’ll have to change it quite a bit in the future but it is fine for now.
Next I am going to take the parts I’ve been creating and make buildings a thing. Than I’ll make collectables and the blood axolotl 
, (probably collectables first).
Things are going swimmingly. The project should be wrapping up in the coming weeks. The last few things I’ve coded for this project haven’t been supper hard by any means it’s just that I got school and my robotics team is doing a thing for homecoming so I’ve just been kind low on energy :/.
2h 52m 55s logged
I have made “stairs” in my game Blood Axolotl!
To be honest, the idea is very simple. All that is happening is that the Physics Object is being displaced to sit on a line. That’s it.
y = mx + b?
To make the Physics Object sit on a line, what I have to do is change the y value (stairs move you up/down). To get what the y value should be all I have to do is solve for y on a slop, such as y = mx + b (my 5th grade math teacher would be so proud of me). But, to be honest slope intercept form kinda sucks, (my 5th grade math teacher rn: 
), so I’m using point slope: y - y_1 = m(x - x_1) more specifically, y = m(x - x_1) + y_1 to get just the y value.
It works good, more like a ramp, but the game needs more development in every other aria before making the stairs more like stairs.
1h 49m 26s logged
I added a simple player system!
I set up a unit struct called Player that is used to make the object that all player systems will use as the player. Than I crated a system to query for the velocity of the player and change it based on pressed keys.
Not supper complex, but that’s nice some times
The AABB system strikes back and stopped working when ever it felt like it. Here is the code with the error:
if self.center().x < other.center().x{
out *= -1.0;
}
if self.center().y < other.center().y{
out *= -1.0;
}
the fix is to add .x and .y to the two use of out respectively. It took too long to figure that out 
.
Up next, I am going to add buildings 🏙️, which I think is hype.
5h 50m 35s logged
5 and a half new hours of coding time 
🙏 , a fully functioning AABB collision , and maybe something else ¯\_(ツ)_/¯
I got the collision system working, only took a little bit. I ended up asking ChatGPT for some help after the fifth hour, turns out I had it all done hours ago and all I had to rely do was flip two >s to <s; my pain is located in the coding bone ;-;.
Next I’ll try to make a simple player system and than after that building structures. I might also add a few things here or there for fun ;).
I’m a little burnt out soooo, I’m going to take Friday off.
see y’all later
25m 20s logged
I have this idea for a simple horror game that involves the apocalypse (maybe), a scary monster, and (you guessed it) an axolotl. This is going to be epic.
With less than 5 week left of Stardance, I am going to have to think small and hustle. Here is the premise:
you are in the apocalypse and you are stopping at a town to resupply. You need to get three items and get out while not falling pray to the Blood Axolotl (the big scary monster that will provide challenge so the game isn’t boring). Sweet, simple, and to the point.
This project is less about learning something new; I am going to try to increase my programing proficiency. Meaning that I am going to try to come up with systems at a faster pace than normal.
School started a little while back for me so development will be slowed. I don’t think this will be too much for me, the systems will likely somewhat simple. If I end up taking more than 5 week to finish this, feel free to bug me on Slack for updates on the project ;).
I feel good about this and I think I can do it!
(First image is an altered version of this one, more info in project description)
