Regigigas RNG Abuse

This section of the guide aims to provide a worked example for how to RNG abuse Giratina. Ensure that the Autosave is disabled before attempting to follow this guide.

Important - If you've reached this point, you should have already completed the initial setup and acquired a basic understanding of how to utilize Moarencounterbots, the Main RNG calculation script & PokeViewer.NET. If you do not yet have an understanding of how to use all of the relevant tools, click here to go back.

Getting Started (Delay Calculation):

You will need to calculate the rough delay for this encounter. The term 'delay' refers to how long it takes for the Pokemon to generate after the final A Press. Since the number of frames that advance during the cutscene is variable, it's important to take a few practice attempts to determine a delay that is consistent for you.

Calculating Delay (Step-By-Step)

Save outside Regigigas then walk towards it to begin the cutscene, a text box will appear, this is the screen of the final A press.

Press the Home button (⌂) to freeze the RNG state, then check your current seed by running EncBotCopySeedLA in Moarencounterbots.

Paste your seed produced in the Logs tab into the Main RNG script, then search without filters. This will provide the starting frame.

Quickly unpause the game, then mash the A Button as quickly as possible to initiate the cutscene and enter the battle.

Use PokeViewer.NET View function to read the details of the encounter, take note of the PID of the Regigigas.

Search for the PID in the search results of the Main RNG script, you can manually search through results or use CTRL+F).

Take note of advancement that generated Regigigas, this will be your delay for this attempt. Repeat this process a few more times to get a rough average delay.

Figure 1 - Calculating Delay

After following the delay calculation steps and searching for the PID of the encountered Regigigas, we find that it was generated on frame 13. Therefore, our delay for this attempt is 13. After 5 attempts, we have the following delay values:

Attempt	Delay Value
Attempt 1	13
Attempt 2	13
Attempt 3	10
Attempt 4	11
Attempt 5	16

This means a safe delay value to target in future attempts is 10-16. The delay values shown here are based on how quickly I was able to mash the A button to get into the battle, your results may vary.

Now that we have a rough delay range, it's time to focus on finding a suitable seed and target frame.

Figure 2 - Setting Search Filters

In this example, the filters are configured to search for any Regigigas with 6 perfect IVs (31/31/31/31/31/31). You can further customize the filters if desired, such as specifying a particular nature or optimizing for 0 IV values, such as 0 Attack.

Figure 3 - Target Found

Great! We discovered a Serious natured Regigigas in 1888 advances within a cluster of 8. A cluster refers to a group of frames that produce the same end result; the larger the cluster, the greater the chances of hitting the correct target frame.

Now, we need to advance close to our target frame. Monitor your RNG state by running EncBotRNGMonitorLA in Moarencounterbots; this will track the number of advancements that occur in real time.

Figure 4 - Monitoring RNG State

The RNG state at in Snowpoint Temple advances at a slow rate. Moving to a more populated area allows you to advance the RNG state much more quickly. In the example image above, the player is standing next to a large body of water in an area densely populated with Pokemon.

Consider leaving Snowpoint Temple and heading to a location where the RNG state advances more rapidly if you need to cover a large amount of frame advancements. If you have moved locations, make sure to leave enough time to reposition yourself to avoid overshooting your target frame.

Example

If it takes you roughly 3,000 frames to get back to Regigigas from your position, start to head back to it at roughly ~3500 frames away from your target, leave enough time to reposition yourself to avoid overshooting!

Figure 5 - Advancing To The Target

We are now back next to Regigigas and 194 frames away from the target, now it is time to get to the screen of the final A press and wait for the optimal time to initiate the battle.

Figure 6 - Final A Press

Stay on the final A press screen (pictured above), and let EncBotRNGMonitorLA run until the Logs tab displays the correct target frame. You can use the Home button (⌂) to close in on your target frame at your own pace.

x (earliest target frame) - y (delay) = z (frame to press A)

Figure 7 - Hitting The Target

Here we can see the target is now on frame 92 after re-entering the seed into the script. The calculated delay from earlier is roughly 10-16. This means that once the SysBot log output displays that we are on frame ~82 we have reached the desired target frame.

Once you reach the expected target frame, begin spamming the A button as quickly as possible, then inspect the Regigigas using PokeViewer.NET View function to see if we hit the correct target.

Figure 8 - Result Found!

We hit our target frame and have secured a Regigigas with 6 perfect IVs! That's all there is to it!