Cosmetics update checked September 10, 2026

TFT Unreal Engine: Cosmetics & PC Client Status

TFT moved to Unreal with Set 18. Patch 18.2 adds more converted cosmetics, with further batches planned. The dedicated PC client is a separate rollout.

Independent publication — not affiliated with or endorsed by Riot Games.

By Riot Updates Research Desk Article updated September 10, 2026 Historical sources reviewed August 26, 2026 Sources 8 Read 7 min

Did TFT move to Unreal Engine?

Yes. Riot's patch 18.1 notes describe Enchanted Wilds as TFT's first live set on Unreal. This is an engine migration, not “TFT 2”: the game, team, Riot-account login, and currencies continue, while settings reset and parts of the cosmetic catalog are still being ported.

What changed in Patch 18.2? Riot's September 9 patch notes confirm another cosmetics batch, with more conversions planned for 18.3 and later. Riot says the full catalog will return, but does not give a completion date. This update was checked September 10; the historical technology record below retains its August 26 review date.

Why are some TFT cosmetics unavailable?

Conversion to Unreal is unfinished. Riot is prioritizing popular and high-rarity items while checking performance and quality. Its patch notes list returned cosmetics and planned batches; a planned conversion is not proof an item is already usable.

Check Riot's Patch 18.2 cosmetics availability list.

Core archive sources: TFT-S060 TFT-S061

Status, separated

What is live—and what is still scheduled

The engine, game content, launcher, account, and cosmetic catalog are different layers. Treating them as one release produces misleading answers.

Live

Patch 18.1 and Set 18

Enchanted Wilds launched on August 26 with Wisps, a new roster, and Space Gods temporarily remaining playable on PC.

Live

Unreal game engine

The playable game moved from Riot's shared Hextech technology to Unreal with patch 18.1.

Scheduled

Dedicated TFT PC client

The August 26 source review recorded October 9, 2026 as Riot's planned client date. Patch 18.2's cosmetics update does not independently reconfirm that schedule. A planned date is not a completed release.

Continuity and change

Why this is not TFT 2

Riot presents Unreal as a long-term production foundation, not a sequel, account reset, or immediate redesign of TFT's core rules.

What carries over

The same Riot account remains the login.
RP and TFT-specific currencies carry over.
Owned cosmetics are being ported into Unreal, although the full catalog is not available immediately.
The product remains Teamfight Tactics, maintained by the same team.

What resets or changes

Preferred settings and favorited cosmetic loadouts reset to defaults.
The initial Unreal download is larger; later patches are expected to return to normal sizes.
The PC minimap is gone, and replacement social pings were not ready at launch.
Mobile receives a replacement Unreal app rather than a separate new account.

Cosmetic continuity needs a qualifier Riot says owned cosmetics will be ported, but not every cosmetic is available in Unreal at launch. Its FAQ's detailed catalog language is specifically marked for players in Riot-published regions.

31. The long dependence on League technology

TFT’s speed of creation depended on League.

It used League champions, skins, accounts, regional infrastructure, engine technology and PC client. This reduced the cost of reaching millions of players but created technical constraints. The first prototype already struggled because League’s engine was optimized for a ten-player action game rather than eight boards containing large armies and benches. TFT-S002

As TFT grew, shared technology created a different problem: the product’s needs diverged from League’s. TFT wanted tools for rapid roster replacement, board presentation, mobile parity, experimental modes and unique UI. Changes to League could create conflicts for TFT even when they were unrelated to TFT’s design.

The Game Analysis Team illustrates another kind of technical institutionalization. By 2023, Riot described a group of former analysts, coaches and high-level players using simulations, data and playtesting from early set development through live balance. TFT-S072

TFT was increasingly a distinct production organization even before it had a distinct engine and client.

32. The 2026 Unreal migration

TFT moved from the shared Hextech technology to Unreal with Set 18 on August 26, 2026; Riot’s 18.1 patch notes now verify the live release. TFT-S061

The company emphasized several controls:

this was not TFT 2;
the same team and recognizable game would continue;
the migration was for future innovation rather than an immediate visual sequel;
the team had retrained and worked across several sets to prepare;
cosmetics, currencies and account progression would carry over;
downloads and minimum specifications would change;
mobile users would transition to a replacement application;
a TFT-specific client would follow four patches later.

Riot scheduled the dedicated client for October 9, 2026. TFT-S061

Historically, the migration represents TFT’s transition from “a permanent League mode with mobile apps” toward “a distinct Riot game that still uses League intellectual property.”

It does not eliminate every dependency. Accounts, champions, cosmetics, publishing and company infrastructure remain connected. But engine and client separation give the team more control over its release process.

The immediate risks are also real: larger downloads, device compatibility, migration bugs and a period where old and new technology need transition support. Riot’s FAQ said Set 17 would temporarily remain playable on PC during parts of the migration, another reason not to describe August 26 as one instantaneous universal switch. TFT-S061

33. The dedicated TFT client

A dedicated client is not merely a new launcher icon.

Inside the League client, TFT navigation, patching and social systems must coexist with a different game. A TFT-specific client can organize sets, modes, cosmetics, history, onboarding and esports around TFT players rather than around League menus.

It can also reduce the perception that TFT is secondary content. The product became permanent in 2019, launched on mobile in 2020 and developed its own esports and modes, yet its desktop delivery continued to signal dependence on League.

At the research cutoff, the client remained an announced future event. It must not be written as already launched. TFT-S061

Structured record

From a League mode to a separate engine

These archive rows distinguish the game engine from the PC client and preserve the announced sequence of the transition.

Selected Teamfight Tactics platform and technology milestones
Date	Layer	Milestone	Sources
2019-06	PC/Mac	TFT launched inside the League of Legends client and custom Hextech technology	Sources: TFT-S002 TFT-S003 TFT-S010
2020-02	Mobile beta	Closed-beta and launch architecture described; cross-play and shared progression planned	Sources: TFT-S014
2020-03	iOS/Android	Standalone mobile applications launched across most regions during Galaxies	Sources: TFT-S013 TFT-S015
2020-06	Mobile commerce	Mobile store capability expanded during Galaxies II	Sources: TFT-S016
2021-11	Mobile currency	TFT Coins introduced on mobile for back-end commerce	Sources: TFT-S029
2023-08	APAC mobile expansion	Pre-registration opened for multiple Southeast Asian and Greater China markets	Sources: TFT-S065
2024-2026	Engine migration development	Team retrained and built several sets while preparing Unreal transition	Sources: TFT-S061
2026-08-26	Unreal migration	Set 18 scheduled to move TFT from shared Hextech technology to Unreal	Sources: TFT-S060 TFT-S061
2026-08-26	Mobile replacement	Unreal transition requires replacement mobile application/download while account content persists	Sources: TFT-S061
2026-10-09	Dedicated TFT PC client	Riot scheduled a TFT-specific client four patches into Set 18	Sources: TFT-S061
2026 onward	Product independence	Riot says Unreal enables TFT-specific tools and reduces conflicts with League updates	Sources: TFT-S061

Launch limitations

What Riot says is incomplete

Patch 18.1 is evidence that the migration is live. It is not evidence that feature parity, performance, or the cosmetic port is complete.

League engine / Hextech

Documented retrospective

Risk: Engine designed for ten-player League matches rather than eight TFT boards with armies and benches.

Recorded response: Prototype and production team worked around constraints.

Sources: TFT-S002 TFT-S003

League PC client

Riot explanation

Risk: Shared client and technology can create dependencies or conflicts unrelated to TFT design.

Recorded response: Unreal migration and dedicated client announced.

Sources: TFT-S061

Mobile application

Documented launch limitation

Risk: Feature parity, UI density, store and chat limitations at initial launch.

Recorded response: Mobile systems expanded over later patches.

Sources: TFT-S014 TFT-S015 TFT-S016

Unreal migration

Prospective

Risk: Deployment bugs, performance variance and toolchain transition cannot be evaluated before release.

Recorded response: Riot staged dedicated client four patches later.

Sources: TFT-S060 TFT-S061

Dedicated client

Prospective

Risk: Date and performance outcomes remain unverified at cutoff.

Recorded response: Live-check after October 9.

Sources: TFT-S061

Known launch gaps Riot's patch notes warn about extra bugs, longer loading, unfinished cosmetic parity, no launch-day friend spectating, and pings being unavailable while their replacement is developed. Those are publisher disclosures, not independent measurements of every platform or device.

Read Riot's patch 18.1 release notes or inspect the controlled archive sources below.

Sources: TFT-S002 TFT-S003 TFT-S014 TFT-S015 TFT-S060 TFT-S061

52. What the Unreal migration can—and cannot—prove

The 2026 engine migration is an architectural milestone, but its first live patch should not be converted into a long-term performance verdict.

Riot moved TFT from its inherited Hextech technology to Unreal with Set 18. The team framed the change as long-term infrastructure: better TFT-specific tools, fewer conflicts with League’s development and a foundation for future work. Riot explicitly said the migration was not “TFT 2” and should not be expected to produce an immediate visual reinvention. TFT-S061

The planned dedicated client follows four patches later, on October 9, 2026. TFT-S061

Those announcements support several claims:

TFT’s technical needs had diverged enough from League’s to justify migration.
Riot expected a transition period rather than a single instantaneous separation.
The company was willing to invest in product-specific tools after seven years.
The dedicated client was not scheduled to arrive on the same day as the engine migration.

They do not yet prove:

that performance improved on every device;
that the migration launched without major bugs;
that development became faster;
that mobile parity improved;
that the dedicated client met its announced date;
that TFT became fully independent from every League service;
that players preferred the new architecture.

Riot’s patch 18.1 publication confirms that Set 18 and the Unreal migration went live on August 26, while the October 9 dedicated client date remained scheduled. TFT-S060 TFT-S061 TFT-S063

Place the engine change inside TFT's full history.

Trace every technology milestone, compare every set, or inspect the sources behind this dated status page.

TFT history 348-event timeline Sets in order TFT sources