Select/confirm soundset needs punctuation.
Bio: Could use a bit more fleshing out, and misspells Candlekeep.
APPEND ~pdialog.2da~ // TOB append
~CMNINAF CMNINAFP CMNINAFJ *** *** *** *** ***~
This isn't good, it means she doesn't have any TOB DLG files. Better fix it.
A general proofreading pass would be good. There are a lot of places where punctuation is lacking.
" Look at the sunset <CHARNAME> beautiful is it not?" , for instance.
"Look at the sunset, <CHARNAME>. Beautiful, is it not?"
In the one-day edition you have a LOT of dialogues that have just one PC reply, or one "good" PC reply and one "screw you" PC reply. This, of course, isn't necessarily surprising for a one-day project but really needs to be improved for a proper, full NPC release. In general I feel strongly that there should NEVER be only one PC option unless, say, the NPC is going to interrupt the PC regardless of what they say, and that you should try to offer at least three options whenever possible.
~Ninafer you appear to be a valiant and noble person.~ Aside from needing a touch of punctuation, you want to be REAL careful about BioNPCs declaring your NPC to be an exemplar right away. This is their first conversation together. And the conversation opens with Mazzy bookending very short comments around a monologue by Nina. It should be more give-and-take.
The LG Anomen banter... needs to be imploded and started anew. Anomen's way too over-the-top and the punchline isn't very punchy.
Keldorn banter has a similar issue to the Mazzy: He opens with a "gosh, you're wonderful" and it turns into a mutual admiration fest. More groundwork would be good.
Minsc isn't quite the type to say " Minsc ain't got time to bleed."
~This makes me happy <CHARNAME> (kiss the player on the cheek).~ IF ~~ THEN EXIT
Action-text in this style is typically done as second-person narrative.
~This makes me happy, <CHARNAME>. (Ninafer kisses you on the cheek).~