were they

>>3231298
yeah, n64 gamesharks were terribly built hardware, so they fail and brick themselves very frequently, but their actual function is insanely cool and gives you a lot of room for creativity, like making your own codes.

like all this shit the speedrunning community came up with:

https://sites.google.com/site/sm64gameshark/

>>3231294
Are we talking specifically about N64 ones, because my PS1 and PS2 gamesharks were fuckin aces.

>>3231393
I opwned 4 gamesharks in a span of 1998-2004
The first one lasted me the longest, while 2 and 3 died shortly after, and 4 is still with me today.

It has the link port on the back but i havent been able to get it to twork

No idea what you're talking about, I used an N64 Games harm for years and it never died on me.

>>3231457
>works on my machine ;)

They only really brick themselves when they've been connected to a Windows machine. Otherwise the only risks for the long term are corruption of long codes.

>>3231641
>They only really brick themselves when they've been connected to a Windows machine.
Nah dude. Out of 6 new in box gamesharks we got our hands on, 2 were already bricked right out of the box. These things have a massive failure rate, and it happens for no reason.

Maybe I'm wrong but aren't n64 gamesharks useful as they allow you ti bypass region lock?

>>3231679
I had the same experience, and not only with N64 gamesharks, although I did go through about three of them back in the day. My GBA gameshark also bricked itself after barely any use at all. I miss being able to modify my games but it's hard to justify sinking more money into these things.

>>3231683
Yeah, and they also let you do cool stuff like dump image and sound data from the cartridge