Saxonberg Server API
    Preparing search index...

    Interface BidirectionalExitOptions

    Options for addBidirectionalExit. The shared door installs the SAME instance on both sides so opening from either side flips one state.

    opposite is inferred from NavigationApi.invertDirection(direction) for cardinal directions. For semantic labels (spherical zones, vessels) the caller MUST supply opposite explicitly — there is no canonical inverse for 'office' or 'portal'.

    interface BidirectionalExitOptions {
        blocked?: boolean;
        door?: default;
        hidden?: boolean;
        keepLiveDestination?: boolean;
        messageInBack?: string | null;
        messageInForward?: string | null;
        messageOutBack?: string | null;
        messageOutForward?: string | null;
        muffled?: boolean;
        noFollow?: boolean;
        opposite?: string;
    }
    Index

    Properties

    blocked? door? hidden? keepLiveDestination? messageInBack? messageInForward? messageOutBack? messageOutForward? muffled? noFollow? opposite?

    Properties

    blocked?: boolean
    door?: default
    hidden?: boolean
    keepLiveDestination?: boolean

    Hold BOTH sides' destinations as within-session live refs (Pattern B) rather than templatePath resolution. Required when the two endpoints are non-singleton runtime clones sharing a template path (Warren hub exits). See Exit's keepLiveDestination.

    messageInBack?: string | null
    messageInForward?: string | null
    messageOutBack?: string | null
    messageOutForward?: string | null
    muffled?: boolean
    noFollow?: boolean
    opposite?: string

    Settings

    Member Visibility

    On This Page

    Properties