Mission tracking

[Delaide]

Like the others, I am setting up a shared Google Sheets document for mission tracking, so all missions can be tracked for DSP.
https://docs.google.com/spreadsheets/d/ ... sp=sharing

[tagban]

If you want some really updated feedback, I have a very active community that keeps me updated with whats working and whats not, and we setup a test server to track actual crashes.

http://bnet.cc/forums/bugs-issues-reporting.40/ - General reports
http://bnet.cc/forums/crash-reports.95/ - Special assignments to find issues.
http://bnet.cc/categories/what-works-doesnt.98/ -- Our eventual list of what works/doesn't. To be melded into DSP Wiki once I have it completely compiled.

[Delaide]

Right now, I am actually just listing out each criteria of the missions.
Get mission from guard
Talk to Halver
Rage at Halver...wait, this isn't a step
Do BCNM
Turn in
Etc.

Anyways, basically, each step that should modify something in the database.
Once I have all steps listed, I will move to the variables - list out what gets set where (That currently exists). Hopefully this will help give a full map of how everything progresses, to help identify missing points (For example, many of the additional dialogue/cs options), and identify trouble points or unimplemented areas.

[tagban]

Okay, hopefully you can find some posts on my page helpful. I encourage my members to test things for what's working and not.