Hi,

 

When you go to the website to download something anything like a: Mod, Plugin, script, anything. There should be a option to request removal. 

 

 

What I mean: There should be a button called request removal on plugins, scripts, cars, mods. Because if they are outdated and someone download's the thing, it could mess their game up.

For example: Albo's mods. They are outdated, the policeradio mess the game up. That's why we need a option to request content removal. I don't like it when there is outdated mods. 

I vote no. There is no reason to remove old mods. They're still useable if you've an old version of GTA 5 for modding (which many still do). 

 

A way to mark which version it is compatible with though could be nice, but it's a difficult thing to enforce moderation-wise all together. 

 

Car mods don't really get outdated (anything that modifies models really). 

3 minutes ago, ineseri said:

I vote no. There is no reason to remove old mods. They're still useable if you've an old version of GTA 5 for modding (which many still do). 

 

A way to mark which version it is compatible with though could be nice, but it's a difficult thing to enforce moderation-wise all together. 

 

Car mods don't really get outdated (anything that modifies models really). 

Okay.

I'm up for adding markings to outdated files, however I'm not too much a fan of removing them outright.

You'd be surprised the amount of people still using LSPDFR 0.3 for example, and who have never really updated their game.

15 minutes ago, Cyan said:

I'm up for adding markings to outdated files, however I'm not too much a fan of removing them outright.

You'd be surprised the amount of people still using LSPDFR 0.3 for example, and who have never really updated their game.

please get rid of outdated files it really bugs me 

14 hours ago, Cyan said:

I'm up for adding markings to outdated files, however I'm not too much a fan of removing them outright.

You'd be surprised the amount of people still using LSPDFR 0.3 for example, and who have never really updated their game.

I like this idea, honestly. A small orange warning box with a note that 'users have reported it as incompatible with the latest versions and blah blah crashes blah blah oddities such and such' near the top would help with mods that aren't actively maintained, such as (as mentioned) Albo's plugins.

 

I think an implementation similar to the way it's done on LSPDFR: The Mod would probably be good - you could use the 'clean install' warning box where the 'antivirus false positive' box is, and rework it as necessary - that way, it's up at the top before the screens, yet it still draws attention. Alternatively, adding the warning box to above the "About This File" header would still make it rather visible for those reading the description without being as out-of-the-way as a header.

 

EDIT: I did a piss-poor job of explaining what I meant when I typed this bit out, so I made a couple of mockups in my other reply.

Edited September 4, 20205 yr by EvilJackCarver

I would prefer just a little forum marker before the name that states OUTDATED or USES OLDER API. But outright removing them would not be fair to the community nor the mod makers themselves. By forum marker, I mean like the ones uses in the general forums to indicate if the thread is a suggestion, issue, or complaint. It would be a nice compromise between the two ideas.

Tacking onto my previous reply:

 

Yeah, I didn't really do a good job of explaining myself, so I made a quick mockup of the "warning box" idea I had, made via element inspector using LML as the guinea pig (sorry, LMS!)

 

With it above the gallery header:

Spoiler

 

With it above the "About This File" section:

Spoiler

 

16 hours ago, EvilJackCarver said:

Tacking onto my previous reply:

 

Yeah, I didn't really do a good job of explaining myself, so I made a quick mockup of the "warning box" idea I had, made via element inspector using LML as the guinea pig (sorry, LMS!)

 

With it above the gallery header:

  Reveal hidden contents

 

With it above the "About This File" section:

  Reveal hidden contents

 

I very much like this idea. Perfect compromise. 🙂

If something like this is implemented, it should send a notification to the mod creator and give them at least 48 hours to respond before putting up a big banner saying "this mod is outdated". Frankly, a lot of users are idiots, and will say "your mod is outdated and needs to be fixed!" when in fact the user has merely installed it incorrectly or has other issues with their game. If the file is updated after the notice is posted, then the notice should be removed, as that would indicate the mod has been updated. 

Actually, PNWParksFan, I think this can be partially solved with an existing feature implemented in the website.

 

 

We have tags in the downloads system for the LSPDFR API version already; we could theoretically use that to compare to the current LSPDFR version (set somewhere in the backend) and if the version doesn't match (or, for a more advanced implementation, is less than) the current LSPDFR version, we display the banner message.

 

In theory, we could do something similar with game versioning (a "Game API version" filter), but that'd probably require quite a bit more upkeep on the LCPDFR.COM team's end.

Edited September 8, 20205 yr by EvilJackCarver
Example image

41 minutes ago, EvilJackCarver said:

Actually, PNWParksFan, I think this can be partially solved with an existing feature implemented in the website.

 

 

We have tags in the downloads system for the LSPDFR API version already; we could theoretically use that to compare to the current LSPDFR version (set somewhere in the backend) and if the version doesn't match (or, for a more advanced implementation, is less than) the current LSPDFR version, we display the banner message.

 

In theory, we could do something similar with game versioning (a "Game API version" filter), but that'd probably require quite a bit more upkeep on the LCPDFR.COM team's end.

 

Most plugins don't need to be updated for every minor LSPDFR version. Some plugins originally developed for LSPDFR 0.3 still work fine on 0.4.7 even! So no, automatically listing something as outdated because it's selected an older API version doesn't make sense. But, it would make sense that if it's marked as using the latest version then it would not display the warning. 

As you can see, adding the warning is the easy part. Knowing when we should do that is another story.

 

We are working on quite a large website update right now and we will include something to mark files as outdated / broken. It's likely this will be based on community intelligence/marking and moderator oversight but will be able to overridden by the author of the file. It's likely the ability of an author to override the judgement will not lead to any issues, as most of the files that we have that are chronically outdated usually the interest has dissipated to keep the file up to date anyway.

 

I like @PNWParksFan's suggestion of giving creators fair notice as to when this is going to happen, and that's likely how we will implement this.

1 minute ago, Cyan said:

As you can see, adding the warning is the easy part. Knowing when we should do that is another story.

 

We are working on quite a large website update right now and we will include something to mark files as outdated / broken. It's likely this will be based on community intelligence/marking and moderator oversight but will be able to overridden by the author of the file. It's likely the ability of an author to override the judgement will not lead to any issues, as most of the files that we have that are chronically outdated usually the interest has dissipated to keep the file up to date anyway.

 

I like @PNWParksFan's suggestion of giving creators fair notice as to when this is going to happen, and that's likely how we will implement this.

Honestly, that would be an amazing idea. Perfect compromise between the two. Thank you PNWParks for suggesting that as well as EvilJackCarver and thank you Cyan for working with us to find a solution. 🙂