Unfortunately whatever people say, vBulletin is not designed (source-code wise) to expand functionality. If this were the case you'd find vBulletin would be designed around classes with each feature of vB and it's sub-features and behaviours represented by objects. It would be great to see this one day - sort of like how PHP nowadays has class libraries such as PEAR and the new template engine that i've forgot the name of