Troubleshooting & FAQ

A frame is off-screen or in the wrong place

/fui frames lists the frames you can move. /fui reset <frame> puts one back in its default spot, and /fui reset all (or Reset all positions under General → Layout in /fui) puts every frame back.

To place frames yourself, type /fui unlock (“Unlocked: drag the handles. /fui lock when done.”), drag the handles, then /fui lock.

Source: Core/Slash.lua (frames, reset, unlock), Core/Options.lua (General: Layout) in the ForeverUI addon repository.

Colors or fonts look wrong

/fui theme reset puts every theme setting back to default (it's also the Reset theme button under General → Look). /fui accent reset resets only the accent color.

Source: Core/Slash.lua (theme, accent), Core/Options.lua (General: Look) in the ForeverUI addon repository.

One part of ForeverUI misbehaves

Type /fui modules to see the parts (modules), then /fui disable <module> and /reload. The README says: “Turn any module off under Modules to keep the default one.” The options window's Modules page adds: “A module that's off builds nothing and costs nothing.”

/fui enable <module> and /reload bring it back. Please report what went wrong.

Source: Core/Slash.lua (modules, enable, disable), Core/Options.lua (Modules page), README.md (Options) in the ForeverUI addon repository.

Chat says a module “failed to load”

In v0.3.0, when a part hits an error while it starts, ForeverUI prints “module ΓǪ failed to load: ΓǪ” and keeps loading the others. Turn that part off (see above) and put the whole line in your report.

Next release Errors like this are listed by /fui errors instead: an error in one module, skin, event handler or after-combat update is kept here and doesn't stop the others.

Source: Core/Modules.lua (v0.3.0), README.md (Commands: /fui errors) in the ForeverUI addon repository.

Everything is broken

/fui profile reset puts the profile you're using back to defaults (“Profile <name> is back to defaults.”), then reload.

To test without losing your settings, switch this character to a new, empty profile instead: /fui profile Test. In v0.3.0 the switch is at once (“This character now uses profile <name>.”). Next release It happens at your next reload: “This character will use profile <name> after the reload.” See Profiles.

Source: Core/Slash.lua (profile, profile reset) in the ForeverUI addon repository.

Import failed

When an import string can't be used, ForeverUI says “Import failed:” and one of these reasons:

• ΓÇ£not a ForeverUI profile stringΓÇ¥
• ΓÇ£the string is incomplete (was it cut off when pasting?)ΓÇ¥
• ΓÇ£the string is damagedΓÇ¥
• ΓÇ£the settings in it can't be readΓÇ¥

Most often the string was cut off when it was copied or pasted: export it again and copy all of it.

Source: Core/Serialize.lua, Core/Slash.lua (import) in the ForeverUI addon repository.

Some numbers don't show in instances

The game client hides some values from addons, for example in instanced combat. The README says those values “go to the bars unread”: the bars still fill, but ForeverUI can't print a number it isn't allowed to read. This is expected.

Next release /fui status says when aura values are “hidden right now”.

Source: README.md (what the client hides), Core/Slash.lua (status) in the ForeverUI addon repository.

A setting didn't change anything

Settings marked Needs reload on the Settings page apply after a reload. In v0.3.0, type /reload in chat: that release's Reload now button asks the game to reload directly, and WoW Forever blocks that for addons.

Next release The Reload buttons are made the way WoW Forever allows. One made during a fight works once the fight ends; until then it says “Type /reload in chat to apply the change (the game only lets addons reload out of combat).”

Source: Core/OptionsWindow.lua (v0.3.0), Core/Dialog.lua, README.md (Options: reloads on WoW Forever) in the ForeverUI addon repository.

Something won't change during a fight

Some changes can't be made while you're in combat. ForeverUI holds them and makes them when the fight ends. The second line of /fui status counts them: “<n> change(s) waiting on combat”.

Source: Core/Slash.lua (status) in the ForeverUI addon repository.

My settings reset every time I start the game

The addon's code notes that WoW Forever beta builds older than 70009 lose addon settings at every launch, and break the raid frames, click casting and bar paging. Update the game.

Next release On an older build, /fui status says: “update the game: this build loses settings at every launch”.

Source: Core/Slash.lua (FIXED_BUILD, status) in the ForeverUI addon repository.

Hover keys don't work Next release

Some WoW Forever beta clients can't run the code hover keys need. ForeverUI then says at login: “This client can't run secure snippets: hover keys are off; bar 1 pages and the raid frames are set up without them.”, and /fui status shows “secure snippets: no (hover keys off)”. The Click casting page says: “This client can't compile the secure code hover keys need; mouse bindings still work.”

Mouse click casting still works, bar 1 still changes with stances, forms and Shift+number, and the raid frames still work.

Source: Core/Client.lua, Core/Slash.lua (status), Modules/ClickCastOptions.lua (hover keys), README.md (secure snippets) in the ForeverUI addon repository.

The setup wizard didn't open Next release

The setup wizard opens the first time you log in on an account. If you're in a fight it waits: “Setup opens when combat ends.” Once you've finished or closed it, it doesn't come back on its own: type /fui setup to open it again.

Source: Core/Setup.lua, README.md (First-run setup) in the ForeverUI addon repository.

ForeverUI's frames don't show in Edit Mode Next release

When you open the game's Edit Mode, ForeverUI's handles show too, with a note: “The labeled handles are ForeverUI's frames: drag them here too (right-click one for more).” If they don't, tick Show these handles in the game's Edit Mode too under General → Layout in /fui.

The game frames that ForeverUI hides or replaces (its action bars, XP and reputation bars, unit frames and so on) get no Edit Mode handle on purpose. Move ForeverUI's frames instead.

Source: Core/Movers.lua (Edit Mode), Core/Options.lua (General: Layout), README.md (Look and layout) in the ForeverUI addon repository.

Chat says my profile uses an Edit Mode layout this account doesn't have Next release

A profile remembers which of the game's Edit Mode layouts you use with it. When a character loads that profile, ForeverUI switches Edit Mode to the layout of that name, if your account has one. If it doesn't, ForeverUI says “Profile <name> uses Edit Mode layout <layout>, which this account doesn't have.” and leaves Edit Mode as it is.

Source: Core/Profiles.lua (Edit Mode layout), README.md (Look and layout) in the ForeverUI addon repository.

There's a red number on the addons button Next release

That's how many errors ForeverUI caught this session. The options window's footer says the same (“<n> errors caught this session: click to list them”). Type /fui errors to list them for a bug report, and /fui errors clear to empty the list; the number goes away. With nothing caught, /fui errors says “No errors caught this session.”

Source: Core/ErrorBadge.lua, Core/Slash.lua (errors), README.md (Options) in the ForeverUI addon repository.

Is ForeverUI slowing my game down? Next release

/fui perf shows ForeverUI's CPU time and memory now, and its ten busiest functions. To measure ForeverUI's CPU cost yourself:

1. Type /fui perf cpu, then /reload.
2. Play a while (a raid pull is the hard case).
3. Type /fui perf and read the numbers.
4. Type /fui perf cpu and /reload again to turn measuring off: it slows every addon a little, so turn it off when done.

No performance numbers are published yet.

Source: README.md (Commands: /fui perf), Core/Perf.lua in the ForeverUI addon repository.