Will

Seems like we had a similar start around the same time. NB was the one that introduced me to LCPDFR through his YouTube channel, which led to me joining the old FCRP SAMP server, which somehow led to me joining the staff team there (and abusing the admin car), fast forward a few years and I end up the Community Manager here.... Anyways, always nice to see someone who's been around since the early days! Glad you were able to follow your dreams in the real world, too.

I would be impressed if RPH was able to launch GTA VI before it releases...Topic moved to the correct section. Did you follow the instructions?

No. Most likely a configuration issue. Remove all EUP Menu files (including the presetoutfits file), then reinstall EUP Menu. Then reinstall the latest RAGENativeUI from here: https://github.com/alexguirre/ragenativeui/releases (do NOT use the one included with EUP Menu. Overwrite it if you installed it).

You will likely have to wait for SSLA to update.

Try removing SirenSettings_Limit_Adjuster and let us know if your lights work. Other users have reported it is broken with the latest update. For the pause menu crash, please upload RagePluginHook.log from the main directory.

The plugin timeout threshold has nothing to do with letting the game engine prepare on load. RPH will terminate plugins that cause the game to freeze for longer than the timeout threshold. The only reason increasing it is recommended is because, due to how complex LSPDFR is, slower systems will fail to fully load LSPDFR in the default 10,000ms. LSPDFR is likely the only RPH plugin in existence that requires this to be changed, or at least one of very very few.

I've already mentioned this issue internally and hopefully it will be fixed in a future maintenance release.

Yes - the disclosure is mandatory. If a moderator has reason to believe AI was used and not disclosed or disclosed improperly, they will kindly ask for the disclosure to be added or corrected.

Yup. Although, tbf, if would be nice if the vehicle became more disabled, instead of easily driving away after pitting it. But LSPDFR gives a chance of the person running, surrendering, or fighting back once the vehicle is brought to a stop. I believe in certain circumstances, the PIT alone could trigger those options, even if the vehicle has the opportunity to drive off. StreamableWatch PIT | Streamable

This is partially in LSPDFR already - it has a pit detection and if it is considered a "good pit" there's a chance the driver surrenders.

@JhnDoe See above, the differentiation you are asking for is there. These options are there to be transparent about the level of AI use. Your file will only get the AI tag at moderate or significant. Other than that tag, the disclosure is simply text added to your description. There are no further filters or any changes to how your mod is displayed on our site if you disclose AI use.

@JhnDoe I think you've missed the point here. If you look in our downloads section, there has been a large influx of mods written entirely by AI. I think the first or second mod to use this disclosure said "AI made this for me in one hour." The idea with this system is simply to be transparent about AI use in development, not to prohibit or punish it. AI can be an excellent tool when used correctly. We don't want anyone to think that if they used AI in creating their mod that they are not welcome here - we welcome all sorts of mods. Everyone has to start somewhere and if your first mod was made by AI, so what? Take what you've learned from that and apply it to make greater things. Maybe you've been making mods for years and AI lets you do things you've never had time or been able to do before. We just want our users to know what role, if any, AI played in what they are downloading. It's really no different than putting everyone who contributed in the credits.