71 réponses à ce sujet

[Taziel]

Just downloaded the patch and loaded to a previous save before act 2 and merril's quest STILL auto completes

[DeadInHell]

Yeah, that was also the first thing I checked. Sucks.

According to the 1.03 planning thread, the bug is "fixed" but only if you reload a save from prior to entering the Deep Roads entirely. So...incredibly lame. But I guess now I finally have a reason to be thankful that I've been away from the game for a month, being that now it will be a little less dull when I replay the stupid Deep Roads just so I can finally experience this bit of content.

[Mongoose22]

Have they already confirmed that you can reload from before the Deep Roads? I was going to drop down to Casual and speed run through that part again (so not fighting the boss on Hard for a third time). Glad I've not overwritten any saves so far...

[TheRaggyGandalf]

I'm getting seriously pissed. I've waited 4 weeks for a patch to fix this. Stopped right before Act2 and now they tell me I need a pre Deep roads Save (which I do NOT have).

Give me a ****ing script to set the flag right we have a Console damn it.

[DeadInHell]

Well, for those of you have not yet (or can't) replayed the Deep Roads, don't bother. I just played through the whole thing over again and the quests is STILL BROKEN.

Awesome.

[Mongoose22]

TheRaggyGandalf wrote...

I'm getting seriously pissed. I've waited 4 weeks for a patch to fix this. Stopped right before Act2 and now they tell me I need a pre Deep roads Save (which I do NOT have).

Give me a ****ing script to set the flag right we have a Console damn it.

No one ever said it was fixed before the Deep Roads, just that the flag for the quest being active might be set before then.  I was going to test whether it happened if I started before even going on the expedition (because it certainly can't have been set by then), but apparently that makes no difference.  It's just plain broken.

I dunno if you want to bother waiting longer; from the sounds of it, it's simply a short dialogue cutscene with Merrill about your sibling.  But yes, disappointing to still not have it fixed despite apparent attempts to do so.  Makes me wonder what the test plan for that was.

Modifié par Mongoose22, 12 avril 2011 - 08:34 .

[Mongoose22]

On second thought...

Luke Barrett wrote...

After talking to the design team it was established that this quest was supposed to be cut from the game and somehow remnants of it stuck around in some fashion. Rest assure it has no affect on anything going forward (and even when it was in the game it was a very brief conversation with not plot modifying flags). Sorry for the confusion.

Modifié par Mongoose22, 12 avril 2011 - 08:34 .

[pete1138]

That's all very well and good, but if every other companion has a "catching up" conversation after the deeps roads, what is Merril's? How esle would one get Merrill's "After Deep Roads" codex entry? (Besides the consoling words conversation) Maybe they should put it back in?

[christrek1982]

I'd like to know why it was cut? regardless of how un imprtant it was cant you put it back in? was it a space thing?

[Glycerine Queen]

I'm assuming this means it was cut because they only did a variation on the scene where Merrill refers to your sibling dying, not for them joining the wardens. It is odd that Merrill didn't get a start of Act 2 catching up conversation, though.

Oh, and I got the "Merrill- After Deep Roads" codex entry later in the act...not sure when. Maybe after completing her Mirror Image quest?

[Zsofi]

I created a new character (female) and when ,,I" was already in Kirkwall, patched the game (1.02). After the Deep Roads I recieved Merrill's Consoling Word quest correctly. With my first character (male) I replayed the Deep Roads (from choosen the companions in Kirkwall), but in this situation Merrill's quest was still broken. Knows somebody how far have to go back in the story to recieved this quest correctly?

[PaganOak]

BeLikeHan wrote...

Yeah, that was also the first thing I checked. Sucks.

According to the 1.03 planning thread, the bug is "fixed" but only if you reload a save from prior to entering the Deep Roads entirely. So...incredibly lame. But I guess now I finally have a reason to be thankful that I've been away from the game for a month, being that now it will be a little less dull when I replay the stupid Deep Roads just so I can finally experience this bit of content.

Thats no truth i've played the game from beginning with the patch , i have the SAME BUG of mourning quest...

[Zsofi]

Hah...:/ At least the ,,Consoling Word" works already...

[PaganOak]

bah. blind bioware

[Mongoose22]

So does anyone know of a way to get this quest to fire through the dev console?

[Ross42899]

If it was cut Bioware should complete it and put it in again...

[TallBearNC]

I never got this quest... but I've always wondered.. why would anyone let their sibling die? You can make them a warden, circle mage, or templar... Why would you want them dead?

[Epona222]

TallBearNC wrote...

I never got this quest... but I've always wondered.. why would anyone let their sibling die? You can make them a warden, circle mage, or templar... Why would you want them dead?

If you're playing for the first time, or if you never took them to the Deep Roads on previous playthroughs, you don't know that they will die.  And there is a scenario where they WILL die, regardless of what you would like to happen - namely if you took them to the Deep Roads and did not also have Anders in the party.  So suggesting that people only encounter a dead sibling scenario because they "wanted them dead" is way off the mark.

Edit to add:

On my 1.01 playthrough, Bethany was taken to the Circle and I got "Consoling Words" quest from Merrill.  On this current 1.02 playthrough, Carver was made a Warden, and I got NO catch up quest for Merrill at the beginning of act II.  I was directed to speak to every other companion but her.  I find it hard to believe that the developers intended that everyone else but her wants to speak to me at the beginning of the act.

Modifié par Epona222, 16 avril 2011 - 12:59 .

[Mongoose22]

Well, I finally got this quest to trigger using the dev console:

• Load a game where you're still in Act 1.  Since the quest auto-completes at the start of Act 2, it won't trigger after that (unless someone knows how to reset quest flags).  The best time to do this is right before the Deep Roads; otherwise, you may have to wade through Merrill's other conversations first.  Note that this will screw up your game pacing, so I would load another save after this to reset the game state.
• Use the command runscript zz_mrl_debug in the dev console to bring up Merrill's debug script.
• Choose Other Dialog > Act 1 > Deeproads before mother visit.

Given how the conversation goes I somewhat understand why this was cut if Bioware was pressed for time.  Apparently this conversation was supposed to trigger in between when you came back from the Deep Roads and went back to talk to your mother, presumably because the game allowed you to wander the city between the Deep Roads and the end of Act 1.  Now that there's no free time in between, one of the conversation lines makes no sense.  It could've been trimmed to fit the context of the final game, though.

If anyone wants me to post a transcript of the conversation, lemme know.  It's very short.

Modifié par Mongoose22, 16 avril 2011 - 03:24 .

[blufire burner]

I played las night and got to te beginning of act 2 and had this auto-complete issue, so I didn't save.

Today I installed patch 1.03 and now the bug is worse, the quest doesn't even show at all. I hope I still can get Mirror Image

[Cyakura]

Good good.. Merill is evil... she needs to die.. Bioware will make everytime someone talks to merill, that she will drop dead )

[Mongoose22]

blufire burner wrote...

I played las night and got to te beginning of act 2 and had this auto-complete issue, so I didn't save.

Today I installed patch 1.03 and now the bug is worse, the quest doesn't even show at all. I hope I still can get Mirror Image

It's fixed now; the quest was cut, so it was never intended to be logged.