Pokemon Conquest Password Generator

This tool generates passwords for Pokemon + Nobunaga's Sister, aka Pokemon Conquest—the official English version of that particular page is offline now, so you'll have to make do with a maybe slightly outdated copy from the Wayback Machine.

Those pages should tell you enough to figure out how to use the password feature as intended.

In addition to spawning pokemon, the password also has the (officially undocumented??) ability to unlock a few events and scenarios that were, in the distant past, wifi distribution. For those of us who no longer live in 2012, though, that's not really an option anymore.

Questions Nobody Asked

Why does this even exist when plenty of these passwords are floating around on the Internet?

Well, aren't you a lucky anglophone?

There are, in fact, zero pages in Google's index which publish a correct password for Okuni's scenario on the Japan release.

What the heck is "order" and how does it matter?

Honestly, it probably doesn't. The game uses a few shoddy mechanisms to "encrypt" the passwords to make them harder to analyze, and one step involves permuting the data bytes based on a seemingly random entry out of a lookup table whose index is essentially left as the third digit of the password.

It's probably not something you need to touch.

What's a "slot" and why are so many of them greyed out?

So rather than actually keep track of what passwords have been used, the game has a fixed number of flags that indicate that no password using that flag has ever been entered. Whenever you enter a password, it marks off the flag corresponding to a number encoded in the password and prevents all future attempts to use a password with the same number, regardless of what pokemon the code was supposed to swarm.

All official passwords use unique slots, and I've left the slots already used by passwords with official sources that I could track down disabled by default, to prevent accidents. You can disable the lock if you think you know what you're doing.

Event passwords use a similar mechanism to mark off whether you've unlocked the event, but this shouldn't matter very much since you only need to unlock them once...

Why are there so many unselectable pokemon?

There is a list of pokemon species for which passwords are always rejected, even though they're perfectly representable by the password encoding. Some of the choices are pretty dumb.

I've left them in the list but disabled mostly just to show that I didn't forget about them.

Why the fuck are the "region" ids 8 and 10? Where are 0~7? What happened to 9?

Look, at one point I had the code parameterized over permutation list * digit list * password length, but considering how different the last step in generating the printable passwords actually, I decided to just flatten the code out into two paths in the process of porting the code to JS.

Anyway, those numbers were originally the password length.