Hi Wyrmsworth ! 😊 

Thank you for the compliment and suggestions. 

The NFO format:

Well, it's an almost XML (not proper) formatted file format which is commonly used by most media managers to import/export/share metadata for about 2 decades already. It may even go back to the first KODI version - which was called XBMC in 2002 and created for the original XBox.
For example KODI and JellyFin (and others) in some fashion work with these files. See also the documentation on NFO files for Kodi and JellyFin.

I have kept the implementation to a bare minimum since there seem little demand for it (you're honestly the first person even asking about it) and I wanted to keep the data uniform and supported by the other data providers as well (at that time - it's been in RMTV for quite a while now).

My best guess why people don't ask about it: Most users probably rely on their other tools to deal with this (like Sonarr, Plex, JellyFin, Kodi, Emby, Tiny Media Manager, etc).

Note:
You're right about the NFO extension being used for other purposes on the Windows platform as well. And it's used for ASCII drawing like files as well. See also this Wiki page. Unfortunately, I didn't define this "standard", and if it were up to me I'd pick real XML or even better: JSON - but at the time of conception I suppose neither file format was very commonly used.

Dumping it as a TXT file: what format would one use?
I mean; it wouldn't be impossible to implement this in a new release of RMTV.
May not even be all that tricky to clean up with a tiny tool - I'd have to write one though.
In essence:
- Remove all "</*>" tags
- Replace "<tag>" with "tag: "

Assuming your example:

<episodedetails>
<title>Good Luck, Father Ted</title>
<season>1</season>
<episode>1</episode>

What would you like this to look like? Something like this?

Title: Good Luck, Father Ted
Season: 1
Episode: 1

Note: since NFO's are not following proper XML formatting, most XML-2-TXT converters will probably fail.

Note: before modifying these files, better make sure NFO files are not used by you software. RMTV doesn't use NFO files by itself, but does generate them (if set) for other applications.

Coffee

As for coffee - oh wow you went all pro there 🤣 .
Honestly, I've never realized there would be YouTube host suppliers?
I used to get my favorite coffee from Minneapolis, but that has been more than a decade ago now. 😜 

x86 32 bit

Why x86 is being referred to as 32 bit? I suppose because x86 was based on the 80386 and 80486 Intel CPU's, which are 32 bit processors, with a 32 bit instruction set. Hence x86. I can argue though that this not to be entirely correct, but who am I to argue that there as also 8086, 808186 and 808286 and those were 16-bit.
The x64 bit term, was originally called x86–64 or AMD64 (since it's using the AMD 64 bit instruction set, not to be confused with Intels failed Itanium 64 bit instruction set). I suppose people got lazy. 😉 

Anyhoo - for the Windows platform I'm sticking with 32 bit for now, just so it keeps running on [very] old PCs.
Just thinking that won't harm anyone, since 32 bit applications run very well in 64 bit Windows versions (Intel or ARM CPU).
There will be a 64 bit in the future of course now that the 32 bit market share drops to almost zero.