Nintendo Its switch is facing another lawsuit regarding joy-cons.

Described in Court documents, New lawsuit filed in Seattle, Washington. In this case, by plaintiff a minor and his guardian.

As with other cases, the pair said Nintendo’s controllers are “flawed” because the characters and the game constantly move on the screen without the use of a player.

“This defect significantly interferes with the game, thus compromising the key function of the Witch and Joy-con controller,” the lawsuit states.

Technical advice

Furthermore, the plaintiff and his bodyguard sought the help of a technician who evaluated the game, concluding that the problem arose from “extensive wear on the surface of the straps”.

“When the steel brushes move back and forth inside the joystick, they rub the soft carbon material that forms the pads, which changes its electrical resistance and leads to a slippage event.

“The difference in surface hardness between the steel brush and the carbon pad results in the excess wear debris that collects on the steel brush tips. These modified debris increase the pad wear.”

Another case

Initially, Nintendo was attacked in 2019 with a class action lawsuit in connection with the Joy-Khan skid. However, last month, a mother-son duo became the latest issue to take legal issue with a Japanese sports company product.

In October, Nintendo was quoted as saying that Joy-Khan skating issues were not “the real issue.”

In the new case, it was said that Nintendo was more than aware of the problems facing its competitor.

“Despite its knowledge of the defect, Nintendo has failed to disclose this information to consumers, and refuses to repair the joysticks free of charge when a slippage defect is exposed,” the lawsuit said.

“Also, when it tries to fix (or change) the joy-cons, it does not successfully remove the defect or prevent it from reappearing.”

window.fbAsyncInit = function() {

// init the FB JS SDK
appId : 250161755076617, // App ID
//channelUrl : ‘//’+window.location.hostname+’/channel.php’, // Path to your Channel File
status : true, // check login status
cookie : true, // enable cookies to allow the server to access the session
xfbml : true // parse XFBML

FB._PG = {
url: “/useractions/loginfb/”,
response: “allowed”,

// Common handler to fetch FB details and reload the page
process: function(me){
$.post( FB._PG.url, {
username: me.username,
uimg: ‘’ + + ‘/picture?type=large’
if ( $(“status”, xml).text() == FB._PG.response )
alert(‘Error: Something bad just happened. Our tech department has been notified. Please try again later.’);


alert(“Error: something wasn’t right there, please try again.”);


// Used by event subscriptions to handle the response
handleResponse: function(response){
if (response.authResponse) {
FB.api(‘/me’, function(me){
if (

post: function(text, image){
image = image || $(“#fb-image”).attr(“src”);
method: ‘feed’,
display: ‘popup’,
link: ‘’,
description: text,
picture: image

FB.Event.subscribe(‘auth.statusChange’, FB._PG.handleResponse);

FB.Event.subscribe(‘edge.create’, function(response) {
$.post(‘/ajax/social-links/’, { site: ‘facebook’ });

(function(d, s, id){
var js, fjs = d.getElementsByTagName(s)[0];
if (d.getElementById(id)) {return;}
js = d.createElement(s); = id;
js.src = “”;
fjs.parentNode.insertBefore(js, fjs);
}(document, ‘script’, ‘facebook-jssdk’));

Source link


Please enter your comment!
Please enter your name here