Is your feature request related to a problem? Please describe.
The current cargoship functionality no longer works correctly after the update. When running the in-game cargo command while the cargoship is already active, the calculation for when it will leave the map appears to be inaccurate or broken.
Describe the solution you'd like
Update the cargoship logic so the bot can correctly calculate when the cargoship will leave the map again after the recent game update.
The approximate leave-position prediction should also be reviewed and adjusted if necessary, in case the update changed cargoship movement or timing behavior.
Describe alternatives you've considered
An alternative would be to keep the current behavior and only provide limited cargoship information without a leave-time prediction. However, fixing the calculation would be much more useful and would restore the reliability of the feature.
Additional context
This issue likely started because a Rust update changed how cargoship timing or movement works. Both the leave-time calculation and the predicted leave position may need verification.
Is your feature request related to a problem? Please describe.
The current cargoship functionality no longer works correctly after the update. When running the in-game cargo command while the cargoship is already active, the calculation for when it will leave the map appears to be inaccurate or broken.
Describe the solution you'd like
Update the cargoship logic so the bot can correctly calculate when the cargoship will leave the map again after the recent game update.
The approximate leave-position prediction should also be reviewed and adjusted if necessary, in case the update changed cargoship movement or timing behavior.
Describe alternatives you've considered
An alternative would be to keep the current behavior and only provide limited cargoship information without a leave-time prediction. However, fixing the calculation would be much more useful and would restore the reliability of the feature.
Additional context
This issue likely started because a Rust update changed how cargoship timing or movement works. Both the leave-time calculation and the predicted leave position may need verification.