Will there be an update?

This bug is related to desync, the client believes we are on that coordinate but the server knows better, to fix this we have to input at least one other movement command. Since I'm hella lazy to find out if it's really only one or more movement commands to fix this I just spam drive.moves in the middle of the jump gate.

File: SafetyFinder.java in tick() switch (jumpState)

case JUMPING:
prevMap = hero.map;
drive.stop(false);
LocationInfo desyncFix = safety.entity.locationInfo;
desyncFix.now.x = desyncFix.now.x + (int)(100.0 * Math.random());
desyncFix.now.y = desyncFix.now.y + (int)(100.0 * Math.random());
desyncFix.now.x = desyncFix.now.x - (int)(100.0 * Math.random());
desyncFix.now.y = desyncFix.now.y - (int)(100.0 * Math.random());
drive.move(desyncFix.now.x, desyncFix.now.y);
hero.jumpPortal((Portal) safety.entity);
return false;

Since I'm auto selling my cargo I jump a lot of gates per day, this fix is definitely working, you might not like my approach, feel free to change it to just one move, but I try to change as little as possible to get the result I want, I just want to get this fixed for everybody.

i have add that string in MainGui.java (line 118):
Main.hero.drive.move(hero.locationInfo.now);
and i have change varible hero in Main.java to static

the bot will no longer move after pressing the button to stop it

when i git in intelliJ there are too error in code, why?

There is an issue with the dll native where it would hold down the mouse button and never releases. (I know we don't have the source of dll)

Fixed by replacing the native import with:

//public native void mouseClick(int x, int y);
public void mouseClick(int x, int y) {
this.mousePress(x, y);
this.mouseRelease(x, y);
}

you could post the source code of the last legacy version and the .dll file

bot don't run from enemy

Hey, I just wanted to note that the signature of the verifier.jar in github doesn't match with the base64 of POPCORN_PUB, build throws.

fixed by taking verifier.jar from discord stable downloads

why not just use sha-256?