Screenshots from a patched bug.

And here's a little guessing game. How do you think something like this was done? And what effect do you think it had?

 

Well I think that has been a follower null of somekind and possible effect was that you could bring that follower to places where you normally wouldn't be able to take it to.

Not sure though cause I haven't seen that before.

Ps. I think I know you from few years ago and we used to do some glitching on rs together.

 

Hmm..were you able to use that pet as a familiar. E.g. make ur yaks look like that rhino. I havent played rs in a while but probably is another familiar named null or something and u made it look like the rhino. Not really a glitch but maybe similar to how you did it. Did u die with it or something. Think i remember seeing a reddit post about someones pet having a weird name of random characters in it but am clueless atm, gonna look for the post.

 

Eh... Actually let's just forget the guessing game. It is quite unfair for me to make y'all guess considering that I am fairly certain that it was only me and the team I was in that knew how to do this.

The glitch to perform it in itself was labeled "Pet fusion" by its founder. Technically pet fusion is not entirely patched, so I won't really tell how to perform it, but I will say that after all of Jagex's attempts to patch it, it is pretty much useless now, as far as I can tell.

The basic idea is that you could fuse any two Solomon's pets together. In most cases, the results were pretty useless. But there was one type of fusion we did get an interesting result from. And that was the fusion of a pet that could be renamed with a pet that could not be renamed.

The result of such a fusion was the weird pet names you see in my above post. And here is the interesting thing. Pet's having erroneous names like that resulted in client errors. Client errors so bad that it would disconnect any player as soon as the name of the pet was loaded. And as such, from the very moment pet fusion was discovered, we knew it was possible to do an area wide mass DC, as players within the pet's loading range would error out.

For a good while, we could only ever perform the bug in such a way that it would disconnect everyone, including the glitcher that performed it. But it was I (as in it was me personally) that figured out the one loophole that allowed the glitcher to stay connected, allowing for a free walk mass DC where player's couldn't stay logged in long enough to even be able to see the players in the area.

However that gets into one thing with this glitch. You'll see in my above post there are two names. The one in the first screenshot was taken in the standard Java client. The one in the second was taken in the HTML5 client. And here's the thing. The main thing that I found that allowed the DC to be free walked was to use the HTML5 client.

It's actually quite odd really. The first name you see above was the first version of the DC bug that I freewalked. And for the life of me, I couldn't tell why that version of the freewalk DC only seemed to disconnect some players. And to be honest, while I don't truly know all the technical reasons why this was the case, but that version (the result of fusing a rhino with a legendary pet) did not disconnect everyone on the Java client. I figured out a little bit of the reason why at least, for I did find that I personally could stay connected on the Java client with that particular fusion so long as I had logged into the HTML5 client at some point since the last server update. But I tended to avoid that version of the fusion as it only disconnected a guesstimate of about 65% of players.

The second one however was the result of a different fusion. And I found that this version could only be freewalked IF and only if you are using the HTML5 client. If you try to login with the Java client with it, you would be DCed no matter what. But it was also for this same reason that I could guarantee that this version of the DC bug would disconnect 99.999% percent of players as for a number of reasons, almost no one actually uses the HTML5 client.

Honestly, I didn't abuse the bug for as much as I could. I didn't want to risk the duel arena for fear of name exposure. I found it to be a complete waste of time trying boss graveyards. So the wilderness was the best I could do. Only made like 70m RS3 gp.

The glitch was patched by Jagex just simply making it so that fused Rhino's don't have weird names anymore. They probably made some kind of change so that even though you still can't rename them, it won't result in errors anymore if they do happen to be renamed in some way.

 

How could you "abuse" this glitch? I don't understand how you could make a profit out of it?

 

Isn't it obvious? Use the glitch to disconnect players in combat and stand over the spot they died to claim loot. Only I could claim the loot as no one else in the area could stay connected except me.