Yes. The strikes are DIRECTLY from the campaigns. But Destiny 1 had their strikes related to the story, reused areas only to go into a new section of the map that was never before seen. We're talking about the areas in which the strikes take place and combining the bosses here. As I said with Destiny strikes, we got to go to a new area on the map. Granted it was connected to older parts of the map, but when we played the new strikes, it was new, fresh. People were interested to see what they were and how they played out. Ripping a story mission and making it the EXACT same thing but boosting up the level is just lazy. The bosses, though, are pretty good IMO. If they could just COMBINE the boss mechanics and then grant us access to new areas specifically for the strikes, that would be great. Bungie handled their strikes better in D1 than they do in D2. You didn't see complaints about strikes in D1 DLC. I can guarantee if you make a poll right now, people would prefer to have brand new strikes over the "newer ones". Omnigul wasn't the only one, dude. Dark Blade wanted to take Oryx's thrown. He failed and was imprisoned for doing so. SHANK. Had to do with making connections to Rasputin and potentially making him an ally. (Which IDK wht Zavala hates him so much. He LITERALLY said he hoped he would be our ally). Malok wanted to take control of the taken and become kind. The strikes made sense. The "new" strikes even act as if you never went through the story too. Not even a "oh no. XOL GOT REVIVED AFTER YOU LEFT" Nope. You start the strike as if nothing happened.

[quote]Yes. The strikes are DIRECTLY from the campaigns. But Destiny 1 had their strikes related to the story, reused areas only to go into a new section of the map that was never before seen. We're talking about the areas in which the strikes take place and combining the bosses here.[/quote] The Pyramidion? Arms Dealer? Savathuns Song? D2s strikes use their own areas too d00d. [quote]As I said with Destiny strikes, we got to go to a new area on the map. Granted it was connected to older parts of the map, but when we played the new strikes, it was new, fresh. People were interested to see what they were and how they played out.[/quote] See above. [quote]Ripping a story mission and making it the EXACT same thing but boosting up the level is just lazy.[/quote] Bruh, they arent ripped missions, they [b]are[/b] strikes, and they were when you first played them. They just werent optional for progression like D1s. The Strike levels were bumped up from D1s story director strikes to the playlists as well. This is nothing new. Again, [b]they were actual strikes which were worked into the narrative arc.[/b] [quote]The bosses, though, are pretty good IMO. If they could just COMBINE the boss mechanics and then grant us access to new areas specifically for the strikes, that would be great.[/quote] Apart from Exodus Crash, I agree. However, is there a boss area/runup to it thats accessible outside of the Strike? Other than the patrol areas they start in, or cross, I dont think there is. And D1 did that too. [quote]Bungie handled their strikes better in D1 than they do in D2. You didn't see complaints about strikes in D1 DLC. I can guarantee if you make a poll right now, people would prefer to have brand new strikes over the "newer ones".[/quote] Not TTK onwards, granted, but then they showed better design from there on. Before that it was dull bullet sponge fights, and yes there were compaints. [quote]Omnigul wasn't the only one, dude. Dark Blade wanted to take Oryx's thrown. He failed and was imprisoned for doing so. SHANK. Had to do with making connections to Rasputin and potentially making him an ally. (Which IDK wht Zavala hates him so much. He LITERALLY said he hoped he would be our ally). Malok wanted to take control of the taken and become kind. The strikes made sense.[/quote] Darkblade wasnt mentioned before his strike. Nor was SHANK. [quote]The "new" strikes even act as if you never went through the story too. Not even a "oh no. XOL GOT REVIVED AFTER YOU LEFT" Nope. You start the strike as if nothing happened.[/quote] I refer you to stepping into a war with the Cabal. But yes, whilst not a new criticism, I can agree with that.

[quote]The Pyramidion? Arms Dealer? Savathuns Song? D2s strikes use their own areas too[/quote] We're talking about the 4 DLC strikes here that were story missions as well. Not the launch strikes. Of course they have their own areas. It's a new game. The launch strikes are fine. They are related to the characters. Pyramidian is a strike for getting payback for Asher. Savathuns Song is foreshadow of whats to come with the Hive. Exodus Crash: Stop the fallen from Dismantling Failsafe. It makes SENSE as to why those strikes exist. They relate to the characters that were introduced from the Launch story. [quote]Bruh, they arent ripped missions, they [b]are[/b] strikes, and they were when you first played them. They just werent optional for progression like D1s. The Strike levels were bumped up from D1s story director strikes to the playlists as well. This is nothing new.[/quote] No they weren't. They are story missions that had their level amped up to make them harder. It doesn't even matter as to what they're called or referred to as. The point is that taking a story mission and making it into a strike rather than making new strikes is lazy. It doesn't even have to be a super related to the story. Asher mir warned us about a threat in the Pyramidian. Etc. If this was the case, then I guess you could say they turned strikes into story missions. Either or, Nokris should have been a SEPARATE entity. It should have been a strike ONLY being as Xol is the stories VILLAIN. Same goes for The Giant Cyclops in CoO. [quote]Apart from Exodus Crash, I agree. However, is there a boss area/runup to it thats accessible outside of the Strike? Other than the patrol areas they start in, or cross, I dont think there is. And D1 did that[/quote] Wait doesn't that prove my point though? Strike areas and runups that are specific for strikes. That's a good thing. And we're talking about DLC strikes. So in this statement, aren't you saying that having new areas for strike bosses and runups is a good thing? Then why are you saying that turning a story mission into a stirke is OK. [quote]Not TTK onwards, granted, but then they showed better design from there on. Before that it was dull bullet sponge fights, and yes there were compaints.[/quote] I'll agee with you in this one. There were complaints about strikes, but only the bosses that were borimg to shoot at. There weren't any mechanics. Now that there are, people arent complaining about the bosses anymore. Nothing about the runups and areas in which they were in though. No mission in Destiny 1 and Destiny 2 Launch turned into strikes. Not one. Every strike was an original, had a reason for existing. Nobody complained about the areas in which they took place. In fact, people were complaining about new story missions being in reverse in Destiny 1. They wanted NEW areas for missions. So taking a mission and having it be a strike is absurd. I know you can't please everyone, but why are you against getting new strikes. In the middle of your statement, it seemed that you longed for new areas for strikes. Asking for Bungie to improve on strikes and giving them feedback isnt a bad thing. And many people in this post agree.

[quote]We're talking about the 4 DLC strikes here that were story missions as well. Not the launch strikes. Of course they have their own areas. It's a new game. The launch strikes are fine. They are related to the characters. Pyramidian is a strike for getting payback for Asher. Savathuns Song is foreshadow of whats to come with the Hive. Exodus Crash: Stop the fallen from Dismantling Failsafe. It makes SENSE as to why those strikes exist. They relate to the characters that were introduced from the Launch story.[/quote] The 4 DLC strikes were blended into the narrative just like vanilla D2s Strikes. You cant level the accusation at one and not the other. They all have their own areas too, though I will concede Xols strike used a large portion of patrol zone. [quote]No they weren't. They are story missions that had their level amped up to make them harder. It doesn't even matter as to what they're called or referred to as. The point is that taking a story mission and making it into a strike rather than making new strikes is lazy.[/quote] Putting Xol to one side, all strikes from D1 through to Nokris have the same damn structure, noticeably different from story missions. Again, I see where Xol falls short here. [quote]Wait doesn't that prove my point though? Strike areas and runups that are specific for strikes. That's a good thing. And we're talking about DLC strikes. So in this statement, aren't you saying that having new areas for strike bosses and runups is a good thing? Then why are you saying that turning a story mission into a stirke is OK.[/quote] The only strike you could possibly apply this to is Xol. The rest are largely made up of unique areas. And again, they arent story missions. Please drop that inaccurate, misleading statement. [quote]No mission in Destiny 1 and Destiny 2 Launch turned into strikes. Not one. Every strike was an original, had a reason for existing. Nobody complained about the areas in which they took place. In fact, people were complaining about new story missions being in reverse in Destiny 1. They wanted NEW areas for missions. So taking a mission and having it be a strike is absurd. I know you can't please everyone, but why are you against getting new strikes. In the middle of your statement, it seemed that you longed for new areas for strikes. Asking for Bungie to improve on strikes and giving them feedback isnt a bad thing. And many people in this post agree.[/quote] Because if you take away the strikes and look at the raw mission numbers, you find that there is little to no difference between mission counts between D1, D2 and relevant DLCs. Add the strikes back in and its still essentially the same, big difference being D2s campaigns are mostly superior and the DLCs both came with new locations whereas D1s didnt. A lot of people in this thread are blindly bandwagoning. Look, I dont give a shit if I push a button on the map that says [b]THIS IS A STRIKE[/b] or whether its part of a seamless campaign flow. A strike is a strike.

There are ONLY two sides to this argument. So saying that one side has more people is just a bandwagon is just false. What the heck do you expect? It just so happens that the majority wants orginal strikes with new areas.