Skip to main content

Week 2

This week was made up of a multitude of planning. We finalised our in-game mechanics aswell as a notation system for level design to help make it quick and efficient. The item-based mechanics that we finalised on where:
- Freeze, which pauses all movements from anyone except the user for a turn or two (still deciding)
- Time rewind, which rewinds all actions except the users two turns back
- Duplicate, this consists of two different items, one to start the duplication and one to end it. when the duplication begins an extra person will be spawned at the spawn point. when one of the characters land on the end duplication item, the other duplicate will disappear.
We have settled on a single guard type who can see you from down the line and will move towards your direction in order to attempt to catch you, if he lands on your square you will fail the level.
another concept we added is blocked paths which can be triggered by landing on the corresponding button/lever (guards can also trigger them).
As for level design, we have design our first few levels, introducing each concept in a new level, which we will spread out through the multitude of levels. We have designed a notation system to quickly design levels, this includes symbols for each item, guard, path type, gate, spawn point, obstacle and lever/button. This coming week we aim to work on the pygame tutorials aswell as record any level ideas we have so that we can start programming. We will also be working on our proposal.



Comments

Post a Comment

Popular posts from this blog

Final Post

This past week I've been working on fixing issues with the program to make it run as smoothly as possible. I didn't think I would get the stats for nerds page done and was going to scrap it so I could focus on getting the documentation done and fixing the minor issues so it would be more polished but I decided to do the stats for nerds page anyway and spent the past day and a half working on it. The notable issues from its development were mainly around gathering the data, in which I found some other errors in how I was collecting data such as not updating the data files when quitting the program. But i managed to finish the page as well as the rest of the program. My final solution was reasonably successful in comparison to my proposal and design, the only main things that I wasn't able to achieve was customisation of genome numbers and generation size and stuff like that, but that would have required a lot of digging through files in the libraries I was using to edit th...
Post a Comment
Read more

Week 13

this week I’ve been mainly focused on effectively parallelizing my AI so it can run multiple tests at once and be a lot faster, however I’m having trouble interacting with the neat library in order to do this as during some of its processes I need other functions to help me keep track of different things within the program, so I’ve been trying to work out how to edit the library and I’ll continue to work on that this week and hopefully have a finished AI soon enough.
Post a Comment
Read more

Week 14

This week I kept trying to parallelise my ai but found it quite tricky to edit the libraries functions, as they seemed to be working with each other in some weird ways which meant what I thought should work and made perfect sense was just not working. So I decided it was too late in my project to pursue it more, so I reverted my ai back to running one test at a time and began working on the display for when the ai is being tested. So far I've got some stats blitting next to the test, and this week I'm going to work on getting them scrolling as they need to and maybe get the buttons for the testing display done and working.
Post a Comment
Read more