Blue Ninja
Member
You still have Gorgon Checkpoint right?
Normal or Hard?
Yeah, Hard mode.
You still have Gorgon Checkpoint right?
Normal or Hard?
Thanks Darknyss!Are you at Crota now? I can jump in and help w/ my hunter.
OK, boys; you had your BloodBorne fling, get back to work:
8:30 PM Eastern: (note a slightly earlier start time)
- Gorgon's chest (I see captscience already has HM, but can anyone snag NM?)
- 1x full NM CE (note that we're going to use CENTER strategy going forward to train ourselves for HM)
- 2x NM Deathsinger and Crota kill
- 1x Gorgons -> Atheon HM
- 2x Atheon kill
Save please! I'll be home for lunch around 1:30 Eastern if you'll be around...Yeah, Hard mode.
OK, boys; you had your BloodBorne fling, get back to work:
8:30 PM Eastern: (note a slightly earlier start time)
- Gorgon's chest (I see captscience already has HM, but can anyone snag NM?)
- 1x full NM CE (note that we're going to use CENTER strategy going forward to train ourselves for HM)
- 2x NM Deathsinger and Crota kill
- 1x Gorgons -> Atheon HM
- 2x Atheon kill
1) stb (PSN Berried_treasurE)
2) stb's pal (PSN Capt_Verde)
3) captscience (PSN captscience)
4) Dave_6 (PSN DaveS78) ?
5) GRIP (PSN GriP17-) ?
6) schwagger15 (PSN spyder_ur) ?
a) StereoType (PSN Haybro_) ?
a) ich00 (PSN ichabod00) ?
a) LTWood12 (PSN LTWOOD12) ?
a) Frostburn (PSN US-Frostburn) ?
a) Lnkn52 ?
a) Hung Wei Lo ?
Yeah, Hard mode.
300 plus you actually have to throw the rocket launcher at him after the last shot to kill him.
Save please! I'll be home for lunch around 1:30 Eastern if you'll be around...
I've got it on three characters, I'll keep it around.
I'll be around at that time for sure. CE Normal is the first order of business as I still need boots and the chest piece on my Warlock. I can switch to my Hunter or Titan to run sword as a 32 though if needed. Happy to play w/ you guys, or if there's too many we can make a second group. I'll be on regardless.
Regarding saving Raid checkpoints, is there anything that wipes those for a given character besides going further in the given raid and the weekly reset? Like other missions/strikes, the other raid, the same raid at a different difficulty?
count me in, as well, please!I'd be up for creating a second group if that is all full. Going to run NFs when I get home and then try to find someone with the Gorgon chests.
The Quest for the Horn continues...
OK, boys; you had your BloodBorne fling, get back to work:
8:30 PM Eastern: (note a slightly earlier start time)
- Gorgon's chest (I see captscience already has HM, but can anyone snag NM?)
- 1x full NM CE (note that we're going to use CENTER strategy going forward to train ourselves for HM)
- 2x NM Deathsinger and Crota kill
- 1x Gorgons -> Atheon HM
- 2x Atheon kill
1) stb (PSN Berried_treasurE)
2) stb's pal (PSN Capt_Verde)
3) captscience (PSN captscience)
4) Dave_6 (PSN DaveS78) ?
5) GRIP (PSN GriP17-) ?
6) schwagger15 (PSN spyder_ur) ?
a) StereoType (PSN Haybro_) ?
a) ich00 (PSN ichabod00) ?
a) LTWood12 (PSN LTWOOD12) ?
a) Frostburn (PSN US-Frostburn) ?
a) Lnkn52 ?
a) Hung Wei Lo ?
I'd be up for creating a second group if that is all full. Going to run NFs when I get home and then try to find someone with the Gorgon chests.
The Quest for the Horn continues...
I've got it on three characters, I'll keep it around.
I will play Nightfall now...
2 spots open.
someone record party chat when narmer is trying for the horn, I want to hear him haha.
OK, boys; you had your BloodBorne fling, get back to work:
8:30 PM Eastern: (note a slightly earlier start time)
- Gorgon's chest (I see captscience already has HM, but can anyone snag NM?)
- 1x full NM CE (note that we're going to use CENTER strategy going forward to train ourselves for HM)
- 2x NM Deathsinger and Crota kill
- 1x Gorgons -> Atheon HM
- 2x Atheon kill
1) stb (PSN Berried_treasurE)
2) stb's pal (PSN Capt_Verde)
3) captscience (PSN captscience)
4) Dave_6 (PSN DaveS78) ?
5) GRIP (PSN GriP17-) ?
6) schwagger15 (PSN spyder_ur) ?
a) StereoType (PSN Haybro_) ?
a) ich00 (PSN ichabod00) ?
a) LTWood12 (PSN LTWOOD12) ?
a) Frostburn (PSN US-Frostburn) ?
a) Lnkn52 ?
a) Hung Wei Lo ?
Regardless, I'm confident Bungie has enough power over their own systems to intercept a weekly strike update, especially given they are scheduled out so far in advance. From a data gathering standpoint, it makes a lot more sense to roll this strike out right after the update, not before, so they can see how the changes play out. Identifying that this particular strike is one of the lowest completed weeklies, then queuing up an identified solution, and then rolling out the same problematic strike right before the solution goes live....that's just really bad form, IMO.It was modified with a patch, which is, again as I understand it, the only way these changes can be made now. I'm no authority on the matter, but I don't believe it is as easy as just "pressing a button" to add a burn. These strikes and modifiers are similar to Xur's inventory in that they are selected a long time in advance and are randomly generated at the time the are initially selected. According to dataminers, the only way they could thwart dataminers from pulling Xur's inventory early was to create a 2nd Xur with inventory that would not appear until the day he was set to appear in the tower. I believe nightfalls/weekly work the same way.
They did not make an announcement about how the mars strike needs to be patched and then intentionally put up the most difficult version of that strike the next week. It was in line to show up today no matter what.. they just should've picked a different time to make that announcement.
That's what I'm saying though... the bad form is making an announcement when you should've known what was coming in the next week for the nightfall/weekly line-up (hell, the dataminers did), not that they intentionally dropped this NF on us after that BWU hit.Regardless, I'm confident Bungie has enough power over their own systems to intercept a weekly strike update, especially given they are scheduled out so far in advance. From a data gathering standpoint, it makes a lot more sense to roll this strike out right after the update, not before, so they can see how the changes play out. Identifying that this particular strike is one of the lowest completed weeklies, then queuing up an identified solution, and then rolling out the same problematic strike right before the solution goes live....that's just really bad form, IMO.
At the very least, it looks awful. Don't tell your player base you know as strike is not good, tell them a fix is on the way, and then drop the strike on them again.
Who said they think Bungie is incapable of changing things or that it was totally out of their control? I know I didn't.I continue to be baffled that people believe that Bungie is somehow incapable of changing things like no-burn Valus. Like it's totally out of their control.
I continue to be baffled that people believe that Bungie is somehow incapable of changing things like no-burn Valus. Like it's totally out of their control.
They have Hot Fixed Xur, while he was live in the Tower. Surely they have control on burn modifiers. It would be terrible design if they had Zero control after release.
I will play Nightfall now...
2 spots open.
NP. Any bullet helps to kill himSorry I wasn't of more help. Glad you got it done!
Last call for NF before I take the LFG plunge . . .
OK, boys; you had your BloodBorne fling, get back to work:
8:30 PM Eastern: (note a slightly earlier start time)
- Gorgon's chest (I see captscience already has HM, but can anyone snag NM?)
- 1x full NM CE (note that we're going to use CENTER strategy going forward to train ourselves for HM)
- 2x NM Deathsinger and Crota kill
- 1x Gorgons -> Atheon HM
- 2x Atheon kill
1) stb (PSN Berried_treasurE)
2) stb's pal (PSN Capt_Verde)
3) captscience (PSN captscience)
4) Dave_6 (PSN DaveS78) ?
5) GRIP (PSN GriP17-) ?
6) schwagger15 (PSN spyder_ur) ?
a) StereoType (PSN Haybro_) ?
a) ich00 (PSN ichabod00) ?
a) LTWood12 (PSN LTWOOD12) ?
a) Frostburn (PSN US-Frostburn) ?
a) Lnkn52 ?
a) Hung Wei Lo ?
I'm in, PSN same as here
Great! Let's give it a couple minutes, and then I'll do LFG for 3rd . . .
I think we largely agree, but to clarify my stance: Bungie gathered data to identify which strikes are being completed the most and least often. They identified Valus on the weekly rotation as landing at or near the very bottom of the list. The moment they saw that data and put plans in place to get a fix lined up, the strike should have been pulled from rotation. This was identified many weeks ago; I don't think it was Deej's announcement that was problematic, but rather the decision to keep it in the mix.That's what I'm saying though... the bad form is making an announcement when you should've known what was coming in the next week for the nightfall/weekly line-up (hell, the dataminers did), not that they intentionally dropped this NF on us after that BWU hit.
I'm saying I don't believe they rolled out the strike after making this announcement on Thursday. If what I'm "guessing" is correct, and the only way to make a change to the weekly/NF is via a hot fix, do you think they should've launched one between Thurs when the update came out and today when the reset took place? Im with you 100%, it is bad form to make that announcement and then have this strike (esp considering they knew this strike was coming), but what I'm saying is, I think it was just bad planning on the BWU side of things to make that announcement given this strike was coming with these modifiers. I in no way believe they made that BWU and then decided to drop this strike on us today, nor do I believe it can be changed without implementing a patch (similar to Xur). So once DeeJ posted it, they were kind of screwed unless they wanted to drop a hot fix between Thurs and today.
Who said they think Bungie is incapable of changing things or that it was totally out of their control? I know I didn't.
Great! Let's give it a couple minutes, and then I'll do LFG for 3rd . . .
PSN Doublesith, I'm in.
I'll hop in nowLooking for one more for Nightfall. Join on RetroMG.
I will just go to tower and get into your gameLooking for one more for Nightfall. Join on RetroMG.
I see what you're saying. Yeah I wasn't sure when they gathered that data (I must've missed the part where they said that it was gathered weeks ago).I think we largely agree, but to clarify my stance: Bungie gathered data to identify which strikes are being completed the most and least often. They identified Valus on the weekly rotation as landing at or near the very bottom of the list. The moment they saw that data and put plans in place to get a fix lined up, the strike should have been pulled from rotation. This was identified many weeks ago; I don't think it was Deej's announcement that was problematic, but rather the decision to keep it in the mix.
If Deej did not say anything, the blowback would have just been backward looking: you rolled out that strike knowing it was a problem, and had a fix a week or so away, and didn't tell anyone? People would be at least as annoyed then as now. So I don't put this one on Deej - I put it on Bungie for not acting more promptly on their own data. They had plenty of time.
for as many times as i've been party to Crota's End, i've never examined his sword very closely, but looking at it now, it looks like it's a butchered torso... a rib cage is visible, and i'm guessing that the hilt of the blade is the pelvis of the torso.i just can't un-see it...if that's the case, ummm... what's the hilt?
for as many times as i've been party to Crota's End, i've never examined his sword very closely, but looking at it now, it looks like it's a butchered torso... a rib cage is visible, and i'm guessing that the hilt of the blade is the pelvis of the torso.i just can't un-see it...if that's the case, ummm... what's the hilt?