I've posted a few graphics of some of the new features that I've been working on for the upcoming v1.0.3. Take a look.
Here's the new State Explorer: http://screencast.com/t/ldGOojlyDQ
You will be able to open a State Explorer on any State Editor and it will show a tree of all the nested states. You can hide/display each level and open up a menu for each item. See: http://screencast.com/t/cUtMS7sN
From there you can open up various editors relating to the State.
For the next feature I put in a new error reporting system for the code generation which will now check all LSL code in the model at code generation time for syntax errors, undeclared variables (new!) and validate LSL Actions. See: http://screencast.com/t/0IN2Uc8hVuy
This should save being surprised in SL with a syntax error after copying the generated code. From the error dialog you can open up the containing State Editor for the component as well as the actual properties editor.
This shows the modified code windows and how errors will be shown after being selected from the error list dialog. See: http://screencast.com/t/gx7PN2OSQy
Note that code lines are now numbered!
Direct Access to Event Arguments
Lastly (for now) is the feature that will allow you to directly access event arguments from the transitions leaving a Choice Point (if that Choice Point only has a single transition into it). See: http://screencast.com/t/mKtcPk4iN4c5
The graphic is from the door script from one of the tutorial videos. Note that in the Done transition you can now directly reference the data argument of the dataserver event of the transition leading into the Choice Point. I think that will remove alot of confusion for new users to MOAB who would naturally expect to access the arguments in this situation directly.
I'll post more info on additional features as they continue to be developed for v1.0.3.