Mario Kart MB - Print Page

Mario Kart MB
https://www.mariokart64.com/cgi-bin/yabb2/YaBB.pl
Mario Kart >> Mario Kart 7 >> MK7's Protocol
https://www.mariokart64.com/cgi-bin/yabb2/YaBB.pl?num=1520800026

Message started by Dos Santos on 03/11/18 at 12:27:06

Title: MK7's Protocol
Post by Dos Santos on 03/11/18 at 12:27:06

Hello guys,

This is a thread that most people hate to see to appear on their game. Sadly,as you may know,hacking in MK7 has been possible for quite some time,and things like modifying your CC as well as adding shrooms or whatever is now possible (including CTs)

Now what confuses me is that I recently came back to the game and some players are accused of cheating. And somehow,none of the players have actually made a decent protocol,that is good enough for players to prove themselves legit.

And thats why I need everybody's thoughts tonight on how we can prove no one in this game is worth banning.I have been thinking about a new protocol,that does much better than Ray has done to prove his rAF WR was legit.

[media]http://www.youtube.com/watch?v=D2y0Yiryzb0[/media]

This video says a lot about how Ray proves himself legit. I honestly think it is decent enough to prove legitimacy. HOWEVER... I have heard that it is possible to still hack despite what he has done. Therefore,the new protocol would include:

- separately showing your console(s), your mk7(s) ( both sides to show they are not customized), and your SD card.
- launch the console live
- go to the system settings to prove this console is not hacked ( instead of Ver., Sys. should be appearing for hackers)
- Prove you can update your console.
- insert mk7 live
- launch mk7 live
- go to the mk channel and prove your stats
- go to time trials,depending on the track,you will have to prove each wheel and each glider does not affect by any mean the actual speed,accel,etc of your combo
- play the track against 7 ghosts ( also has to include Super Staff ghost )
- keep up with your own pr, i understand that not pring live by showing hands is hard

Thats what i would add to this protocol.

Please share your thoughts.

Thanks for reading

Title: Re: MK7's Protocol
Post by Frederiek on 03/11/18 at 13:36:44

Hey Diogo,

I find your protocol very detailed and severe, but also useful in certain cases. If you need to take away all doubts from a certain player.

If you ask for a protocol, I made this text in April 2016, and I think WillD, Ray and Nicola agreed with it back then.

5C687F7E7F68737F712A2C1A0 wrote:

Picture proof, like on twitter, has low value.

Graphic screen pictures (doesn't matter if it's on miiverse or not) and timescrolls have also low value.

Better proof is:

-A Miiverse post that shows a picture of the track and the endtime (topscreen) + the splits (bottom screen) posted in the comment
-or video proof (replay or live).

Maybe we can require one of those two for a WW top 10 time. If they don't provide such proof, they risk that their time will end up in the pending section.
For WR proof, we can ask (or recommend) both. Video proof + the use of miiverse what gives us some kind of guarantee that there was no hacks used for that run. (I wouldn't immediately deny the WR if it lacks proof, but it would raise suspicion. But if the majority thinks we should be more strict and we should deny WRs when there is insufficient proof, that could work for me too)

The video proof would even be more trusted if it uses the original sound and no music was added. And/or that the video shows top and bottom screen simultaneously during the entire run.

But they shut Miiverse down later. That was a problem. Miiverse was a platform where proof could somehow be trusted. Because its use required the latest 3ds software update.

The current protocol that the WW top 10 is using is this:

754B4E4E121B1B1B16220 wrote:

Notes:
-Times that are proven with picture proof MUST show both screens, or the top screen shows "NEW RECORD!" and/or "New ghost data created." visible, otherwise the time will be invalid and placed in the "Pending times" list.
-All No-Glitch times require a video as proof from players that haven't earned a trusted status in the community.

I can agree with this protocol. But it should be more severe for players who are new to the community imo.

So... that’s what I wanted to add.

Title: Re: MK7's Protocol
Post by Saakito on 03/11/18 at 14:04:41

I don't really understand the steps "prove your stats" (since the stats have nothing to deal with time trials) + "play the track against 7 ghosts" (why 7 ghosts specifically ?)

I would add that if i remember correctly players who have boot9strap installed on their 3DS can update their system while keeping the 3DS hacked, so the step "prove you can update your console" could be bypassed.

but otherwise it's certain that this is a very solid protocol.

Title: Re: MK7's Protocol
Post by Dos Santos on 03/11/18 at 23:11:11

Stats should be shown because you'll have to show your combo's stats to be sure that no kind of add has been put to the kart or your mii's general stats.

7 Ghosts - It would be to make sure the ghosts dont glitch or whatever could happen. On MKW you were forced to race Expert Staff Ghost in order to prove you were legit,but in this game you can race it along with your ghost.

Ok,I believe you onto update things. Therefore the Data Management has to be shown.

Title: Re: MK7's Protocol
Post by Dos Santos on 03/12/18 at 03:18:35

Jacob is the first player that has proven 2 players's legitimacy.

His and Thomas.

[media]http://youtu.be/VEyq6acgNaQ[/media]

https://youtu.be/VEyq6acgNaQ

Title: Re: MK7's Protocol
Post by Derek Maguire on 03/12/18 at 11:17:30

Luma game patching can be used. So the protocol video Diogo made is lacking one thing. The only way to prove that you don't have luma or that game patching is disabled Is to hold select before you power on your 3DS. Also the custom version string sys doesn't appear on a hacker's 3ds unless they enable that option in the luma config. Same as game patching isn't used unless enabled. Holding the select button right when you power on immediately should be done. What hackers most commonly use though is NTR. Which contrary to what most people think. Luma game patching can also be used. Additionally. NTR only breaks usually when native firm is updated. And luma survives system updates because of preventing native firm from being written to the firm0 partition on the nand. As for data management showing system apps and games; games installed from something else would not work if you had flashed back to native firm on your firm0 partition. Note: your console would use firm1 if you corrupted firm0. If both firm0/1 were corrupted at the same time you would get blue bootrom error screen. Provided the firms were invalid. If they have a valid header, signature, and hash it would be black screen only. Both cases would mean a bricked device that wouldn't boot into home menu. Default consoles with no custom firmware have native firm flashed to firm0 and firm1. Firm0 is how a device boots up. It is launched and then sysmodules are loaded and then home menu would load. the best possible proof would be pressing select while it's booting and holding it before power on and then start on another power on. As well as taking out your SD card and showing your folder file structure on it on a computer. Since a hidden luma was made before by a guy that forked the original. Hope all this knowledge now helps

Title: Re: MK7's Protocol
Post by cros107 on 03/12/18 at 14:21:28

I understand most of this, except showing inserting your cart and proving your system isn't hacked. My system is hacked and I don't play with a cart. Hacking your 3DS has a lot more uses than just cheating.

Title: Re: MK7's Protocol
Post by Kleenex on 03/13/18 at 00:40:31

51405D41030205320 wrote:

Yeah, I've got PKHex since a year or so and I set all of my latest PRs on a hacked 3DS except for rDKP. I don't think PRing on a hacked 3DS should be an issue, especially when the hacks in question don't even affect the gameplay.

Title: Re: MK7's Protocol
Post by Dos Santos on 03/15/18 at 01:20:02

Proving hacks are disabled after showing your system shall be added.