"Compounded" Peg Lists

[Lukelustre (Luke)]

Potentially someone else might be able to expand on this topic and give other examples, because I think it could be an interesting way to extend a peg list without expending much more memory on it.

Here’s a list of 5 Pokémon, in the order the games have tracked them:

Making a peg list of these are fairly straightforward and pretty easy to retain. However, each of these Pokémon have 2 pre-evolutions attached to them as well.

There’s no point including the other 10 in a peg list as it would be redundant, but while it requires pre-requisite knowledge to actually know the Pokémon, it’s a case where you don’t need to memorise everything in a list in order to still recall them all.

I’ve coined in “compounded” because I think it works by 1 peg being compounded in memorising up to 3 overall; and I’m curious if there’s any major utility to this as a concept, or some other examples where you can retain pegs implicitly.

[Leksanders]

The utility is that you have 2 extra peg lists for free. The only immediate downside that I see is that going through the pre-evolution peg lists will probably require recalling the base list first, and then deciding which pre-evolution list you want to jump to. But that’s until enough repetition makes you familiar with both.

Another way to look at it, though, is that you now have a peg list that is 3 times longer, in which your path is POKEMON1 → POKEMON1 PRE-EV1 → POKEMON1 PRE-EV2 → POKEMON2 → …