https://en.wikipedia...mming_interface
When two groups are writing software independently, like Playata and Nutaku, they agree upon an API. This allows them to proceed on their own way, building updates. Theoretically, Playata can add a special event, test that it works, then submit their code into production on the Nutaku system. The Playata code calls the appropriate functions within the Nutaku code, and it should all work.
This time, and several times in the past (as you know), it didn't.
I am not a developer, and have no insight into exactly how Playata tests that the system will work on Nutaku before releasing into production. But I do know, that where Playata has full control over the development system, there is no bug. Either Nutaku has a bug in their code, or there is an unforeseen interaction on the production systems.
That is not to say there is nothing to be done. I am just saying, this is an issue where there are more than the normal number of moving parts. There are likely to be more problems here (we have proof of that statement), and it is harder to get fixes made, because Playata and Nutaku may have to work together before solving the issue.
I know Playata is working on it, but have no further information about an ETA for a fix.
I have retired from the game, but not from life.
In love with my Baby.