Alliance Tower Defense is active under the official Roblox title [👻 Part 2 👻] Alliance Tower Defense! ⚔️. The experience belongs to MrUpTime’s Games, uses root Place ID 99703116573266 in universe 10393438342, and its public description promises weekly updates. Roblox’s game data showed an updated timestamp of October 17, 2026 at 16:38 UTC when checked on October 18.
That timestamp proves the experience record changed; it does not explain what changed inside the game. The Part 2 title proves that Part 2 is the current official label; it does not prove a particular unit, map, reward, event end date, code, or balance change. Use this page to separate confirmed status from items that still need a live update log or current in-game test.
Current official snapshot
What to recheck after the title or timestamp changes
Start with the lobby update log if one is visible. Read the exact build text before relying on a creator thumbnail or copied post. Then inspect the controls most likely to affect a player’s next decision: the current Summon pool and costs, mode picker, unit cards, codes area, trading interface, and event panels.
Run one manual Easy City baseline before enabling Auto Skip. A change to enemy timing, unit damage, range, cost, or upgrade order can show up in a familiar route even when no detailed public note is available.
Open the Codes hub and treat every reported code as a new test. A new title often causes lists to publish quickly, but title text itself is not a redeemable code. Record the game’s result message and the reward actually received.
Open the live value source before trading. An experience update can affect supply, demand, or unit desirability even if the dated value snapshot has not yet moved.
Part 2: confirmed and still unknown
Part 2 is confirmed because it appears in the official title. The public description still describes the same core loop: earn Coins in matches, spend Coins on Summon, equip a team, pursue the leaderboard, and expect weekly updates.
This page does not assign specific units, maps, bosses, rewards, odds, pity changes, event windows, or code strings to Part 2 without direct evidence. Community pages and creator videos can identify candidates for testing, but a popular claim is not automatically official.
If your client displays a Part 2 panel, record the exact text and date. Check whether the content is permanent, event-limited, server-specific, or locked behind a visible requirement. Avoid converting a lobby banner into a universal mechanic before opening the related control.
How to verify a community update claim
First confirm game identity. The video, screenshot, or page should show Alliance Tower Defense, universe 10393438342, or the correct Roblox URL. Similar names and shared character themes make cross-game mistakes common.
Second check the date and build context. A guide from before the current Roblox update timestamp can still teach placement, but its costs, rewards, rates, and balance claims need rechecking. A newer page can also be wrong if it copies an older source.
Third reproduce the claim with the smallest safe test. Read a unit card before spending, open the mode picker before planning a route, or try a reported code once. Do not risk a rare item merely to verify an uncertain trading claim.
Finally label the result correctly. A developer post is Official. A direct live observation with a date is In-game verified. Agreement between independent current sources is Community corroborated. One relevant source is Community reported. A plausible claim without enough evidence Needs in-game testing.
Update-sensitive pages on this site
The Units hub keeps exact stats out of broad role guidance unless a current source supports them. A unit identity can remain useful while damage, cooldown, placement cost, or obtainment changes.
The tier list is intentionally role-first and provisional. Re-test Camera Man as the opening benchmark and economy timing after balance changes rather than moving every unit from one unverified screenshot.
The Values hub treats community market data as dated. Always follow its live-source link before a trade; a static snapshot is for context, not execution.
The summon calculator starts with empty inputs so it survives cost and reward changes. Read the current game, enter the new numbers, and calculate again.
The Modes hub avoids permanent wave counts and payout promises. After a patch, re-clear a familiar queue manually before assuming the old skip timing remains safe.
A practical post-update checklist
- Confirm the official title, creator, Place ID, and universe.
- Read any lobby update log or creator-owned announcement.
- Inspect the live Summon pool, cost, rates, rotation, and visible guarantee text.
- Read the active unit cards for your opening carry, economy unit, and late anchor.
- Open the mode picker and note which maps and difficulty labels are actually present.
- Re-run Easy City in one player with Auto Skip off.
- Test reported codes once and record the exact result message.
- Check the current value-list date before trading.
- Measure rewards again rather than reusing an old Coins-per-run note.
- Change one team variable at a time when diagnosing a new failure.
This checklist is deliberately conservative. It turns an update into a small set of player decisions without pretending that every timestamp change is a major patch.
Update history
2026-10-18 - Part 2 official status checked
Type: Official identity review
The Roblox experience displayed the title [👻 Part 2 👻] Alliance Tower Defense! ⚔️ under MrUpTime’s Games. The public description continued to name Coins, Summon, equipped teams, the leaderboard, and weekly updates as the core loop. Detailed Part 2 mechanics were not published in that description.
- Root Place ID confirmed as 99703116573266.
- Universe ID confirmed as 10393438342.
- Part 2 treated as a title status, not a license to invent features.
Source: Official Roblox experience
2026-10-17 - Roblox update timestamp advanced
Type: Platform activity signal
Roblox game data returned an updated value of 2026-10-17T16:38:19.479Z. That is evidence of recent activity at the experience-record level. Without a matching detailed announcement, the timestamp does not identify which gameplay values or assets changed.
- Recheck live unit cards and Summon inputs.
- Re-run the Easy City baseline before restoring skip timing.
- Do not infer new codes from the timestamp alone.
Source: Roblox Games API
2026-09-11 - Endless coverage became a strong community signal
Type: Community corroboration checkpoint
Recent creator and guide coverage converged on Endless as an Alliance Tower Defense survival topic connected with the harder progression path. This is not presented as an official patch note here; it supports checking the live mode picker and preparing only after Insane is repeatable.
- Confirm Endless is visible before planning a run.
- Treat wave rules and rewards as live-build fields.
- Use measured success and duration when comparing farms.
Source: Community Endless guide
Updates FAQ
Is Part 2 live?
Part 2 is the current official title label as of October 18, 2026. The public page does not provide a complete Part 2 feature list, so confirm individual mechanics in the live experience.
Does the Roblox updated timestamp equal a patch date?
It proves the experience record changed around that time. It does not provide patch contents and can reflect changes beyond gameplay balance.
Are updates always weekly?
The official description says weekly updates are waiting for players. It does not name a fixed weekday or promise that every week contains the same size of change.
Where should I look first after an update?
Read the lobby update log, inspect the live Summon and mode panels, then run a manual Easy City baseline. Those checks affect immediate player decisions.
Why is there no separate patch article for every change?
This direct Updates page keeps the official status and verification route together. It avoids thin pages built from a title change or unconfirmed rumor.