Week 5 report

list what you did in week 5 here

Weekly Report 4

List what you did in week 4 here.

Weekly Report 3

Report what you did in week 3 here.

Weekly Report: 2

Report what you did in week 2 here.

Weekly Report: 1

This is the first weekly report for the Grimwood project.
All team members need to reply to this.

If you are confused read the style guide.

Script and Engine changes. Who currently is doing what!

To-do List

·         Rotate the character when dressing it         (script) - Jordan

·         Implement a crosshair        (script) - Tyler

·         Floating Enemy Nameplates (script) - Tyler

·         Have mounts that can be bought and mounted       (script) – Tyler

·         Have a warning sound or message when base is being captured     (script) - Kevin

·         Colors of names above players heads (green – friendly, red – enemy) (engine) – Tyler

·         Be able to sprint for short bursts    (script) - Sean

·         Have music in game             (script)

·         When under water health goes down         (script + minor engine) - Steven

·         Spend money on upgrades of armour/clothes etc.                                (script)

·         Spend money on upgrades ingame                               (script) – Tyler

·         Buffs, debuffs, team boost’s                            (script) - Tyler

·         Record match data – kills/deaths, time played, money …   (script)

·         Have a friends lists                               (script)

·         Be able to save different character profiles              (script) - Jordan

·         Have tool tips         (script) - Jordan

·         Game credits           (script)

·         If central point is captured, then you can spawn there.       (script)

·         If players group up a buff is applied to the grouped up players       (engine) - Kevin

·         ^ also, a torque script function shall be ‘raised’ when this occurs   (script) - Kevin

·         Black Arrow Spell                  (script) - Jordan

·         Apply sprint script to buffs implementation and add c++ speed functions (engine) – Sean

·         In-game Radar, it shows: players, enemies, capture points               (engine) - Steven

·         Fix Bugs/Errors       (engine + script) – Tyler & Jordan

Green = Complete

Red = currently being worked on

White = yet to be assigned to a person

Bug List

This is a list of all bugs discovered in the Grimwood game (hopefully none):
-
-
-
-
-
-
-
-
-

STYLE GUIDE

This is the style guide for programmers of the Grimwood project at the West Coast Institute of Training. It will cover all the necessary information to keep your documentation up to date and how to successfully comment and submit code to the stage 2 programmers.

Blog Posts:
This blog will be used to pass on information to you. Every week, we will create a weekly report on our shared project class (friday) and you will be expected to reply to this post with a comment in the following format:

Name - Current Feature Assignment - Date

List What you did:

-

-

List any problems you had:

-

-

Which files did you change:

-

-

Which files did you add:

-

-

Have you completed Your current task:

- (Yes/No)

------------------------------------------------------------

Code Changes:
Throughout this project you will hopefully be making a lot of scripting and C++ changes. In addition to listing what you changed (and submitting these files to the stage 2s) you should also comment your code in a uniform format.

The format that we will be using is simple:
//PUT YOUR FULL NAME HERE
Code changes
More code changes
I'm being optimistic about how much work you will do
//PUT YOUR FULL NAME HERE

This may seem tedious but it will be significantly easier to find out what you changed for both yourselves and us, and will reduce the workload for everyone. It will also make it easier for us to find out who is doing the least work ;)

Bug Reports:

If you find any bugs during your playtime in Grimwood, you should promptly shout across the room and inform us of these no doubt rare problems. Make sure these bugs are recreatable and worth fixing (I think we'll be ok if there is a prop missing or something unimportant) and we will make note of them. Try not to report the same bugs repeatedly by listening to your fellow stage 1's shouting.

We will list all of these bugs in a gigantic file and work through them whenever possible. We may also assign you to fix these bugs (so don't report anything too difficult!)

Welcome!

This blog is for the stage one and stage 2 diploma programming students.