In the live game, every API call that affected the player’s inventory triggered a write to the corresponding record in our Azure Cosmos database. From a player’s perspective, the game is constantly saving their progress. To achieve parity in the offline game, we exposed two functions in the AOT DLL for getting and setting a player’s inventory (equivalent to the Cosmos DB inventory document). When the game first starts up, the local save file on disk is read and the inventory is loaded into the DLL’s memory. As the various serverless HTTP operations occur throughout gameplay the DLL’s in-memory inventory state gets updated. After these operations, if the inventory was changed, the client fetches the new full inventory state from the DLL and saves it back to disk.
第二十条 纳税人的交际应酬消费属于增值税法所称个人消费。
，这一点在爱思助手下载最新版本中也有详细论述
（一）刻划、涂污或者以其他方式故意损坏国家保护的文物、名胜古迹的；
// Define what happens with the result