Journalator's current development file includes the Forever interface target, but check the release you actually download before relying on its logs. The main branch lists interface 16001 among its targets. That is evidence of development support; it does not by itself establish which packaged release includes the change or whether every transaction category works in your Forever client.
Before relying on Journalator for your Forever records, inspect the exact current file and changelog for an explicit Forever declaration. If you cannot find one, treat its behavior as unverified. Do not interpret an empty transaction history as proof that you made no purchases or sales.
Separate Journalator from an auction buying tool
Journalator's main job is recordkeeping. Its author describes logging auction activity, vendor transactions, quest rewards, drops, mail and trades, with summary views and CSV export. It is not presented as the search-and-buy interface you use to choose an auction listing.
That distinction matters when deciding why you need the addon. If your goal is to buy materials more easily, an auction interface addresses the immediate task. If your goal is to review income, expenditure or sale history, Journalator's logging is the relevant function—but only after support and actual recording are confirmed for your client.
A familiar Journalator window in another WoW version does not establish that the Forever event handling and transaction categories behave the same way.
What the support request actually tells you
The GitHub support issue was opened on September 27, 2026, requesting Forever support. An open request is not a release announcement. However, the author's current main-branch Journalator.toc now includes interface 16001, alongside targets for other WoW clients. The development file provides stronger evidence of a Forever target than the issue status alone.
Keep the development branch and the downloadable release separate. The project description lists Retail, SoM and Wrath; that older description cannot establish that no newer Forever implementation exists. At the same time, a main-branch interface declaration does not prove that your chosen release contains the change or that every log category has been tested on the live client. Inspect the selected release and its notes before drawing a stronger conclusion.
Use these checks in order:
- Open the project's Files view and inspect the actual file you intend to install.
- Look for Forever among that file's declared game flavors.
- Read the corresponding release notes for support and known limitations.
- Check whether the Forever request has a linked fix or maintainer clarification.
- Keep the file version with any report of what you observed in your own client.
The author main branch lists interface 16001; this is source code, not a verified release package or gameplay test.
A project's general WoW category, an all-version download count or a third-party recommendation is weaker evidence than a file declaration tied to the release you downloaded. A multi-flavor file can still be valid when Forever is explicitly among its targets.
Understand the normal Journalator workflow
On its documented supported clients, Journalator opens through the minimap icon or /jnr. Its tabs group the kinds of records you want to inspect rather than performing every transaction itself.
| Documented area | Records described by the author |
|---|---|
| Auction House | Auction mail, postings, sale rates and expired or canceled items |
| Vendors | Vendor purchases and sales, repairs and flight costs |
| Questing | Received quest rewards, including reputation |
| Looting | Gold, items and currency from monsters and chests |
| Gold sent to and received from other players | |
| Trades | Items and gold exchanged with other players |
Some documented functions are expressly Retail-only, including crafting-order and Trading Post categories. Their presence in a general description does not make them Forever systems or features to enable there.
If your selected release establishes the support you need, inspect the transaction category relevant to your task. A vendor record and an auction-mail record describe different events. Do not expect every tab to provide a duplicate history of the same purchase.
Check filters before interpreting a blank view
On a supported setup, the author documents controls that can intentionally exclude records. Journalator → Monitors lets you turn tracking categories off. Ignore Transfers excludes interactions with specified characters.
Before concluding that logging failed, inspect those settings and the view's selected period or category. A filtered display and an unsupported client can both produce missing-looking data, but they require different responses.
Keep the support question first. Correcting a display filter cannot add missing Forever compatibility. Conversely, if the author has explicitly added support in a later release, an old open request is not a reason to ignore the current release's documentation.
Export and tooltip features remain conditional on support
The documented Export Results button exports the current view as CSV for a spreadsheet. It is useful for reviewing the records the addon actually collected; it cannot reconstruct transactions that were never logged.
Journalator's optional tooltips can show previous purchase and sale prices, auction failures or successes and a personal sale rate. These are records about your observed activity, not a market quote or a guaranteed future sale.
Keep an export before clearing historical records if you need that history. Also remember that a spreadsheet export and a settings backup protect different things: one preserves the visible records you exported, while the other preserves the addon's saved state.
Do not use an extension as proof of base-addon support
Journalator Extended Features is a separate extension that requires Journalator. Its compatibility list names other WoW versions and does not explicitly establish Forever support.
The extension advertises expanded date filters and a craft count for the crafting-orders tab. Installing it cannot be assumed to supply a missing Forever port of Journalator itself. Confirm the base addon first, then the extension's own release support.
Report an observed failure with the right context
If an author-declared Forever build is available and logging still fails, record its version, the transaction type, the relevant monitor setting and any error text. Describe the specific action and whether another tab logged anything.
Preserve existing records before reinstalling or resetting. An unsupported or unverified client is a reason to avoid relying on the history, not a reason to erase the evidence needed for a useful bug report.
Check one new record before trusting a larger history
If your chosen author release explicitly supports Forever, verify the particular kind of record you intend to use before treating the addon as your ledger. Begin with a transaction you already planned to make, rather than spending gold solely to generate a test.
Note the item, quantity and visible amount at the time of that transaction. Then inspect the matching Journalator category and the selected time period. Check that the relevant monitor was enabled before the action. If the row appears, compare the recorded item and amount with what you actually observed.
One successful record establishes only that observation. It does not prove that auction mail, vendor activity, loot and direct trades are all captured, or that records survive your next session. Verify the category you need instead of assuming every category shares the same implementation.
If a row is missing, preserve the surrounding context: which category you opened, whether a filter was active, the characters involved and any error message. Check Ignore Transfers if the action involved one of your other characters. Do not repeatedly perform more purchases simply to see whether the counter eventually changes.
Export a view you can interpret later
Before exporting, choose the category and period you actually want to analyze. Export Results represents the view you selected, so keep a note of that selection alongside the CSV. Otherwise, a later comparison can mistake a filtered month for an all-time total.
Open the exported file and inspect a few recognizable entries before relying on spreadsheet totals. Confirm that the export contains the records visible in the selected view. An empty or partial export should prompt a check of the view and support status; it is not evidence that the corresponding gameplay activity never happened.
Keep the original export when making spreadsheet changes. That preserves the records you actually received without treating a cleaned or filtered spreadsheet as a complete reconstruction of your transaction history.