Crash while on main story quest

[lovehandel]

Hi all.

Let me start this by saying i'm getting used to came crashes while on leves and other quests, etc. I just wait and restart them. It sucks but i'm ok with it. My laptop is not all that great and therein is the source of the problem-

However:

Today I was doing a main story quest (Lord Errant to be exact) when I crashed during the battle portion. My journal is exactly where I was when the game crashed. It is impossible to abandon and restart main story quests and I also cannot physically access the area where the quest had me in-order to resume where it left off.

I created a GM petition describing the problem. They replied with a cookiecutter response that said to submit a bug report at the Support Center website- which I then did. This is as i mentioned earlier not a bug- i just have a shitty system. The support center will not respond to any bug reports.

I recontacted the GM and this time got a different cookie-cutter response that said to reach out to the community. so here i am

Has anyone experienced this or know of any way to resolve it? It would suck to be stuck here indefinitely. I would consider quitting.

Thank you for your help^^

[Eruantien]

ive seen it happen before, but usually you can trace back the quest to enter the instance again. so for i assume this quest, you would head to the cutscene below broken water

[Catapult]

This is gonna suck.

I'd essentially treat it as if you'd dies and had to return to your home point. You'll need to head back to the Amal'jaa stronghold in the NW section of Broken Water and search till you find the right instance spot. I can't remember if it involves simply heading into the central area or one of the surrounding caves.

Sadly, trial and error on location (unless your journal shows a destination point with a map).