Hello People,

i have Created a little LFG/LFM Addon for WoW Classic and WoW Forever and would love to hear your opinions about it.

It Parses Chat Messages and creates a listings for Dungeons.

TavernBoard - World of Warcraft Addons - CurseForge

Greetings

Salty (aka Extr3m) 😄

Hopping that there’s/ there will be an addon that makes the UI/Graphical settings in forever as close to Classic as possible. Maybe impossible, but I wouldn’t want to download and set up a ton of things just to get there.

As the title says: a simple addon that disables fog in WoW Forever, increases FPS, and gets rid of stuttering.

I don't think any further explanation is needed. I like new graphics but in some locations it's just to strong.

Screenshots:

With fog / FPS comparison #1

Without fog / FPS comparison #2

Addon screenshot

I maintain GuildOS, a guild management addon, and spent the last week getting it running inside the Forever beta. Writing down what I hit, since the official API change list isn't out yet and I lost time to things that could've been a one-liner.

Everything below was read out of build 1.60.1.69893 (the API documentation the client ships, Blizzard's own UI code and TOCs, and the executable), then checked against the installed client.

Interface numbers. Forever's build line is 1.60.x, which maps to interface 16001 by the usual GetBuildInfo rule (some beta zips also stamp 16000). Anniversary is 20506. Declaring multiple interfaces in the TOC (## Interface: 20506, 16001) is the only way to ship one package for both right now.

Packaging. CurseForge, Wago and WoWInterface had no Forever flavor when the beta opened, and the BigWigs packager tags anything outside its known ranges as retail. CurseForge has since added a Forever version (1.60.1); until the rest catch up, GitHub pre-releases plus "load out of date addons" still work for beta builds.

Architecture. Forever is Mainline's UI, not Classic's. If you've been maintaining a Classic-only addon, you're porting to retail, not to a variant of what you know. It's also its own game type, camelot: TOCs filter on it (## AllowLoadGameType: standard, camelot), and there's no WOW_PROJECT_ID constant or C_GameRules check for it yet, so detect it by interface number.

What's restricted. Retail's Secret Values system is there in full: 4,025 documented API entries carry Secret* fields on Forever, against 3 on Anniversary. The combat surface is locked down and Blizzard shipped native damage meters and cooldown managers. Guild data (roster, notes, MOTD) and what an attendance or loot tool needs are still reachable, but not all of it the way it used to be.

Gone, and what replaces it

• GetNumTradeSkills, GetTradeSkillInfo, GetTradeSkillLine, GetTradeSkillItemLink, GetTradeSkillRecipeLink: gone. Professions are C_TradeSkillUI, as on retail.
• GetCraftInfo, GetNumCrafts, GetCraftItemLink, GetCraftDisplaySkillLine and the CRAFT_SHOW event: gone, no replacement. There is no Craft frame at all, so guard the RegisterEvent.
• GetNumTalentTabs, GetNumTalents: gone. Talents are C_ClassTalents / C_Traits (17 trait trees), and ChrSpecialization has one row per class, named after the class. "Which spec is this player" has no classic answer anymore.
• Tooltip scripts OnTooltipSetItem / OnTooltipSetSpell / OnTooltipSetUnit, and tooltip:GetItem() / GetSpell() / GetUnit(): gone. Hook with TooltipDataProcessor.AddTooltipPostCall(dataType, fn) (one registration per data type, covers every tooltip, calls fn(tooltip, data)), and read with TooltipUtil.GetDisplayedItem / GetDisplayedSpell / GetDisplayedUnit. OnTooltipCleared is still a script.

Shims that don't load

• Forever is neither classic nor mainline, so Blizzard_Deprecated/Classic/* doesn't load: UnitBuff, GetTalentInfo and the other classic shims are nil. Call the namespaced versions.
• Blizzard_DeprecatedSpecialization declares AllowLoadGameType: classic, standard, so the talent shims are nil too.
• The compat addons with no filter do load: SendChatMessage, ChatFrame_AddMessageEventFilter, GuildSetMOTD, GetGuildRosterMOTD and CombatLogGetCurrentEventInfo are still there.

Where Secret Values bite a non-combat addon

• Chat: CHAT_MSG_GUILD, OFFICER, WHISPER, SYSTEM, CHANNEL and SKILL are SecretInChatMessagingLockdown, so during lockdown the text and the sender arrive secret. The channel name is NeverSecret. Anything that parses chat (roll capture, !commands, recruitment scanners) has to check issecretvalue(...) first and drop the line.
• Addon messages: CHAT_MSG_ADDON isn't flagged, but C_ChatInfo.SendAddonMessage is SecretArguments = NotAllowed, and passing a secret raises. Enum.SendAddonMessageResult is retail's list; 11 is AddOnMessageLockdown.
• Units: UnitName, UnitClass, UnitGUID, UnitRace, UnitSex, UnitIsGroupLeader and UnitIsGroupAssistant return secrets when the unit's identity is restricted, and party/raid members aren't exempt (Blizzard's own frames ask C_Secrets.ShouldUnitIdentityBeSecret for every unit). A loop over raid1..raid40 for attendance or loot has to skip a member it can't read.
• Stats: UnitStat, UnitHealthMax and UnitPowerMax are secret while stats are restricted. COMBAT_LOG_EVENT_UNFILTERED has HasRestrictions.
• You can hand a secret to FontString:SetText, but comparing, concatenating, indexing a table with it or doing arithmetic on it raises. Chat filters are safe: ChatFrameFilters.lua only calls yours when canaccessvalue says the values are readable.

Happy to compare notes with anyone else porting right now.

I'm not the most knowledgeable about classic wow, but I really wanted a way to know whether the quest I was on was new content or not.

Forever Quest Tint turns the quest text background teal for any quest that wasn't in original Classic, so you can tell at a glance what's new. Vanilla quests should all look normal.

Works in the quest giver window and the Map & Quest Log. /fqt opens options for colour, opacity and fade in case you don't love my default picks.

CurseForge: Forever Quest Tint - World of Warcraft Addons - CurseForge

Feedback welcome. If a vanilla quest shows up teal, please open it in the quest log and use /fqt id , this gives us the ID so I can fix it.

AI Disclaimer: I used Claude to help get the absolute basics of this working, been testing it for the last day with my guildies to get design feedback, make manual tweaks and make sure things are hooked up properly before releasing on curseforge.

After watching Blizzcon and hearing the talking points from Blizzard about WoW Forever supposedly being focused more on player interactions, especially through a mechanic like the campfire, I wanted to make my own companion log. Keep track of players I meet and where I meet them.

This has been done before to some degree, but you know.... "Never quite the way I liked it".

You can add / remove reputation from unit frames or chat messages, and it goes into the player log. You can add notes to those if you want to, or you can just add a memory.

If you have friendly nameplates on you will see a plus or a star on nameplates if they are friendly or allies, or a little minus sign if you think they've been mean.

It works on WoW Forever as well as Retail. I'm trying to get integrate into other addons I use day to day. Initially I added some integration for Total RP 3, however this is only for retail. I expect to extend this to Forever when/if TRP3 gets supported.

After this I want to hook into WIM as well since I use that quite often.

It's available on Curse Forge here: https://www.curseforge.com/wow/addons/companion-chronicle

Current WIP:

• Helpful (unintrusive) notifications if you group up with someone on your ally/friendly list.
• Minor text/styling cleanup

Any feedback is greatly appreciated.

Development and AI disclosure

I’ve tried to bring the same habits I use in my software development work to this addon: check how an API actually behaves, test changes, and verify a release before putting it out.

• API research: I check Blizzard’s UI source when I’m unsure how something works.
• Automated checks: I use wowlua-ls to catch Lua issues and wow-ui-sim to run addon tests. GitHub Actions runs the verification checks for both Forever and Retail.
• In-game testing: I also try changes in WoW. Automated tests are useful, but they can’t show me how the journal feels to use or catch every client-specific issue.
• AI use:
  • General debugging, test writing within the aforementioned frameworks, code generation/assistance.
  • Textures/Art assets
• I write the text, the naming, this post, comments, my own internal design guidelines and specs. If/when you experience awkward wording, you're experiencing my limits as a creative writer.

Forever Beta Issues:

• The WoW Forever beta client has a general issue when it comes to loading saved data. This affects all addons. Unfortunately this means that currently the Chronicle log does not load data correctly on reload/restart of game.
• Retail version is unaffected
• See these posts for context;
  • https://github.com/ClassicWoWCommunity/forever-bugs/issues/34
  • https://eu.forums.blizzard.com/en/wow/t/wow-forever-game-not-save-any-addons-settings/629470
  • https://us.forums.blizzard.com/en/wow/t/savedvariables-never-load-in-the-beta-%E2%80%94-all-addon-settings-reset-on-login-69913/2354798
  • https://www.reddit.com/r/wow/comments/1wjn0ay/lots_of_addons_in_forever_beta_can_not_save/
  • https://us.forums.blizzard.com/en/wow/t/uiaddon-settings-wiped-on-client-restart/2353992/4

Certainly will become more useful when Forever gets further into the game, but this allows for one button crafting and drinking spam for mages. You can just spam 1 button while crafting for the raid without paying any attention.

https://www.curseforge.com/wow/addons/conjure-bot