Repository navigation
Replies: 2 comments 6 replies
|
Thanks for this. It's now in the client:
Things I found that may help your C# version:
Two questions, if you know:
|
|
Thx for tips, i fixed them. AI response: Researched against the primary artifacts (the SDK DEX/smali). The developer is right — Last War does not collect a63. Here's the chain, then what I fixed.
Re a63: you're right, Last War never collects it — we re-traced with the gate included and withdrew our earlier claim. The SDK does define the a63 field (l11l1111lIIl.l11l111Il, List) and the collector can fill it from InputMethodManager.getInputMethodList(), but it's gated on the exclusion set: We've dropped a63 from our template and corrected the a84 (…=___ composite) and a167/a168 (=0 until first registration) as you described. The "input"/"protect" values aren't aNN keys, they're collector categories — if you have the cloudconf notCollect shape, worth checking whether the server ever returns literal aNN keys there (that's the other half of the gate). |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
This is a fully mapped, production-ready C# implementation. While the logic is quite complex and ideally requires high-quality input data, my testing shows that the endpoint currently accepts all payloads without strict validation.
The system collects extensive device telemetry from mobile phones. This likely explains why this specific ID isn't required for iOS, as Apple has completely blocked the underlying library.
Update: Interestingly, my physical device was flagged and hardware-blocked. This implementation bypasses that restriction by spoofing a new device identity. The restriction targets the device itself rather than the user account, as I can still log in and play on the same account using this method.
ShumeiInnerTemplate.txt
GetShumeiBoxId.txt
All reactions