YouTube
Updates
Portal Sandbox Updates: Announcements and Beta Help
Choose between a Portal Sandbox announcement question and a repeated beta issue. The update guide explains the More Content event’s Bounties and More Upgrades scope. The bug guide helps describe a failed action without mistaking future content for a released fix or a complete patch history.
Announcement statusUpcoming content and a confirmed repair are different questions.
Choose your question
Open the answer that matches the task or obstacle in front of you.
I want the announced content scope
Read what More Content names, its recorded upcoming status and the control reference useful for returning play. The guide keeps planned features separate from released changes.
Read the announcementAn action keeps failing
Check the key and order, make a calm retry and describe the visible symptom. This guide prepares a useful report rather than promising a universal beta fix.
Describe the issueAll updates guides
Current beta context and verified released changes.
An announcement and a repair answer different questions
More Content is captured as an upcoming event, with Bounties and More Upgrades named in its description. That scope does not establish a payout table, upgrade price list or a release date. The update article preserves the announcement status and helps a returning player prepare the existing controls. Beta Bugs instead checks the intended action, separates one failed input from a wider session problem and explains what a useful repeated-issue report contains. Use the destination that matches the question you have now; neither a new video nor a product name should be treated as a complete patch note.
Questions about updates
Are Bounties already released?
The captured event listing presents More Content as upcoming. This page preserves that status and does not turn the announcement into a released bounty system, reward list or complete patch history.
Does an announcement confirm my bug is fixed?
No. A future feature announcement and a repeated input problem are separate. Record the action and visible outcome, then compare an actual later fix or current behavior rather than assuming the announced event resolves it.
Prepare the existing actions
Use the exact T/Q/E/F/X reference and the F-before-entry condition before starting a return session.