ZenRowe

The Valentine's event was one of the first ones to use the active event system. When that one was set up the multipliers were hardcoded (I believe it predated the newer dynamic config) so it was pretty much the only event that did rates this way (and it never will again)

Also sometimes the particle effects just kind of stop working on them for some reason it seems. if they are reddish coels there is a decently good chance that they are vday coels

The dynamicConfig ini looks off because vday was one of the first first events where we implemented the active event system. There were some quirks with how vday was set up that didn't come to light until the last minute basically.

End result, yes the 1/3 baby food consumption rate is in effect. as is the 2x mate boost range and all the other 3x breeding/mating settings.

the timing for the autostart might be a bit off. It looks like it should activate but might not happen until tomorrow.

I was promised a nutshell...

It should be a relatively small update; however, I can't really promise that. Thanks to the way console updates get chunked for their delta updates (we don't really have any control over that) updates for consoles can end up much larger than we expect. We might only add or change about 200 MB worth of data, but the deltas might register 5 GB. It's really unpredictable.

I am not sure if this can be done safely without potentially introducing other issues. The whole reason the exp bug, the one this thread is about, came to be was because of what looked to be a safe change made to prevent the bug that affected you from ever occurring again but had a cascading effect elsewhere in the code.

That occurrence of exp loss some people experienced is something we have been discussing so I'll bring up the idea you suggested and see if it has already been considered, but I can't make any promises as I don't know if we can do it safely without risking another xp problem. that system is pretty delicate as you have seen.

tis true.

Yes that would have been the cause of the issue for you. What was happening was that if any point along the path that experience was being shared something was at max level, it stopped passing experience down the chain.

So if you were on a max level dino, neither your player or your reaper or any chibis would get experience

If you yourself were at max level, Chibis and baby reapers would not get experience.

Achievement based item skins are tied to your account and don't ever get lost.
Event skins that are purchased through the cooking pot can be lost, stolen, etc. but they don't get deleted when the event ends.

It's not really an expiration, it's that the item version changes to prevent resource rollover on officials for the events. I don't know that it's even going to occur this time, I'm not sure it ever happened before, or if they all just got used up. For unofficials if it does happen, yeah existing ones will vanish but that won't prevent you from turning on the event and earning more again.

Chocolates don't stack, we haven't changed their functionality for this event. If they did ever stack before it was changed at some point. You will be able to keep the chocolates, at least for a while after the event, but I can't be sure for how long.

as for the 1/3 baby food consumption, there was a bit of an oversight with that one and it was too late to try to get it in.

Oh, believe me, there is not an engineer in the office that doesn't wish we were working with a more recent version of UE4.
But it's just not that simple, upgrading across major engine versions is not just a difficult task but in some cases nearly impossible.

I'm not just talking about ARK here, I am talking about pretty much any game. Major engine versions don't just constitute additions but also major rewrites of core engine code. Games getting major engine conversions after release is a rarity, the work involved in that can potentially end up being even more than just making a whole new game from scratch because you have to untangle what has just, mostly likely, become completely inoperable code and figure out where the breaks are to get everything functioning again.

The anti-mesh system doesn't apply to singleplayer and dedicated servers have control over whether or not the system is used.