I’ve already explained exactly what’s going on with the system. There’s nothing more to say on the matter that’s more appropriate than the hard truth. As much as it sucks, the system is currently working as it was implemented with the update.
Re-read the lines you are citing. The key phrase here is:
When does the server determine that the dragon is defeated? As soon as the first asynchronous player reports damage through a completed defense run instance that pushes the cumulative kingdom damage total to a level that is at least equal to the required amount of total damage to win the Kingdom Defense Event.
Ok, onto the second part of the patch note.
That’s not an incorrect statement.
“That point” refers the first part of the statement, which is the moment the first asynchronous player reports enough damage to accumulate enough cumulative kingdom damage to the dragon to win the event. At that exact moment, the server calculates who is eligible for Silver and Gold rewards, sends out the appropriate rewards to the relevant players, and ends the event. Any damage reported to the server by any kingdom player after that exact moment where rewards are calculated is ignored by the server because the server has officially ended the defense event.
If there is anything that could be considered a bug, it would be that the game is allowing the kingdom leaderboard to be updated with the disallowed damage scores from players who completed runs after the defense event has ended resulting in inaccurate reporting of leaderboard for which Silver/Gold rewards were determined.
The system is working as designed and described in the patch notes. It’s just very hostile to players, which seems to be intended. We’ll talk more in the other thread on that, as there is much to discuss on that topic.