Babies Dying with S+ Nanny and AA feeding trough?

[Juncky]

I dont know why this is happening but it seems if i leave a baby by the nanny and feeding trough when i log out or go out of range of my base the baby dies of starvation. I have put food in their inventory but yet they still die. If i dont leave my base, then they survive and everything works as normal. Is anyone else having this issue? and if so is there anything i can do to fix it.

[Veeshan]

Lol phew, I JUST downloaded Nanny, glad I didn't hatch a bunch to test. Wish I had something useful to contribute!

[Gran]

You could start with reading the S+ Discussion Board and the Patch Notes for S+
The Problem is know, there is a workaround.

[Humpenstilzchen]

I had this happening a few days ago and was also wondering as to why it happens. In my case it was only a dimorphodon baby that starved to death, but nevertheless it was irritating, since the nanny had honey and more then enough food.
And it happened while I was almost next to it in my base.
Sorry, I can´t tell you why this seems to happen sometimes, I assume it´s just a bug that rarely happens.

[Vesuvius]

Nanny has always had random issues feeding dinos in baby stage.... just got worse with the update.

I always put enough food on them to get to juvenile.

[Juncky]

Originally posted by Gran:

You could start with reading the S+ Discussion Board and the Patch Notes for S+
The Problem is know, there is a workaround.

do you just post comments to be a troll or entice people? I was looking for an answer, not a wild goose egg hunt.

[Juncky]

Originally posted by Vesuvius:

Nanny has always had random issues feeding dinos in baby stage.... just got worse with the update.

I always put enough food on them to get to juvenile.

I do to but they just keep dying. I will look for more info.

[esthergray]

I'm probably wrong but my understanding was that she fed them once they could eat from a trough and gave them their imprints. I think you have to put food int their inventory til then.

[Juncky]

S+ Mod has been fixed, it had a couple updates in the last few hours and i no longer have dead babies when i go out of render.

[Opal]

Still died for me. Put babies out, log off for 4 hours, come back, and 2 are alive, 2 died as soon as I logged in. Got the death message immediately on log-in. Plenty of honey, and different meat types.

S+ nanny is clearly not reliable.

[Seftak]

Originally posted by Opal:

Still died for me. Put babies out, log off for 4 hours, come back, and 2 are alive, 2 died as soon as I logged in. Got the death message immediately on log-in. Plenty of honey, and different meat types.

S+ nanny is clearly not reliable.

Post that on the s+ mod page. Wild card are not responsible for that.

[zerassar]

Also this thread is no longer relevant nor are the fixes and suggestions. The nanny was patched since this thread. This is why some get antsy over necroing old threads.

[Opal]

Originally posted by Seftak:

Originally posted by Opal:

Still died for me. Put babies out, log off for 4 hours, come back, and 2 are alive, 2 died as soon as I logged in. Got the death message immediately on log-in. Plenty of honey, and different meat types.

S+ nanny is clearly not reliable.

Post that on the s+ mod page. Wild card are not responsible for that.

I never said it was wildcard's problem, but it is relevant to this post, hence why I put it here. It came up during my search. Last post was in July so I figured it may still pop up for others, as it did for me.

Originally posted by zerassar:

Also this thread is no longer relevant nor are the fixes and suggestions. The nanny was patched since this thread. This is why some get antsy over necroing old threads.

The S+ mod may have been patched, but it's obviously still a problem. Necroing threads is fine if the information is still current - which this problem appears to persist, since I just had it happen.

Not sure why you bother to respond if it's so egregious to you. You could just...not respond? Move on? You're not "teaching" me anything here. Just flaming.

I'll walk away now and not respond, further. See how nice and easy this is? Magic.

[zerassar]

Wasn't trying to be flaming or teaching. Truly hope you're not so sensitive to think my post was flaming as that was certainly not the goal? You'll be shocked to see what the toxicity is like on twitter then lol.

Was just saying this thread isn't current as it refers to a nanny which no longer exists. The work arounds and fixes described are not current.

[retsam1]

Originally posted by Opal:

Originally posted by Seftak:

Post that on the s+ mod page. Wild card are not responsible for that.

I never said it was wildcard's problem, but it is relevant to this post, hence why I put it here. It came up during my search. Last post was in July so I figured it may still pop up for others, as it did for me.

Originally posted by zerassar:

Also this thread is no longer relevant nor are the fixes and suggestions. The nanny was patched since this thread. This is why some get antsy over necroing old threads.

The S+ mod may have been patched, but it's obviously still a problem. Necroing threads is fine if the information is still current - which this problem appears to persist, since I just had it happen.

Not sure why you bother to respond if it's so egregious to you. You could just...not respond? Move on? You're not "teaching" me anything here. Just flaming.

I'll walk away now and not respond, further. See how nice and easy this is? Magic.

The issue exists not because of S+ but because of other settings and factors. Im pretty sure you already know this. As stated before the previous issue related to S+ was patched. Attempting to misdirect all that into a justification for necroing is a disingenuous reason to say there is "relevance".

But S+ features discussions, whether inane or not, are better served on the S+ forum section of the workshop vs gen pop.

[donovanm21]

Anyone still having this issue? Have giga babies dying when you log out from Genesis 2