Implemented Allow control over description replacement

[anna]

I've seen feedback from a couple people that they dislike Heliosphere replacing the PMP descriptions with the mod page description. The reason that Heliosphere does this is so that people don't need to visit the mod page to get relevant information about the mod, and it also prevents the mod creator from needing to duplicate information in two places.

I can make this a client-side setting defaulted to off, give control over this behaviour on a per-mod basis to mod creators, do both, or do nothing. What do people think is best?

 

[My'rie]

If we are not going to keep it as is I would prefer it to be up to the mod creator as to whether or not the modpack description is overwritten. The fact I only have to write the mod description once is one of my favourite things about Heliosphere though I can understand how that can be frustrating for others

 

[thefinalwitnessxiv]

i definitely think an option to either copy the mod page description into the .pmp or not copy it would be the best option for everyone! i can totally see why it was implemented, both to ensure SOME kind of description is there to help users identify info about the mod if a creator didn't add any, as well as a quality of life thing so as to not have to write a description twice, but i definitely prefer to make my mod page descriptions very detailed whereas my .pmp descriptions are condensed down so as to not require so much digging to find relevant information by a user who has already downloaded it. i figure if they need the more detailed information, i've included the link back to my helio mod page, so they can check there for further details.

personally, maybe the best option for everyone could be something like, if the .pmp already has a unique description, give the option to overwrite it with the helio mod page description or not, but if it doesn't have a unique description (i don't know if it'd be possible to check for, like, textool's default "a modpack made in textools" description or whatever it is), autofill it with the helio mod page one? that way, people who do have intentionally different .pmp descriptions could choose, but the idea of ensuring SOME kind of information is in the description in cases where no description was written to begin with could still be fulfilled? again, i'm not sure if there'd be a way to detect textool's default description (or penumbra's, assuming it has one and it isn't just blank, i've never checked), but that SEEMS like the most "this covers everyone's concerns" solution to me?

 

[Dragoness]

I've got to echo what thefinalwitnessxiv said, give an option to override the description if it already has a unique description. Personally, for myself what is done won't affect my work just because I already import the description I write for the PMP into Heliosphere. Although I know that isn't the case for other people's mods so having a button to add the Heliosphere description to the PMP would work best. We've already got an option to get the PMP description imported into Heliosphere so having a button to do the opposite would just make sense to me.

 

[Bizu]

the fact that HS already changes the URL bothered me (severely so)
And this is how I found out that it changes the mod description too.

I dont like that it changes the description.

I specifically try to modpack my things so the modpack contains information that's relevant to the user during usage (such as toggle efficiency/usage, colorset optimizations etc. Stuff that's not relevant until you are in-game, using penumbra, and stuff i Don't want cluttering the mod description page. )

And I keep the modpages simple and copy-pasted between HS/Patreon, as theyre not there to help a user USE the mod, but determine whether or not the mod is for them (body sizing/compatibilities/item pieces)

I don't want any part of the modpack to be overidden by HS at all as a creator.

Edit:
The fact that HS changes the URL of the modpack means you shouldn't even have to change the description, since the link to the page is built into the modpack >:|

 

[Octoprincess]

I agree with thefinalwitnessxiv, I also sometimes make my modpack descriptions a deliberately condensed version of what's on the modpage if there's a lot of info, or if there's info that's only really relevant once you've already installed it. I don't want the modpage version of the description to overwrite that.

I understand the intent to ensure modpacks *have* a description, I do think that's convenient for modpacks that don't have a description at all or wouldn't warrant them being different between modpage and modpack.
But I think making it something creators can choose on a per-mod basis would be better.

 

[LorefiendRX]

I make small vanilla edits/mashups, and I would love for the possibility to include more in the mod description itself that isn't on the mod page. The goal was to make the mod itself say where textures are being pulled from in more detail to help fix potential issues with texture upscales, something not necessary to the people just looking at the mod.

In fact, that's what I did, but I didn't know the mod page description would overwrite the mod file's for a long time, since I simply kept using my local file for months.

I would like to see a checkbox that is ticked by default to copy the mod description into the modpack instead. Empty descriptions on mods still seem to be the norm, so Heliosphere's behavior is an upgrade, but people going above and beyond should be able to opt out of it and be able to provide two separate ones if they're willing to put the effort in.