Connection ErrorBad RequestThis page went staleSession ExpiredSign in requiredForbiddenNot FoundToo Many RequestsServer ErrorBad GatewayService UnavailableGateway TimeoutHTTP Version Not Supported
Session Expired
Your session has expired. Please log in to continue.
Sign in required
You need an account to do that. Sign in or create one — it only takes a minute.
This page went stale
Your security token was rejected, usually because the page sat open too long or you signed in elsewhere. Nothing was saved. Reload the page and try again.
Request Failed
We encountered an issue while processing your request.
Please check your internet connection and try again.
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.
Here, a silly idea struck me this morning))) What if, when creating the NCF_CORE file on the computer, I set the date to, for example, 11.11.2011, would I not need to update the packs?)))