Alrighty, I see people really want to engage on this topic, so I’ll do my best to keep going with this.
First things first, before I begin answering these latest posts - I do want to apologize if communication has been lackluster in the past. I’m going to do better going forward, and I’ll be making sure to discuss the important points with the rest of the staff so that we can do something about it as and when we feel it is needed for the game’s improvement.
One point that everybody seems to be bringing up is that it’s taking much longer than any of us would like. I know I said that “things take time” earlier, because I’ll freely admit I don’t know how long it will take for the underlying issue (egg shinies having the same static rate for all eggs) to have a better implementation ready, and the last thing I’d want is to rush the programming work.
In general, when plans are made to do something in a specific way, we try to stick to those plans and avoid temporary/janky workarounds (as it’d cause even more work to do later to clean things up). That’s probably why we’ve been roadblocked on this for a long time now, as this is a programming issue and PMU’s codebase can be difficult to work with.
But as with certain other issues, like evolution forms not quite being supported yet, we’ve occasionally done something to make a Pokemon accessible such as specially flagging Exeggcute in Sandy Shallows to evolve into Alolan Exeggutor or with Espurr/Rockruff evos. We are open to change our minds on this stuff if things aren’t moving fast enough.
So, after looking at this, and chatting with people on the subject, and thinking about how long it’s been (and how much longer it would probably take)…I think we’re more open to the idea of making egg exclusives have a recruit option somewhere. We’ve been discussing this internally and have come up with a number of ideas - several of which I’d like to see greenlit. And these changes to add/modify recruits in places is something that can be done fairly quickly when we know what needs done, as Drayden/Zappeh pointed out with the example of an unrecruitable shiny Abra in Spectral Thicket.
But we’re also taking the time to talk things out and get opinions and viewpoints shared before committing to changes; if things are changed too quickly, it might not have enough quality control to make sure that these changes make sense, and it’ll be difficult to undo a change that was committed to without making people upset. We don’t want to be rash about this, but we do want to work on this.
Now on to more specifics, since I’m sure you guys want to hear at least a bit about what we’re thinking about. I don’t want to say too much and spoil/promise stuff that’s still being discussed, but we’re looking at the list of egg-exclusives and brainstorming what we could do. Some of them are pretty straightforward, such as the Dewpider that’s already been added as a recruit to the three Lakes dungeons (which at some later point we’d like to just completely overhaul to give them more character/purpose, they feel rather empty and off-putting right now). Some are less straightforward, like the discussions we’ve had about Munchlax, Cleffa and Happiny (due to their status as baby/incense mons where they have an egg-related gimmick). Some actually had prior plans in place to be introduced in upcoming stuff we’ve been working on, but I won’t say which one(s) specifically here. There’s even been an idea proposed for Lapras specifically that has merit.
I can’t promise that we’ll get to the entire list, but some (more) changes may be coming shortly.