7/5 Day Thirty-Four Of Game Project 2
This blog entry is also delayed by one day, but I will still write in the usual manner I always do.
So today we had only one programmer on set, which means that the productivity of that department was limited. They did do an awesome job and kept a steady flow of implementations and bug fixes, though.
What we are most worried about at the moment is to get the AI presentable until next week and we have therefore decided to change the responsibility of the AI to a more experienced programmer in our team in order to make that happen. This might not be ideal, but since the AI might not get done otherwise, we have to try and change strategy as we are dealing with it. We might come up with a different solution today since our lead programmer is busy doing the small, but essential implementations at the moment, we will have to see if there is enough time for it.
Because of this, we cannot rely on the AI getting completely fixed by the end of next week and thus have to change our last puzzle into something else. My co-designer worked on that new puzzle today, and it does not revolve around enemies going through doors or having a collision with rocks. Our goal is to have the enemies move correctly and only if we are quick enough, we may implement collision as well. We will not risk it, however, and therefore made this change.
It is not much time left, but overall we are doing really well on time. Apart from the AI that is.
We will see how it goes tomorrow!
// Samuel K.
So today we had only one programmer on set, which means that the productivity of that department was limited. They did do an awesome job and kept a steady flow of implementations and bug fixes, though.
What we are most worried about at the moment is to get the AI presentable until next week and we have therefore decided to change the responsibility of the AI to a more experienced programmer in our team in order to make that happen. This might not be ideal, but since the AI might not get done otherwise, we have to try and change strategy as we are dealing with it. We might come up with a different solution today since our lead programmer is busy doing the small, but essential implementations at the moment, we will have to see if there is enough time for it.
Because of this, we cannot rely on the AI getting completely fixed by the end of next week and thus have to change our last puzzle into something else. My co-designer worked on that new puzzle today, and it does not revolve around enemies going through doors or having a collision with rocks. Our goal is to have the enemies move correctly and only if we are quick enough, we may implement collision as well. We will not risk it, however, and therefore made this change.
It is not much time left, but overall we are doing really well on time. Apart from the AI that is.
We will see how it goes tomorrow!
// Samuel K.
Comments
Post a Comment