Week 7. A good review.

This week was the final presentation for this half of the project. So far everything has been going well and we didn't have any big flaws pointed out. So now we just need to keep up this work and finish up the project. All that's left is finalizing some things, polishing, and possibly adding Kinect depending on client feedback.

So far what I see ahead for what I need to do is fix up the intro a bit more to deal with small inconsistencies I didn't see, and ensure that there is very little to no way to break the game through the UI. Right now I know of a possible way to at least kind of break it. It should be a fairly easy fix, which only needs some small code change and\or a kismet addition.

Week 6. A slow week.

This week most of my work for this session is done. All that's left for me at this time is making sure that the HUD is fully complete for the presentation. Which mostly involves small touch ups. I may also add in small details that would make the simulation better, but they will not likely be added this session.

Week 5. My main work begins.

This week is big on the HUD. I have to make sue that the code behind the pallet button works with the code the map has set up now. I also have to build new clipboard icons because the clipboard with objective we are using for some reason was done with pictures rather than movie clips and dynamic text. Quite an odd way to build the program seeing as how it is very inefficient. After new clipboard icons are done I also have to add in new buttons to deal with making a new icon for getting an empty box.

The final step after getting all the icons and the quick reference change fixed is adding the new code for the program. The code needs to be set up three different times for the three different difficulties. But because we have the difficulties planned, it shouldn't be that bad.

Week 4. Starting work on the UI.

This week I've started looking into new images for the UI. We need to have a pallet image for the new section we are adding. I'll also need to modify the image so that it has a transparent background and uses the same effects as the other UI buttons.

The flash UI has a different code method than I use normally. It mostly seems like its coded with movie clips instead of buttons and has all its code on the frames. The code on the frame makes the clips act like buttons. Its an interesting way to do it when buttons are one of the types you can pick over a movie clip. Perhaps they found something more effective in coding it this way.

It also seems that kismet shouldn't be much of a problem with integration because kismet has fscommands, which is something that is used a lot in the flash code and is very easy to combine.