Rust / Rumours & Unconfirmed

Rust rumours: what looks real, what is still guesswork

Rust Premium is planned. Player customisation is planned. Underground trains are planned. The interesting part is what Facepunch’s public development work hints at — and what can still change before release.

This page follows rumours and open questions that have something concrete behind them: roadmap gaps, Facepunch commits, old feature lineages and persistent community theories. A commit can show that work exists; it cannot tell us when — or whether — the final version will ship unchanged.

Updated 7 October 2026PC RustPlans and rumours kept separate
How to read this page

Four different things often get called a “rumour”

Separating them matters more than assigning a confidence percentage.

Official planFacepunch has publicly listed it

The feature itself is not a rumour. Release timing, mechanics or implementation details may still be unresolved.

Development clueFacepunch is visibly working on it

Commits, branches or assets can establish active work, but not public release or the final design.

UnconfirmedThere is a real clue, but not enough for a firm answer

More than one explanation still fits what we can see.

Resolved / contradictedNo longer an active rumour

Kept only where the correction is useful because the old claim still circulates.

Q4 2026
Official plan
Rust Premium, Animals, Dogs, Biofuel Generator, Player Customisation and Bug Reward System are published roadmap items. Livestock/Biofuel have partly or wholly delivered; the remaining items require separate delivery evidence. [1]
2027
Official plan
Nexus System, Server Transfer, Deep Sea Nexus, Improved Animal AI, Procedural Caves, Nomadic Dweller, Improve Underground Trains, Terrain Deformation, Grappling Hook and New Weapons are official planned items — not rumours. [1]
Stretch goals
Official direction
Items such as Global Networked Bases, BDU/Kevlar, Bounty System and Cobalt Hovercraft are already published Stretch Goals. Their existence is not a leak; unresolved questions concern delivery, scope or whether an older system maps to the current label. [1]

One rule: roadmap placement and commits can show intent or active work, but neither is the same as a public release. Each section below focuses on the part that is still genuinely unresolved.

Official plan + unresolved mechanics

Rust Premium is real; the final product mechanics are not yet public

The question

Is Rust Premium just the old battlepass idea under a new name?

Partly resolved

No. Facepunch’s June 2026 explanation draws a direct distinction: the existing server-access product became Premium Access Pass, while the Rust Premium name is reserved for a separate future monthly opt-in offering with additional skins/perks. Facepunch explicitly said the future product is not a battle pass or VIP system. The current roadmap lists Rust Premium in Q4 2026. [2][1]

Why people are watching it

The public Premium branch contains a Premium tab/screen, FAQ modal, skin viewer, premium manifest and a SteamInventoryBundle item type. That is development evidence for a Premium product/store pipeline, not proof of final benefit delivery, entitlements or billing. [8]

What tempers it

The June article says the exact system was still being finalised. Bundle objects could support only part of the store/product pipeline rather than entitlement delivery itself. [2]

What we know

Rust Premium is an official Q4 roadmap item and is described as a future monthly opt-in for additional skins/perks. Price, complete benefits and final technical delivery remain unpublished. [1]

What is still open

Facepunch’s “not a battle pass” description rules out a simple public rename, but it does not establish what happened internally to the earlier battlepass-style proposal. Rust Premium could be a substantially redesigned successor, a separate product that reused some work, or a later replacement with little technical continuity. Current evidence does not choose between those histories.

What would settle it?

A Facepunch product/store announcement defining price, entitlements, cadence and launch mechanics — or released implementation that can be tied to that announcement.

Official plan + strong development clue

Player customisation is planned, and the branch reveals possible rules — not final policy

Current evidence

Character selection appears to be getting server/wipe boundaries

Development clue

Player Customisation is an official Q4 2026 roadmap item. In June, Facepunch said it hoped to implement a player customiser by year-end but that how it would work was still being discussed. [1][2]

The public development branch adds more specific possibilities. Commit #163815 sets up a pre-join server character selector; #163832 describes binding the selected character to that server until its next wipe; and #165177 adds capability to limit race/gender changes relative to the Steam-ID-derived original. The branch remains actively worked on at the 6 October check. [5]

Why it looks real

Explicit first-party branch text names server binding and a capability to restrict race/gender changes.

Why it could change

These are branch capabilities, not a published player policy. Selection rules could change, restrictions could be optional or differently scoped, and branch activity does not establish public release.

Where it stands

Official Q4 feature; active development; pre-join selection, wipe binding and restriction capabilities are evidenced in development, while final release behaviour remains unconfirmed.

What would settle it?

A release/devblog defining what players can choose, when they can change it, whether the rule is server-specific and how wipes affect identity.

Official 2027 plan + active work

Underground-train improvements are visibly in development — that does not move them out of 2027

Development clue

Random rooms, stations, puzzles and train-network work are appearing in commits

Development clue

Improve Underground Trains is an official 2027 roadmap item. The live underground_train_network_update branch is now a substantial workstream rather than a lone trace: it contains station redesigns, randomised rooms, puzzles, doors, train-spawn areas, track work and procedural-generation support. That strongly establishes active development of the published concept; it still does not move the public window out of 2027. [1][6]

What the commits show

The breadth of station, room, puzzle, track and procgen work makes the development link much stronger than a single filename or isolated commit.

What they do not show

A large branch can still precede release by months. It does not establish that work is feature-complete, merged to Main, enabled in public builds or moved from the official 2027 window.

Where it stands

Official 2027 plan with active development evidence; public release unconfirmed.

What would settle it?

A roadmap revision changing the window, or release notes/Main evidence showing the train-network update has shipped.

Dated event + unannounced product details

The 22 October Halloween update is confirmed; the DLC/package details are still development clues

Current evidence

Halloween items are being prepared, including Steam-facing data

Development clue

The Livestock update explicitly announces a mandatory Rust Halloween server/client update for 22 October 2026 at 18:00 BST. That dates the event gate, but does not announce a specific paid décor pack. [4]

Separately, the live halloween2026DLC branch contains a spooky_halloween_decor_pack bundle/item definition, String Lights, wall lamps, wreath work, wallpapers and Steam-facing metadata; a separate costume stream includes an alien costume. That is strong evidence of commercial/content preparation, but the internal labels are not a public store announcement. [7]

Why it looks real

Bundle/item definitions and Steam-facing metadata support a real package-preparation interpretation rather than a generic seasonal prototype.

What remains unknown

The final public name, price, exact contents and whether the alien-costume work belongs to the same commercial package remain unestablished.

Where it stands

Halloween event date confirmed; DLC/store package not yet publicly specified at the updated.

What would settle it?

A Facepunch store/news announcement naming the pack, contents, price and release availability.

Programme identity questions

Bug Reward and the unnamed anticheat layer are published plans with unresolved identities

Bug Reward System

Is the roadmap item the same system Facepunch described for good Staging bug reports?

Unconfirmed mapping

The roadmap officially lists Bug Reward System in Q4 2026. In January, Facepunch separately said it planned to look at rewarding “good and accurate” bug reports later in the year, partly to encourage Staging testing. The similarity is meaningful, but the inspected public material does not explicitly bind the two labels. [1][3]

This should also stay separate from Facepunch’s existing HackerOne security-vulnerability bounty programme, which the same January article describes independently. [3]

Why the mapping is plausible

Both the January statement and the Q4 label concern rewarding useful reporting, and both sit in the same year’s development planning.

Why it is not confirmed

“Bug Reward System” could be broader or differently implemented. Facepunch has not explicitly equated the roadmap label with the earlier Staging incentive description.

Do not merge

HackerOne is a security-vulnerability bounty, while the roadmap separately lists a Stretch Goal called Bounty System. Neither can be silently folded into Bug Reward.

What would settle it?

A roadmap/devblog statement explicitly defining Bug Reward System and tying — or not tying — it to the Staging-report incentive.

New anticheat layer

What is the third-party anticheat layer Facepunch said it would introduce?

Identity unknown

Facepunch said in January that Rust would introduce a new third-party anticheat layer and that details would follow when ready; the roadmap lists New Anticheat Layer in Q1 2026. That roadmap window has passed, but elapsed timing alone proves neither delivery nor cancellation. The same January article separately identifies ongoing Easy Anti-Cheat work, so EAC itself cannot simply be assumed to be the unnamed additional layer. [3][1]

Later Secure Server / TPM / Secure Boot work is also a separate security mechanism unless Facepunch explicitly maps it to that January promise. The public sources available here do not identify a vendor or product name.

What is known

January promised an additional third-party anticheat layer and the roadmap still carries that named plan.

What is still unclear

The public evidence does not name the vendor or show that EAC, TPM/Secure Boot or Secure Servers are that same layer.

Other possibilities

It could remain planned, have changed identity, have been superseded, or have shipped without a located public identity statement. Silence does not choose among them.

What would settle it?

A first-party statement naming the third-party layer and explicitly linking it to the January/Q1 commitment, or an explicit cancellation/replacement statement.

Official plan + lineage ambiguity

Dogs are planned; old Pets2 assets do not prove the old design is returning

Q4 roadmap

How much of the abandoned Pets work survives in Dogs?

Origins unclear

Dogs are an official Q4 2026 roadmap item. The dogs_2026 branch explicitly records extracting dog models, materials, animations, harness models and entity prefabs from the old Pets2 branch because that branch was too old to update normally; the extracted entity prefabs were noted with their entity class missing. This is concrete asset lineage, not evidence that the old gameplay system survives. [1][9]

What is clear

Models, materials, animations, harnesses and prefab assets are demonstrably being reused from Pets2.

What is not clear

The missing entity-class continuity and asset-extraction wording leave taming, ownership, AI, progression and other old Pets2 mechanics unproven.

Animal AI wrinkle

Improved Animal AI appears once under Q4 Animals and again as a separate 2027 roadmap occurrence. A staged-phases interpretation is possible, but Facepunch has not defined the relationship.

What would settle it?

A developer explanation comparing Dogs with the old Pets design, or released/test evidence detailed enough to compare mechanics rather than assets.

Returning official concept

Global Networked Bases is back on the roadmap — but technical continuity is unknown

Stretch Goal

Is the current Global Networked Bases goal the same system as 2023’s Global Rendering experiment?

Technical continuity unknown

Global Networked Bases is already an official Stretch Goal. The name also has real history: Facepunch shipped an experimental Global Networked Bases system in September 2023, exposed through the Global Rendering option, then documented repeated problems and later said the work had gone into development limbo. [1][12][13]

What is continuous

The published concept and name clearly recur: longer-distance visibility/networking of player bases remains a Facepunch development goal.

What is not established

The current Stretch Goal does not prove the same code, renderer architecture or rollout model has simply resumed from 2023.

Best reading

Describe it as a revived or continuing concept with technical continuity unresolved, not simply “the old feature returning”.

What would settle it?

A current technical explanation explicitly tying the Stretch Goal to the 2023 implementation, or a new release/engineering account defining the replacement architecture.

Community lore theories

Project Nova theories remain community interpretation, not established Rust canon

A located March 2025 community theory proposes that Project Nova explains human production, uncontrolled respawning, island containment and a cosmic-consciousness mechanism. That post establishes where the theory came from; it does not authenticate the theory. [11]

The first-party Cobalt Space Suit vignette establishes a much narrower Project Nova fact: urgency around the project led Cobalt to acquire early Soviet EVA-suit designs and produce protective suits. It does not identify Nova’s destination, connect it to respawning, describe human production or explain island containment. [10]

No longer active rumours

Claims that should not keep circulating as open questions

Resolved by releaseLivestock and Biofuel were not merely October predictions

Both shipped in the 1 October 2026 Livestock Update. Critter wildlife and the repairable Air Wolf helipad also moved from development clues into delivered update scope. [4]

Contradicted“Battlepass was simply renamed Rust Premium”

Facepunch’s June explanation says the future Rust Premium product is not a battle pass and separately renames the existing server-access product Premium Access Pass. A broader design ancestry remains unknown, but simple public equivalence is not supported. [2]

Deliberately omittedLow-value commit churn and duplicate speculation

Individual minor commits, raw roadmap ordering guesses, uncorroborated forum repetition and theories already handled more completely by Lore were excluded rather than padded into separate “rumours”.

Continue exploring Rust

Related Sourceborne pages

Sources & notes

This page compares Facepunch’s roadmap, release notes and public development branches with the origins of persistent community theories. Commits can show active development, but not a final feature, release date or default behaviour. Community posts are used to identify where a rumour came from, not as independent confirmation.

  1. 01
  2. 02
    Built Different — 4 June 2026 ↗

    Player-model/customisation intent; Premium Access Pass rebrand; future Rust Premium described as monthly opt-in skins/perks and explicitly not a battle pass or VIP system.

  3. 03
    Surviving 12 Years — 1 January 2026 ↗

    Battlepass-style exploration, bug-report reward intent, public HackerOne context and announcement of an unnamed additional third-party anticheat layer.

  4. 04
    Livestock Update — 1 October 2026 ↗

    Resolves Livestock/Biofuel signals and announces the 22 October 2026 mandatory Halloween update.

  5. 05
    Facepunch Commits — character_customisation ↗

    Character-customisation branch. Relevant commits include pre-join selection (#163815), server-until-wipe binding (#163832) and a capability to restrict race/gender changes (#165177). Shows development work, not a released feature.

  6. 06
    Facepunch Commits — underground_train_network_update ↗

    Facepunch development branch covering stations, randomised rooms, tracks, puzzles and related tunnel work. Not a public release.

  7. 07
    Facepunch Commits — halloween2026DLC ↗

    Development work for Halloween items and store metadata; separate costume work also exists. Final commercial package is not established by commits alone.

  8. 08
    Facepunch Commits — premium / steam_bundle work ↗

    Premium branch containing the Premium UI/FAQ/skin-viewer work, premium manifest and SteamInventoryBundle implementation trace. Useful for what Facepunch is building, not proof of final entitlements.

  9. 09
    Facepunch Commits — dogs_2026 / Pets2 asset extraction ↗

    Dogs 2026 branch. Commit #161116 records extraction of models, materials, animations, harnesses and prefabs from Pets2, while noting missing entity-class continuity. Shows asset reuse, not gameplay continuity.

  10. 10
    Elevator Update — Cobalt Space Suit — 1 October 2020 ↗

    First-party Project Nova vignette. Establishes the EVA-suit procurement story, not respawn/human-production/Mars theories.

  11. 11
    Rust backstory theory — r/playrust, March 2025 ↗

    Community origin for the Project Nova human-production/respawn/consciousness theory. The source places the theory in March 2025; it is included to show where the idea came from, not to confirm it.

  12. 12
    Airborne — 7 September 2023 ↗

    First-party release of experimental Global Networked Bases; the feature used the Global Rendering option and was explicitly described as experimental.

  13. 13
    Surviving a Decade — 4 January 2024 ↗

    Facepunch retrospective describing Global Rendering / Global Networked Bases problems and development limbo; also provides historical Pets and Nexus context.

Back to Rust Overview
Email updates