Leaderboard

I've played a few Soul Link's so far and every time I start my play session for the day it's always kind of an annoying process. Loading up 2 separate emulators, 2 roms, having to rekeybind the controllers every time. I was wondering if someone would be able to make a program that could make it easier. If your unfimiliar with a Soul Link Nuzlocke, heres the rules. 1- Any Pokémon that faints is considered "dead," and must be released or stored in a specified PC box for "dead" Pokémon. 2- You can only catch the first Pokémon encountered in each area, and none else. If the first Pokémon encountered faints or flees, there are no second chances. 3- You must also nickname all of your Pokémon, for the sake of forming "stronger emotional bonds." 4- In a new area, the first encounters for both players will be, "linked," together until death. 5- If one Pokémon in a linked pair is placed in the PC, it's Soul Link partner must be placed in the PC as well. 6- If one Pokémon in a linked pair dies, it's Soul Link partner is considered dead as well. 7- If one player fails to capture their first encounter in an area, the second player must forfeit their encounter in their corresponding area. 8- Across both players parties, primary typings may not be repeated. Basically what I'm looking for is a program that emulates 2 roms side by side and be able to control them individually. I've thought of a few features to make it better. Features -Emulators from all consoles built in - Ex. VBA, Desmume, and Citra -Saves both roms under 1 "project" and loads them on the same side every time -Type Chart ready -Online Remote Play - Be able to join your friends session online to see and control one of the games. -Games connected locally so you can trade and battle -Database where you can input your linked pokemon pairs and where you caught them -Built in Pokedex Database (Not necessary but would be helpful) -Program reads both your teams and displays them between the game (I'm aware that's not an easy ask but if it's possible, why not) I feel like except for a couple of them this is a completely possible thing to create. I know it probably wont happen but I just thought I'd get the idea out there. I love doing Soul Links and I'm so happy people found a way to make Pokemon Co-op. Thanks for your time.

Generation 5 encounters aside from Mystery Gift are generated from two separate RNGs; one for IVs and another for everything else. The range of randomness is sufficient for any value combination to emerge.

The term you are referring to is "PID/IV correlation", which is when the game generates a Pokemon and can reliably be reversed into a starting "seed" that, when run forward, produces all the values expected. For SW/SH raids, the game uses a 64-bit seed to generate the same Pokemon for all raid participants. PID, IVs, nature, gender, height, weight, ability, and level. If the original seed is back-calculated, we run it forwards and check if all the values on the Pokemon match what the correlation gives us. Besides SW/SH raids, there are other encounter types that have correlations, and others that don't; if the game uses the built in cryptographically secure RNG to generate a specific encounter type, each "random" result is effectively unrelated to the previous or next. Wild Pokemon in S/V use the CSPRNG, so therefore are not correlated. However, this does not mean you can use any values you want -- you still should respect the feasibility of probability, in that something with 6 flawless IVs is immediately suspect as "cheated", due to the chances of randomly encountering this result being 1:32^6, or 1:2-billion. It's up to the user to know the differences between each encounter type, and to know the rules and probabilities of how individual Pokemon can be acquired. PKHeX is able to tell you details about the encounter type and seeds it detects if you check the verbose legality report, which can be done by holding control when requesting a legality check.

Editing your Pokemon gives you full control over PKM data; if you change ribbons, only the ribbon byte will change. If you change the string for nickname or OT, then you have to make sure that the data allocated for it matches whatever the legal state should be. Same goes for other correlated properties like PID and IV. PKHeX does a majority of these checks automatically, but some checks like shiny raids take too much time and are skipped.