Hide

On 2/6/2017 at 6:50 PM, evandixon said:

Nintendo has released update 11.3.0-36.  It patches safehax, so if you do not have CFW installed, do not update if you wish to install it (instructions can be found here).  Without CFW, updating will prevent you from using save editors like PKHeX or ROM hacks until homebrew is updated.

Evan, I got OOT Hax on my system, and it's been working fine (I have not updated to 11.3.0-36).
I want to make things clear, if I update, Am I going to need/wait the new payloads?

10 minutes ago, neto3333 said:

If i dont have my game synced can i get banned??

Editing your save-data is not a guaranteed ban. You need to connect to their servers, and they need to tell whether or not you changed the information they care about.
That's why people recommend not connecting to Pokémon servers at the moment.

13 hours ago, Sabresite said:

For the sake of argument, lets say I wanted to go fully legit.  Could I wipe my savegame and be ok? Or would that count as changed data too?

I believe you will be OK.
Isn't your Pokémon player ID different from your Device & Marketplace User ID?
Market wise, it would not be good banning a device, lest they disturb their other franchises.

 
I wouldn't be so scared; it could have been anything from powersaves to PKHEX.
 
As a game-shark user from the gameboy era, I noticed that generating Pokémon or (anything else) trough HEX editing was not a simple task. Your code has to take into account all the stuff involved with the changes you make: For example, sometimes, in-game acquired items trigger changes in your save/game, while "illegally acquired items" do not. If you own the original code, you can “quickly” scan the game and detect such irregularities.
 
It was rather obvious when the things scaled to GBA and the DS, it was a pain getting your Pokémon right. I remember it was when the first “Pokémon consistency check” software was launched.
 
Perhaps there will be need for a “Pokémon saved-game consistency check” software, in the future?
 
If you ask me, I think it most of it was powersaves, because their codes do not take into account trainer data or the fine details. As far as I know or as far as I am concerned, they just duplicate the same stuff in whatever saved-game you tamper with.
 
That happens when you are deprived from making your own codes.
 
On the other side, I believe PKHEX is primarily intended to help you grow with your Pokémon and have fun with them; I don't know how PKHEX works from the inside, but if I was going to work with save data, I would try my best to make my edits work -exclusively- with my target-data. And I think the science behind PKHEX's is focused on that subject.
 
As long as you stay within the boundaries, you will be fine, I think.
 
So, it is pretty obvious to me: Whatever method they employed, those bans are the result from exceeding the limits of the game using external devices. Pretty much, it was people getting greedy.
 
I did not expect that people capable of editing their saves were so privileged… I think that 6'000 of banned individuals is a very small number (considering market size and demography).
 
You can always start over, just take smarter shortcuts.

Well, what you said simply confirms what I Just told.

I don't see why would home-brew communicate to the official provider by its own. As far as I know, booting home-brew lets you work "on the fly"... It is like booting Linux from the USB.

Most probably, those banned played "restricted software" trough home-brew and connected with such software to the provider; the provider just did the standard thing: Checking their physical addresses, and telling whether or not this software was standard-compliant. They could have bricked the devices, but they did not...

Copies from "the other marketplace" and their accessories (i.e. tickets), are often tagged in the wrong way. So, home-brew stuff should have been running a fail-safe to protect your system. That's basic, and a must for auditing. Surely that's going to be "the solution" for this situation; some kind of way to renew and cover your "console's ID".

Has anybody tried replacing the console's network adapter? It is one of the cheapest ways to flag a device (that's what other companies did in the past, with other components from their consoles).

It seems there is a lot of speculation around this. Most obviously it is players gaming on-line with the same software all around the world. Thousands of copies of cloned data from a single source going back and forth from local systems to N's servers shall definitively raise a flag.

How is it going by now?