Artifacts are part of the power and reward layer tied to Vaultbreakers expeditions and Vaults. The public Demo reaches the first Vaultbreak, while October Alpha notes discuss additional Vaults and the named paths Darkness, Elemental, Arcane, Holy, and Void. That is enough to explain the system boundary, but not enough to publish a complete drop table or guarantee where every Artifact appears.
Separate playable Demo facts from Alpha names
The Demo lets players experience progression through the first Vaultbreak. Learn how its reward presentation works in AppID 4488770: what is offered, whether a choice is permanent for the run, where the result appears, and how extraction affects it. Record the exact build, because the Demo can still receive patches.
Vaults 3 and 4 and the five named paths appear in October Alpha notes. They should be labeled Alpha material until players can verify their live entrances, conditions, rewards, and behavior. Do not tell a Demo player to search for an area or path that the official Demo scope does not promise.
Darkness
An announced Alpha Artifact path. Confirm its live theme, mechanics, costs, and counters before choosing around the name.
Elemental
Record which elements and triggers the client actually lists; do not combine effects from old test notes.
Arcane
Test resource and ability interactions independently from item rarity or visual presentation.
Holy and Void
October notes mention holy orbs, corruption, and wards; the Alpha must establish how each path uses them.
Read an Artifact as a condition and payoff
Break every choice into trigger, effect, duration, scope, cost, and cooldown. “After using an ability” is a different trigger from “after dealing a particular damage type,” and a party effect is different from a self effect. Check whether the tooltip changes when another perk, item, or path is selected.
Choose the condition you can produce safely. A spectacular payoff tied to a rare state may contribute less than a modest effect that occurs in every encounter. Test against a known enemy, then observe the entire exchange: damage taken, control gained, recovery spent, and final position.
Build a path around the expedition job
Start with the run’s purpose. A route toward a Vault, a quest expedition, and PvPvE extraction can value different tools. If the party needs safe area control, choose effects that create or extend that window. If survival is failing because of wounds, do not assume a damage path solves the underlying resource problem.
Avoid selecting by color or path name alone. Darkness, Holy, and Void carry familiar fantasy meanings, but the current client’s tooltip is the rule. Elemental and Arcane likewise need observed triggers before they can be assigned to a hero or item category.
Understand corruption, orbs, and wards in context
October notes mention corruption, holy orbs, and wards while describing the expanded Artifact system. These words show that Alpha paths have their own mechanics, but not a complete public formula. In Alpha, note how the resource appears, what creates it, its cap, what spends it, and whether it persists between rooms or expeditions.
Test ward behavior against a controlled hit and distinguish a ward from ordinary health, armor, or a hero shield. For orbs, observe who can collect them and whether the effect is personal or shared. Do not merge visually similar effects into one mechanic without a tooltip or repeatable test.
Evaluate a choice before leaving the Vault
Read every option fully and consider your remaining route. A reward that needs a new equipment type may be weaker during the current run if that item is not available. A defensive effect can be valuable when healing is low, even if its long-term damage is smaller.
In co-op, tell teammates what the choice changes. If rewards are personal, each player can solve a different weakness. If the current client shares a decision, agree on the party’s next objective before selecting. The live Alpha must verify the exact ownership rule.
Record acquisition without inventing a farm
For each Artifact, capture its name, path, exact tooltip, Vault or source, difficulty, mode, party size, hero, build, and date. Repeat the source before calling it deterministic. A single reward does not establish probability, and an October patch name does not establish a current Demo location.
Screenshots should include enough interface to identify the client but omit account information. If the same Artifact changes after a patch, retain the older observation as historical rather than averaging the values.
Combine Artifacts with gear carefully
An Artifact can make a weapon, ability, potion, or hero action more valuable, but test the interaction one layer at a time. Establish the equipment baseline, select the Artifact, and repeat the same encounter. If several effects trigger together, remove one before assigning credit.
The Weapons and Armor guide provides the comparison method, and Ability Items covers active item powers. Use those pages to identify opportunity cost rather than chasing a theoretical combination that cannot be acquired in the same build.
Know when to extract
A meaningful Artifact or Vault reward can complete the purpose of an expedition. Check health, wounds, supplies, gear condition, and portal route before taking another optional fight. If the reward only matters after a successful return, extraction is part of the acquisition process.
Until Alpha opens, the reliable short answer is that the Demo reaches the first Vaultbreak and the Alpha notes name five Artifact paths plus later Vaults. Exact lists, odds, and routes remain unverified.