Vortex Forever

1. Reads your talents and picks the tree you have the most points in (Forever has trees, not Retail specs).
2. Each tick it takes one snapshot of you, your target and the enemies around you, then walks the tree's priority list.
3. Spells are rank-aware: it always casts the highest rank you have trained.
4. Range, line of sight, facing and the global cooldown are checked before anything is pressed.
5. In PvP mode a second layer adds crowd-control chains with diminishing returns, kicks on heals, peels and burst windows.
6. Every decision is logged as FIRED or HOLD with a reason, so a wrong cast can be traced to the exact rule.

Feasibility: High. Blizzard has published no Forever priority lists, so priorities come from the class deep dives and testing in game. First three trees (one tank, one healer, one damage) come first, then the rest.

1. Watches enemy casts and channels and matches them against a Forever kick list.
2. Picks a natural delay so interrupts do not land on the first frame.
3. Scans friendly and enemy auras for dispellable or purgeable effects by priority.
4. Predicts incoming damage and triggers your defensive cooldowns at a threshold you set.
5. Works together with the loader's own universal modules instead of fighting them.

Feasibility: High. The kick, dispel and danger lists for Forever's dungeons and raids are ours to build and grow from logs.

1. Knows which of your buffs are party-wide or raid-wide (Forever made Battle Shout, Trueshot Aura, Moonkin Aura, Leader of the Pack and several totems raid-wide).
2. Rebuffs out of combat, or in combat when a buff is about to fall off and nothing more urgent is waiting.
3. Records every important cooldown when it is used, so the rotation and the HUD know when it is back.

Feasibility: High. The loader's cooldown tracker has no Forever list, so the plugin keeps its own. Beta values may still change.

1. Holds a talent build per tree (51 points at level 60, talents from level 10).
2. On every level-up it spends the new point on the next talent of your build.
3. Plans a trainer visit when new ranks are available and buys them.
4. Switches between your two builds once dual spec unlocks at level 40.

Feasibility: Medium. The exact link between Forever's talent trees and the game's talent API is still to be confirmed in game.

1. Plans the next eligible quest from the quest database (level, prerequisites, chain order).
2. Walks to the quest giver using the navigation layer and highlights them.
3. Talks to them, accepts the quest and confirms it in the quest log.
4. Works the objectives: kill and collect targets come from the database, with positions where known.
5. Walks to the NPC who takes the quest back, turns it in and chooses the reward by upgrade value or sell price.
6. Verifies the quest is completed and moves on to the next one in the chain.

Feasibility: Medium. Quest givers are known for about 91% of Forever quests. The NPC who takes a quest back is known for about half, so the quest recorder fills the rest as people play.

1. When you pick up or hand in a quest, it notes the quest, the NPC and your position.
2. Never saves your character, realm, account, chat or any game ids that identify you.
3. Stores the rows locally; uploads them only if you switch sharing on.
4. A position counts as confirmed once at least two players report the same NPC in the same place.
5. Confirmed positions go into the next data update that the questing module uses.

Feasibility: High. Off by default. Upload only after you opt in.

1. Chooses the best activity for your level: quests in range, a grind spot, or travel to the next zone.
2. On level-up: spends the talent point, trains new ranks, equips upgrades.
3. Eats and drinks when low, repairs and sells when bags are full.
4. On death: releases, runs back to the corpse and resumes.
5. Starts the new Skyborne race on Zephras Isle with its own route.

Feasibility: Medium. Needs questing and navigation first. Data gets rebuilt from the first live build after launch before this phase starts.

1. Lists every achievement and its criteria from the game data.
2. Infers progress where a criterion is tied to a quest, treasure or rare.
3. Shows what is left and, where known, where to go for it.

Feasibility: Low. The loader cannot read your earned achievements yet, so most criteria stay manual until it can.

1. Converts map positions to world positions.
2. Plans ground paths with the loader's navigation server; falls back to recorded routes.
3. Uses the flight graph (100 flight points) when it beats walking.
4. Detects being stuck and replans.

Feasibility: Medium. The navigation mesh for Forever's maps is not documented yet. The travel layer is swappable so a fallback always exists.

1. Follows a route you recorded or picked.
2. Finds targets by their game id (Forever scrambles the per-object ids).
3. Fights with your rotation, then loots and skins.
4. Steps aside from other players and elites as you choose.
5. Sells and repairs when bags are full, then returns to the route.

Feasibility: Medium. No public data has herb, ore or mob spawn points, so routes are recorded in game.

1. Picks up loot from corpses in range, retrying if a window does not open.
2. Follows your rules: gold only, whitelist or everything, plus roll rules in groups.
3. Confirms bind-on-pickup prompts only when you allow it and stops when bags are full.

Feasibility: High. None known.

1. Reads NPC flags and quest markers around you.
2. Matches them against your quest plan.
3. Draws a glow, ring or label in the colour of each category.

Feasibility: High. None known.

1. Knows the shape and size of dangerous boss spells and live missiles.
2. Draws them on the ground and, if you allow it, moves you to a safe spot.
3. Shows enemy players, range rings and your planned path.
4. Draws lines to treasures, rares and quest objects (67 treasures and 378 rares are known).

Feasibility: High. The danger-spell list for Forever's dungeons and raids is built and grown over time.

1. A dock bar to switch modules on and off.
2. HUDs for the global cooldown, casts, kicks, buffs, quest tracker and farm stats.
3. Settings pages per module and per tree, with profiles you can import and export.
4. Notifications for anything that needs you.

Feasibility: High. None known.

1. Opens the vendor, sells by your rules, repairs.
2. Collects mail and sends items you set to send.

Feasibility: High. Selling is done the same way the game does when you right-click an item at a vendor.

1. Searches, posts and cancels within the auction house limits.
2. Crafts queued recipes.
3. Fishes with the loader's fishing helper.

Feasibility: High. A price source for Forever is still to be found.

1. Queues, accepts and plays the battleground with the PvP rotation.
2. Lists event tasks (Scourge Invasion, Ahn'Qiraj War Effort, holidays) as they come.

Feasibility: High. Event dates are confirmed in game.

1. Each system is checked against what the loader can do before it gets a module.

Feasibility: Medium. Feasibility is decided one system at a time.

1. Refuses pulls above a level gap or with elites you did not allow.
2. Watches health and predicted incoming damage and escapes early.
3. No unattended mode by default; stops on anything it does not recognise.

Feasibility: Medium. Hardcore arrives after launch; detecting the ruleset is checked in game.

1. Tracks flagged state and nearby enemy players.
2. Alerts you and pauses automation when you choose.

Feasibility: High. None known.

1. Releases, runs to the corpse and resurrects.
2. Replans the path when stuck.
3. Logs back in after a disconnect.

Feasibility: Medium. Corpse position reads wrong on Forever today, so the plugin keeps the position where you died. Relog is only proven on another game version so far.

1. Logs at five levels with one tag per feature, into a rotating file next to the loader.
2. Keeps the last lines in memory for the in-game log page and for crash evidence.
3. If you opt in, sends errors and feature health in small batches after combat.
4. Never sends character, realm or account names unless you choose to; never sends chat.
5. Errors are grouped on the developer dashboard; each group gets a fix, a version, and is watched for coming back.

Feasibility: High. Uploads are opt-in. Fixes are reviewed before they ship.

1. Import and export profiles.
2. Checks the latest version and changelog from this site.
3. Reloads the plugin in place.

Feasibility: High. None known.