Добредојде на GTA5-Mods.com

@Trancenath91 I'm very sorry. Because the fuel script's computational content is inherently larger and more complex than other typical mods, I will do my best to optimize performance in future updates. Thank you for your appreciation.😭

@TroopahGaming Sure, like [ChargingStations]
-51,-1762,28
-53,-1764,28
-57,-1743,28
and [FuelStations]
-64,-2530,5
-67,-1760,29
173,-1560,28

@DirtSpray It's just caused by your CPU loading speed or too many mods installed in the game, causing the vehicle spawn timing to be missed. You can now update to my latest version 1.1.2.

@LamarDav1s Thank you for your cooperation and feedback. I'm glad to hear that too.

@LamarDav1s Version 1.1.2 has been updated. Please try again to test if the functions work normally.

@LamarDav1s Thank you for the feedback. I roughly know what the problem is now. I should be able to create and upload a version 1.1.2 tomorrow, which should solve your current issue.

@LamarDav1s Please follow the steps below and send me the results: 1. Delete all .sav files in the SavedVehicles folder. 2. Enter the game, get into a vehicle, and press Space + K to save. (Note: After saving, you must exit the vehicle. The first time you save a vehicle, the coordinate position is only written after you exit the vehicle. Then quit the game.) 3. Open the latest .sav file in the SavedVehicles folder with Notepad, copy the first line (e.g., -3077.614,537.9761,1.7086,12.34). 4. Open SavedVehicles\VehicleSaver_Log.txt and copy the last few lines (including the line with LOADED) to me as well. This way I can compare whether the original saved coordinates match the coordinates parsed by the script, and determine if the issue is a position offset caused by the system's decimal format. Thank you for your cooperation!🤝

@LamarDav1s Thank you for the feedback. However, this script saves the vehicle's spawn location based on where you last exited the vehicle, not the original location where you first pressed Ctrl+K to save it. Could this be the reason for the issue?

@DoctorTech97 The issue is most likely fixed. It may have been caused by the vehicle loading too early in version 1.0. Please try updating to v1.1. If you still have problems, feel free to report back, or send me the contents of the VehicleSaver_Log file in the SavedVehicles folder. Thank you for your feedback.

@DoctorTech97 The saved vehicle is recorded at your last exit location. Did you drive it somewhere else? It might be at your last exit location, not the original save location. Because from my testing, the script logic should be fine.