As in, do more than just skim them for technical info. I mean read the ones that go into detail about the rhyme and reasoning behind the changes that were made... sometimes in rather great detail.

It's just something that came to my mind as I was working on the small novel I have packaged along with my mod. I started to wonder, "seriously, has anybody ever actually read this damn thing?"

For general software readmes, admittedly no, I usually believe that I can simply figure things out on my own.

Morrowind readmes, however, I take quite seriously. I've spent a long time and a lot of effort developing my primary modded install and I like to know what I'm installing and what will go on "behind the scenes" at runtime, in order to avoid conflicts or unwanted behavior.

I do in fact actually read the readme's, though probably not for their intended use, but because I have come across some that just happen to be filled with very extensive and intelligent humor that I find very appealing, yes, some are just standard, install this like this and so, but many have extra tidbits that give insight into the creator's process of thought that is, to me, very interesting and normally very entertaining!

Well, thanks for making me feel like I'm not wasting my time doing this, then.

Actually, writing the readmes out is a helpful thought process in and of itself, as I often find myself encountering new problems that need fixing while explaining the changes I've made.

Mod readmes, yes. Especially if the mod is complicated. I'm definitely not installing something big until I know what it does and how to use it. Changelogs I usually don't read, unless I had an issue with an old version, or if the mod really interests me.

Of course. However I'm pretty certain that those of us who do (such as all the above) are rare beasts.

I'll be very surprised if someone posts to this thread "Course I don't, why should I do that? After all, when the mod doesn't work because I didn't even read the instructions, how would I be able to throw this brickbat at the poor suffering modder?" (grin). However, that seems a common attitude to readmes. I've always like Wrye's attitude to such people myself.

Actually I only look at installation instructions and incompatibilities. I may go back to the read me if I find something unusual or am completely stumped but really want to be surprised in game and try to figure out things on my own as intended by the mod's creator. While it is probably important to list spoilers, I usually, if the mod is well written and put together, do not need to go back to the read me for that.

Like for your alchemy mod, I probably will not use your html read me. I would rather find an alchemy book in game by purchasing, stealing and/or questing whereas I will find and keep as any alchemist would - far more enjoyable than looking at a read me.

I read them all. I always like to know what goes into making a mod and how to use them. It's like reading instructions for a TV or PC game. I like information and knowledge. Call me old fashioned. Well...maybe kind old.... :yawn:

Raed

The basic readme that tells me what I am looking forward to in a mod, yes I read them. I also read the other text files to see what else is there to know about the mod I am about to use.

It really depends on whether the author has a gun pointed at me head or not.

I skim most readmes as in I normally avoid the "how to install a mod" as I know how to that. I normally go stright to the description and changelog. If I want to use anything from the mod I look at credits, If i need to contact then I read the contact etc...

so basically I read the bit of the readme that I need at that moment. Theres rarely a time where I dont read at least a part of the readme fomr a mod I downloaded.

The only time I never read a readme is if its a mod that I have downloaded and used extensivly before and know inside out ( i.e better bodies, better heads, darknuts retxtures ) some of the mods that I always have in my install. ( I have had to reinstall morrowind countless times over the years and so when you download X ammount of mods that you constently use I tend to not read the readmes if I have already read them)

I really appreciate a comprehensive readme specifically with mods like yours BTB that have wide arching gmst changes and massive spell system changes etc. I can say I have spent quite a bit of time reading your readmes. So, yes I read most readmes because I like to know exactly what is being changed in my game. That said if a readme doesn't look at first glance to contain much information then I skim it for technical procedure.

Well, all I can say is that in the process of writing the readme for the "Spells" and "Alchemy" plugins for my mod, I just ran into about three issues I had to go back and revisit.

I think I get far more out of it than anyone else here ever will

only to find out where I need to go in game if I'm having trouble.

If its a read-me for a simple mod, ( as an example ) model replacer or textures or even a new armor, then i skim them.

For complex stuff is generally reading!

I used to did.

Now since I mod 99% of the time I only skip right to the usage and permission part

Usually, if only to make sure I'm installing it correctly. Those that don't read the files that come with the mods they download do at their own risk if they haven't read them before.

I read Readmes entirely, from the description to the credits. Learning about the reasoning and history behind the mod is quite interesting to me. After checking the mod's description, I always check the changelog to see how the mod evolved over time. Some modders also insert a bit of humor in their Readme, which is nice to read too.

I only ever read the install instructions and incompatibilities with other mods, just to make sure I install everything correctly if it's a complex mod. Other than that i really hate when authors throw in banter into their readme so i just ignore it.

Like most of us, who have installed a thousand mods, I just check for special instructions and compatibilities.
But I think it is incredibly important for ReadMes to be well made, and taken seriously by both the modder and user. There is nothing worse than people asking for help, or thinking the mod doesn't work, just because they didn't read the instructions.

I do, actually.
For many reasons already stated.

I always skim it before actually installing in my game. I pay most attention to compatibility/installation issues, but do actually read it all.

I don't like installing a mod if it doesn't come with a readme and if the readme is poorly written or has a lot of spelling errors I won't install the mod as the readme gives a reflection of how much care has gone into the mod

I normally check the credits to see who else has contributed to the mod and if anything can be reused - if the mod has anything to do with mge then it gets read several times

If there is a troubleshooting section that is always appreciated

I'm sure plenty of people read the readme - the proper question is do they comprehend what's written?

I read each and every word. I've had too many problems with my game in the past to not check for possible bugs, conflicts, warnings, etc. If there is anything vital I need to know before adding a mod to my game - and risk breaking it - I expect such information to be in the Read-Me.