A few suggestions from a skim:

1. I think there's a lot of data that would be best factored out somewhere, if only to make the code easier to read. This might just be a flat text file for the script, for example, where you can just look up "story_intro" and get the text starting "The Story: ..." back without it being embedded. It might be an interesting exercise to look at writing some code to auto format/decorate that text e.g. with your hashes down the sides for a specified console width.

2. I would prefer to use a single Console.WriteLine with the string split over multiple lines. If you had the auto-formatter that I mentioned, then you could just do something like Console.WriteLine(Resources.GetFormattedString("intro_story")). Other alternatives would be to use a verbatim string literal (prefix with @) or just concatenate them together with +. (I'm sure the compiler is smart enough to do these concatenations at compile time if the strings are known.)

3. There's quite a lot of duplication of structure (e.g. *UserDMG, *Damage, *Ability) and code (e.g. the big switch statement) - this would be better refactored into various classes and functions. This will make your code easier to read, as well as much easier to modify. Things seem a bit confusing, e.g. greenscale.greenscaleAttackPower. Why isn't this just greenscale.attackPower?

4. What is the purpose of the userInformation abstract class? (Why is it abstract?)

5. I find a naming convention that distinguishes types and variables (e.g. MyType myTypeInstance) easier to read. Personal preference, though!

Hi,
the first obviouse mistake, without reading one line of code, is that it's just one file. This way it is almost impossible to get the structure if you haven't coded it yourself and even you will probably get problems if you look at it after one month not working on it.

It should be possible to find a way to seperate those over 2000 lines of code into multiple files. Also it would be nice if you would provide a runnable version, so that someone can run the code he is looking at and actually see what it is supposed to do.

Anyway, from what I've read so far there are no errors in what you are coding, it's just not "the best" way to do it. You should have a look into functions, and, if you want to be fancy and push your game to the next level, into state machines as well.
I think this will teach you the basics pretty well:
http://www.programmi...org/en/fsm.html
I hope this helps you!