Skyrim talk:The Battle for Fort Amol

Fort Amol Empty

After having a lot of issues trying to get Legate Rikke to have the option to "Report for Duty", I finally got it but the Fort now is empty. There is a stormcloak corpse near the entrance though. I have loaded a previous save (before getting the "Report for Duty" prompt), and the Stormcloak soldiers are alive. To reiterate, I have not cleared Fort Amol but somehow after reporting to Rikke, they are now dead. Anyone else with this issue and possible solutions/fixes? Continuing with the Main Quest is out of the question as I saved the Civil Questline for last. Djo201 02:10, 15 January 2012 (UTC)

I had this problem to - well Rikke spoke to me, but I had an empty fort. Tried all sorts of console commands to progress/reset the quest and nothing worked. No idea how to fix it. 134.176.247.178 09:33, 22 March 2012 (UTC)Tim Bostick

One possible cause, and I have no way to confirm this, is that I let Hadvar get kind of crippled in the preceding fort fight. I was letting the Stormcloaks constantly attack me in order to level light armor, and Hadvar had the inenviable task of taking them all out, which he did surprisingly badly and slowly. At the end, he was on his knees panting, but I could still talk to him. I couldn't heal him, nor would he get up, no matter how long I waited. There were no other Imperials left alive. If Hadvar's still on his knees at the Riften fort, perhaps that's why the Amol fort has no attackers. 134.176.247.178 09:39, 22 March 2012 (UTC)Tim Bostick

Game freezes when I use the door to the prison in the fort

Like the title says. With any of the previous fort battles, I was free to loot the interior zones afterward while they were devoid of enemies. Not this one. The game freezed twice when I tried to enter the prison section.--Playerseekingbugs 03:49, 21 July 2012 (UTC)

Confirmed with all 3 entrances (Prison, Upper and Lower Amol)71.197.154.211 01:27, 5 March 2024 (UTC)

0% Remaining = Additional Kills Are Murder?

I just finished the Battle for Fort Amol, and then the Battle for Windhelm immediately afterward. When last I checked (fairly recently), I had only one murder on my stats list. As I was walking around the Palace of the Kings after the Civil War questline was complete, an NPC made a commment about my holding my honor cheaply, so I checked my crimes page. It now shows that I have seven murders to my name, but no bounty associated with the recent murders. I did chase down and kill the Stormcloaks fleeing after the Battle for Amol, but I had done that with previous Fort-capture quests without my murder count increasing. I don't know what else it would be though. I don't have a save to go back and check, so I'm hoping someone can offer some insight here. Thanks. username12345 18:56, 3 August 2012 (UTC)

I don't know about the randomly added extra murders, but that commented was probably from Jorleif. He says it because you helped remove his previous employer, just like the female blacksmith will now want to kill you, but thankfully is not stupid enough to actually attack.--Playerseekingbugs 07:50, 25 August 2012 (UTC)

Alternate fix for bug

I encountered the bug in which I didn't have the option to tell Rikke I was reporting for duty and thus get the order to attack Fort Amol. No dragons showed up, and conjuring and killing a fire atronach did nothing except singe my eyebrows. So I went home, dismissed my follower, slept for eight hours, and returned to the camp, and this time the conversation with Rikke went as planned. If others can confirm this, I'll put it on the page. Wordmama (talk) 16:56, 14 October 2012 (GMT)

I tried sleeping there in the camp but that didn't help any. I DID find success in doing a radiant quest for Jorleif, went back to the camp and I could report for duty.- Vainamoinen-Talk-Stuff 04:54, 13 December 2012 (GMT)

It seems that sleeping in a house for so many hours and then returning to Rikke works.

Very weird series of glitches

Since I've finished Dawnguard, I decided to start the battle by summoning Durnehviir It did its thing and cut down the Stormcloak population, after which we rushed in. However, the Stormcloaks in the fort were glitching weirdly. Four of them on the wall were melted together into a single multi-arm, multi-leg, multi-head, multi-healthbar entity that could still do considerable damage with its archer component, but which was effectively immortal. Crossbow bolts and arrows fired at it went right through without any effect; fire spells and melee attacks also seemed totally useless. It lost a bit of health, less than ten per cent, but I'm not sure how. In the end, the only way to get rid of it was to bring up the console, click on each of the four soldiers that made it up, and use the "disable" command. After that, I had to deal with another multi-monster further along the wall, this one composed of three Stormcloaks, which was again almost invincible, and had to be dealt with the same way. I finally cleared off the walls and the whole exterior of the fort, but the "quest completed" indication did not come up. I then went into the fort, on the upper level, and while there was attacked by no less than three (ordinary) Stormcloaks that were still inside the building. Finally, after I killed these three, the quest reported itself completed and I got out of there before anything else happened. I wonder if Durnehviir's swooping and breath attacks were somehow the cause of these odd compounded and displaced figures. 174.6.51.17 03:45, 13 January 2013 (GMT)

No Imperials and the Stromcloaks are dead.

I encountered the bug where when you go to meet up with the Imperials, they are not there, and the quest still advances. When you go to take the Fort, all of the Stormcloaks are dead and considered "Corpses." I fixed this but by using the Console Command "player.setstage CWFortSiegeFort 100" and it spawned a bunch of Stormcloaks (which were hostile) and withing a few minutes of fighting them, the Imperials came running in, so I'm guessing it spawned the Imperials as well. — Unsigned comment by 69.42.12.188 (talk) at 20:31 on 9 February 2013