My I ask why you guys are not using the blockchain api so you would not need to wait a week this time or next time this happens for the wallet to resync?
Short answer: Use of third party services introduces risk without benefit. The one you refer to in particular has a history of being unreliable.
Long answer: Lucky Bit has a dedicated full node to ensure that it has access to an impartial data source. It also immunizes Lucky Bit from MITM spoofing attacks targeting the chosen API. Lucky Bit also stores history in a local data cache so the game and API won't be delayed by node lag.
The node fell out of sync, but the Lucky Bit engine continued operating as though it hadn't. This resulted in the engine, and the local data cache, reflecting payments as having been sent when they were not. In turn, the engine falsely marked coins as spent in the local data, meaning the node and the engine would never be able to reconcile nonexistent transactions. The only solution is to rebuild the local data from the blockchain itself, which requires a complete rescan of the node.
Getting this information from an independent API wouldn't speed the process since the entire blockchain needs to be parsed, but introduces several risks such as MITM spoofing, repair delay due to API downtime, loss of progress due to a fork, or errors in the API-provided data.
