Tonight I listed two of my wolves for stud, and was caught off guard by them seeming to have immediately been put into Resting. I made a thread in Help about it, because I didn't understand how that would make the feature even functional with a 7 day max listing and an 8 day cooldown, and after some back and forth being super confused, I got a notification that one of them got used, so he wasn't in an actual cooldown.

This is the wolf that was successfully studded: https://www.lorwolf.com/Play/WolfDetails?id=12619

This is the other wolf I listed that (as of now) has not been studded: He got bred after posting so he's now on actual cooldown https://www.lorwolf.com/Play/WolfDetails?id=12084

This is Siri's “cooldown” that I see on my end. Strawberry's was identical until he was bred and reset to 8 days upon being bred.

@Tserin
did a little test and it seems that your wolves do actually get put on cooldown when up for stud
…it seems that you get cd when you put them up for stud and when someone buys the listing. i wouldn't say its a fake cooldown since it still functions as a normal breeding cooldown you get when you breed your wolves together (siri shows up as resting to me too, by the way) (i hopefully didnt make you any more confused… i can give you 100 corn as an apology…)
this is just. weird. lmao.

@monarch

Huh, yeah, I assumed I just couldn't breed him myself because he was listed for stud, but that checks out if it's an actual cooldown. I don't really want him to take him down to test that idea bc I'm trying to raise the money for a wolf on hold for me lmao and having him on cooldown for 8 days would not be helpful, but yeah, that's so weird. I guess the first cooldown just doesn't work properly because it's probably not supposed to be happening in the first place (because again, 8 day cooldown + 7 day max listing = ??????????) or something?

The cooldown of a stud happens at the time of listing the wolf, not at the time of breeding, which makes no sense. I asked about it in the discord but I was told that it was how the site was coded. It wasn't elaborated on further so I don't really understand what it means in regards to how or if they will fix it.

I listed this wolf for stud but then decided to change something, so I took his listing down.
https://www.lorwolf.com/Play/WolfDetails?id=7895
He had immediately gone into cooldown so now I can't do anything with him for over a week. He's on cooldown when he didn't even breed.

There is no warning about this happening and it feels extremely punishing. You can list and unlist all other FM listings at will, so why would anyone assume unlisting a stud would make him unavailable?

Fun fact: this means it also happens when a stud listing fails to sell, which also feels bad.

There have been a few threads about this and I'm going to keep responding to all of them that pop up because I think it's a really important issue to fix. The studding feature is extremely cool but I don't want to use it if it works like this. I've also responded to a thread about supporting private studding, which is a good solution if the site code truly doesn't support changing when the cooldown of a stud is triggered; if the site supports private studding, at least the wolf will be bred through direct arrangement and the cooldown can serve its purpose.

That's a really confusing way of doing it, because my wolves absolutely went into cooldown upon listing and then had that timer reset back to 8 days upon the studding being bought. It just… makes no sense to have the system intentionally working this way. And it also just doesn't make sense for the wolf to be on cooldown but still breedable like, ???? how did they manage to code it this way lol why have a cooldown that only exists if the wolf Doesn't breed

this just occured to me, i just wanted to adjust their prices and now i cant list them anymore ;-;

Another bump from me. These fake cooldowns are a huge inconvenience. It's one thing if the wolf actually breeds, but when it doesn't and we can't do anything with the wolf anyway, it feels like we're being punished for making a mistake.

Bumping this because it's a frustrating waste of time when the breeding didn't even happen. This needs to be changed.

There are a couple suggestion threads about this, as I believe during beta and/or EA it was confirmed that it was working as intended, and not a bug. Might be a suggestion gets the type of attention it requires to get this ‘fixed’.

Just happened to me too, frustrating to see that this isn't actually a bug. Going to find that suggestions thread.