Velkommen til GTA5-Mods.com

@THarveyKam thanks and I will do that

dammn its really nice! especially call lester feature 🤣 good work bro amitabh bacchan should definetly play this! are you from India?

@xeisenberg Never ignore the README — especially when it already contains the complete installation guide and troubleshooting steps.

You guys skipped the README and then came here asking questions that are already answered there. I’ve put a lot of effort into making the installation as clear and easy as possible.

And honestly, seeing the mod’s rating go down because the README wasn’t even checked first is pretty rough.

Please read the README before assuming there’s an issue with the mod or rating it down for something that’s already explained there.

@AlanPlay If the game is crashing, please provide the crash log and your system/mod setup before assuming that LLAI is the cause.

The mod itself does not automatically mean every crash you experience is caused by it. GTA V has many possible causes for crashes, especially with other scripts, mods, ScriptHook versions, game files, or system issues.

Also, the included README already contains installation and troubleshooting instructions.

I completely understand reporting a genuine issue, but giving a reduced rating because of an unverified crash without providing any log or evidence isn't really a fair way to evaluate the mod.

If you provide the crash details/log, I'll be happy to investigate it.

@Torunas Update your script hookv dotnet nightly

@Darunia1972 @impoliceofficer Oh! Haha, I totally misunderstood you! In game modding, 'polish' almost always means fixing bugs, improving the code, or making the UI cleaner. Because of that, I didn't realize you meant the actual Polish language! My mistake. Thank you both for clarifying. I am looking into how I can expand the AI's multilingual support to include Polish and Russian in a future update!

@Darunia1972 what polish exactly? Please give more details in your comment saying just add polish will not be helpful at all to be honest

@SpeedForceJunkie Fair question, so here's a straight answer.

The installation instructions are not missing — they're in the download. Inside the ZIP there's a full README.html with the complete setup: install requirements, how to get a free Gemini API key, where to paste it, and a troubleshooting section. The README is a proper formatted page , which is why it's a file and not 200 lines of raw text pasted into this comment box.

The mod page describes what the mod does. The download tells you how to install it. That split is deliberate — the description is already long, and stuffing the install steps in there would make it longer, not shorter.

If you download it and the README genuinely doesn't answer your questions, tell me exactly which step is unclear and I'll fix that section for the next release. I'd rather fix the docs than argue about them.

Rating the mod down for documentation you haven't opened yet is a bit rough, though. It's in the file.

@impoliceofficer Both of these were in your logs. Thank you — that second paste is the most useful bug report I've had.

1. Dismiss key unresponsive — found it, and it is worse than "sometimes". You're on a rebound key (Backspace), and the custom-key path was being read at the bottom of the key handler, behind sixteen early returns: text keyboard open, mic key latched, isBusy, drag race active, waiting for a reply, and more. Your log shows you mid mic-turn with a live reply, so the handler returned long before it ever reached the dismiss line. The key wasn't unresponsive — it was never being read. It's now the first thing the handler does, before anything can swallow it, plus a 400ms grace window so a press can't be lost on a skipped render frame. Tested against all seven blocking states: the old code was dead behind 7 of 7.

2. "No response" bug — this one is nasty. Your log

[20:05:28] session not ready after 12s
[20:05:42] Session start triggered ...
[20:05:51] Session start triggered ...
[20:06:22] Session start triggered ...
Every startSession unconditionally closed the previous socket. Google needs 1.5–3s to finish setup. Each time you reopened the chat you killed the socket that was still setting up, so it never reached ready and every queued mic turn was discarded. The retry was causing the failure. Now if a socket for the same NPC is still inside its setup window, the bridge adopts it instead of killing it. Walking to a different NPC still gets a fresh session, and a socket stuck past the window is always replaced so nothing can wedge. Logs as [MAIN_SESSION_ADOPT].

Still open: the safe-zone shoot lock. Haven't reproduced it yet — if you catch a log the moment the shot doesn't register, that'd narrow it the same way this one did.