I like rogue like games and this together with researching that which you encounter is also something I like.
However there are still some bugs even with that mod (assuming I am correctly using it).
So currently I have the suggestion of showing a list while in game which mods are currently loaded into the game and active/inactive.
The crashes I encountered(bugs) occur when I scry someone with the anonimity curse and another one seems to occur when senses are shared and stuff happens (A guess of mine is that the pre-emptive procs to a characters turn create a loop and thus crashes.(Only a guess got no proof, it's only an assumption.))
I like the game.
Another way you could change the player character's interaction with the girls is by giving him traits which can also be obtained and changed by your actions and events.
To other players, crashes aren't really that bad cause it's a roguelike a floor is randomly generated everytime, so when you continue after a crash you just start a new randomly generated floor.
I know that there is/was a bug with Anonymity that I have fixed in the next version, but I don't know anything about a Shared Senses bug. I'm currently putting together an update for (probably) tomorrow though, so even if you can possibly get back to me with any more details to look at, a fix for it probably won't get into the next version.
I can probably throw in a button on the options menu to popup a list of currently loaded mods though, I think that should be quick and easy enough.
Well the thing is the moment shared senses is active something is triggered that causes the crash and I don't really know what as at that point there are to many variables to track from what I remember going on, so I can only try and give more details.
It might also interact with the anonimity curse now that I think about it, I believe al 3 crashes I had with shared senses also involved the one with the anonimity curse but while the first bug could be triggered by scrying one with the anonimty curse perhaps this second variant triggered the same bug but with an event happening while under shared senses.
If so then my current run can't really be used as a test case.