DAY 76

Alrighty, guys and girls, it's that time of the week again...after two weeks, but still. A new entry in the devlog is happening now. And I'm here to talk a little about creative burnout and why this thing is kinda sorta normal and OK to happen.

So, have you guys happened to just have a pretty hot streak in your projects, only for that streak to get colder and colder and colder until it hits ice levels of cold? Well, that is exactly what has happened to me. And honestly this was bound to happen, because things like burnouts are what happen when you try to dedicate yourself to a project such as a full blown game.

So, why is this normal? Well, first and foremost, there's a lot of moving parts and stuff going on that you, the solo dev, must handle personally. It's a daunting task, even for someone who is experienced in solo game devs. I actually came to the conclusion that every dev suffers burnout on their projects at some point, but the more experienced devs are coping much better with it. Either that, or they can manage it a lot better than inexperienced solo devs.

So is there something to do when burning out? Well, for starters, take a giant step back from the project. Like seriously, stop working on it and thinking about it for a couple of days or for however long it is necessary. Then get back right into it if you are feeling revitalized. If you are the kind of dev who goes gung-ho about the project, with the "zero-days-off" policy and whatnot, then at most work on some small part of the project or something that gets fast results....or just do some project management in Excel...or testing...

In my case, burnout occurred thusly: after a user stated that the jumping is floaty, I immediately recognized this as an issue after I posted about it. So I decided to do some tweaking in the character blueprint. At first, I didn't really commit to it, just did some tweaks here and there without saving the changes that were made. After a few days of fooling around with the tweaks, I kind of had a relatively clear idea for what I wanted from the jump mechanic. I knew that the jump (from input to landing) should be under a second, ~800ms to be precise. This theoretically felt the snappiest and the most enjoyable jump and I knew about this for a while. I knew the height should be around 2 times the height of the player character. This further added to the snappy aspect of things. What I didn't knew was what other ingredients to use to make the vision come to life. This mystery didn't last long and I've started messing around with the gravity. And yeah, mesing around with the gravity was for the better. 

But as I started to test out the changes in the levels, I've had a rather unsurprising revelation: all levels needed to accommodate changes to the jump. To be expected, sure. But I did have one surprising revelation: things got way more difficult in the rocky formations level. Which, if you recall, was something that I've complained on more than one occasion. So in that level, *very* few changes were made. Fixed the section where some sequence skipping occurred and made adjustments to the overall layout.

Discovering all these issues, fixing some issues while other issues popped up (of course the height of the character jump affected the jump pad and the monkey bar distances), then fixing those issues as well and the OTHER issues popped up (of course the gravity changes affected the wall run) was just simultaneously draining the joy out of the project and adding to the joy of knowing that the level is closer to being great. 

But in spite all of this, I think I may have regained some of the joy back. Because I've started working on the forest level. I'll only link one screenshot of it, because it's terribly late and I'll be missing my beauty sleep. But here is how it looks as of now: 

I am making a promise to show more tomorrow. Pinky swear.

Well, that is all for today, guys and girls. See you in the next post, buh bye. 

DAY 77

Why, hello guys and girls.

So today I continued to place chopped tree trunks that serve as...well, un-chopped, real living tree trunks. Not much work has gone today, because of a Discord call with a friend (what was supposed to be a short, ten minute or so call ended up being a 2 hour bonanza of talking...not regretting it one bit :D ).

But as promised, here are some more screenshots from the Forest area (including today's work). 

This area would preceed the ginormously large tree from earlier posts and clips. THere are a number of challenges that I would encounter throughout the creation of this level. One of them would be the "kill zone". 

OK, so for falling to the character's death, we've only had heights so far. Continuing having heights will not really go over well, for an obvious reason: variety. So for this area, a thought that keeps popping in my head and doesn't want to let go is the idea of having a huge fire spreading over the area. Or a fire that has already spread wide enough. And that fire would be the kill zone. This allows me to have death situations at low-ground level as well, not just way high above. 

At first I thought about making this area a swamp, but it was already established that the water will not kill you if you so much as touch it. So the next choice would've been fire. Now, the way I want to do it is for it to propagate via blueprints (i.e. controlled situation). I'm not done looking up into this solution, but it is very doable and would look fantastic. Once I have some update on this, I'll tell you guys all about it.

So, that's it for today, guys and girls. See you in the next post. Bye  

DAY 78

Howdy, guys and girls. Hope y'all doing as great as possible. Me, I'm back at it again with an update on the project.

So I've been on again off again working on the Forest level, replacing some assets here and there, making gameplay adjustments and so on. Kind of secretly delaying working on wall climbing and swimming and fixing bugs, but I'll eventually get to that...eventually...

There's still a lot of work to be done, a lot of things to be added and a lot of modifications to be made. First and foremost, I've added a small, make-shift pier with a hut. This would serve as the very beginning of the level, as you'd be arriving in this level via Paraglider.

This pier section would be just for exploration and some exposition purposes. There are two huts (one of them still needs to be worked on) and a toilet, just for fun. Complete with toilet paper.

Inside the first hut there are some computers. I'm not telling why exactly there are computers in a pier near a forest, except that it leaves some story bits for the player to discover.

I've completely replaced the grey tree trunks with a fallen log mesh, just to have a feel about how this level would look. I've also completely replaced all ramps with the bridge blueprint.

So as you can see, work has progressed pretty far in this level. Not up to snuff, tho. I haven't exactly figured out the gameplay: it might be more exploration oriented, it might have some puzzles in it, I don't know yet. But from what I've played, something like solving puzzles to progress to the next area feels right.

Lastly I would actually make a change in how I present the devlog to you guys. In the past few weeks, I've been working on the project bit by bit without updating the devlog. Sometimes literally working just 15 minutes per day, like no joke. Of course, working 15 mins a day doesn't result in a devlog-worthy entry. So naturally, I've decided that devlog entries would be a weekly thing, not a per-day entry. It makes more sense to me both time wise and content wise. Plus I'd have a more balanced work-life-passion project-hobby thing. Hope you guys would also enjoy it in this format.

So that's kind of it for today, guys. See ya in the next post. Bye!

Day 79-82

So naturally, I've decided that devlog entries would be a weekly thing, not a per-day entry.

HAHAHAHAHHA...cool joke, man.....overly optimistic Past Baftis is overly optimistic.

Why hello, ladies and gents. Back at it with an update on how the game is going. 

So I've been struggling quite a bit with working on the game and actually have a work-life balance thing going on. Clearly one of these didn't work out, but I did manage to work on the game more. 

Turns out motivation is a thing and got demotivated in the past few weeks. A vacation (of all things) managed to ease the struggle. Turns out that's what I needed.

So one of the things I've worked on is redesigning the canyon part of the level. There's nothing really wrong with the current version of the canyon, but visualizing the game when falling asleep churns out some pretty inpiring things. One of those inspiring things was the canyon part. Why? I wanted/needed a level where things could get really twitch-y and reflex based and really fast paced. Kind of like Sonic games, but in first person and with jumping. And one of those areas seems to pop up time and again: the canyon.

Now this turned me on big time, and as I started to implement this, I came across what I initially though was a bug. So, I have the jump-pad, right? And whenever you overlap with the jump-pad, the character flings in the air (on the Z axis) and you can go pretty much either way after that. Well, I did try to adapt this jump pad to a monkey bar kinda thing (the pole in DOOM eternal) Where you fling forwards. Well, that monkey bar had a problem: see, the idea is to fling the player forward on the Y-axis of the monkey bar. But lo and behold, the monkey bar does fling you on the Y-axis....of the world!!! So, I though "OK, this is clearly a bug", and went about to fix it. 

Turns out that this isn't a bug. By using LaunchCharacter nodes, the script tells the character to jump on the Y axis of the world, so you can't use relative rotation on the LaunchCharacter node. What this also means is that if I want to fling the character in a certain direction, I'll have to manually input the force on the axes I want that character to fling to. And my brain went "UUUUUUUGH!!?!?!?!" So, for every single directional jump pad/monkey bar that I want in the game, I have to make manual adjustments...."UUUUUUUGH!!?!?!?!" Thank God I don't have to do this on the jump pads that just fling you up, otherwise, I think I might've gotten insane.

So yeah, fun times, guys...really fun times. 

Anyway. For the time being, work on the Forest level is on hold. I've completely ran out of inspiration for it and will touch it once inspiration hits...or I'll visualize it before sleeping again. I'll leave you with only 2 screenshots, since it took a collosal amount of time to get the sequence right.

That's it for now, ladies and gents. See you in the next post. Buhbye. 

Hello, hello ladies and gents. hope you are having a great day. As for me, I'm back with an update on the project.

So the reason I haven't updated the devlog is because I kept putting off making it. Yes, it's that mundane. Because behind the scenes, I actually started working on not one, but two new levels. Let's go!

So the first level I'm going to talk about is the Gap level. This one came (like all good things) in my head, while falling asleep. I though that would be cool to have a level that focuses on wall running and the many ways that it could go to. And, while you can only do so much with a wall-run mechanic, it turns out that it works great when combining it with different mechanics (like, duh), especially the paraglider. 

Now, the Gap level is, to put it simply, a very very narrow canyon. The player, being almost at the top of the gap, must traverse it via wall-running. Here's how it looks: 

It is pretty difficult to capture some screenshots from this level because there is not much space to work with. And because it involves wall running, there's mostly long empty spaces with the occasional small cliff. Oh, but that's not all, there are some Death Traps around this level as well. One of these traps is in the third screenshot, a pendulum axe. The other one is in the BSP brushes, a blade that comes out of the rocks. If any of these traps touch the character, he is dead.

The second level I want to talk about is the Foggy Forest. 

This will most likely be the most simple level in the game in terms of implementation. This is because at it's very core, the level is about orienteering: you simply have some markings on trees/rocks and as the player, you have to find and follow said markings to reach the end of the level. That's it. In this level, you would also have a landmark that coincidentally serves as the end of the level. Said landmark is visible from all across the map if you look for it.

Here's how it looks as of now:

Btw, I was getting really sick and tired of just grayboxes in every single level. SO as a test, I used some assets off the marketplace. So we have GRAPHICS for a change, yay!! I don't know how the level is going to look with all post-process effects on (I'm only using a vignette as a post process effect now, fyi), but I'm sure as hell happy with how it looks as of now. Of course, things will get more populated as time goes. And yes, some trees are not upright (ooooh, that's going to be a pain to fix). 

Now, what makes this level challenging is 1) the low level of visibility 2) finding the markings (they won't be hidden, but they won't be easy to find either. 3) navigating through the forest: it will most definitely have multiple branching paths with dead ends. As such, it will be frustratingly difficult if you DON'T follow the markings. 

Now, there's a fun reason why I made the decision to make a foggy level. 

Initially, I wanted it to be sunny in the level. A hot mid-day kind of vibe. But as it was painfully brought to my attention in the form of hands-on experience, baking the lighting for a level that contains a lot of trees takes literally forever. Like in 2 hours, only 5% percent of the lighting was baked. This was a real problem if I was to iterate a lot on this level. Sure, one could argue that you do not have to bake the lighting at every iteration of the level, and one would be right. But it would still take forever + 6 months to bake lighting if this is how baking the lighting behaves with only trees in the scenery: foliage would be a big pain, props would also be a pain to bake.

So, a little bit off on a tangent, that got me thinking about making photos for textures and how I need to have bad weather so that no weird shadows or anything other than flat lighting appear in the texture. And then it hit me: how about I make a level in bad weather? You know, grey clouds, almost thunderstorm skies. In that weather nothing has a shadow and it looks great, very moody. And then it hit me again: oh, how about fog and/or mist? A little bit of that fog on the trees looks absolutely amazing to me. That definitely set the mood right away. And that is how I ended up doing a foggy level.   

Now, this is not the final layout of the forest because I did this as a test. Trees don't have collision, so that is a big no-no. The path to the end of the level, while defined, I'm not really happy with it. But I'm really happy with the results and I'll continue working on these two levels.

That about sums it up for this update, guys. See you in the next post. Buh-bye

P.S. Hope this time around I'll post more often.