Michael21107

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.

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.

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 Filters
The 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 Exclusions
To 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 Creators
As 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: API
Our 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.

Fixed there too 👍

Just something I noticed as it appears to be happening on another file as well as my pack. My RPD pack currently has 5 stars when you click on it.
but on the "monthly trending" page on the home screen it shows it at 2.5/5 stars. same with MDTPro where it shows 3/5 but actually has 4/5 stars currently

Morning all,

Wanted to share some feedback re filtering on Scripts & Plugins.

I love the addition of the 'Made with AI' tag, but it doesn't work effectively for me because:
It takes 5 clicks to exclude the tag.
The tag needs to be reapplied on each page visit (at least in my experience - please correct me if I am wrong)

For something that is becoming a common tag, this creates a fair amount of friction/difficulty for what feels like a popular user action. There's also a UX/usability perspective as well - when one or two files have this tag, it is much easier for these to stand out. With nearly half the page having this tag, it becomes harder to visually filter them out when browsing (and therefore increasing reliance on filtering tools instead...)

Taking LSPDFR Plugins / Callouts for example. That filter is easier to use, persistent-ish (in the sense it updates the URL) and makes sense because it is something that users would often want to separate.

That sort of sets the scene for why I am making this suggestion. Frequently used filters can work better when accessible and persistent, which is why I would like to see an accessible toggle for the 'Made with AI' tag. I'm not trying to penalise AI files with this suggestion, but I think filters that are often used should be prioritised for visibility.

If you go into the effort of maintaining an AI classification system, you get more out of it by allowing users to take advantage of it in an easier way.

Thanks for considering this suggestion,
Charlie

Due to circumstances outside of our control, Russian users may experience issues trying to download files from our website.

This is a result of your government blocking our providers for our file serving servers. This is not an issue with LCPDFR.com.
This may appear confusing to you, as the website otherwise works, but we use different providers for our website frontends vs our high bandwidth download servers.

Some more technical information on what the Russian government is doing can be found in this article:
The Cloudflare Blog
Russian Internet users are unable to access the open Inte...
Since June 9, 2025, Internet users located in Russia and connecting to the open Internet have been throttled by Russian Internet Service Providers (ISPs).
Whilst we discourage VPN use on our network, VPNs are (generally) not blocked for users with an LCPDFR.com account. We recommend creating an account and using a VPN for downloads. I recommend consulting with other Russian internet users on the best choices, as some VPNs may be exposed to the same blocking.

We will look into what actions we can take on our end (e.g finding a provider which is not blocked in Russia) but this is something which is not a priority at the moment, and risks a cat and mouse game.

Hi folks,
 
If you've not already seen, LCPDFR.com has launched a Patreon service. Alongside our gracious thanks, being a Patreon supporter entitles you to some forum benefits, as well as early access to upcoming projects.
 
To access these benefits, you'll have to associate your Patreon account with your LCPDFR.com forums account. This is a simple, easy process.
 
From your user menu at the top of the site, choose 'Account Settings'.
On mobile, this will be hamburger menu > Account > Account Settings.


  From your Account Settings Overview, note the Patreon section, and hit the Configure button on the right hand side.

From your Patreon settings, choose 'Login to Patreon'
You will be redirected to Patreon to login, and you will be asked to grant LCPDFR.com permission we need to verify your Patronage.
Make sure to hit the 'Allow' button.
And you're done!
You will be redirected to LCPDFR.com, and you should see your Patreon name and avatar shown.
If you have pledged to our Patreon page, your benefits will be instantly accessible and you should now be part of the Supporter group and have exclusive access to our early access programme for the duration of your patronage.
Thank you for supporting us.
 
 
Thanks again for becoming a supporter.
If these instructions don't seem to work for you, please send me a private message and I'll look into it.
 
 
It may take up to 30 minutes for your Patron benefits to become available after pledging to us, although this seems to vary.
This seems to be due to a delay in Patreon sending us your information.

This was fixed as part of a site maintenance update today.

Oh yeah, I would prefer it to be customizable too; I can't see why it is hardcoded.

A common complaint we’ve been getting recently is that our website and downloads are slow for people using Deutsche Telekom (DTAG) and other T-Mobile internet providers in Europe, especially during busy (“peak”) times.

The underlying cause is complicated, but in simple terms: DTAG appears to let some network connections become overcrowded unless the other side pays extra for better access. This can effectively create “fast lanes” for those who pay more. We (LCPDFR.com) and our providers don’t pay for these fast lanes, because it goes against the idea of a free and open internet. As a result, performance can drop at peak times.
This issue also affects major internet infrastructure providers, including Cloudflare.

More information:
German: https://netzbremse.de/
English: https://netzbremse.de/en/

The organisation above has submitted a complaint to the Federal Network Agency (Bundesnetzagentur), which is responsible for net neutrality and enforcement in Germany. They will review the complaint.

If you’re affected and you’re a DTAG customer, you can add your opinion in support of the complaint.

Thank you Michael, I couldn’t have said it better myself😅

Hello!
For everyone who has landed here since the Code 3 Callouts Remastered, welcome!
I hope you enjoy these callouts! Thx Stealth22!

Weird edge-case .zip file which has the path separator incorrect. Should be fixed now - our security service now deals with either case.

Code 3 Callouts
"Attention all units, officer needs assistance. Shots fired. All available units, respond Code 3."
This is a plugin that I have been planning for ever since I started writing scripts for LSPDFR. Now that the LSPDFR API has come out, this idea can now become a reality!
The focus of this plugin will be to create a realistic experience where the player needs to do some actual police work. Police work is not always about flicking on the lights and sirens and flying down the road at 100 MPH. Nor is it always about pulling out an AR-15 and emptying a clip on a suspect.
In fact, most of the time, police work is all about dealing with people. Hearing both sides of the story. Figure out who is lying, and who isn't. Sometimes you have a helping hand when you have an eyewitness, and sometimes not. Or sometimes you will get eyewitnesses who contradict one another. Bob says the bank robber's car was blue. Jane says the car was red. Turns out, Jane was on her cell phone, and wasn't paying attention. Oh, and Bob was in the bathroom, so he didn't actually see anything. You later find out that the car was actually green.
It is YOUR job to determine what actually happened based on the evidence. Its time for your shift, Officer. Gear up, and move out.
Callouts
Assault Intoxicated Person Person with a Gun Unknown Trouble Hit and Run Impaired Driver Police Impersonator Road Rage in Progress Backup Required (Domestic Disturbance) Callouts Coming Soon
Burglary in progress (Next update!!) Future Callouts
Citizen reporting officer in danger Suspicious vehicle, with occupant(s) inside Domestic disturbance (May remove this, depending on how the above domestic backup call plays out) Bank robbery Officer requesting backup (potentially with one of the above calls!) Kidnapping in progress Shots fired ...and more!! (Not all of these callouts may be implemented. Plans are subject to change.)
Features
Framework & logic for managing each callout type Dispatch audio Altering suspect behavior based on the response of the officer Ambient events! ...more to come!! Screenshots
The following screenshots are from the Assault callout. You need to get stories from the victim and the suspect! Figure out who is lying by speaking to the witness!
Check everyone's ID's, just so you know who you are talking to, and so you can run their names in your computer!
Videos
FinKone has done a video demonstrating an early version of Code 3 Callouts, and watch for a video (coming soon!) by Jeff Favignano as well!
 
Developer Information
This plugin will be designed to work alongside callout plugins created by other developers. I am already in conversation with LukeD (Callouts V), FinKone, and Straysify, and best efforts will be made by all of us not to step on each other's toes.
Any other developers that will be producing callout plugins are encouraged to keep in touch with all other callout developers to ensure that we don't unnecessarily duplicate any work.

Whenever i get an callout from an callout pack or lspdfr built in callout only the voice and location comes and not the info like what callout it is. Like it is a pursuit or an arrest warrant or a store robbery. Can someone please help me i've tried everything.

Dear all, 
 
As many of you will have noticed, my activity in the LSPDFR scene has decreased significantly over the past few months. There are many reasons for this, the details of which I won't bore you with. It mostly comes down to being busy with other things in my life, as well as LSPDFR becoming less interesting for me having played it for so long and the introduction of frameworks allowing modded GTA5 multiplayer environments.
 
How times have changed since when I joined the community in 2015, from me taking an interest in learning to code in C# to having multiple plugins released on the site. It's been one heck of a journey here. I recall well the first 'mod' I uploaded for the LSPDFR community, which was called 'More Jail Points' at the time. This was first published for RAGEPluginHook 0.20. This later evolved into 'More Jail Points & Prisoner Transporter' and is now known as the all-so-familiar Arrest Manager. When I was contacted by @dbock1989, who was so enthusiastic about my More Jail Points & Prisoner Transporter plugin at the time, I couldn't quite believe it. He had been so kind as to create a variety of images related to the plugin (see below)! It frankly couldn't have been a more exciting moment at the time and, alongside other overwhelmingly positive and welcoming feedback, served as a major motivation factor for me to continue learning to code and create plugins.

 
Following this, I was looking to give more purpose to the LSPDFR traffic stop system. And so, Traffic Policer was born - a plugin originally intended to add a few ambient events related to traffic offences. This has now grown into one of my most feature-packed plugins to date. By this time, some YouTubers started using my plugins in their videos. Not only was this a great way for me to obtain feedback on my mods' user experience, I also watched @Zachary Houseknecht with great pleasure while my ANPR Hit AI lit many of his police vehicles on fire... An absolute howler: https://youtu.be/4D8HshZzWMQ?t=606
 
Some weeks on and Assorted Callouts was next in line. This was originally created out of a callout idea by  @CaptainSugarFree  and turned into what is now known as the Pacific Bank Heist. This took about 4 weeks of intensive development to fully complete (and am I shocked at the code quality looking back at it now... works though). As the first of its kind, the callout featured voice-overs and an intense, detailed SWAT based LSPDFR callout. I was incredibly proud for this to be featured on @Jeff Favignano's channel and I see now that the video in question has amassed over 1.9 million views... breathtaking. https://www.youtube.com/watch?v=eIXKvUyzylA
 
Moving on again. At this point, @FinKone had managed to get me into YouTube. After having released British Policing Script, longing for an LSPDFR experience closer to home for me, many longed a version of the plugin for international and American users to incorporate the traffic stop improvements and a court system. With that, I released LSPDFR+ by doing my first ever YouTube live stream, which was quite the experience. After this, I released Siren Mastery, PoliceSmartRadio and a variety of other tools and smaller plugins. Many hours of coding, effort, stress, giving support and obtaining feedback had been put in by this point. I was absolutely chuffed to then achieve one million downloads on my published files...
This figure has since risen to over five million.
 
Following some negative coverage of LSPDFR in some of the Australian media, I'm also very happy that Wired UK decided to publish an overwhelmingly positive article on the whole GTA5 police modding scene: https://www.wired.co.uk/article/gta-5-mods-lsdpfr-british-police?utm_content=buffer9ca53
 
After PoliceSmartRadio's release - with the infamous April FoolsRadio download giving four thousand people a perhaps frustratingly good laugh - I placed the whole modding scene lower in my priority list. As mentioned previously, this has since been pushed far further down.
 
Some thoughts on the community's development over time
I would describe the LSPDFR community as healthy. @Sam @LMS and all the other contributors have created something very special for all the right reasons and this is largely reflected in the attitudes of the staff & moderation team and community members. With publishing mods on a popular website like this, unfortunately, comes some drama and negativity - and while I have not always agreed with the way and speed the moderation team dealt with my reports relating to me and my work, they have done a good job overall. The few issues that I experienced were all resolved. From my experience in the plugin side of the modding scene, this continues to be the case now.
 
One thing I noted during the months that passed is that both experienced but particularly newer modders are now frequently treated with disdain in the scene. The modding scene has grown massively since when I first started and unfortunately, in this area, it shows. Everyone starts somewhere and the fact someone is spending their free time creating something for all of you to download, for free, has become massively underappreciated and taken for granted. Sure, a new modders' release may be full of bugs and be nowhere near as feature-rich as more developed plugins, but this takes time to solve. Had I received the negative feedback I've seen on many a new modder's release page back in 2015, you can rest assured I wouldn't have continued my development here. When providing feedback, by all means, point out the issues, but do so in a friendly, constructive manner, not in an entitled, toxic one. Have a look at the first few comments on my Arrest Manager download page to see what that is like - this was a major factor for me to consider continuing development! It is essential for the development of the LSPDFR modding community that this attitude is changed back to what it was in the 'good old days'.
 
With all that said, I also hope the release of LSPDFR 0.4 kicks a breath of fresh air into the now somewhat stale core LSPDFR modification. With over 2 years having passed since the latest update of the core modification, I'm sure we all agree that an update would be a very welcome step. From the various preview posts released by the development team, it looks that we all have something great to look forward to there.
 
'Retirement'? So does that mean you're permanently done with the LSPDFR modding scene?
No, but I won't be actively developing plugins for LSPDFR any more. To be fair, nothing's really changing much now compared to the past few months. I intend to remain as a member of the LSPDFR Testing Team and I'm sure I'll be drawn back in at some point to explore some of the new development options in the 0.4 API. I'll also stay around on my discord and occasionally the forums and I intend to continue publishing occasional videos on my Youtube channel. If my time and motivation levels allow, I may publish some minor updates to my current mods before 0.4 is released. The fact remains, however, that I would currently classify myself as 'inactive' in the scene. With so much other stuff going on, I simply don't have the time to commit that I used to. It would be a pity to say the least to let all my work slowly deteriorate and waste away. Therefore, I've decided to publish the source code to some of my plugins to https://github.com/Albo1125/. At the very least, I would like it to be a learning resource for other ambitious plugin developers in the scene. At best, I hope other developers will take it upon themselves to improve the code where necessary (yes it is very necessary!) and create pull requests to share those improvements. These can then be merged and released, with credits obviously included for contributors.
 
Back when I started developing for LSPDFR, very few learning resources were available bar the great example project by @LukeD . This hasn't really changed since, despite the creation of the LSPDFR API repository by LMS (https://github.com/LMSDev/LSPDFR-API) and some posts aiming to document the LSPDFR functions by myself in the API development subforum. A noteable step was the creation of the LSPDFR Developers Discord server thanks to  @Stealth22 A full post with current development resources can be found here: 
I'm planning to publish the source code to a number of my plugins one-by-one to improve this and give something to the community:
Arrest Manager: https://github.com/Albo1125/Arrest-Manager  Assorted Callouts: https://github.com/Albo1125/Assorted-Callouts Albo1125.Common: https://github.com/Albo1125/Albo1125-Common Traffic Policer: https://github.com/Albo1125/Traffic-Policer LSPDFR+: https://github.com/Albo1125/LSPDFRPlus British Policing Script: https://github.com/Albo1125/British-Policing-Script  
By no means do I claim that any of the code I post is perfect or amazing - on the contrary, far from it. With the experience I have now gained, reading through some of my old code makes me want to tear my hair out. This is only to be expected, though - most of my plugins were created as part of my learning experience of C#. Prior to this, I had no coding experience or knowledge. It's fascinating to see how the quality of my code has evolved over time by looking at my various different plugins in order of initial release date.
 
Wrapping up. I hope this post provides some clarification and closure for those of you wondering where on earth I've been over the past few months. It's been an absolute blast and a pleasure. To all of you who were a part of my journey here, thank you.
 

This should now be restored and working.
Add/removing contributors has changed to a new 'Manage Contributors' link/dialog on the author pane.

I can't tell if it's worse that this feature was forgotten about (and therefore not ported to the new downloads page) or that it took someone multiple months to notice

It should be back in an update later today.

Hi, 
I made an topic for every gta v car modder and hoping they will learn or use this.
This is very important against bugs.
You have some lods.
you have a normal.yft and a high.yft.
When you are sitting in the car the game uses high.yft. that's the one with the most details.
then you have normal.yft with and L0, L1,L2,L3.
How further you stand from the car how less detailed it is. that is for the efficiency for the game engine. then it doesn't load the whole model. and giving the vid mem more space for other things.

what some people do, (let say the cvpi what is current.) they use one detailed version for all L0,L1,L2.
eventually the game will crash or you get texture popins because of the use of that vid mem in the distant.
That's why i am making a version that meets the game standards.
I hope that car modders will use this for his own convert. That will make the game more stable.
Regards,
F5544

Hello,

I am a developer for the mod MTFO: Move the F*** Over. @Guess1m also develops the mod with me. Before the site design, it was very visible who all the developers were in a project. I had added him onto the mod before and it showed. Currently, I do not see any of that information anymore. I also do not see a place to add new developers.

Generative AI is being used more and more in mod creation, and we believe transparency around its use is important. While AI offers exciting new possibilities, we understand that not everyone wants to engage with AI-made content. We hope that clear disclosure helps everyone make an informed choice before downloading a mod, and makes it easy to filter out AI-made content.

Starting today, we’re rolling out a new AI disclosure system. It allows authors to disclose the extent of their AI usage, and to be specific about which parts of a mod were AI-made or AI-assisted.
The following AI disclosure options are available:

Description
Tick this if your description was generated or rewritten/refined using AI.
We would also like to note: if you use AI to help write your description in any way, please make sure you verify all claims about your mod. We’re seeing an increase in AI-written descriptions that mention features the mod doesn’t actually include, so this is now enforced under our File Guidelines.
Images
Tick this if any images on your mod page were generated or edited/refined using AI.
Mod & Mod Content
Minor: AI helped with small refinements to the mod or its content (for example: using a chatbot/agent for assistance, or generating assets used in the mod).
Moderate: AI contributed more than 50% of the mod’s content (code, images, data, etc.).
Significant: AI created most or all of the mod (for example: full generation). Tick this as well if you wouldn’t have been able to make the mod without AI.

Some light use doesn’t need disclosure — for example, basic autocomplete or bouncing ideas off an AI.

Disclosures will appear below the file description. If you've ticked Mod & Mod Content, you will be asked for a 'Reason'. You should enter more information (why and how AI is being used) in here.
If you select Mod & Mod Content at Moderate or Significant, your file will also be tagged with the “ai” tag. This makes it easier for the community to filter AI-involved mods if they want to, and makes AI usage clear at a glance.

This is now required for new submissions, and we ask that creators also start updating their submissions if they have an AI disclosure to make. We'd like to request that all disclosures are made by the end of February.

We are hoping we do not have to enforce this too broadly, and creators will come forward and be honest about their work. There are ways of detecting AI work in images, description and content and our moderation team will kindly remind you to make a disclosure if they receive a report of AI work that looks valid. If our staff feel that the AI disclosure is inaccurate or incomplete, files may be hidden until we believe they are in compliance. Making inaccurate AI disclosures may also lead to negative reputation by our automated approval systems.

This is a first step toward balancing the new possibilities AI brings with individual preferences and a changing modding landscape.
Thanks for helping us keep things clear and transparent for everyone.

And to support that same goal of clarity and choice, we’ll be sharing more soon about global filtering options for mod discovery. Separately, we’ll also have some news to share shortly regarding the new LCPDFR.com website API.

Thanks all - this feels like a genuinely positive first step for transparency & inaccurate descriptions.

I think it's also worth acknowledging the wider impact, with low-effort uploads affecting developers who invest significant time into creating, testing & maintaining projects - so it's not just a user filtering issue, but a fairness and visibility one too.

Thanks for this update, I will be looking out for this disclaimer soon 👀

Thank you!