Cyan

Any .exe is flagged and requires a manual approval by our team. Additionally, we only approve executables if we feel the benefits outweigh the risks. Our policy does not match GitHub's policies. Please contact the reviewing moderator in regards to your file, or contact a blue management member if you'd like a second review.

I just deployed a new version of the site that should fix the issue you were having (and others, with certain special characters in file names).

Hello @LGC Gaming After some debugging, please re-upload your file without the following characters in the filename: ( or )

Hello @LGC Gaming It looks like the file upload was unsuccessful, as the file is not on our servers. Please try uploading again via Upload a new version and let me know if that works.

Thanks for your thought out post, it is appreciated. I am skeptical to make too many changes to our disclosure system in terms of the categories, I feel that the categories you have listed are a little biased towards Script Modifications in particular, whilst our AI disclosure system is designed to suit all types of mods - we probably aren't that far off models and more being AI generated. Not to say we won't, I just think we need to look at this more. We do have a description of what we consider Minor, Moderate and Significant use of AI here: https://www.lcpdfr.com/forums/topic/155394-marking-ai-content-on-your-files/ - did you manage to find this when you were looking? It's clear that some content is not being correctly tagged, and we aim to increase enforcement i.e. including but not limited to harsher penalties. I feel like we probably have to document better objectively what we're expecting before considering stronger enforcement, however. It does need some extra consideration that we do not penalize harmonic AI use like you describe. We are very open to feedback here, this is something a little new, and the current system is not perfect, so refinements and changes seem inevitable. I think some other sites have just settled with AI used yes/no and filters based on the sole boolean, so we are trying to do something a little more expressive than that.

Usually caused by VPN/privacy services. Disable anything that may be concealing your IP, and try again.

Disabling comments / reviews is only something which can be done at file submission time.

Replied in the developer Discord: The change on June 1st is just the extended APIs (do=getAssemblies,do=getAllVersions) the main users of this (discord bots) have already migrated to the new API. Infact, I'm not seeing any usage from our telemetry data (apart from a really badly misconfigured plugin that is receiving an error response anyway) in the past 24 hours. The legacy check for updates API has been phased out for new files, but for existing files this will be done in staged brownouts later in the year (with better notice). We'll obviously need to assess if it's even viable to completely get rid of, whitelist certain things that break that aren't going to be fixed/etc (although ultimately our hand might be pushed on it at some point - if we have to turn off old TLS versions for a critical security issue for example). If you're using checkForUpdates there will be no change on June 1st. Sorry, my initial post is a little unclear.

It's not our intention that things in the featured feed would be there forever. In reality, things can end up there for a long time. There is no per-author limitation, I'm not sure what you mean by that? We also have the 'Essential Mods' category, which is baked in with other GTA5 Mods category. This is meant to be longer term, and with mods we feel are essential to the 'LSPDFR' experience. It’s hard to determine which mods are objectively “the best.” We have strong discovery mechanisms, but we don’t necessarily make a definitive judgment on which mods are objectively great. In many ways, the community makes that call through what they share, what gains traction in their own spaces, what trends, and what gets downloaded most. But all of those signals are shaped by multiple factors, and they don’t always point to the same answer.

any improvement today?

As a reminder, the API documented in this article has been deprecated and is being retired in stages. The “Get user-facing version for a file” request, do=checkForUpdates, has already stopped working for new files uploaded after 8 May 2026. We currently intend to turn off all remaining endpoints on 1 June 2026 and are moving to our new authenticated API. For checking updates to your own files, we recommend using our new Version Check Keys. These include API documentation in your Account Settings. Please note that Version Check Keys are limited to checking updates for files you own. For other use cases, our new Public API keys are available on request for non-commercial use. These allow you to retrieve file details in bulk, up to 10,000 files at a time, sorted by file update date by default. These new endpoints include far more details about files, including tags, screenshots and more. We plan to share more in the coming months about the full deprecation of the “Get user-facing version for a file” endpoint. If you have any questions, please let us know.

Clear all cache, try again.

Any screenshot or copy paste of this error would be helpful.

Should be sorted for now!

Have brought this back today, you'll see an 'Updated' tag inside the top right of a mod image when browsing. You can also see your download history and see updates from your history, Mods > My History or here https://www.lcpdfr.com/downloads/history/.

We’ve mitigated this on our side by temporarily taking the Europe content server out of rotation while we investigate and fix the issue. It appears to affect uncached files only. For future reference, one reason we maintain multiple download servers, beyond traffic management and load balancing, is to provide alternatives if one region is having problems. In this case, the US East and US West servers were not affected, so selecting either of those would have avoided the issue.

Thank you for posting some information which I can use to troubleshoot the issue.

Can you be more clear what you mean? Are you saying to rename featured? The featured feed is meant to be things that we, at LCPDFR.com, find special. The trending system supplements this, showing what's popular in the community.

Please link to a file or let me know if all files are affected. Please also let me know what download server is being used (this should be listed on the post-download page). For some background - I'm not seeing any drop of download traffic from our telemetry data nor have we made any changes the past few days.

Out of curiosity, what was the problem?

No.

Your topic has been moved to LSPDFR 0.4 Support. Please post in the correct location in the future.

Hello everyone, I just want to say thank you for sticking with us through the biggest site update we’ve ever rolled out. Last year’s launch didn’t go as smoothly as we’d hoped and we know there have been some issues along the way, so we really appreciate your patience and feedback. It’s helped us get to a much stronger place moving forward. Now that things have stabilised a bit, today we’re launching a bunch of new features and changes that we think you’re going to love. Discovery: Tag FiltersThe whole point of our tag system has always been discovery. You’ve been able to click into tags and explore everything connected to them, but proper filtering on category pages was missing. That’s now changed. You can now explore and filter by tags directly on category pages, with the system built to expand much further over time. To start, we’ve added brand, country, and year filters to vehicle pages, along with a “Made with AI” filter on script pages. You can now filter by Brand, Country and Year on Vehicle pages. A small change on the surface, but a big step toward making discovery faster, cleaner, and far more useful across the platform. Discovery: Site Wide Tag ExclusionsTo give you even more control over what you see on LCPDFR.com, we’re introducing account-level, site-wide tag exclusions. Any files matching the tags you choose to exclude will be hidden across the site — including the downloads portal, download feeds, trending and featured sections, and search results. The tag filtering controls, now available in Account Settings. In this example, files tagged as outdated are being hidden. The downloads category page, showing 1 active account tag filter and 34 files hidden as a result of excluding the outdated tag. Whether you want to hide AI-generated work, certain vehicle types, specific countries, or even particular vehicle years, we hope this system helps you fully customize how you browse content on LCPDFR.com. Note: We're aware of an issue of going to Account Settings, then navigating to Downloads Filters will not load the tag box correctly and we're working to fix it. Refreshing the page if the tag box doesn't load will workaround this for now. Site Experience: Thanking CreatorsAs a thank you to our creators and contributors, we’ll be removing external advertisements for community members who are actively engaging with the community. The exact criteria may evolve over time, as our community contributes in many different ways. Whether you're helping new members with questions, uploading mods, or simply being an active part of the site, we want to recognize and reward those contributions. For creators who share their mods with the LCPDFR.com community, ads will be removed once you reach 1,000 verified unique downloads. For all other members, ads will be removed once you achieve the Sergeant rank (1,000 community points). Our rank system awards points for a variety of community activity, including forum posts, gallery uploads, comments and reviews (+1), giving or receiving reputation (+1), gaining followers (+2), and more. This change is going live today, though it may take some time after reaching the requirements for the benefit to be applied to your account. Logging in and out if you meet the criteria may help this apply sooner. We also plan to add a way for members to track their progress toward these thresholds in the future. This is one small way we can give back to the creators and community members who help make the site what it is. Developer: APIOur old API has started to show its age and wasn’t really built with the growth of the website in mind. Historically, we’ve had to handle security on LCPDFR.com in some fairly unique ways. While we want to discourage automated traffic, serving an API directly from our main website domain meant we also had to keep certain protections less aggressive than we would’ve liked. The API has been moved onto its own dedicated infrastructure, allowing us to properly monitor usage, apply separate security procedures, and relax some of the harsher caching behaviour that existed previously. We’ve also adopted the more standard approach of enforcing API keys across the new API. This allows us to better track usage, apply limits where necessary, and manage access more effectively. API keys are issued in line with our new API Guidelines, which outline acceptable usage and restrictions around commercial use. There are currently two key types available: Version Check Keys — designed for embedding into your own plugins, primarily for update and version checking. Full API Keys — provide broader access to the API, including mass file listings, extended file metadata (such as tags), .NET assembly data, and more. Full API keys require approval. We may contact you with questions about your intended usage. Both full and limited API keys require an active LCPDFR.com account that has been active for at least one week. You can request API keys in your Account Settings. You can see usage limits, documentation and regenerate your key from Account Settings. With the new downloads listing API, you can list up to 10,000 files at once. Full documentation available in Account Settings with an issued key. Overall, this new API infrastructure gives us a far more scalable and maintainable foundation moving forward. Separating the API from the main website allows us to improve security, reliability, and performance without impacting the experience of regular community members on LCPDFR.com. We’ll be deprecating the old API in stages. Effective today, the old version check API endpoint (checkForUpdates) will no longer be available for newly submitted files. All remaining endpoints, apart from checkForUpdates, will be turned off on 1 June. We understand that deprecating checkForUpdates may cause issues for some plugins. We plan to phase this out later this year in stages and with planned brownouts and will share more details in the API forum closer to the time. We’re not stopping there, either. While these updates are a big step forward for discovery, customization, and the overall site experience, we already know where we want to focus next, on search. The truth is, we’ve largely outgrown the search system our current software provides. It was never really built for our mod heavy platform with this much content, this many tags, and the kind of discovery features we now want to support properly. Because of that, search is probably going to involve a lot more custom work from us moving forward. Better relevance, smarter filtering with the new options announced above, and a generally cleaner experience are all things we want to improve over time. As always, we do appreciate your feedback. We try to guide LCPDFR.com based on what the community wants, alongside the areas where we feel we can improve and do better ourselves. We’re looking forward to seeing everyone use these new features, and we’re excited to keep improving the platform alongside the community that makes it what it is. Cyan.