How many of us have actually completed Destiny? (Destiny)

by Kahzgul, Tuesday, October 07, 2014, 14:17 (3937 days ago)

I'm seriously curious how many DBOers have actually 100%-ed the game's missions.

All main story missions, all side story missions, all strikes, the raid, and at least one match in each PvP map and/or mode that we've seen so far. At least 5 different patrol missions on each world, and the three public events: Kill guy X, defend the warsat, and destroy a Fallen Walker (are there any others? I haven't seen them). I guess maybe seen a "enemy forces are moving against one another" mini-war also.

Obviously I'm using the term "completed" loosely - I just mean have you finished the activity at least once, rather than done it on all difficulties etc...

Oh, I'll make a list here for ease:

Main Story:
Side Missions:
Strikes:
Raid:
Public Events:
Patrol:
PvP:

The reason I'm asking is because I've played a crapton of this game, and I know I haven't finished the stories at all. The people who are complaining that it's "too short" make me think they're not actually exploring the whole game.

--

Following is my breakdown for the curious:

Main Story: Incomplete
Side Missions: incomplete
Strikes: Complete!
Raid: Incomplete
Public Events: Complete!
Patrol: Complete!
PvP: Complete!

I'll be honest: I didn't even bother to unlock Mars until last week, and I haven't done several of the side missions. I *did* do most of the main story, but was disconnected after killing the second big enemy at the end of The Black Garden last night, so I've not actually completed it yet (seriously bad timing on the disconnect - It happened just as I killed the guy so I thought it was a cutscene when it was actually a Cattle error. Grr).

I've done all of the strikes at least once (twice, probably) and some of them a bajillion times (Tiger Strike, why do you want me to kill Sepiks Prime so badly? 3 times in a row is dumb - why does the code even allow a strike to be repeated immediately after completion? Seems like one line of code to fix... If PREVIOUS_STRIKE == CURRENT_STRIKE then ChooseNewStrike(CURRENT_STRIKE). There, fixed.), and I've done all of the PvP stuff a few times.

For the raid, I've only ever done the last fight (joined friends mid-raid) and we didn't quite win. Oh so close though!