A news ticker is motion in the chrome: a thin strip that cycles three true sentences and then gets out of the way. It is not a CMS. It is not a homepage. It is not a shop product you have to keep buying. Styles Factory once sold Ultimate News Ticker. That storefront is gone. If an old product URL landed you here, stay. What survives is the pattern — short, time-bounded, dismissible motion — and the stock XenForo tools that already implement it.
This is not the newsroom article. That sibling owns how staff publish: article forums, featured threads, stickies, the weekly edition. Read it. This one owns the strip itself: when a ticker earns the pixels, when it is banner blindness, how official Communication → Notices replace a marquee add-on, and how widgets should not become a second ticker. It is not the portal first-screen decision. If you have not picked the door’s job, do not install motion on the door.
The historical product, honestly
Ultimate News Ticker sold a look: headlines sliding under the nav, often fed from a forum or a feed, often with more animation than a reader needed. It solved a 2010s problem — “the forum list does not feel like a site” — by adding movement. It did not give you an archive, a byline, or a URL you can 301 next year. Those are article threads.
We will not invent a 2026 version number, a price, or a feature matrix. The product is discontinued. A zip on a staff laptop is the same liability as an old FiveStyle parent: 2.2 jQuery, a customized PAGE_CONTAINER, a merge you will not get help with. Sunset it. Keep the job if the job is still real.
The job, in one sentence: everyone who loads this page in the next 72 hours should see one or two short facts, then never see them again.
If your sentence is “we need a magazine,” you want the newsroom and maybe the portal. If your sentence is “we need a campaign button,” you want a landing page. If your sentence is “we need motion so it feels alive,” you want a healthier What’s New habit, not a marquee.
Stock replacement: Communication → Notices
Official notices chapter: Communication → Notices. Title + HTML message. {name} becomes the viewer’s name. Optional image (their avatar or a custom file). Display styling (stock styles or your CSS class). Visibility: hide below a screen width so phones do not drown.
Official notice types — this table is the ticker product:
| Type | Where it sits | Ticker? | Use for |
|---|---|---|---|
| Block | Top, under the nav, until dismissed | No — it is a static strip | Downtime, a policy that must be seen once |
| Scrolling | A cycle of several; only scrolls if more than one is visible | Yes. This is the ticker. | Two or three one-liners with an end date |
| Floating | Bottom-right, quieter; can auto-dismiss after fade | No | “Season 3 is open” once |
| Fixed | Full width, stuck to the bottom, covers content | Almost never | It covers the reply box |
Dismissable: members close it; they can review dismissed notices in the account. Floating can auto-dismiss after fade — official: once-only, not critical.
Display order: higher number first among the same type.
Criteria (official examples): User is a guest; User arrived from a search engine; plus the usual user / page / time criteria (avatar, message count, where they are). A notice that fires for everyone, forever, on every page, is not a ticker. It is a billboard you trained people to ignore. The engagement article already said that.
A scrolling notice is the honest replacement for Ultimate News Ticker: short titles, three items, guests + members or guests only, an end date on a staff calendar. It is not a masonry newsroom. It does not replace featured/ or /forums/news/.
HTML that stays a strip
Official notices accept HTML and {name}. Keep it a strip:
<strong>Season 3 applications close Friday.</strong>
Apply in the whitelist forum — do not reply here.No iframe. No 800-word policy. Link the article or the landing page. {name} on a guest notice prints nothing useful. Do not use it on guest-only notices.
Inline style="color:#fff" will not flip with a dark variation. Use a notice CSS class you defined with @xf- tokens in the child’s extra.less, or accept that the strip is one theme. The branding article is where those tokens live.
When a ticker helps
Motion earns its keep in a small set of situations. If you cannot tick one of these, do not scroll.
A deadline the whole board shares. Applications close Friday. The realm is offline Saturday 02:00–04:00 UTC. The map wipe is Sunday. A Scrolling pair (the fact + the link) or a single Block for 72 hours is correct. A featured article can sit behind it for people who want the long version.
A launch window you will actually end. Season 3 opens. The new landing page is the button. The ticker is “Season 3 is open — apply here” for guests this week. Monday you disable it. If you cannot name the disable date before you enable it, you are about to ship a permanent banner.
Guests arriving from search, once. Official criterion: User arrived from a search engine. One Block: what this board is, one link to the right room. Dismissable. Not a sales deck. Not on every subsequent page view after they have an account.
A status that is true right now and false tomorrow. “Match day — live thread in Events.” Floating, auto-dismiss, dies at midnight. Do not scroll last Saturday’s score.
A multi-item strip that is still three facts. Patch in news, event Saturday, applications Friday. Three scrolling notices, display order set, all with end dates. A fourth item is how you recreate the old product you do not need.
Gaming hubs feel this more than newsrooms. A FiveM city has wipe clocks. A roleplay architecture already put those clocks in rooms. The ticker is the hallway sign, not the lore wiki. The culture article owns the calendar. The ticker only prints today’s line from that calendar.
When a ticker is noise
Most tickers we are asked to “fix” are not broken. They are doing a job nobody needed.
It is the archive. If the strip cycles twelve headlines from the last month, you built a poor article listing. Use an article forum (Preview or Expanded) and a Featured content widget. The newsroom article already drew that line. Scrolling twelve titles trains people to see motion, not words.
It is the homepage. A ticker plus a hero plus three featured cards plus an RSS dump on / is four first screens. The portal article will not save you. Pick the door’s job. If the door is “today’s edition,” feature it. If the door is “pick a room,” you do not need a marquee above the rooms.
It never ends. A notice without an end date is a stain. Staff will forget it. New members will think the downtime is still this weekend. Put the kill date on the staff calendar the same hour you create the notice.
It repeats the sticky. If Support already has “read this before you post” pinned, a site-wide scrolling echo is how you annoy the people who live in Support. Stickies stay in one room.
It repeats Discord. If the only news is a Discord ping, you do not need a forum ticker. You need to decide whether the forum is the record. Discord integration is a bridge, not a second newsroom.
It autoplays video or a slider. That is not a ticker. That is an LCP problem. The performance article does not want ticker JS, autoplay, or a XenPorta slider fighting lazy-load. Official scrolling notices are HTML in a strip. They are enough motion.
It is the only place a policy exists. Legal and billing belong in a locked article or a help page, not in a marquee people dismiss. Link the article from a Block. Keep the Block one sentence.
Phones drown. Official visibility can hide the notice below a width. Use it. A scrolling strip under a hamburger is how mobile members never reach the first thread. If the fact matters on a phone, it should be a Block they can dismiss in one tap — or it should be the thread they came to read.
Guest page cache serves a stale strip. If you run $config['pageCache'] or LSCache, a notice you just disabled can live on the cached guest HTML until purge. Plan the purge. Do not debug “the ticker will not die” as a XenForo bug until you have purged the guest cache.
Ticker versus the other three publishing tools
The newsroom table is worth repeating from the strip’s side, because this is where people mix jobs.
| Sentence | Tool | Ticker? |
|---|---|---|
| “This 1,800-word patch note is the story” | Article thread in an article forum | No. Link it from a one-line notice if the window is short |
| “This thread should be on the door this week” | Feature it / featured/ |
No. Featured is a card, not a marquee |
| “Everyone must see this until Friday, then never again” | Notice, dismissible | Yes — Block or Scrolling |
| “In Support, read this before you post” | Sticky in that forum | No |
| “We syndicate a vendor RSS” | RSS feed importer, prefixed | No. Never auto-scroll other people’s feed |
Do not use a notice for the 1,800-word patch note. Do not feature a private staff thread. Do not sticky twelve threads in one room. Do not scroll the RSS.
Widgets are the other mix-up. A New posts widget is a list. An HTML widget with a <marquee> (or a JS slider) is how you reinstall Ultimate News Ticker inside a sidebar. The widgets article already told you an HTML widget is not a plugin. It is also not a ticker you can criteria-filter the way notices can. If you need guest-only, search-arrival-only, width-hidden motion, that is a notice, not a widget.
XenPorta 2, if you installed it after reading the plugins landscape, will offer sliders. A slider is a portal job. A ticker is a notice job. Running both on / is how the first screen moves in two directions. Pick one.
Criteria that keep the strip honest
Official criteria are the difference between a ticker and graffiti.
User is a guest. Onboarding one-liner. Members who already applied do not need “Season 3 is open” for a month. Combine with a landing URL.
User arrived from a search engine. Explain the board once. Do not upsell.
Page / node. A notice that only fires in forums/support/ can replace a second sticky. A notice that fires on every page including the editor is how people lose the reply box (especially Fixed).
Time. If your ACP shows date windows, use them. If it shows “display continuously” and you mean Friday, set a staff reminder anyway. The product will not unfeature a notice for you any more than it expires features — the newsroom article already warned about featured dates.
Message count / user group. “Registered, fewer than two posts” is a softer guest strip for people who created an account and then froze. Do not also shout at Established.
Stack as few criteria as you need. A notice with six criteria is a bug you will not reproduce.
Display styling: stock is fine. A custom class is a brand token — child’s extra.less, @xf- chips, both variations. Do not ship a red-on-red strip on the dark half and blame 2.3.
A weekly cadence for the strip (not the newsroom)
The newsroom already has Monday / Wednesday / Friday for articles and features. The strip has a shorter clock.
| When | Strip action |
|---|---|
| When the fact becomes true | Create the notice. Type matches urgency. End date written |
| 24 hours later | Look at guest and member. If nobody can say the sentence unprompted, the HTML is too long |
| When the fact becomes false | Disable. Do not “leave it, it’s fine.” Purge guest cache |
| Friday sweep | Any notice older than seven days without a written reason is disabled |
Staff page: who may create notices. That is not the same person who may feature, and not everyone with a moderator hammer. A ticker is site-wide chrome. Treat it like a header change.
Worked ACP: three lines, then Friday
You have a wipe Saturday 02:00 UTC, a Season 3 apply URL, and a patch note already in news.
- Communication → Notices → Add notice. Title
Wipe Saturday. Type Block (one critical fact) or Scrolling if it will sit with two friends. HTML: one sentence + a link to the staff calendar thread or the news article. Dismissable. Hide below a phone width if the thread is the real destination. Display order 100. - Second notice:
Season 3. Criteria User is a guest. Link the landing page. Floating if it is a nudge, Block if applications close in 72 hours. - Third notice:
Patch. Scrolling. Link/forums/news/…. Do not paste the patch note into the notice. - Write the three disable dates on the staff page. Wipe notice dies Saturday 05:00. Season 3 dies when you close applications. Patch dies when you unfeature the article.
- Guest window. Member window. Disable one, confirm the others remain. Purge guest cache.
That is a ticker. It took twenty minutes and no add-on. If you cannot name the three disable dates, you do not have three facts. You have a habit.
Banner blindness is operational
Members do not “stop seeing” a strip because they are rude. They stop seeing it because it has been true for three weeks. Official dismissable notices already admit this: people close them. If you undismiss by editing the notice every day to force it back, you are training them to ignore the next downtime. Change the fact or kill the strip.
A prefix on the patch thread (Patch) is for people who opened news. It is not a ticker. Do not also scroll the prefix text site-wide.
If the old add-on is still installed
Worked path, because this is the ticket after a 2.3 upgrade.
- Screenshot the public strip. Copy the three sentences that are actually true this week. Discard the rest.
- Note where the add-on injects:
PAGE_CONTAINER, a widget position, a template modification. Appearance → Template modifications will tell you. - Create official notices for those three sentences. Scrolling if they should cycle; Block if one of them is downtime. Criteria and end dates.
- Disable the add-on on staging. Confirm the official notices still show. Confirm no empty hole in the header (a customized parent that expected the add-on’s wrapper).
- If the header hole exists, you have a customized template. The upgrade-safe customization article is the revert/merge. Do not keep the add-on to fill a hole you created.
- Three sessions. Then production. Uninstall. Do not leave a disabled ticker add-on “in case.”
If step 1 produces twelve sentences, you do not have a ticker problem. You have an editorial problem. Open the newsroom article and unfeature last month.
RSS is not a ticker
Official RSS feed importer (manual index under forums/threads) pulls an external feed into threads. That is a newsroom input. It is not motion. Prefix those threads Syndicated. Do not feature them by default. Do not point a scrolling notice at “latest RSS title.” A strip that cycles other people’s headlines is a scraper with animation. The newsroom already said a newsroom that is 90% syndicated RSS is a scraper with a theme. Adding motion does not make it yours.
If the only way you can fill three scrolling slots is an imported feed, you do not have a ticker. You have an empty editorial calendar. Turn the notices off. The quiet header is cheaper than a copyright complaint.
Add-on tickers in 2026
You might still want a third-party ticker if official scrolling notices cannot do a thing you can name in one sentence: a feed from a specific resource category, a per-node strip the notice criteria cannot express, a design your brand insists on that extra.less cannot restyle. Confirm the add-on has a 2.3 build, does not require jQuery, does not fork PAGE_CONTAINER, and survives both style variations. Test it against guest page cache.
Most boards that think they need that sentence actually needed a Featured widget and a shorter notice. The plugins landscape already put “ticker on day one” in the do-not-install table. Stay there until the stock strip has failed a real criterion.
We will not name a 2026 paid ticker as “the successor to Ultimate News Ticker.” That would be a product we did not vet. The successor is Communication → Notices.
Gaming versus news versus support
| Board | Ticker default | Why |
|---|---|---|
| FiveM / wipe-clock hub | Short Scrolling or Block on wipe week only | The clock is real; the rest is Discord |
| Magazine / newsroom | Usually off | Featured + article forum are the news |
| Support / docs | Off site-wide; maybe a node-local Block | Stickies and the KB |
| Mixed city + news | One strip, one fact | Two jobs on / is how both lose |
Light vs dark is a design decision for the surface under the strip. A bright yellow ticker on a dark gaming palette is contrast you should check on purpose, not a default “alert” colour from 2014.
Performance is a design constraint
A ticker that janks the first screen is a bad ticker even if the sentence is true. Official scrolling notices are HTML in chrome. They do not need a slider library. They do not need autoplay. They do not need a second request for “ticker.json.”
The performance article already asked you not to dump campaign CSS into global extra.less. A notice class in the child’s extra.less is fine — it is small. A XenPorta slider plus a lazy-load add-on plus a leftover Ultimate News Ticker script is how LCP dies and the plugins landscape’s XenPorta warning comes true.
If you run guest page cache, the strip is part of the cached HTML. Plan the purge when the fact dies. A cached “we are down” banner on Monday morning is how you invent a second outage.
Checklist
- You can say the ticker’s sentence and its end date
- Official Communication → Notices tried first (Scrolling = ticker)
- At most three scrolling items; HTML is one or two lines
- Criteria are narrower than “everyone, every page, forever”
- Dismissable unless it is genuine downtime
- Hidden on small widths if the thread is the point
- Not doubling a sticky, a feature, an RSS import, or a Discord ping
- Guest cache purge planned when you disable
- Notice class uses
@xf-tokens if you styled it - Old Ultimate News Ticker (or a PAGE_CONTAINER marquee) is on a sunset path
- Staff page names who may create notices
- Three sessions: guest sees it, member can dismiss, staff can disable
Takeaways
- Ultimate News Ticker was a pattern, not a 2026 product. Official Scrolling notices are that pattern.
- A ticker helps when a shared deadline or a 72-hour status must hit everyone, then die. It is noise when it is the archive, the homepage, or a banner with no end date.
- The newsroom publishes editions. The portal is the door. The ticker is a hallway sign. Keep those jobs off each other’s URLs.
- Widgets, sliders, and leftover add-on marquees are how you reinstall a shop product you no longer need.
Write the sentence. Set the Friday it dies. If you cannot, you do not have a ticker. You have a habit of moving type. Break the habit. The quiet header is a feature.