Open Bread-NiceCat opened 3 weeks ago
当我发现所有的冲突都指向/Container/method_(5438|5442)
,然后我去查了混淆表,发现他们也都是RecipeInput
中的成员。冲突的原因是Cotainer
和RecipeInput
中都有getItem(int)
和isEmpty()
方法,我把他们分离,然后解决了。
當我發現所有的衝突都指向/Container/method_(5438|5442)
,然後我去查了混淆表,發現他們也都是RecipeInput
中的成員。衝突的原因是Cotainer
和RecipeInput
中都有getItem(int)
和isEmpty()
方法,我把他們分离,然後解決了。
When I realized that all of the conflicts were pointing to /Container/method_(5438|5442)
, I then went to the obfuscation map and found thatThey are all members of RecipeInput
.The reason for the conflict was that both Cotainer
and RecipeInput
had getItem(int)
and isEmpty()
methods in them, which I separated and resolved
ArchLoom能否智能识别这类问题,然后同时反混淆? ArchLoom能否智能識別這種問題,然后同時反混淆? Can ArchLoom intelligently identify such problem and remap them together?
已解决,看2楼 已解決,請參考第二樓的內容
Loom 1.7.412
project build.gradle here