I put a stop to writing, area and quest design until I got some lower level systems things done and troubleshot. It's still building the module, but doing the under the hood things that go on behind the scenes.
Hidden weapons: If you played Assassin's Creed you'll know what I mean. The player has instant access to a weapon that the npc's do not see, like the Assassin's Creed pc had the daggers that popped out.
In the first picture you can see the hidden weapon system in action. Our intrepid thief has picked up a hidden weapon, equipped and been caught pickpocketing. The weapon is visible to the player, but the npc simply does not "see" the weapon. Our player only takes the standard reputation penalty of -20, as if he was unarmed.
Then he picks up a spear, equips it, and tries again. Caught this time, the npc can "see" the weapon, and so thinks they are getting mugged. As a result, the player takes the -20 rep penalty for pickpocketing, and an extra -20 for using a weapon! What about dual wielding? The system catches that too. It doesn't identify two visible weapons as more threatening than one (I don't think it should), but if you have a hidden weapon in your main hand, and a visible one in the left, the npc sees the weapon in the left hand. So no tricking the system.
In addition to the custom hidden weaponry, some weapon types are always considered to be hidden, as they are designed to be hidden on the body for surprise use anyway, or unanticipated weapons. So darts and shuriken are "hidden", and unarmed and torches also qualify since they are unexpected.
The same weapon detection code is going to run when you talk to npc's. They will not be friendly if you're pointing a weapon they can see at them, in fact you will lose a few points of reputation with them, Crimmor is civilized!
The system relies on detecting substrings of weapon tags and item types, and comparing the substring with the predefined prefix for the tags for all hidden weaponry then comparing the weapon type for the weapon types that are "hideable by definition" like shuriken. So for me, the code detects if the tag begins "sh_hidden_", the remainder of the tag does not matter.
I had to get this code down and set, as substring detection forms the basis not only of weapon detection, but several other system things I'm putting in place such as clothing with hidden pockets.
I finally started opening up the toolset the other day after having it closed for the better part of two months. This work was done before I closed the toolset a while back. Right now I'm working on filling in the main plot. Since I had initially made Crimmor a smaller concept module I had to expand the plot.
Initially it was just a "find and get the item" plot, without explaining why you would want it. A fairly straightforward plot designed to drive something that was just a proof of the gameplay concepts. 
As an urban module, many of the traditional villains one might find in an adventure were out. No orc tribes, drow, dragons etc. No imposing temples of evil dominating the landscape either. With the player being an employee of the Shadow Thieves, I wanted to play up the intrigue that the Shadow Thieves are known for, but of course couldn't use a thieves guild as an enemy, since the Shadow Thieves already run things and you work for them.
Don't worry, I found some things. ;-) 
