Charlie686

Hiya,
 
You can indeed decrease the callouts multiplier to change the amount of callouts you receive.
I feel with 25 you'll get near to none so I'd suggest trying 150-200 first!
 
Choice is yours 😜 

Thank you !

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

Thanks as always, glad to hear it is on the roadmap. Have a nice bank holiday weekend 🙂

It would be in the lspdfr.ini file 
Path: GTAV/lspdfr 🙂 
 
You'll want to change "Callouts.Multiplier"

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 👀

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 👀

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 👀

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 👀

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 👀

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 👀

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 👀

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 👀

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 👀

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.

Thankyou so much

Hey James,

I'm assuming you mean the grey line of sight-styled area? That's not a blip but a native (though attached to a blip): SET_BLIP_SHOW_CONE

Thanks Lenny 🙂

Remove S136Callouts and retry.

Hi Charlie,

Whilst the current editor translates most of the old editor content to the new editor; it's not perfect, and for some things there is not a 'direct equivalent'.
For the 686 Callouts header and other larger text, this should being translated, but it looks like it is not. This might be a bug due to the colour (see below). You should be able to manually highlight then set as a heading.
Colours have changed-- it is no longer completely free choice but colours that have both a light and dark mode equivalent.
Background colour has been changed to highlight colour, and also has colours which should translate to both light and dark mode. You can also use boxes to achieve separation, and you can change box background colours.
Not sure entirely what's going on with the Stop the Ped highlight/link, but it looks like the new editor wants to remove it at least.

Example in the new editor (have a look in both light and dark mode)

The current way of handling the migration to the new editor is that old content descriptions are not translated until it has been edited in the new editor, so what you see from the new editor, if you save it, will be what's on your file page.

Happy to say the website is now looking and performing much better than it did on Monday morning. We’ve been deploying bug fixes and feature updates throughout this period—75 in total so far. I’m also aware of an issue affecting download buttons (e.g., donation buttons) and will be prioritising a fix for that next.

By default, Search only looks within the content you’re currently viewing (so if you search here, it’ll search just this topic). To search across everything instead, choose Everywhere in the quick search bar before you run your search.

I understand what you mean—I’ll look into whether we can find a middle ground.

Please make a topic in the website support forums if you're still experiencing this, from our data it looks like downloading is okay right now.

Most of the things on this list have now been fixed, but the others are still on my list. Thanks again.

Good work on the website improvement, it is great to see new improvements for LCPDFR.com being driven forward. I will certainly hold you to it in regard to those API improvements! :)

My current observations that I hope will be helpful to you:
Unable to use the login modal (which can be worked around via lcpdfr.com/login/)
Unable to edit my uploaded file.
"This content can no longer be edited. It may have been moved or deleted, or too much time may have passed since it was posted for it to be edited."
My public file has the option to 'show file to the public' rather than an option to hide it.
Choosing the burger menu on a file comment > Feature displays two pop-ups when opening.
You are no longer able to view the VirusTotal results, other than the Clean/Flagged icon. Being able to view a flagged result is important context if this was an intended change.
The Albums tab on my profile is empty, when for others it is hidden (have I done something here?)
The Creator Dashboard/Centre is no longer accessible.
Profile > Manage File Update Notifications does not work. I am not sure if this is a new feature compared to following a file.
Viewing File Stats occasionally results in a Bad Gateway error, and any attempt to change the date range causes the stats page to disappear.
Once again, this version marks a huge improvement. Time well spent and I look forward to using the new customisation options available for files.

You're welcome, Cyan.

Just on VirusTotal, I agree it doesn't serve a hugely positive purpose - no file uploaded to LCPDFR.com has a virus as your team checks scripts & plugins, so what point is there in showing a flag from VirusTotal? It is like admitting some files have a virus! If it is kept though, the first thing anyone thinks when they see a flagged file is "Why?!" so yes, the balance is a bit off currently.

Best wishes with future development. This upgrade has gone down well.^^

Since October of last year, we’ve been hard at work on a modern, refreshed redesign of LCPDFR.com. Today, we’re excited to finally share it with you.

This new version of the site isn’t just a visual upgrade. Behind the scenes, we’ve rebuilt a lot of the core systems that power LCPDFR.com – from the way pages load, to how content is organised, to the tools we’ll be able to build on top of this platform going into 2026 and beyond. We’ve also migrated our custom downloads system and several other bespoke features onto this new foundation.

This launch marks the ninth design update LCPDFR.com has had, and it’s the biggest change since our last major overhaul in 2015 – almost a decade ago.

A Fresh Look, Built for Today
The new site introduces a clean, modern interface designed to be faster, clearer and more intuitive to navigate.
Light & Dark Mode
The site now supports a fully integrated light and dark mode that follows your operating system’s preference. If you’d rather choose manually, you can toggle between themes using the control at the bottom of the site.
Redesigned Editor
Our content editor has been completely rebuilt. It’s more powerful, more responsive, and much easier to use than the previous version. Whether you’re writing mod descriptions, making posts, or writing private messages, the editing experience should feel significantly smoother.

Mods: Front and Center
Mods are at the heart of LCPDFR.com, so we’ve made sure they’re easier than ever to find and browse.
Mods First in Navigation
You’ll now see the Mods portal prominently placed as the first item in the navigation, reflecting what most visitors come here for.
New Grid-Based Layout
Mods are now presented in an expansive grid view, making it easier to scan through content, compare options at a glance, and discover new creations.

Improved Tag Browsing
Tags now play a much bigger role in helping you discover content. Clicking any tag will take you to a dedicated tag results page, where you can explore all related content in one place.



Smarter Search
Finding exactly what you’re looking for should feel quicker and more flexible.
Quicksearch with Filters
The quicksearch has been upgraded with built-in filters, including the ability to search directly by tags. This makes it easier to narrow down results and jump straight to the content you care about.

A full search overhaul is in progress, and what you see in quicksearch today is just a small preview of what’s coming.


Known Issues
As with any major platform change, there are a few rough edges we’re already aware of:
Some content pages under LSPDFR, LML, and RESOURCES may currently appear broken or incorrectly formatted. We’re actively working on fixing these layouts.
The GTA V Native Database is currently not displaying.
Some profiles are showing an error 500.
There are some issues with LSPDFR Sync, we have paused our Pateron until fully resolved.
A small amount of users may be experiencing issues with notifications.
Multiple issues reported by community members (thank you) in this thread.
Some of these have now been fixed. Please continue to report any issues you see.
Thank you for your patience while we work through these issues. Your feedback here is especially helpful, so if you spot anything else that looks off, please let us know.

What's Next and Fixes
This redesign is just the foundation for what’s coming next. With the new platform in place, we’ll be able to iterate more quickly and deliver new features faster than before. Over the next days and weeks, our main focus will be on tightening up the rough edges from this migration and fixing the issues that you might find.
Here are some of the things at the top of our list:
New API for the Mods Center
We've almost finished work on a new API for our mod center - we just have a few changes to make and we hope to share updates on this in the coming days.
Full Search Overhaul
Beyond the improvements you can already see in quicksearch, we’re planning a complete search upgrade to make finding content more accurate, more powerful, and more pleasant overall.
Visual and UX Polish
You may notice small visual quirks, spacing issues, or inconsistent elements across the site. We’re tracking these and will be rolling out incremental polish updates as we go.

This is a big milestone for LCPDFR.com, and we’re really excited to finally share it with you. Take a look around, try out the new features, and let us know what you think – your feedback will help us shape the next round of improvements.

We also hope to have some LSPDFR Enhanced news to share with you in the coming days.

Cyan.

If you are experiencing infinite loading:
 
This means you have not updated your mods folder / have not installed a new custom gameconfig. Follow the below steps.
 
To update your mods folder:
Please delete update2.rpf from your mods folder & re-add a fresh copy from GTAV/update. 
Note that any graphics modifications will need to be re-installed, this cannot be avoided.
 
To download a new gameconfig:
Download a new gameconfig such as the one found here. Once downloaded, drag & drop it into mods/update/update.rpf/common/data.
 
Hopefully this helps you resolve your issue.