# Quest\[spoken and unspoken\] is stuck and can't continue

**URL:** <https://forum.norestforthewicked.com/t/quest-spoken-and-unspoken-is-stuck-and-cant-continue/3747>\
**Category:** Wicked Bug Reporting\
**Created:** [April 21, 2024, 8:11am UTC](https://forum.norestforthewicked.com/t/quest-spoken-and-unspoken-is-stuck-and-cant-continue/3747 "2024-04-21T08:11:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ggg](https://yyz1.discourse-cdn.com/flex003/user_avatar/forum.norestforthewicked.com/ggg/32/1857_2.png) [@ggg](https://forum.norestforthewicked.com/u/ggg)\
**Post date:** [April 21, 2024, 8:11am UTC](https://forum.norestforthewicked.com/t/quest-spoken-and-unspoken-is-stuck-and-cant-continue/3747/1 "2024-04-21T08:11:24Z")

</div>

I came here and talked to the npc before I got the old leather tome. And when I got the old leather tome the item fell to the ground because the rune backpack was full.

But now even if I had the book, the quest couldn’t continue.

 ![2024-04-21 171012](https://canada1.discourse-cdn.com/flex003/uploads/wickedforum/original/2X/e/ecc0df348196107a647524130bc996462fedcada.jpeg)

---

<div class="post-metadata">

**Author:** ![Azor](https://avatars.discourse-cdn.com/v4/letter/a/4af34b/32.png) [@Azor](https://forum.norestforthewicked.com/u/Azor)\
**Post date:** [April 22, 2024, 8:00am UTC](https://forum.norestforthewicked.com/t/quest-spoken-and-unspoken-is-stuck-and-cant-continue/3747/2 "2024-04-22T08:00:18Z")

</div>

I have the same issue here. I don’t think it was because of the full pack but anyway I have the tome but cannot trigger the dialogue to continue.

Please fix asap because this is stopping me proceeding with the storyline

---

<div class="post-metadata">

**Author:** ![Azor](https://avatars.discourse-cdn.com/v4/letter/a/4af34b/32.png) [@Azor](https://forum.norestforthewicked.com/u/Azor)\
**Post date:** [April 25, 2024, 5:54am UTC](https://forum.norestforthewicked.com/t/quest-spoken-and-unspoken-is-stuck-and-cant-continue/3747/3 "2024-04-25T05:54:27Z")

</div>

The problem still remains
