Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I have not encountered this as a bug, but, you can knock combatants unconscious then they get up and attack you again. This can happen, rarely, more than once. So, if he is unconscious you could wait a few moments to see if he gets up to continue the fight before you use the console KILL command.
It is a while since I did this quest, but, if I remember correctly you get a message when Agarmir is dead.
You wrote 0001FC540 using SetStage, 0001FC5 is Agarmir's ID not the quest ID. You would use:
"SetEssential 0001FC54 0", this sets Agarmir's to not be essential, thus killable.
SetStage is for moving to the next quest stage and isn't one word. The quest ID is MS29 and killing Agarmir is stage 90 so you should write:
"SetStage MS29 90", this sets the quest to after his death.
SetStage is a command that can't be undone without reloading, so use it only if the other command doesn't work first, but it will.