Maintenance for the week of November 25:
• PC/Mac: NA and EU megaservers for maintenance – November 25, 4:00AM EST (9:00 UTC) - 7:00AM EST (12:00 UTC)
• Xbox: NA and EU megaservers for maintenance – November 27, 6:00AM EST (11:00 UTC) - 9:00AM EST (14:00 UTC)
• PlayStation®: NA and EU megaservers for maintenance – November 27, 6:00AM EST (11:00 UTC) - 9:00AM EST (14:00 UTC)

Black Sacrament: kill Lucky bonus objective- lucky respawns causing failure

vrumpet
vrumpet
Doing a black sacrament today and the bonus objective was to kill Lucky, the neutral kagouti.

I did this first, it registered as complete and I went on to kill the main target. As I approached the exit with plenty of time to spare and no alerts, my journal updated and I saw text saying that the bonus objective had failed, confused, I ran back to the first area and saw that Lucky had respawned.

Killing Lucky again did not help as the quest entry had already registered as failed.
  • Braffin
    Braffin
    ✭✭✭✭✭
    ✭✭✭
    Are you sure it wasn't another bonus objective, which failed, like staying in time or killing the main target (today was Borcholim) with poison?

    Never had problems with Lucky, and was also fine for me today.
    Never get between a cat and it's candy!
    ---
    Overland difficulty scaling is desperately needed. 9 years. 6 paid expansions. 24 DLCs. 40 game changing updates including One Tamriel, an overhaul of the game including a permanent CP160 gear cap and ridiculous power creep thereafter. I'm sick and tired of hearing about Cadwell Silver & Gold as a "you think you do but you don't" - tier deflection to any criticism regarding the lack of overland difficulty in the game. I'm bored of dungeons, I'm bored of trials; make a personal difficulty slider for overland. It's not that hard.
  • vrumpet
    vrumpet
    I also have never had problems with Lucky before, though I can't say whether I have noticed him respawn or not.

    It definitely wasn't time running out. I had a clear run back with no delays.

    The only other failure that was possible was the poison did not count for some reason. Unfortunately it doesn't tell you which objective failed, so I can't be sure.

    When I killed the main target, there was no message of failure to suggest the poison failed, it only popped up at the exit when the quest entry updates to tell you to speak to the quest giver. Perhaps the bug (or oversight) is the failure message not triggering in the correct place.
Sign In or Register to comment.