Maybe its changed since I was last active on the site, but it's not letting me predict pups with wolves that haven't originated from my den, i.e. randoms on the flea market
@Gilneas What device are you using? Like, is it a desktop? Android phone? ios?
I've noticed that people on android in particular have a hard time getting the puppy predictor to work, and someone mentioned it being a little broken in a discord server last night, too. Even the wolf bio editing on mobile is either difficult or impossible for some people, but specifically on android.
It works just fine for me, but I am on ios, and for some reason ios seems to be the more working mobile version of the site. If you're on android, that's probably why it isn't working.
I hope that staff gets the puppy predictor working fully for android devices. I'd suggest posting in the bugs forum as well if you haven't already, since that's the best way to give staff feedback on bugs.
Just in case, unless it is broken for me too, the predictor does not work with custom saves.
I don't think it can be OS specific, but perhaps browser specific, and different OS versions of a browser can potentially have differences.
If I open the console on PC it returns an error, which does however not break it for me and is otherwise invisible. But who knows whether this might break things on other setups. "Uncaught TypeError: n is undefined"
That was the issue I guess! I had saved a preview of a flea market pup as an adult and was trying to use that. Just tried using one without changing it to an adult worked fine
It's doing it to me now as well, both on my PC and Android-based Kindle Fire. Trying to preview my wild wolf I caught as well as a stud I have saved, and won't let me put them in the puppy predictor. So it seems to be an issue with wolves not owned, not device.
@Pewpewkachu Hm, it does still work here However, "Custom" does not work. It needs to have a name showing.
I had to refresh and re-add them to get it to work for me. It also went wonky again after while of using it on my PC (Chrome browser), but this time the Regenerate button didn't want to do anything (which also fixed itself after refreshing).