MEGApack update.

These are some interesting findings.

The problem was indeed in _AdvMapObjectLink. I fixed it, and now it works correctly for new creatures.

HOWEVER - the new creature, 2993, is displayed correctly, but the old ones are not.

This is because the files added to GameMechanics, or more likely in the links or somewhere else - are newer, and they are read over the already added creatures.

That is, if we add Core with new files, then we need to update all creature packs with at least a minimal edit, so that they are newer and read over the blank creatures. Because replacement files are read by date.

I will re-upload the files, and I will think about what to do with the problem of old (by date) creature pack files.

Today I added a normal new Core; yesterday, I mistakenly attached the standard one to this message.