Include the LSPDFR folder with the download

[Reddington 4,447]

Something I (and UnknownBastion) see a lot on ULSS is people who place their LSPDFR plugins inside of the lspdfr folder in the main directory.  For reasons still unknown to me, you guys included a lowercase lspdfr folder, then named the plugins lspdfr folder LSPDFR, which isn't even there by default. 

 

Going forward, I think either:

 

1) The lowercase lspdfr folder needs to be renamed to lspdfr configs, or something that tells people this folder is for audio and data, not plugins,

 

2) Rename the LSPDFR folder to LSPDFR plugins

3) Include the LSPDFR folder with the download, and include a text document that explains what that folder is for.

 

 Either way, something needs done to alleviate the constant confusion for new people. Logically, it makes no sense having two of the same named folders for modding anyway.

Edited September 5, 2020 by Reddington

[UnknownBastion 2,337]

2 minutes ago, Reddington said:

Include the LSPDFR folder with the download, and include a text document that explains what that folder is for.

I like this if people would actually read the text documents included with downloads. The amount of readme's that go unread is astronomical. 

[Reddington 4,447]

Just now, UnknownBastion said:

I like this if people would actually read the text documents included with downloads. The amount of readme's that go unread is astronomical. 

 

That makes it easier for us.  If people don't read it, we can tell them that we don't give help to people who don't read readmes.

[UnknownBastion 2,337]

Just now, Reddington said:

 

That makes it easier for us.  If people don't read it, we can tell them that we don't give help to people who don't read readmes.

Perfection. 

[LMS 2,065]

I admit that it is a bit confusing, especially for newcomers. What we did for RDRFR, and could do here as well, is have a plugins folder in the "lspdfr" folder (where audio, data etc. is). That way everything is in one place. I am not sure if I want to remove support for the "plugins/lspdfr" folder as that has been around for many years now, but perhaps having the two folder co-exist. What do you think?

[Reddington 4,447]

2 hours ago, LMS said:

I admit that it is a bit confusing, especially for newcomers. What we did for RDRFR, and could do here as well, is have a plugins folder in the "lspdfr" folder (where audio, data etc. is). That way everything is in one place. I am not sure if I want to remove support for the "plugins/lspdfr" folder as that has been around for many years now, but perhaps having the two folder co-exist. What do you think?

 

 

I think that could work with how things are currently.  If folks want to do the plugins/LSPDFR, they still have to make it themselves.  That way there's no conflicts from which LSPDFR folder is being read/

 

When you say have a plugins folder inside lspdfr, would it be plugins-->LSPDFR, or just lspdfr-->plugins?

 

If the latter, that could work.

[UnknownBastion 2,337]

6 hours ago, LMS said:

That way everything is in one place. I am not sure if I want to remove support for the "plugins/lspdfr" folder as that has been around for many years now, but perhaps having the two folder co-exist. What do you think?

If you could have it co-exist that would be great. I would still like the old way because it works and is super easy....if only people could just read readme's. Then this all wouldnt be an issue. 

[LMS 2,065]

13 hours ago, Reddington said:

When you say have a plugins folder inside lspdfr, would it be plugins-->LSPDFR, or just lspdfr-->plugins?

 

If the latter, that could work.

 

It would be lspdfr->plugins, but we would also still read plugins->lspdfr. The only potential issue I see is if someone installs the same mod in both places, but I suppose I can work around that too.