Details

Addon ID: 25691
Addon Version: 1.0.4
Expansion: 1.60
Upload date: Oct 06, 2026
Last Updated: Oct 06, 2026
Downloads: Less than 100
Website: Source Link

Expansion



Developers

walord3
walord3 Creator

This addon has moved. Auto quest is now built into ForeverForge, the core of the ForeverForge suite for WoW: Forever, and that is where every update goes. This version is no longer updated - please install ForeverForge, then disable or delete this one. Questions or bugs: ForeverForge Discord

Forever AutoQuest

Stop clicking through quest dialogs. Forever AutoQuest accepts and turns in quests for you, so you can keep moving.

Built specifically for the WoW: Forever client.


✨ Features

  • Auto-accept quests. Talk to a quest giver and available quests are picked up automatically.
  • Auto turn-in. Completed quests are handed in without any extra clicks through the dialogs.
  • Classic-only mode. Limits the automation to original Classic quests by filtering on quest ID, so newer or custom content is left for you to handle yourself.
  • Lightweight. No bulky options window; it does its job and stays out of the way.

⌨️ Slash Commands

CommandDescription
/faqOpens the Forever AutoQuest commands
/autoquestAlias for /faq

💾 Saving Your Settings

The Forever client writes SavedVariables but doesn't load them back at login. To make your settings survive every login and /reload, Forever AutoQuest reads them from StartupProfile.lua in the addon folder.

  1. Set things up the way you like in-game.
  2. Copy your settings into StartupProfile.lua inside the ForeverAutoQuest folder.
  3. They'll load automatically every time. You won't need to re-import anything.

📦 Installation

  1. Download the latest release.
  2. Extract the ForeverAutoQuest folder into your InterfaceAddOns directory.
  3. Restart the game, or /reload if it's already running.

📝 Changelog

See the Changelog tab for the full version history.


🐞 Bugs & Suggestions

Found a problem or have an idea? Leave a comment or open an issue on the project page. Please include your version number and what you were doing when it happened.

You must be logged in to leave a comment.

Comments (0)