The exact Roblox Machine Party is universe 10635348596 and root place 127775478639865 by Aura devs studio. Official Roblox sources verify an Action experience, a 32-player server limit, a creator-described 2-to-4-player party-game format, test-subject customization, friend interference, six approved media records, and four current product labels. They do not publish the round roster, controls, matchmaking, product effects, salvage formula, codes, rewards, or ending. Search results for the separate PC Machine Party are not source material for this universe.
Canonical identity record
Canonical game ID is roblox:10635348596, universe ID 10635348596, and root place 127775478639865. The official creator is Aura devs studio, and the current title is [UPD2] Machine Party. Roblox classifies the experience under Action and exposes a maximum server size of 32. These fields identify the product; they do not explain how one activity fills the server or how a party is created. The canonical link in this reference always returns to the root Roblox place. Same-name Roblox copies, fan recreations, the Steam release, and pages that omit a universe or place binding are not interchangeable sources. When the title changes, the universe and root place remain the primary identity checks.
Verified creator-published gameplay categories
The creator publishes four useful categories: the experience is a collection of party games, it supports 2 to 4 players, players can customize a test subject, and friends have multiple ways to interfere with one another. Those statements support a small-group party premise and two player tasks: learning the current round and checking the current customization or interaction state. They do not publish a fixed round count, named game list, control map, scoring model, team structure, matchmaking rule, public-lobby behavior, or completion condition. The reference therefore records the categories as verified and keeps every exact procedure dependent on the current client.
Party size and server capacity are different fields
The creator's 2-to-4-player statement describes the intended party-game format. Roblox's 32-player value is the universe's maximum server capacity. Neither source says that 32 players share one round, that multiple groups run simultaneously, that spectators exist, or that a minimum of two automatically starts play. Keep both fields with their labels rather than merging them into a single player-count claim. A current capture of the lobby or activity selector would be required to document how the server divides players, how a group readies, or how a missing participant affects the start.
Creator media inventory
The official media endpoint returned six approved records during the checked window: one GamePreviewVideo record and five image records. These assets are useful for recognizing the exact Roblox experience and reviewing current presentation. Media can show a scene, character, interface, or possible activity, but a still image cannot prove a control, win condition, hazard rule, damage value, reward, or sequence. Even a preview video may be edited and may not describe every current round. Treat media as identity and visual context unless a replayable capture reproduces the task in the live root place.
Official product-label ledger
The current game-pass endpoint exposes four labels: Prime, VIP+, VIP, and 2x Salvage. The official records returned no descriptions for those products. This reference can verify the labels and dated presence, but not the benefits, status hierarchy, stacking, salvage eligibility, multiplier application, duration, refund behavior, or value. Prices and sale state can also change independently of page meaning. Never infer that VIP+ includes VIP, that Prime outranks both, or that 2x Salvage affects every reward. Publish benefit details only after creator text or a current in-game purchase description states them explicitly.
Badge endpoint status
The official badges endpoint returned an empty data array for this universe during the checked window. That is a dated endpoint result, not proof that the experience has no achievements, quests, milestones, badges added later, or non-badge progression. A same-name PC achievement list is especially unsafe here: it belongs to another product and cannot fill an empty Roblox badge response. Recheck the exact universe endpoint after an official update and only add badge names or triggers that Roblox returns for universe 10635348596.
Demand evidence does not become game facts
The exact-name demand collector found current videos from multiple independent channels about the Roblox version, including session and walkthrough-shaped interest. That establishes that players are looking for explanations and current gameplay context. It does not make a video title authoritative, prove a permanent round list, or allow a creator's PC-game explanation to cross products. Use videos to discover player questions and to prioritize a replayable capture. Durable instructions still need official text or a trace-bound current observation showing the exact universe, step, input, and result.
Held claims and future evidence requirements
This reference holds the exact minigame roster, individual rules, controls, matchmaking and invite flow, damage, cooldowns, scoring, salvage sources, payout formulas, product effects, item catalog, rarity, codes, redemption steps, rewards, endings, tier lists, and calculators. To release one of those topics, bind it to the exact Roblox universe and collect the complete input needed for the task. A minigame guide requires replayable current round captures; a pass comparison needs creator-published effects; a code page needs a verified string and redemption result; a calculator needs stable units and formulas. Search popularity, a same-name PC wiki, or a single clip cannot replace those inputs.
Refresh policy
Refresh this wiki when the official universe identity, creator description, classification, server capacity, party-size statement, customization promise, interference premise, media inventory, badge response, or product descriptions change. Counter-only movement does not refresh the semantic page. If Aura devs studio publishes exact round rules or product effects, add only the claims the source states and retain unknown fields. If a source becomes unavailable, mark it unavailable rather than converting the gap into a negative fact. The same-name PC game remains excluded unless the Roblox creator explicitly and verifiably connects a specific fact to this universe.
What this guide does not assume
This wiki verifies exact Roblox identity, creator, current title, classification, server capacity, the creator-described party-size, customization and interference categories, official media count and types, the dated empty badge response, four product labels, and current exact-game demand. It does not certify the separate PC game, exact rounds, controls, matchmaking, scoring, damage, salvage, pass effects, items, codes, rewards, endings, rankings, or formulas.
Refresh trigger: Refresh after official exact-universe sources or replayable current captures change identity, party structure, rounds, customization, interactions, media, badges, product descriptions, or another held system.