Reskins MountsJournal to match EllesmereUI.
You need MountsJournal, and EllesmereUI: either the full suite or any one of its standalone addons, such as Standalone Raid & Party Frames. This addon contains no part of either, and if you're not running both it quietly does nothing.
The whole idea is that it follows your EllesmereUI setup rather than imposing a look of its own. Window colour, transparency, accent, font and border all come from your active profile, read fresh each time. Change something in EllesmereUI and the journal changes with it.
- Rematch EllesmereUI Skin is this same skin for Rematch, the pet journal one tab over, built on the same foundation so the two Collections tabs match each other as well as the rest of your UI.
- Or try my other addon, Postbox, a full mailbox replacement: clear a full inbox in one click or just the mail you choose, complete recipients as you type, and see what is waiting without visiting a mailbox. It wears your EllesmereUI or ElvUI look.
Drop the folder into World of Warcraft/_retail_/Interface/AddOns/, or grab it
from the releases page with your addon manager.
Nothing is hardcoded, and no profile gets special treatment. Imports like atrocityUI or AES work simply because they write these same values.
| Look | Where it comes from |
|---|---|
| Window colour and transparency | EllesmereUI.GetDarkModeFill(), your profile's Dark Mode fill, colour and alpha both |
| Accent (selections, checkmarks, sliders) | EllesmereUI.ELLESMERE_GREEN |
| UI font | EllesmereUI.GetFontPath("blizzardSkin") |
| Window border | EllesmereUIDB.windowBorderTexture and windowBorderSize, including a size of 0 meaning no border |
| Window style | EllesmereUI.GetBlizzWindowStyle("collections") |
These get re-read every time something is painted, never cached. Switch profile, reopen the journal, done. There's nothing to import or keep in sync.
On a standalone addon the same values come from that addon's own copy of EllesmereUI. It has no window border or window style settings, so there "Follow EllesmereUI" means no border, and the window style is the default one.
Game Menu > Options > AddOns > MountsJournal EllesmereUI Skin
| Setting | Default | What it does |
|---|---|---|
| Window backdrop | EllesmereUI Dark Mode | Uses your Dark Mode colour and alpha. The other choice, Blizzard window art, uses EllesmereUI's own window texture, which is fully opaque and can't be made see through. |
| Follow EllesmereUI opacity | on | Uses your Dark Mode alpha. Turn it off if you'd rather set the transparency yourself. |
| Opacity | 90 | Your own transparency setting. Ignored while the option above is on. |
| Window edge | Thin dark line | A crisp 1px edge. The alternative, EllesmereUI window frame, matches its windows exactly but brings a soft inner shading with it. |
| Border style | Follow EllesmereUI | Whatever border you've set in EllesmereUI's own options, texture and size. You can also pick one yourself from its border list, including Glow, Shadow and any LibSharedMedia borders. |
| Border size | 2 | Thickness, 1 to 4. Ignored while following EllesmereUI. |
MountsJournal's own frames, all over: the journal window, the mount and pet
lists, the filter bar, the map and model tabs, and the config, rules, snippets
and icon picker windows. Art is only ever faded, never hidden. Nothing is
reparented or has its scripts replaced, and every hook is a HookScript or
hooksecurefunc.
Blizzard's Collections and MountJournal frames, in one specific way. Their chrome is faded while the journal is open and put back when it closes. MountsJournal parents its window inside Blizzard's mount journal, so both sit right behind it, and without this they'd show through a transparent backdrop. Only regions are touched, never frames, and only the parts that actually overlap our window. The Collections tab row underneath is left alone.
The Model/Map/Settings row follows whatever the Collections tabs next to it wear. If atrocityUI (atrocityEssentials) is skinning that row, ours take the same flat plate, hover, font and selected tint, read live from the row beside them. If EllesmereUI's own Blizzard skin is dressing it, ours get the same treatment. If it's stock Blizzard, ours are left completely alone, since they're the same widget and already match.
Cost is a one off pass at login plus hooks. There's no OnUpdate, no polling and
no per frame work, and the internal registries use weak keys so recycled rows can
still be collected.
/mjeuiskin tells you what actually ran: which backend is live, the colours and
border it resolved, and any stage that failed along with the Lua error. Each
section is isolated, so if a frame moves in a MountsJournal update you lose that
section rather than the whole window.
There are two more focused commands. /mjeuiskin behind lists anything still
drawing behind the window, biggest first. /mjeuiskin tabs compares our tab
row against the Collections row beside it: where each tab and its label sit,
the label's font and colour, and the visible art. Both print what the frames
really carry, which is usually the fastest way to tell a bug here apart from a
Blizzard, EllesmereUI or MountsJournal change. If something looks like it
moved, run tabs before and after and compare the two. /mjeuiskin list and
/mjeuiskin pet do the same for the list column and the pet button.
Right-clicking the resize grip snaps the window back to its smallest size, which is the same size as the other Collections tabs. Hover the grip and it says so.
Works on EllesmereUI 8.6.6 and newer. On 8.6.8+ with the Blizzard Skin child
addon running, it registers through the official skinning API: the skin shows
up under EllesmereUI's Blizzard Window Skins > Third-Party Addons and follows
its toggles there, and a live accent or profile change repaints the journal
without a reload. The window shell, scroll bars and checkboxes are always
drawn by this addon itself, so the look is identical on every version and the
backdrop and opacity options keep working. On 8.6.6, or without the child
addon, the same set of primitives is rebuilt from the public helpers
EllesmereUI does export. You don't need to do anything either way, and
/mjeuiskin will tell you which backend is running.
EllesmereUI's standalone addons (Standalone Raid & Party Frames and its siblings) work too. Each one carries its own copy of EllesmereUI, and the skin uses whichever EllesmereUI is running, the full suite first. None of them include the Blizzard Skin module, so they always take the second route, which looks the same. Checked against all twelve standalone addons at 9.3.
GPLv3. This is a derivative work of MountsJournal ElvUI Skin by sfmict. The map of which frames need skinning came from there; the EllesmereUI implementation is new. Thanks to sfmict, who wrote both MountsJournal and the ElvUI skin this was translated from, and to EllesmereGaming for EllesmereUI.
Unofficial, and not affiliated with either project.



