![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
5:26pm - Well it's back to work for me apparently. I thought I was going to play video games but I ended up opening all my work stuff instead. Hah-ha!
First thing's first, I've gotta import and modify Unity's example event manager into my PlayManager.
5:38pm - Hokay I've got the event manager set up in PlayManager. Next I have to make it so that InputManager triggers the appropriate events on inputs.
5:46pm - Hmm... My head's running in circles again. I think there's a problem with my design. Maybe it's reached the point of complexity that I can't contain it all in my head anymore? It seems early for that though.
Anyways I'm having trouble figuring out how I want to handle the inputs, after all I said. I was going to have it send an event whenever there was an input event, but there's already an input event system that comes with a lot more data attached.
I think that, instead, I should have a hard reference in the input manager to the player object as well as the gui/dialogue system/menu so that it can move them as neccesary.
But should the input manager move them, or just tell them to move? Probably just tell them to move, let them interpret what that means. But by using a hard reference I can carry over input information that wouldn't be carried by the event system.
I'll probably still need the event system though for handling things like talking to NPCs and going through scene transitions.
Alright. So, my next step is to make a MobileController script, to handle the player's movements and later NPC movements. It'll be a component attached to the player and NPCs sprites, so that the player can theoretically control any sprite, by switching the hard reference in the InputManager. And later, the AI engine will be able to move the NPCs using the same controller.
6:05pm - Okay stress is starting to pile up so I'm gonna take a video game break.
11:28pm - Ended up taking a nap after my game, and now it's time for pathfinder...
First thing's first, I've gotta import and modify Unity's example event manager into my PlayManager.
5:38pm - Hokay I've got the event manager set up in PlayManager. Next I have to make it so that InputManager triggers the appropriate events on inputs.
5:46pm - Hmm... My head's running in circles again. I think there's a problem with my design. Maybe it's reached the point of complexity that I can't contain it all in my head anymore? It seems early for that though.
Anyways I'm having trouble figuring out how I want to handle the inputs, after all I said. I was going to have it send an event whenever there was an input event, but there's already an input event system that comes with a lot more data attached.
I think that, instead, I should have a hard reference in the input manager to the player object as well as the gui/dialogue system/menu so that it can move them as neccesary.
But should the input manager move them, or just tell them to move? Probably just tell them to move, let them interpret what that means. But by using a hard reference I can carry over input information that wouldn't be carried by the event system.
I'll probably still need the event system though for handling things like talking to NPCs and going through scene transitions.
Alright. So, my next step is to make a MobileController script, to handle the player's movements and later NPC movements. It'll be a component attached to the player and NPCs sprites, so that the player can theoretically control any sprite, by switching the hard reference in the InputManager. And later, the AI engine will be able to move the NPCs using the same controller.
6:05pm - Okay stress is starting to pile up so I'm gonna take a video game break.
11:28pm - Ended up taking a nap after my game, and now it's time for pathfinder...
