PTC Account Gen (Unsupported)
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
PogoPlayer @ 3cce0d5
output/screenshots
.gitattributes
.gitignore
.gitmodules
.travis.yml
LICENSE.md
README.md
config.js
config.py
gmailverify.js
index.js
index.js.original
install.bat
install.sh
makeaccounts.bat
makeaccounts.sh
nicknames.json
package.json

README.md

Nintendo PTC Account Generator Build Status

Supported once again! Please use the PokemonGo-Map Discord for questions.

It seems Nintendo has patched the + e-mail trick for Gmail. Some users on our Discord have tested and reported that Gmail now requires a 220+ second cooldown period between creation of accounts. Using another e-mail provider (tested with hotmail) still works. For automatic validation, forward all PTC account e-mails to a Gmail account and use our auto-verifier.

Please be sure to clone RECURSIVELY example: git clone --recursive https://github.com/sebastienvercammen/ptc-acc-gen.git

An automation script based on Nightmare.js that can create any number of Nintendo Pokémon Trainer Club accounts with a single e-mail address. This only works because Nintendo doesn't check for "email+1@domain.com" e-mail tricks, where the e-mail host completely ignores any part after (and including) the plus sign and sends it to "email@domain.com".

This project was started as a proof of concept: even multi-billion dollar companies that just released the single most popular mobile game (Pokémon Go) sometimes miss the details.

More about plus signs in e-mail addresses on StackExchange.

If you're using Gmail and want to automatically verify all accounts, use https://gist.github.com/sebastienvercammen/e7e0e9e57db246d7f941b789d8508186 The instructions are at the top of the file.

The new version on Nightmare.js now:

  • Checks for usernames/e-mails that are already taken
  • Can screenshot the result page (both on success and on failure)
  • Handles server issues better
  • Doesn't require PhantomJS/CasperJS or fiddling with the PATH environment variable

Requirements

Prerequisites

Usage

Windows Instructions:

  1. Make sure you clone recursively (git clone --recursive [origin])
  • if you download the zip, make sure you also download the submodule PogoPlayer.
  • if you cloned non-recursively, be sure to run git submodule init && git submodule update or ToS verification will not work.
  1. Install requirements with npm install
  2. Run config.py or edit config.js manually. (you will have to edit manually for 2captcha)
  3. Run using makeaccounts.bat.
  4. Wait for the generator to fill in the second page, then accept the captcha and hit submit.
  5. Repeat for all accounts
  6. Find the generated accounts in PogoPlayer/accounts.csv.

It is recommended to keep the username set in your config to around 6 characters.

Linux Instructions:
Headless systems will no longer be able to use the gen due to the captcha requirement, unless you use the autovalidation using 2captcha service (see below)

  1. Run npm install
  2. Run config.py or edit config.js manually. (you will need to edit manually for 2captcha)
  3. Run using makeaccounts.sh.
  4. Wait for the generator to fill in the second page, then accept the captcha and hit submit.
  5. Repeat for all accounts
  6. Find the generated accounts in PogoPlayer/accounts.csv.

There is a few command line arguments for index.js if you run manually. node index.js -h for more info.

It is recommended to keep the username set in your config to around 6 characters.

Auto-validation Instructions:

  1. Create a 2Captcha account at http://2captcha.com/
  2. Make a deposit or start working to have a positive balance
  3. Navigate to "2Captcha API" page and copy the API KEY
  4. Update config.js to enable autovalidation and paste your API KEY
  5. That's it, run the script as usual. You will be switched back to headless mode automatically

Configuration

1. Generate 10 accounts in the format USERx, where x is 0 to 9.

This example corresponds to the default settings. It will generate 10 accounts in the same format: user0, user1, ...

In config.js:

// Starts gen from startNumber to endNumber, determining how many accounts are made startNum: 0, endNum: 10,

// Creation Options
nicknameFile: false, // Use nicknames file, or just append numbers to username?
randomPassword: false, // If true generate a random password, If false set "password" field below
screenshotResult: true, // Saves a screenshot per account creation when set to true
screenshotOnFailure: true, // Saves a screenshot even if registration fails when set to true

// Creation Requirements
username: 'CHANGEME', // Keep the '', User- & display name. Make sure any "(username + number)@domain.com" is 100% unique, and is 6 characters minimum, but under 14 characters after the numbers are applied.
password: 'CHANGEME', // If you set randomPassword to 'false' above change this to your chosen password (so you have same password for all accounts)
emailUser: 'email', // Enter your email address name. If your address is email@domain.com you'd enter 'email'
emailDomain: 'domain.com', // Domain of email address. If your address is email@domain.com  you'd enter 'domain.com'
latitude: 'LATITUDE', // Location Latitude for initial login
longitude: 'LONGITUDE' // Location Longitude for initial login

2. Generate random passwords per account.

Set randomPassword: true, in config.js.

Password for accounts will be random, aftyer finished find usernames and passwords in /PogoPlayer/accounts.csv

3. Save screenshots (Default directory is /output/screenshots)

screenshotResult: true, // Saves a screenshot per account creation when set to true
screenshotOnFailure: true, // Saves a screenshot even if registration fails when set to true

4. Use a list of unique usernames instead of USERx combinations.

To create a number of accounts with custom usernames instead of user + number combinations, change index.js:

Set nicknameFile: true, in config.js.

The list of unique usernames must be stored in nicknames.json. An example is available on the repo.