Velkommen til GTA5-Mods.com

@jtfromkc397 You talk 💩

@jtfromkc397 It's the same there isn't any difference

@jtfromkc397 That's what NPCAI 3.0 does

@jerome74 Mine when it's released does this

@VICTOR RIVERA De todas formas, ya tengo tu código, así que no necesito nada más de ti.

@VICTOR RIVERA You say *I don't even speak Spanish* but other things tell otherwise. Stop using GPT for the replies.

Just a heads up though Toxic Scripts Pressure Washer scripts are distributed as compiled .dll files, so this SP conversion raises questions about how it was made.

The promo video from Toxic Scripts is being used here, but a lot of the features shown don’t seem to match what’s actually in this version.

Might be worth clarifying how this was developed, because it doesn’t quite line up with the original FiveM release.

@VICTOR RIVERA I presume the code was converted using AI or you paid someone else to code it, since the code shows it's in Spanish.

@VICTOR RIVERA Twat

@VICTOR RIVERA I understand your position, but moving everything to Enhanced only doesn’t really solve the compatibility issue for everyone. A lot of users still rely on SHVDN Nightly or Legacy setups, and Enhanced introduces its own issues for some environments, including registry adjustments and inconsistent script behaviour depending on the build. That’s exactly where the problem comes in, it’s not a universal “better”, it’s just a different ecosystem.

From my side, I already have the (Code) script working properly with my models in my current setup, so switching frameworks or repurchasing anything doesn’t really make sense for me. The compatibility is already solved on my end, using Nightly SHVDN.

Also, I don’t use Instagram, so that wouldn’t be a viable way to communicate.

If anything would improve the mod for broader use, it would be optional configuration support (for example an .ini file). That would allow users to adjust models, offsets, language, and other values without needing different builds. Right now, the lack of configurability and the hardcoded Spanish text limits usability for non-target users.

Ultimately, I think the best approach for a community release is optional compatibility rather than locking it to one runtime or requiring individual paid adjustments. That benefits both sides in the long run.

Also, just to be clear, directing users to third-party apps for payment or custom work isn’t really aligned with GTA5Mods guidelines. I’d prefer to keep everything within the platform and focused on optional improvements that benefit the wider user base rather than individual paid adjustments.

From my side, I’m not looking for any paid customisation or external contact, just raising compatibility and usability concerns for SP users.