A Zelda: Tears of the Kingdom gamer discovered a problem that caused a Zonai Dispenser to dispense an endless number of Zonai devices. As many players of Zelda: Tears of the Kingdom are aware, a significant portion of the game centers around the new Zonai Devices that players can discover and gather throughout the globe.
Zonai Devices are an essential part of some of the wackiest builds that players have been able to make, and they’re generally helpful in beating adversaries in battle, completing shrines, and a lot more. One Tear of the Kingdom player has discovered a bug leading to one Zonai Device Dispenser spewing out Zonai Devices indefinitely, which might pave the way for even more bugs.
Player of Tears of the Kingdom finds limitless Zonai Device bug
The problem was discovered by Littleawkward1, who posted a message on the Tears of the Kingdom subreddit with the headline, “Zonai device dispenser won’t stop?!” The OP posted a 30-second video of the glitch in use. The Device Dispenser started spewing out Zonai Devices as usual once the users inserted their Zonai Charges to turn the device on. The maximum number of devices one may typically receive when inserting five large Zonai Charges is 60. However, it didn’t stop there. Instead, even after the clip had ended, the device kept releasing Zonai Devices.
Unfortunately, there appears to be no agreement within the community as to what malfunctioned; therefore, as of this writing, there is no method to duplicate it. That has kept some players from making educated guesses about the bug. One player stated, “This looks like a cut scene error. Typically you have to wait a little while for some of them to spawn in.
This is accurate because there usually is a forced cutscene where Link drops the goods into the dispenser, but there doesn’t appear to be one in this particular footage. They said, “However since you didn’t, it keeps spawning them in until it hits its minimum amount spawned in.’ And because you keep picking them up, they cannot reach the cap. Fans are curious as to whether there is a definite way to duplicate this potential cutscene skip problem, regardless of whether this caused the glitch.
Comments are closed.