Quote:
Originally Posted by
Woo482

I was just thinking about that while finishing off implementing vessel -> vessel transfers. The best way I can think is to have an oMMU vessel interface exposing functions to be called when events happen in the core - allowing custom behaviors on events, denying ingress when a docking port is closed etc. Something along the lines of this (excuse the pseudocode):
Code:
class IMMUVessel{
public:
bool OnTryTransferCrew(const oMMU &otherVessel, const oMMUCrew &crewMember,int dockingPortID = 0) = 0;
bool OnTryCrewEnter(const oMMUCrew &crewMember, int airlockID = 1) = 0;
}
Playing around with this some more I think having a proper event system will be far more robust, and allow for add-ons that need to hook into vessels (e.g., XRRR) to function more cleanly; the structure I'm thinking of can be seen in the docs -
http://files.woo482.co.uk/oMMU/html/..._1o_m_m_u.html If anyone has any feedback I'm open to it, but I think this is the best way to implement it. I think this (after too many changes

) can be considered the final API, while you're in there find the unannounced scope creep