vasik
Auto-translated
Interesting observations, though.
The problem was indeed in _AdvMapObjectLink. I made the change, and everything is now working correctly for the new creature.
HOWEVER - the new creature, 2993, is displayed correctly, but the older ones are not.
This is because the files added to the game mechanics, or more likely in the links or somewhere else - are newer, and they are read over the already added creatures.
In other words, if we add the Core with new files, we need to update all the creature packs with at least a minimal edit so that they are newer and read over the blank creatures. Because replacement files are read based on their date.
I will re-upload the files and think about what to do with the problem of the older (by date) creature pack files.
Today, I added a proper new Core; yesterday, I mistakenly attached the standard one to this message.
The problem was indeed in _AdvMapObjectLink. I made the change, and everything is now working correctly for the new creature.
HOWEVER - the new creature, 2993, is displayed correctly, but the older ones are not.
This is because the files added to the game mechanics, or more likely in the links or somewhere else - are newer, and they are read over the already added creatures.
In other words, if we add the Core with new files, we need to update all the creature packs with at least a minimal edit so that they are newer and read over the blank creatures. Because replacement files are read based on their date.
I will re-upload the files and think about what to do with the problem of the older (by date) creature pack files.
Today, I added a proper new Core; yesterday, I mistakenly attached the standard one to this message.