Nice work....

[DarkGreyCat]

So the answer to lazy ass mod pack makers is to take control from mod maker?

 

What percentage do they give back to mod creators? I'd be impressed if it was more than 5%.

Also, modpack makers won't share anything with the creators when they plaster the modpack section with Patreon begging.

 

If I read it right, Mod list curators (collections) won't be getting Donation Points for their list.

 

Yeah, but it won't stop this from happening.

Edited July 10, 2021 by DarkGreyCat

[showler]

 

So the answer to lazy ass mod pack makers is to take control from mod maker?

 

What percentage do they give back to mod creators? I'd be impressed if it was more than 5%.

Also, modpack makers won't share anything with the creators when they plaster the modpack section with Patreon begging.

 

You assume not wanting to update is a result of laziness. Which indicates that you haven't read the explanations of how Collections might be used.

 

I haven't seen percentages. It was reported that they had distributed $750,000 to Mod Authors with 95% coming from site advertising revenues and memberships.

 

Anything done by "patreon begging" has nothing to do with Nexus and nothing prevents the Mod Author from starting their own Patreon.

 

 

 

And again, authors update mods for a reason. Why is the onus on mod authors to make sure some list curators list doesn't change? Do we really WANT them distributing mods with known bugs??? That's just idiotic.

Authors update mods for many reasons, not just to fix bugs. If a Collection has a mod that improves the Thieves Guild and another mod that improves the Companions then the author of the Thieves Guild one does an update to also improve the Companions then the Collection curator might want to stick with the old version so it doesn't conflict with the other mod. Or the Collection curator might just prefer the older version.

[FlashyJoer]

 

The main reason why Nexus is doing this, is because they don't have real competition...

Yet.

[Guest deleted34304850]

 

Because they want their system to have more functionality than any other collection system.

 

And Mod Authors have never been able to opt out of any other collection system, so why should this one be hamstrung by such a system?

Mod authors need simply stop updating their mods here and post those updates elsewhere.

 

Nexus may claim infinite rights to the binaries in their database and be able to use them in the modpacks, but it we stop updating here and post updates elsewhere, those binaries are now different AND they are not on Nexus servers, so they will have NO rights to include them in their modpack lists. And if they do use them, we have legal ground to do something about it, because they refused us the means to opt out and removed our ability to remove our mods, and then to go and circumvent all of that to use OFF-Nexus mods hosted elsewhere, that are not within their "rights"? No no.. that would be very bad for them.

 

Mod authors actually do have the power here and we can exercise it. Nexus may win round one with all of this stuff, but in the long run, they've shot themselves in the foot. Literally. Users follow mod authors, not the site. And if the updates to their favourite mods are elsewhere... not hard to intuit what comes after that, right?

 

what would happen if a mod author uploaded an update to their mod that didn't cripple the mod, but simply gave you a bit of the mod - with some sort of readme file packaged that said if you like what you've seen of this mod - you can download the full version at <download link>.

i don't think such a thing breaks any rules does it? the mod works - it just doesn't give you everything up front?

[FlashyJoer]

 

 

Because they want their system to have more functionality than any other collection system.

 

And Mod Authors have never been able to opt out of any other collection system, so why should this one be hamstrung by such a system?

Mod authors need simply stop updating their mods here and post those updates elsewhere.

 

Nexus may claim infinite rights to the binaries in their database and be able to use them in the modpacks, but it we stop updating here and post updates elsewhere, those binaries are now different AND they are not on Nexus servers, so they will have NO rights to include them in their modpack lists. And if they do use them, we have legal ground to do something about it, because they refused us the means to opt out and removed our ability to remove our mods, and then to go and circumvent all of that to use OFF-Nexus mods hosted elsewhere, that are not within their "rights"? No no.. that would be very bad for them.

 

Mod authors actually do have the power here and we can exercise it. Nexus may win round one with all of this stuff, but in the long run, they've shot themselves in the foot. Literally. Users follow mod authors, not the site. And if the updates to their favourite mods are elsewhere... not hard to intuit what comes after that, right?

 

Wabbajack has the ability to interact with many different websites, to download mods. I do not know all the ins and outs of the system, I am just aware that it has that ability.

 

True. However, if you have built an optin/optout for Wabbajack inclusion and have a captcha running at time of download, NO api is going to be able to download your mod via a list.

There are ways to do this to prevent anyone from modlisting/modpacking offsite mods. ;)

[showler]

 

what would happen if a mod author uploaded an update to their mod that didn't cripple the mod, but simply gave you a bit of the mod - with some sort of readme file packaged that said if you like what you've seen of this mod - you can download the full version at <download link>.

 

i don't think such a thing breaks any rules does it? the mod works - it just doesn't give you everything up front?

 

You'd annoy your users to the point that they would find an alternate mod would be my guess.

 

Also, you'd pretty much have to have two mods that worked together to do that since installing a "full version" to replace the "demo version" would break savegames.

[FlashyJoer]

In thi

 

 

 

Because they want their system to have more functionality than any other collection system.

 

And Mod Authors have never been able to opt out of any other collection system, so why should this one be hamstrung by such a system?

Mod authors need simply stop updating their mods here and post those updates elsewhere.

 

Nexus may claim infinite rights to the binaries in their database and be able to use them in the modpacks, but it we stop updating here and post updates elsewhere, those binaries are now different AND they are not on Nexus servers, so they will have NO rights to include them in their modpack lists. And if they do use them, we have legal ground to do something about it, because they refused us the means to opt out and removed our ability to remove our mods, and then to go and circumvent all of that to use OFF-Nexus mods hosted elsewhere, that are not within their "rights"? No no.. that would be very bad for them.

 

Mod authors actually do have the power here and we can exercise it. Nexus may win round one with all of this stuff, but in the long run, they've shot themselves in the foot. Literally. Users follow mod authors, not the site. And if the updates to their favourite mods are elsewhere... not hard to intuit what comes after that, right?

 

what would happen if a mod author uploaded an update to their mod that didn't cripple the mod, but simply gave you a bit of the mod - with some sort of readme file packaged that said if you like what you've seen of this mod - you can download the full version at <download link>.

i don't think such a thing breaks any rules does it? the mod works - it just doesn't give you everything up front?

 

 

In this instance, I dont really know.

 

As a mod author, I wouldnt want to do that to users. Make them go here and there and everywhere to get the pieces to make a mod work. I dont think anyone would like to do that.

 

This issue is NOT about mod authors crapping on the user and we, the ones I know of anyone, are not interested in doing that. Our quarrel is with policies, not with the mod using community.

 

Its really far better to either request deletion before end of deadline or leave the mods there that are there and just never update them again (here) and only release updates elsewhere, where Nexus' API will not have the rights to pull it (especially if they are behind a Captcha).

[FlashyJoer]

Also, you'd pretty much have to have two mods that worked together to do that since installing a "full version" to replace the "demo version" would break savegames.

 

Not true. Well, not for mod authors that actually *know* what they are doing.

[Guest deleted34304850]

 

 

what would happen if a mod author uploaded an update to their mod that didn't cripple the mod, but simply gave you a bit of the mod - with some sort of readme file packaged that said if you like what you've seen of this mod - you can download the full version at <download link>.

 

i don't think such a thing breaks any rules does it? the mod works - it just doesn't give you everything up front?

 

You'd annoy your users to the point that they would find an alternate mod would be my guess.

 

Also, you'd pretty much have to have two mods that worked together to do that since installing a "full version" to replace the "demo version" would break savegames.

 

there are more games out there than skyrim mate. look at the bigger picture for once eh?

[Guest deleted34304850]

In thi

 

 

 

Because they want their system to have more functionality than any other collection system.

 

And Mod Authors have never been able to opt out of any other collection system, so why should this one be hamstrung by such a system?

Mod authors need simply stop updating their mods here and post those updates elsewhere.

 

Nexus may claim infinite rights to the binaries in their database and be able to use them in the modpacks, but it we stop updating here and post updates elsewhere, those binaries are now different AND they are not on Nexus servers, so they will have NO rights to include them in their modpack lists. And if they do use them, we have legal ground to do something about it, because they refused us the means to opt out and removed our ability to remove our mods, and then to go and circumvent all of that to use OFF-Nexus mods hosted elsewhere, that are not within their "rights"? No no.. that would be very bad for them.

 

Mod authors actually do have the power here and we can exercise it. Nexus may win round one with all of this stuff, but in the long run, they've shot themselves in the foot. Literally. Users follow mod authors, not the site. And if the updates to their favourite mods are elsewhere... not hard to intuit what comes after that, right?

 

what would happen if a mod author uploaded an update to their mod that didn't cripple the mod, but simply gave you a bit of the mod - with some sort of readme file packaged that said if you like what you've seen of this mod - you can download the full version at <download link>.

i don't think such a thing breaks any rules does it? the mod works - it just doesn't give you everything up front?

 

 

In this instance, I dont really know.

 

As a mod author, I wouldnt want to do that to users. Make them go here and there and everywhere to get the pieces to make a mod work. I dont think anyone would like to do that.

 

This issue is NOT about mod authors crapping on the user and we, the ones I know of anyone, are not interested in doing that. Our quarrel is with policies, not with the mod using community.

 

Its really far better to either request deletion before end of deadline or leave the mods there that are there and just never update them again (here) and only release updates elsewhere, where Nexus' API will not have the rights to pull it (especially if they are behind a Captcha).

i was thinking more as a reaction to this "you cant delete your stuff" rule. okay so i can't delete my stuff, but i can put up a version that can't be deleted, but simply points people to where the updated files will be found. mind you, you could do that with the addition of a readme file that says the same thing i suppose. just saying that "the version you just downloaded is no longer supported, if you want the latest/greatest version of my work go to ...."

 

that way no-one gets messed about - aside from this place which seems to specialise in messing everyone about to suit their own agenda.