
Eventually, we found that we could use a Chrome extension to essentially take certain scripts and redirect them to modified versions, allowing you to access almost anything, and even making it all visible to other players. But at the same time, we found a much easier way to do things.Īt this point, we were trying to find a more efficient way to access, well, everything. But eventually, again, we found another called Boot. Eventually, Prodigy did manage to patch sprintF, and we were without hacks for a while. But eventually, we found that we could run a very simple script as a bookmarklet to counter this.

(Not the easy one.) Eventually, Prodigy even blocked the Chrome console, making it almost impossible to use these said exploits.

This worked the same way as the first enableDebug method. But fortunately, soon after, we found a new function, called sprintF. The function enableDebug was deleted completely as of. We only had that for about a day or two, unfortunately. This made it possible to do things like not need to answer questions, monitor the game FPS, and possibly set your Arena Rank (we didn't look into it.) Yeah. We found that we could use a more complicated string to return script-based hacks. Anyways, for a while, we lived with that, and it was hard for some inexperienced people to access these hacks. Due to how it wasn't very user-friendly, we started to lose views on our website, and that was that. So we tried to explain how to access this. The method to exploit was much harder, and I'm not going to go into it, but you couldn't just copy and paste. We found another vulnerability, found in a function called enableDebug. After this, we thought we didn't have anything else we could do. We could access everything they had patched by using Phaser.GAMES instead of PIXI. This was patched soon after, a week or two after, even. Soon after, however, we realized Prodigy was STILL just as vulnerable as it was. Prodigy announced it would fix the PIXI variable. As you may know, Prodigy reset these accounts, but it had the desired effect. Some of you might know what the name was, but for those who don't, it was Bobby Fancywoman. How else would we be able to show Prodigy that their security was fleeting? Something EVERYONE can see! So, we created 30 identical accounts, with the same name, level, etc.

We had started to be able to hack arena points. Until.Īt this point, we had developed an idea. We found things like free membership, level hacks, currency/gold hacks, basically anything you can think of. We reported this to Prodigy multiple times, and they didn't do a thing for the longest time. Basically, anything you put under the string was going to save and was exploitable. PatheticMustan found a variable in Prodigy called PIXI that could be accessed from the Chrome console (Like, control+Shift+I).
