Cooldown on sending Stud Requests

• Force people to think more carefully about who they send a request to
• (Hopefully) decrease the amount of people impatiently removing SR 
• Hopefully be a benefit overall!

Cons:

• If you don't time it right you may waste a wolf's heat. (Ie, removing a SR right before RO on her last day of heat). This could be fixed by maybe a Game Notification blurb : "your wolf is on her last day of heat!" as a reminder. 

Thank you for reading!

Edit: Missed that the cool down was in minutes, need to think on this longer.

Why not tie it a wolf's heat? The cooldown would be active the first three days of the heat, and be inactive on her last day. That way,, we can hopefully avoid the changing studs before ro bit.

Partial support. 

I understand stud racing can be frustrating but at the same time if the female is on her last day of heat that is even more frustrating to have to wait for someone to accept the stud request but they might not accept it in time or at all. I agree with Orias’ suggestion about the cool down being deactivated on the last day of heat. I think if it was implemented that way it would decrease the amount of stud racing but it would also ensure females on their last day of heat getting bred to an outside stud.

not sure if this is even plausible, but perhaps tied to the user’s activity? you can revoke your request with no issue if the user has not been online since you placed it, but once the user has come online the timeout is in session or you can’t revoke your request for a certain period of time?

i agree. 

that is frustrating. 

i think the female wolf that had the studding request moved should be on a cool down. any other female wolf in the same pack can send a stud request to the same male. 

i hope i explain it clearly enough. 

if not please don't please ask me to clarify. 

No support, or the most minor of support if it didn't apply on the last day of a heat or could somehow take into account how long you've been waiting. Stud racing is obnoxious, but so is not getting a response after a long wait, or trying to figure out when it's time to give up on your first choice of stud. I sent a stud request on one of my girl's first day of heat. It is now the last day of her heat. According to the user's profile, they were last online 12 hours ago. I don't know why they didn't respond to the stud request - maybe they meant to and just forgot, maybe they ran out of energy, - but it is now unlikely they will be accepting it in time for this heat cycle, and unlikely that sending them a message would do me any good (and I also find that incredibly awkward and uncomfortable). In situations like this (and this is the second or third time I've encountered something like this) it would be unfair to punish me for their lack of a response. 

The only thing I could think of that would make me accept something along these lines would be if you couldn't revoke your request once the recipient of the request had started to attempt a breeding. Then you'd only be cancelling if they were being unresponsive, rather than cancelling while they're trying to get your female pregnant. I don't know how difficult that would be to code in, however. And, in such a case, I would then like a feature to remind the owner of the stud that they have the request waiting to be finished. 

support! though with consideration to the above comment what if the cooldown only applied if you didn't wait long enough to remove your request? maybe the countdown actually starts as soon as you send the request, and it could be for i was thinking 30min to an hour and if you remove the request before that time is up you still have to wait out the rest of the timer before you can request another stud. but like you said if its been like 12 hours that cooldown would already be gone and you would not have to wait.

no support simply for the last day of heat reason stated above. i'm fine with a cooldown any other time but it's a bit broken that a player has to lose their wolves' heats if the stud wolf's player went offline 30 minutes before RO, just because of a mechanic that protects against stud racing. if you add, say, a 1-2 hour exception before RO there there's no cooldown for wolves on their last day of heat, then you have my support. 

alternatively, i like what HollowWorld7 suggested with blocking revokes after a breeding attempt has been made, but since a permanent block after breeding could be easily abused i want to combine the two ideas together: after an attempted breeding, there should be a 15-30 minute cooldown where a user cannot withdraw their wolves. this way users can freely remove requests if they're panic-studding on their wolf's last day of heat, and if a user requests and revokes a request before the stud owner gets to it, no energy is lost.  

No support unless it's like the users above suggested - the cooldown doesn't apply on the last day, or doesn't apply if the stud's owner hasn't attempted to breed them yet.

I'm one of those people who sometimes need to try to breed a wolf on the last heat day (e.g. because I tried with someone else but they turned out to be inactive) and it'd be really frustrating to be unable to cancel a stud request if someone goes inactive and I need to find an active stud before I go offline myself.

I understand that it's frustrating if you've already started trying to breed and the user removes the stud request, and I agree that it would be good to have a cooldown for those cases.  But if no breeding attempts have been made yet, then there's no harm done if someone removes a request.