安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题






Just trying to help narrow down when/where the conflict might be. But if other people were having the same issues before.. seems odd, since for me they occured afterwards.
If the issue does come back, go ahead and add the conditional patch I mentioned below. If you have any questions about it, feel free to ask. Thanks!
Just a thought.
Anyway, I can't get it to override your values on my end, so, if you would be so kind as to add a PatchOperationFindMod for Anima Fruit
noMatch can stay the original value, if you set the match value to 923, you will get roughly the same lifespan (500 years) and we won't go over the game-breaking limit. cheers
https://gist.github.com/8e9052c822e9c20a98119942affeb962
Tried looking in the log, but I don't really know how to interpret it. Anyone has any suggestions?
https://psteamcommunity.yuanyoumao.com/sharedfiles/filedetails/?id=2297332187
This way you can also increase / decrease the build radius of the anima tree as well as the anima scream debuff.