The Readme in mod files calling all modders

[bombshell66]

Goodmorning, goodday, goodevening to you all

 

I have a problem that everybody on nexus has

 

When installing several mods it always happen that the readme file of the mod is simply called readme.txt or RTF or something else like ODT if your using openoffice( wich i higly recommend mostly because its so good that i would even pay for it but its opensource )

 

what happens is that readme's get overwritten and that vital or non-vital info gets overwritten and lost and changing the readme yourself is time-consuming and exhausting

 

What i suggest is to give readme's a modspecific file name li\ke for EVE create a evereadme.txt or awopreadme.txt ( these are just examples)

 

People this is a serious problem wich can easily be changed

 

I hope my message gets heard

 

Note :: I now that not all mods have a standard readme file but a lot do

 

CHeers and enjoy the summer/or / winter

[Werne]

this is a serious problem

No, it's not. There is no need for readme on simple mods that add one or two things or change a few globals (most have names that explain what it does). And if you like reading readmes so much, unpack the mod's archive manually and read it or read it directly from the archive. There's nothing complicated, exhausting or seriously problematic about it aside from needing to click a few times more.

Edited July 4, 2012 by Werne

[bombshell66]

well your right but some mods need additionel files to work and i just like to search in my Fallout dir ( having short term memory problems lately )

 

another option would be to have an inapp option to rename the readme in fomm or NMM ( i just want the mod community and everytihing else about the modcommu be streamlined so people can just jump in without a lot of hassle ( im looking to the future of this community), just a personal wish )

 

Excuse if i came over a bit rude but i was a perfectionist a few years ago so that still haunts me

 

 

Cheers

Edited July 4, 2012 by bombshell66

[TziporaHalevi]

I hate that too, it only takes a few seconds out of your time to give a file that you created a specific name. Ill admit l forgot I do it with my companion mod, next version I'll rename it after I add more info to it

[Cyberlazy]

Agreed, if your readme has any kind of vital info, name it modname readme.txt, or even just modname.txt

 

All my mods come with a readme named after the mod thats just a copy of the nexus description page, formating and all. if I have 'extra' play info, I add that to a 'modname manual.txt' and post that up as the nexus 'readme' so people can check it out without downloading the mod.

Edited July 5, 2012 by Cyberlazy

[tetradite]

Agree on the readme thing (if it's that important for it to be there at all it ought to be named properly).

 

Disagree on Open Office, the Excel equivalent is useless for complicated stuff.

[Quetzlsacatanango]

Meh

You can rename it just as easily as I can.

[Gribbleshnibit8]

And if you're using FOMM to package up a folder, it will automatically rename the readme file to Readme - Folder Name.txt with no input from the user.

 

By packaging from a folder I mean you download a mod, extract it to a folder on your desktop or somewhere (that's where I put them), then go to the FOMM Package Manager and find the "create from folder" button under the mod screenshot section. I do this for almost all mods I download for several reasons (none of which I will go into).

[senterpat]

I agree with this and support it 100%. I also want esps and esms to not be named "main file", those mods are the first to go when I'm trouble shooting because I dunno what the hell it is. (unless I take 10 seconds to check... But no.)

[luthienanarion]

I repackage all of the mods I download, deleting all junk files like readmes from the archive. Not everyone wants dozens of useless text files or images in their Data folder.

 

 

This wouldn't be a problem for you if you didn't trust NXMM to do all your thinking for you.

Edited July 6, 2012 by luthienanarion