Jump to content

2 Screenshots

About This File

This application can generate TID/SID pairs that can be used with the Cute Charm Glitch in Gen 4, and even outputs an Action Replay Code.

You can:

  • Choose the Cute Charm Lead, Shiny Group, and even specify a Trainer ID
  • Even let the program choose the Shiny Group for you (if you want the shiny natures to be a surprise)
  • Choose the button combo that activates the Action Replay Code (for those with broken buttons. Yes, I'm talking about you, shoulder buttons!)
  • Add an Cute Charm Pokemon to be hacked in

 

Compared to RNGReporter (one of the other programs that can calculate Cute Charm ID pairs), this program is:

  • More user-friendly; there isn't all the RNG abuse stuff to get confused about (I still recommend RNGReporter if you plan on RNG Abusing for IDs)
  • Built with everything you need. You no longer need to go online and find your 'Desired PID', etc.
  • Able to output a Action Replay Code
  • Able to choose Shiny Group for you
  • Able to give you a Cute Charm Lead through the AR Code

 

For more information visit the project's GitHub Page.

Edited by RenegadeRaven
Update Link


What's New in Version 1.1.6   See changelog

Released

Changelog:

  • Translated to French
    • I only know English and French, so others will need to make translations for other languages (see #2 for details)
  • Other general improvements

Notes:
Sorry for being inactive for the last couple years. My life has been hell lately with homelessness, a horrible job, and currently unemployment.

  • Like 1

User Feedback

Create an account or sign in to leave a review

You need to be a member in order to leave a review

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

VideogamemasterVGM

· Edited by VideogamemasterVGM

   1 of 1 member found this review helpful 1 / 1 member

I keep getting this error, plz fix!

image.png

Response from the author:

Thanks for letting me know, but it would've been better had you opened an issue on the GitHub repo instead (I would have heard of the problem sooner).

I believe I know what the issue is, and should hopefully have a fix sometime this month. In the meantime you could use a previous version until it's fixed.

EDIT: I've published a fix, although I have no clue if it works on computers outside of my own; so if someone could test it that would be great.

Link to review
×
×
  • Create New...