Rain and Shine, October '19 update

Alright, this one is a huge update; not only has the intro system been added to and the stats system finally put into place but prompts and everything else have been put in as well.  Unfortunately with a funeral on Tuesday and the pending problems on Thursday and Friday I had all of two additional days to work on it, which wasn't too much I'm afraid.

We've also got the first portal to the corrupted storyline, including the introduction of your new form and all that good stuff.  As a word of warning though I was writing all the way up to the time that I posted this, so there is probably going to be bugs.  With the next update happening on the 29th I'm going to add in the new stuff (bad ends and survivor/corrupter missions) and then just playtest the whole thing, as well as do a typo buster on a few more areas.

Version 1.1.4:

- Implemented Corruption pathing

- Added Species descriptions and stat modifiers

- Finished questionnaire to implement to actually affect stats

- Created separate shelter modules for the bedroom, showers, and kitchen

 -Added prompts to intro so that those that want to see what their choices entail can see them now 

-Added more build options to character including eye color, skin/fur/scale color, hair color, height, and build

-Fixed the majority of spelling errors in the intro

-Finished gazebo, now able to enter into the corrupter pathway

-Finished inital corrupter shelter build, including mentor/first companion integration

-Included build options for male and female endowment choices in the NSFW section

-Built return to gazebo, potential recruitment of NPC Rhentin

-Built kitchen to display items that you got in the last mission

EDIT:  Fixed it so that entering outside doesn't lead you back to the start, however don't forget that it's not guarenteed you'll find the location to the gazebo.  At least initially you have to get the location from someone and there are a number of places in the game to glean it.

EDIT 2:  Certain paths to the gazebo (naturally the ones I didn't test) were still throwing off a False variable answer, that should be fixed now.  Since this is a significant run-time error it's been fixed, but if there any more edits needed they will be done for the next update.