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

@lone-faerie Thanks for the compliment and feedback!

Please help me understand your idea?

To set the stage, as it is now the mechanic (if regard is high enough) will personaly deliver a recovered vehicle if it has been despawned, or a replacement vehicle for one that was destroyed. But only ~once~. For instance, if the player abandons or never enters the delivered vehicle, but later files claim on it again after it has somehow despawned, the insurance company/mechanic will leave it parked at either a parking spot (if it was a recovered vehicle) or an auto shop (if it was a replacement vehicle). Depending on regard, that parking place will either be near the player, or near the vehicle's last known position (ie, where it was last delivered, most likely).

Then there's the as-is case of, say, a player's last-used vehicle when it happens to be insured. The game itself tends to persist last-used vehicles (until you get into another) wherever they were left. So if that happens to be an insured vehicle, the mod will simply mark it on the map and indicated where you can go pick it up again.

So ... basically, I figure you asking if it would be possible for the mechanic (on high regard) will ALWAYS deliver a vehicle, regardless if they once tried before, or if the game hasn't despawned it (but it is far away)? Something like that?

Thanks for bearing with me. I just need to understand your request in the context of the current logic so I can accommodate it correctly in the next build!

@RemixPL1994 Thanks much!

Thanks for checking out the mod! I do my best to respond to any fedback, feature requests, and bug reports, so feel free to send 'em my way.

NOTE: for Legacy users, SHVDN3 nightly 98 is required with version 1.4, but I will relax this in a future 1.4.1 hotfix coming soon.

Lastly ... If you're having problems, or want to know how to customize things, or are just curious about the known issues or roadmap so far, I encourage you to check out the download's README.

Alright, I got to the bottom of it. Yes, the 1.4 build won't work on SHVDN3 less than 98 (although it still works on SHVDNE just fine). This was due to a bone-headed oversight in my build setup that caused a baked-in dependency on 98.

I've fixed it so it will be happy with no more than 93, so I'll make that change in a future 1.4.1 hotfix.

Again, sorry for the trouble but thanks for the feedback - it helped me get to the root of things.

Okay, you're right - I just put it through the test loops through prior versions down to 93 on Legacy ... and oddly it is requiring SHVDN3 98 ... baffling. I have a few theories, I should be able to change this for a hotfix, since the mod itself doesn't truly require anything special from 98; it was originally developed on 93 and still otherwise ran on it during development ... again, sorry for the issue, but I'm working to fix this.

@Malanix Hm. That's unexpeted, but thank you very much for the feedback and follow-up!

FWIW, I'm currently looking into the SHVDN specific version thing -- I don't know off-hand why my mod would prefer a specific version of SHVDN like that (I developed and tested 1.4 on various builds of SHVDNE and SHVDN3 94-98 along the way), so I'll get to the bottom of it for a future hotfix, if possible. Sorry for the trouble, but happy it is working for you now.

As always, I remain open to any/all feedback or feature requests otherwise, too.

@Malanix Hm. Can you check the logs of SHVDN? I have a troubleshooting section of the README that goes into more of how to do that and some things to try/check ... meanwhile, sorry it is not working for you. I'll do what I can to help if I can get some more details based on the stuff I tlak about in th README.

@IInEoII Thanks! I am open to all feedback and feature requests, so feel free to lmk if any come up.

I just tested a quick prototype of a non-cosmetic repair option -- and it works. The engine and general health stats are reset to max (repaired), but the body health and cosmetic damage is left as-is.

So then consider it on-track to be part of the upcoming 1.4 release ... looking like next weekend or so.I gotta wrap up this insurance feature. If it lags past that, I'll for it out and release a 1.35 version with all the other major improvements I've made since 1.3, ha.