Cyan

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.