We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CMS V208 更新起出现了一种新的交易状态:accountSharableAfterExchange。此交易状态也存在于其它已更新 Dreamer 改版的客户端(含 KMS)。 该交易状态的游戏截图参考以下网站。 https://mxdact.web.sdo.com/project/v208/02-4.html#con
accountSharableAfterExchange
目前已知存在该属性的道具为 2637169,即以上网站展示的道具。
The text was updated successfully, but these errors were encountered:
Add accountSharableAfterExchange support, Kagamia#263
96bb018
感谢提交。
我在思考原来有一些道具存在accountSharable和sharableOnce的属性,wc还没有正确实现,当累积到一起的时候会不会出现逻辑错误。 一个示例道具像是这样:
accountSharable
sharableOnce
这个PR可能需要hold一段时间,我们应该先统计全部具有和“道具转移”相关特殊属性的物品,研究布局规律再做综合设计。
Sorry, something went wrong.
No branches or pull requests
CMS V208 更新起出现了一种新的交易状态:
accountSharableAfterExchange
。此交易状态也存在于其它已更新 Dreamer 改版的客户端(含 KMS)。该交易状态的游戏截图参考以下网站。
https://mxdact.web.sdo.com/project/v208/02-4.html#con
目前已知存在该属性的道具为 2637169,即以上网站展示的道具。
![image](https://private-user-images.githubusercontent.com/29157608/342657863-36ecbba5-8bf7-428b-afd8-038af0c17718.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjMzOTQ5MDYsIm5iZiI6MTcyMzM5NDYwNiwicGF0aCI6Ii8yOTE1NzYwOC8zNDI2NTc4NjMtMzZlY2JiYTUtOGJmNy00MjhiLWFmZDgtMDM4YWYwYzE3NzE4LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODExVDE2NDMyNlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTU2ODhkMTE5MDYyMjAwM2VlYmU5M2Q3ODVhMTNiMTU4M2VlOTUwZDA3YzQ5NWJkNWYzYTZhNDhkMDNjZmQyYjUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.hUjdKtru8WCqldpbekFrIjNbK0W6apSMDNzoHbQgt1o)
The text was updated successfully, but these errors were encountered: