Does anyone read the included textfiles in the wads and mods?

[Lizardcommando]

I feel like most people don't bother reading any of the textfiles included in the wads and mods they download. A lot of simple questions can easily be answered by spending a few minutes reading the textfiles. I also feel like I spend a little too much time writing a bunch of information down in my textfiles for my wads and mods that end up never being read.

 

What about you guys?

[Jayextee]

I gotta know where the music's from if it slaps hard or if I recognise it from somewhere, so yes.

[PROTO32TYPE]

I prefer to read any text file or similar (.txt, .doc, .chm etc). 

[Catpho]

People who do read text files are usually silent, because they have nothing to complain about.

[Naarok0fkor]

Yes. You better read mine because it spelled disaster for more than one Youtuber...

[Stupid Bunny]

I definitely do.  I always appreciate when folks read mine because I usually (not always) put some fun flavor text in there, as well as sometimes things they need to know to play the wad.  I definitely put way too much work into things that like a half a person on average will actually end up reading.

[Celestin]

I usually check them out for authors' notes regarding the maps.

[Dusty_Rhodes]

Pretty much always. I'm a sucker for wads with a story, even really barebones ones. I also definitely wanna know where music comes from, if levels are co - authored or inspired by something in particular, etc.

[Flower_XD]

I do. 
I love because I feel that is a time capsule of the moment of the release.
What this person was thining when decided to make their creation public? What inspire them? Any history behind it? Was a creation to be shared with family and friends?
I played a lot WADs, a lot from the 90's and this people are not around anymore for a reason or another, so my only chance to know what they were thinking is by reading the file.

Also I love when people leave a list of the music too :) 

[MundyC]

 

"If you ignore WAD textfiles, you go to hell before you actually go to hell!"

-Captain Doom Albano

[Bald Cyberdemon]

I always read the txt file of a wad mostly to answer 3 questions:

1. When was this wad released?
2. Who made this wad? (Both of these questions are mostly for Hobomaster22's Doom Launcer)
3. What port/compatability-level is this wad designed for?

While a bit pragmatic, I still also bother to read the description for flavor and interest

[Redneckerz]

My title implies that this is part of the description. So yeah, i read them. Some put a lot of effort in them and describe their thought process, so its like a bit behind-the-scenes. It is interesting.

[Dark Jaguar]

10 hours ago, Lizardcommando said:

I feel like most people don't bother reading any of the textfiles included in the wads and mods they download. A lot of simple questions can easily be answered by spending a few minutes reading the textfiles. I also feel like I spend a little too much time writing a bunch of information down in my textfiles for my wads and mods that end up never being read.

 

What about you guys?

If there is one, I read it.  That is, I try to read it, but sometimes the readme files are phrased so oddly or assume so much about what I already know that they're less than helpful.  At the very least, I simply want to know what features are expected for the mod to work (Vanilla, limit removing, boom, or z?).  And no, filling in with the word "obvious" is not helpful.  You don't know where someone found the archive, and many people find these things outside the Doomworld forums.

Edited October 2 by Dark Jaguar

[Lewonx]

I almost always read text files.

[JustHeziel]

Yes, not completely, I admit. But just to answer some basic questions: sourceports/complvl supported, maps/levels count, other wads made by author.

 

Also, the text file is the first thing I read If I find a problem loading the WAD or in-game.

[Lippeth]

Always give it a once over in case there's anything specific I need to know about beforehand, but I'm not usually so thorough as to even read a paragraph(s) long backstory unless I already like the wad and want more without playing more.

[Capellan]

I always at least check details like intended complevel (vital) and the overall pitch.  Anything that describes itself as slaughter, or puzzle-oriented, or talks about how challenging it is (edit: or does not have difficulty settings enabled) generally goes on the 'this is not for me' pile.

 

The text file also provides less critical but still useful context like whether there are new monsters, sounds, or weapons (the last two are generally a negative, in my eyes).

 

I do not check whether there is new music.  I always have it turned off.

Edited October 1 by Capellan

[Li'l devil]

Yes, definitely. Specifically, I always look for what difficulty the authors recommend playing the wad on for the first time. If the text file says UV is for experts and most people should play on skill 2/3, then I know that I shouldn't try UV.

 

Edit: also I look for whether the wad was primarily meant to be played from pistol starts or not, which I think is kind of important.

Edited October 1 by Li'l devil

[DreadWanderer]

If there is a text file I always read it in order to get info on mappers and music if they're not all available on a DW thread or something. Sometimes text files contain super interesting snippets on design, inspiration, the thought process behind making certain maps, or even some extra narrative. It's almost never a waste of time because you nearly always learn something cool.

[Doom_Dude]

I always do, for sure. There's usually good info in there. I find it disappointing when there's no text or it doesn't say much of anything. lol

[roadworx]

ye, ofc. it provides important info about the complevel, number of maps, difficulty implementation, etc. not to mention that it provides a lot of good info as to what you'll be getting into

[id/ea]

I mean, does reading it off of the /idgames Archive Database count?

[Lizardcommando]

3 hours ago, id/ea said:

I mean, does reading it off of the /idgames Archive Database count?

I think it counts.

 

Reading through the replies makes me feel more at ease knowing my spending time writing out a bunch of wad information and tons of lore and extra details about my wads and mods wasn't a complete waste of time.

[Gibbitudinous]

I certainly do since I like to make sure I know the necessary compatibility level and any important notes or warnings on how to play the wad.

 

3 hours ago, id/ea said:

I mean, does reading it off of the /idgames Archive Database count?

 

I mean it's exactly the same information so why wouldn't it.

[Xymph]

Text files are essential when covering mods on the Doom Wiki. The less info and/or the poorer it's formatted, the harder that becomes.

 

[Firedust]

I always read it and find it awesome if the author(s) contextualise the story/inspiration behind the levels as well.

[eteinen]

I’d be a little surprised if people didn’t!

[chexwarrior]

I love it when wads include a story so I always read the text files included.

[purple_ruberoid]

I think I read them most of the times. Especially if wads are really good. Or music, of course

[holaareola]

Usually yep. Find out which people did which maps in a team effort, I also like a bit of author autobiography if it's a wad I'm admiring / enjoying a lot. Unless the author named it readme.txt like it's 1994 in which case it's probably not even for the wad I'm playing!