This is something I need to be careful with now, as multi editing the database can cause conflicts!
...I'll need to code "Locking" events to some functions to make sure only one thread has access at a time (ManualResetEvents).
The obvious benefit of course, is multistage commands. (/Someadvancedfunction... /ok.)
It's necessary for the advancement of development, so it's like swallowing a vile of poison to boost your immune system, in a way.
Coding primite database functions now. going with the approach "/GROUP.*.ADD etc. syntax. These commands won't be used frequently enough to warrant short names, and it keeps commands clean. For example. "/GROUP.YSRAAF.ADD NewUser AtRank" is better then "/GROUP YSRAAF ADDUSER NewUser AtRank" It is easier to distinguish command to parameters.

Back to work on that.
On another note, I'm much more frequently on teamspeak now, drop in and say hi! ys.ysfhq.com