This tracker separates what is playable now from what the developers have only scheduled. Check the date, source, and status before planning a run: an event card on Roblox can announce a future window before its update is available inside Something is Wrong With My Dog. The entries below use official Roblox event pages and were last checked on October 25, 2026.
Current update status
The official experience is currently titled [UPD] Something is Wrong With My Dog…. The active official event window is PUPPIES, which runs from October 23 through October 30, 2026. Two more event windows are publicly scheduled: UPDATE 2 begins October 31, and UPDATE 3 begins November 7. Those dates are useful for deciding when to revisit the game, but a scheduled event is not proof that every feature associated with its name is already live.
If you are joining during an event window, start from the official Roblox experience page rather than a copy or similarly named place. Once loaded, check the title screen and the in-game notices for changes to modes, badges, passes, objectives, or recipes. This site records confirmed navigation and stable player guidance separately; it does not turn a short event title into an invented patch list.
2026-10-23 - PUPPIES
Type: Live event
The official PUPPIES event is scheduled from October 23 at 6:00 PM UTC through October 30 at 10:00 PM UTC. Its Roblox event page points to the same official experience and describes finding puppies. At the October 25 check, this is the current event window players can enter.
- Join the official place and look for the event’s current in-game prompt before beginning a long Story or Survival run.
- Treat the event page as confirmation of the event window, not as a complete mechanical guide; the page does not publish a full puppy location list or reward table.
- If a puppy objective does not appear, return to the main menu, confirm that the experience title and developer match, and rejoin a fresh server.
- Record any limited reward immediately after earning it, because event objectives and availability can change before the next site check.
Source: Official Roblox PUPPIES event
2026-10-31 - UPDATE 2
Type: Scheduled update
Roblox lists UPDATE 2 from October 31 at 3:30 AM UTC through November 6 at 10:00 PM UTC. As of this tracker’s October 25 check, that start date is still in the future. Plan to verify the live client after the window opens rather than assuming the label describes content already available.
- Recheck the official experience page after the scheduled start time and read any developer-supplied in-game notice.
- Compare the mode selection, badge list, passes, and objective text with what you saw before the update.
- Do not spend Robux based on an unofficial preview; inspect the current purchase prompt and its description in the live client first.
- If a guide appears inconsistent after launch, prefer the live objective and official interface until the affected page has been checked again.
Source: Official Roblox UPDATE 2 event
2026-11-07 - UPDATE 3
Type: Scheduled update
Roblox lists UPDATE 3 from November 7 at 4:00 AM UTC through November 13 at 10:00 PM UTC. This is a later announced window, not a claim that UPDATE 3 content is playable on October 25. The event page currently provides a schedule and destination but not a detailed, versioned changelog.
- Wait for the scheduled window, then launch from the official event destination.
- Check whether the experience title, server version, menu options, or objective wording changed before following an older route.
- Verify new badges through Roblox’s official badge list and new passes through the live store prompt rather than relying on screenshots from another server.
- Keep older ending requirements separate from new claims until a current run or official note confirms a change.
Source: Official Roblox UPDATE 3 event
How to tell whether an update is actually live
A date on an event page is the starting point, not the final verification. First, make sure the creator shown on the experience page is • DELTA • and the destination is Place ID 133409496563091. Copies can reuse a similar title or thumbnail while having different saves, purchases, and rules. Then join a new public or private server after the announced start time. An older server can remain on a previous build until it shuts down or restarts.
Inside the game, look for observable changes: a new menu option, an updated objective, a badge that now has an obtainable condition, a new purchase prompt, or a developer notice. A community video can demonstrate a route, but it should match the current menu and environment before you copy its steps. If the video predates the event, use it for orientation rather than evidence that a new mechanic exists.
Roblox event timestamps are displayed in UTC in this tracker so players in different regions can compare the same moment. Convert the time to your local zone before waiting for a launch. Releases can also be delayed or rolled out through new servers, so retrying immediately is less useful than checking the official destination and joining again after a short interval.
What to check after a patch
Start with a low-risk run. Open the mode menu, examine controls, and confirm whether your saved currencies or badges are present. If your goal is an ending, read the objective text and verify the required resources before committing several in-game days. If your goal is Survival, test the early loop and crafting interactions before assuming a balance value from a previous build still applies.
For passes, the Roblox purchase prompt is the current authority for both price and description. Prices can change, and owned entitlements may take a rejoin to appear. The Passes hub records the official values found at its last check, but you should always read the live prompt before buying. For badges, compare the badge’s official name and description with the route you are attempting; do not infer a hidden condition solely from its title.
When an older guide conflicts with the live game, stop before spending a scarce item. Take note of the mode, day, server age, exact objective wording, and where the interaction failed. Those details distinguish an actual patch change from using the wrong tool, playing in the wrong mode, or joining a server that has not restarted.
Update verification checklist
Use this short sequence whenever a new event window opens:
- Open the official Roblox experience and confirm the developer and Place ID.
- Check the official event’s start and end times in your local time zone.
- Join a fresh server after the announced start rather than relying on an already-running session.
- Read the current menu, objective, pass prompt, and badge descriptions before using older instructions.
- Test one reversible interaction before spending Robux or consuming a difficult-to-replace resource.
- Compare community demonstrations only when they show the same mode, interface, and update window.
- Recheck this tracker for a dated entry and source instead of treating the experience title’s
[UPD]tag as a changelog.
This method is deliberately cautious. It keeps scheduled announcements distinct from confirmed playable behavior and gives you a reliable way to decide whether a route needs retesting.
Where detailed help belongs
The update tracker stays chronological. Use the Guides section for first-run setup, controls, and taming Jerry; Endings for route-specific objectives; Modes for Story, Survival, and Creative differences; Badges for unlock planning; and Passes for purchase decisions. Codes remains a single status page until the developer provides an official redemption system or a verifiable code.
That separation matters after a patch. A timeline entry can tell you when an update was announced or became available, while the relevant guide can explain what a player should do. If a mechanical detail still lacks first-party documentation or a reproducible current run, it remains identified as needing verification instead of being promoted into a confident patch note.