Skip to content

Signature resolver to maintain compatibility with the Tanos API#447

Closed
do-gamer wants to merge 1 commit intodarkbot-reloaded:masterfrom
do-gamer:tanos_api_signature_fix
Closed

Signature resolver to maintain compatibility with the Tanos API#447
do-gamer wants to merge 1 commit intodarkbot-reloaded:masterfrom
do-gamer:tanos_api_signature_fix

Conversation

@do-gamer
Copy link
Contributor

This fix is related to targeting the Relay in the LoW gate.

The signature 23(set target)(2626)1016221500 check called from the MapManager

public boolean setTarget(long entity) {
long targetWrapper = API.readLong(mapAddress + 128);
if (ByteUtils.isValidPtr(targetWrapper)) {
return API.callMethodChecked(true, "23(set target)(2626)1016221500", 4, targetWrapper, entity);
}
return false;
}

And this signature works fine for the Kekka Player API.
However, for the Tanos API, it always returns an error: "Invalid flash method signature!"
The correct signature for Tanos API is 23(target)(2626)1016221500

I'm not sure whether this is the correct place or method to specify a different signature for Tanos API only.
Please review and let me know.

@Pablete1234
Copy link
Member

If tanos is producing a different signature than kekka, that is a bug on tanos' side

@do-gamer
Copy link
Contributor Author

@Pablete1234 Thank you for pointing me in correct way.
I have fixed the libdo_lib.so to resolve correct getters/setters names, just like the Kekka Player API.

Signature: 23(set target)(2626)1016221500 == 23(set target)(2626)1016221500

@do-gamer do-gamer closed this Feb 14, 2026
@do-gamer do-gamer deleted the tanos_api_signature_fix branch February 14, 2026 18:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants