One week before we need a playable version of our core mechanics for the class the try, but I have set the deadline to this Thursday instead. That way we will have another half week to fix everything we will not get done until Thursday, (wow, that sounds really confusing, hopefully someone will understand me, maybe).
We had Scrum-meeting today. Scrum is a work method where EVERYTHING that is to be done is written down, like milestones, and each week every team member pick one or more things to work on. We estimate how long we think we will work with each part and set a risk, how high is the risk that we will not be able to finish that part before next week (low, medium or high).
Anyway, the meeting went smooth and everyone got their next quests.
I also did a couple of hours of coding. Started working on our guards sound detection system. When someone makes a sound, the sounds position, volume and cause (player or guard) is stored in a vector. It is also checked if any guard is close enough to hear it if it was the player creating the sound. If they are, a waypoint is to be set for them to the origin of the sound. This check is only made when a new sound is first created, so the reason to save them in a vector is because we will draw ripples from the origin of the sound if the player is close enough to hear them. So not only will sounds have an audible effect but a visual too.
I only had time for about 2 hours of coding today, so didn’t finish it yet. But I got the concept of how it could work and I can’t really see any bigger problem that a couple of minutes thinking can’t fix 🙂
Spörk 