Quick answer: use the Taser on 30 guests
For the version shown in the Steam discussion, Use the Taser on 30 guests is the practical reading of the 0/30 Channel Energy Through Guests task. Steam marks that reply as the answer after the player mistook the objective for a building requirement. The answer does not mention a water gun. It also says the responder could not remember whether only “bad” guests or any guest counts, so guest eligibility and current PC/PS5/Xbox behavior remain Pending verification.
That is the action to test, not a complete unlock guide. The source does not provide coordinates, a named guest, a required area, an exact charge level, or a guaranteed current count. Follow the task shown in your build and use this answer to interpret the intended action.
Before you test it, record the platform, game version, mode, save, host/guest role, full objective wording, and current counter. Protect the park. This page was checked against the source on 21 August 2026, but the action has not been field-tested on every current build.
Why this objective is easy to misread
“Channel energy through guests” is indirect wording; it does not naturally say “use the Taser.” The player in the Steam discussion searched the build menus for a Zen object or energy-related construction, and the marked answer clarified that the task was not about building. That is why the exact phrase sends players looking for a construction item.
An older description can remain in screenshots, videos, translations, or cached search results after the objective changes. Compare the phrase in your build with the discussion before assuming the same stage. If the current game uses different wording, capture it and treat the action as Pending verification for that version.
Localization can add another layer of ambiguity. Do not turn a strange literal translation into a new mechanic or a different tool. Keep the English task name next to the local text when reporting a mismatch.
The objective can also be confused with general cooling, spraying, safety, or guest-service tasks. The marked clue specifically identifies tazing guests for the discussed task. Water-gun objectives are separate reports and require their own evidence.
What the Steam answer confirms
It confirms the action: use the Taser on guests rather than build an object. Steam marks the reply as the solution in the discussion, which is stronger than an unmarked guess. It is still tied to that discussion's version and wording, and it does not document where or when the Taser unlocks.
The task title establishes the displayed target of 30 in that reported build. It does not establish whether repeated actions on one guest count, whether only bad guests are eligible, whether the host must act, or whether modes alter progress. All such conditions are Pending verification.
The answer does not confirm an exact keyboard, controller, PS5, or Xbox input sequence. Use the current game's interaction prompts and control settings. Button names copied from another platform can create a false failure.
Finally, it does not prove that a counter that stays still is user error. Console launch reports included objective and non-host interaction problems, so a version or synchronization issue is a possible lead. It must be documented rather than assumed.
If the counter does not move
Record the counter, perform one clear Taser action according to the current prompt, and record the counter again. Repeat only enough to see whether the action is consistent; the source shows a target of 30 for the reported version. Keep the host, mode, area, and version unchanged.
If the counter advances, note whether it was a new guest, repeated guest, host, or multiplayer guest action. One result supports only that tested condition. Do not publish a universal required count until the task itself displays it or repeated current tests establish it.
If it does not advance, confirm that the Taser effect visibly occurred and that the correct objective is active. Preserve the exact wording and action. A normal water splash is a different interaction and is not supported by the marked answer. Exact Taser controls and unlock conditions are Pending verification here.
Steam 1.0, PS5, and Xbox should be tested separately. A PC solution can identify the intended mechanic while a console patch affects input or tracking. Platform-specific counts and behavior are Pending verification.
Platform and mode differences
Official platform facts confirm Steam PC, PS5, and Xbox Series X|S editions, while Xbox lists online co-op for two to four players. They do not confirm that this objective tracks identically on each platform. Console launch community reports included objective-tracking trouble, but they do not prove that this particular Taser task is currently broken.
In multiplayer, compare host and guest. Have the host perform one action and record the counter, then let the guest perform the same action under the same conditions. A host-only result may indicate progression ownership or synchronization, not a hidden guest restriction.
Easy, Normal, Hard, and Sandbox behavior is also unverified. Do not assume Sandbox disables tasks or Hard changes the count. Include mode in the record and avoid copying a result across saves.
Controller and keyboard prompts can differ without changing the mechanic. Use the current binding shown by the game, and report the action rather than guessing a button. Cross-platform play is not supported, so every multiplayer test stays within one platform family.
If the counter remains unchanged
First stop repeated attempts and preserve the task text, counter, visible effect, platform, version, mode, and role. Confirm the task is active and the current game update is installed. Then return to the title normally and retry one smallest eligible action.
If a host succeeds but a guest fails, preserve the role difference and report it as a multiplayer tracking observation. If neither succeeds, compare a clean unmodified session and current objective wording. Do not install a trainer or PC mod to force progress because that would invalidate the test.
Do not delete the save, clear cloud data, reset research, or abandon the park as an early workaround. The research does not establish those as repairs. A new comparable save can be a diagnostic comparison, not a command to discard the original.
Report unresolved behavior with platform, version, mode, host/guest, exact text, before/after counter, visible effect, and reproduction steps. Link the developer-marked Steam answer and state that current counting remains Pending verification. That gives support enough context without disguising a historical clue as a guaranteed current fix.
The short version: use the Taser on guests, with 0/30 shown in the source discussion, then follow the current counter and prompts. Do not invent an eligible guest subtype. Update the page only after official notes or reproducible current-platform tests add evidence.