Plater’s author master branch declares a Forever packaging target and interface 16001. Before importing a profile, check that the Plater Nameplates release itself explicitly includes Forever. The source declares Interface-Camelot: 16001 and a Forever version block, but those are development and packaging declarations. They do not identify a verified published version or confirm every script you intend to use.
Plater is a configurable nameplate addon maintained by Team Details!, with cont1nuity named as its main maintainer. Its general features include threat coloring, aura tracking, unit-type settings and scripting. Treat the addon, an imported profile and any additional scripts as separate compatibility decisions. The Forever source version is a packaging placeholder, so it cannot by itself tell you which downloadable release contains these changes.
Choose Plater Nameplates, not a similar name
The project you are looking for is Plater Nameplates. An addon called WoW Forever Nameplates is a different project: its description says it brings the Forever nameplate style to Retail, and its file is marked Retail.
That distinction is easy to miss when searching by appearance. A title containing Forever can describe a visual style copied into another game branch. Read the stated target and file flavor rather than choosing by the name alone.
Separate the base addon from the profile
Plater offers settings for different unit types, including enemy players and NPCs, and supports profiles, mods and scripts. Those layers do different jobs.
| Layer | What you are choosing | Check before relying on it |
|---|---|---|
| Base addon | Plater Nameplates itself | Explicit Forever support for that release |
| Profile | A collection of presentation settings | Intended branch and required Plater version |
| Mod or script | Additional behavior or effects | Its own requirements and supported inputs |
| Companion update workflow | Keeping imported content updated | Whether the content and workflow apply to your setup |
A profile that imports without an immediate error is not proof that every behavior works in combat. Similarly, a base nameplate appearing on screen does not verify its aura tracking or a script's assumptions.
Start with the base addon and a simple layout. Only add the profile or script that addresses a specific missing need, keeping enough information to identify which addition changed the result.
The author master branch declares the 16001 target; imported profiles and scripts still require separate checks.
Make the first check about readability
Once you have an explicitly supported file, begin with the information you need to recognize a target: its nameplate, readable text and a clear indication of your selected unit. Then evaluate any extra display you intend to use.
The general project supports different settings for enemy players and enemy NPCs. A change intended for one category may not explain what you see on another. Check the relevant category before changing every plate setting at once.
If a setup uses threat colors, learn what those colors mean for your role. A color designed to warn a damage dealer about having aggro can have a different meaning in a tanking layout. Do not copy a screenshot's color interpretation without checking the profile's actual configuration.
These are checks for the configuration you have chosen, not a claim that every historical Plater option remains available in Forever.
Treat scripts as additional requirements
The project's general documentation describes Lua scripting and mod-specific settings. Scripts can therefore depend on more than the visual layout of a health bar.
Before adding one, identify the information it reads and what it is supposed to change. Forever restricts computational combat addons; an older script's description does not prove that all of its assumptions remain valid.
Plater also documents updating profiles, mods and scripts through WeakAuras Companion. That describes a content-update integration, not proof that the original WeakAuras has a Forever release or that the downloaded script supports this client.
For a first configuration, avoid bundling several unknown scripts with an imported profile. Evaluate the necessary behavior individually so you can retain the readable base layout if an addition fails.
Compare a profile against your actual targeting task
Choose a profile by the information you need to recognize, not by how much it changes the screen. Write down the problem first: perhaps several enemy plates look too similar, the selected target is hard to distinguish, or text is difficult to read. This gives you a specific result to compare after a change.
For a file with confirmed Forever support, evaluate the simplest presentation settings before adding more behavior. Inspect one ordinary target, then a situation with several visible units. Confirm that the name you intend to select remains readable and that you can distinguish the selected unit without relying on an unfamiliar color rule.
Keep the comparison fair. Change the relevant layout setting or profile, then inspect the same kind of situation. Adding a profile, several scripts and another nameplate addon at once makes it difficult to identify which change produced an improvement or a failure.
Separate the role you play from the role the profile expects. If a profile's documentation describes tank warnings, do not assume its colors have the same meaning for a damage dealer. If the documentation does not explain the colors at all, establish their meaning before making them the basis of a combat decision.
Record the difference between appearance and information
A nameplate setup has passed a visual check when you can read and identify what it displays. Information-dependent behavior needs its own comparison. A readable bar does not establish that every icon, timer or threat-dependent effect is accurate.
Use a short record when evaluating an addition:
| Record | Why it matters |
|---|---|
| Base Plater release | Identifies the code underneath the layout |
| Profile name and intended branch | Identifies the configuration you imported |
| Extra mods or scripts | Separates optional behavior from the base addon |
| Unit type and situation | Distinguishes one category's settings from a general failure |
| Expected and observed result | Gives the next check a concrete target |
If you cannot explain what an icon or color is supposed to mean, more customization is unlikely to resolve the uncertainty. Review the profile or script description, or remove that addition from the comparison while keeping the readable base arrangement.
Keep a usable fallback while evaluating changes
Before relying on a new setup, retain a way to return to the layout you could already read. The goal is to make targeting clearer, so a configuration that requires guessing during a fight has not met that goal.
If a profile improves readability but one script fails, separate those results. You may be able to keep the useful presentation while leaving the unverified addition disabled, provided the profile's own requirements allow that arrangement. Do not describe the entire bundle as working because one part looks correct.
After an update, return to the specific behavior that failed. A newer version is a reason to check again, not proof that the import and every dependency are now compatible. This keeps the decision tied to your actual targeting needs instead of an ever-growing list of installed effects.
Diagnose a missing plate differently from a failing script
If the base addon does not appear, establish the installed project and file flavor first. If it appears but an imported effect does not, return to the effect's requirements rather than replacing the entire addon immediately.
When only one unit type behaves unexpectedly, compare that category's settings. When an error begins after an import, retain the import name and the action that caused it. For a useful report, record the Plater version, game version, profile and mod names, and the first complete error.
An October 3 player report about a broken beta setup does not prove the same fault exists in the launch client. It also does not justify editing version numbers to force a package to load. Prefer an author-supported release over a workaround whose effect you cannot establish.
If you cannot identify a supported file, keep a nameplate setup you can already use. The point of the change is to recognize targets and relevant information reliably, and that requires more than reproducing a popular screenshot.