Broodmare retired before foaling

Breeding
1

I just had a broodmare retired before foaling in Feb. What happens to the foal? Will is still be born? Or is it deceased? This is the 1st time it has happened to me & was curious what the outcome of the foal would be?

This is from the FAQ
If a broodmare is set to retire before she has her last foal, the foal has a chance of being born premature, or if the mare dies too early (i.e. in October when the foal is due in March), the foal will die.
Her due date is Feb 9th so she is within the “4 wks early to 6 wks late” foaling time.

Will it show on my page the outcome of the foal?

Thnx in advance to anyone who has had this happen & can give some insight.

2

The way I read it, since the mare retired before foaling, the foal was lost as well.

3

I read it as if she dies the foal is lost. She’s only retired, so you may get the foal early, you may get him/her on time.

4

The code (and FAQ) are meant to mean what people above have said: If the mare is bred and is due Feb 10, but retires on Jan 31, there’s a chance the foal is born prematurely on Jan 31.

The way the code actually works, though, is that there’s a chance the foal is still born on Feb 10. So you’ll need to wait and see if a foal appears.

I’ll be reworking the system/wording in the rewrite.

5

Ive got my fingers crossed the foal makes it. It doesnt say deceased anywhere. So Im hoping that is a good sign.

Thnx guys for the insight

6

I have a broodmare, Lupe Valez, View Horse: Lupe Valez who appears to have been retired today.

According to her Horse Info page, she is in foal to Sponsored and is due on 4/9/2030. Do I just wait until that date to see if she does foal or assume that she will have lost the foal?

I found this topic from FF 2011 but there was nothing to say what the outcome for the foal was.

BTW - There was no notification in our Stable Alerts about the retirement, so I had to wade through our broodmares to figure out which mare it was. The only way that I knew we’d had one of our broodmares retired or deceased was that I saw in our General Statistics that we’d gone from 154 broodmares down to 153

7

Got notification this morning that Lupe Valez had died. Still no news about what happened to the foal she was expecting, due April 9th.

8

I looked into the code - retiring a mare doesn’t stop her from foaling, it just means that it’s her last foal.

Death, however, either kills the foal (if it’s due too much later than death), or causes it to be born premature.

Looks like in Lupe Valez’s case the foal should be dead based on her death date / foal’s birth date.

9

Oh, weird, she had 2 2030 foals, by different sires. One was born on Feb 16 (when she died, so the code handled it fine) - View Horse: Hogwarts Werewolf

The other one shouldn’t exist - View Horse: (I set it to be stillborn on Feb 16 before noticing the other foal)

I’m currently working on migrating the breeding/due dates code over to the new app, so hopefully nonsense like this won’t happen.

10

Hogwarts Werewolf was actually born on April 20, 2029 and, as of yesterday, she was 14.1h.

11

Hm, interesting. Not sure what the code did to change her birthday, then. I’ve changed it back. Her height should reset tomorrow.

So I think that’s everything “working” - the 2030 foal died due to being too premature, it’s just that the code somehow picked the wrong foal to count as the unborn one.