![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
relee9:30am - I'm at home now, just watched the latest Ducktales (2017) and they really went there with that? Wow.
I'm already feeling like doing some more work, though, so I think I'll take a look at that movement problem. I'm afraid it might have something to do with the input timer I put in, though, and I'm not sure how to handle the input without one...
10:03am - I managed to get the inputs working properly. I had copy-pasted some code and didn't change the active string in it, so the movement was acting a bit weird.
So, I've got my little man moving around the dungeon now. Let's make sure he bumps into walls in all directions next...
10:07am - Yes, the little man bumps into all the walls properly.
What next? Well I guess I'll update the HackNPlan...
10:23am - Okay, HackNPlan updated.
Now to decide what to do next!
Currently my little man goes out of order, not following the turn order. Normally he should only respond to inputs on his turn.
Once he does, I can also add baddies to the turn order, and other things.
I can also make the dungeon more interesting at this stage, or hold it off until later. I'll probably hold it off until later, though, since there's no rush for interesting dungeons. Not until I need to test the pathfinding AI for the critters, and implement line-of-sight and lighting, the last two I might not even do in this version. We'll see.
So yeah I think I'll put my little man into the timing system next and see what that does to my code. I'll probably have to add another check on top of 'Is the tile blocking?' and 'Is the InstalledObject blocking?' to 'Is the Actor blocking?'? Heh.
Well for now I'm going to take another break. Think about things perhaps.
I'm already feeling like doing some more work, though, so I think I'll take a look at that movement problem. I'm afraid it might have something to do with the input timer I put in, though, and I'm not sure how to handle the input without one...
10:03am - I managed to get the inputs working properly. I had copy-pasted some code and didn't change the active string in it, so the movement was acting a bit weird.
So, I've got my little man moving around the dungeon now. Let's make sure he bumps into walls in all directions next...
10:07am - Yes, the little man bumps into all the walls properly.
What next? Well I guess I'll update the HackNPlan...
10:23am - Okay, HackNPlan updated.
Now to decide what to do next!
Currently my little man goes out of order, not following the turn order. Normally he should only respond to inputs on his turn.
Once he does, I can also add baddies to the turn order, and other things.
I can also make the dungeon more interesting at this stage, or hold it off until later. I'll probably hold it off until later, though, since there's no rush for interesting dungeons. Not until I need to test the pathfinding AI for the critters, and implement line-of-sight and lighting, the last two I might not even do in this version. We'll see.
So yeah I think I'll put my little man into the timing system next and see what that does to my code. I'll probably have to add another check on top of 'Is the tile blocking?' and 'Is the InstalledObject blocking?' to 'Is the Actor blocking?'? Heh.
Well for now I'm going to take another break. Think about things perhaps.
