SignalsLib

0.2.4-SNAPSHOT

Fixes events being dropped on BungeeCord and Velocity when their only listeners live on a sub-bus, and adds Signal.next, Signal.connectOn, connection-returning dispatcher registration and BukkitSignals.mainThread(). No breaking changes.

Fixed

• signals-bungeecord, signals-velocity: the bridges skipped an event while listenerCount() of its signal was 0. A listener that only lives on a sub-bus (geb().subBus(...), in the README) therefore never received the event, although it does on Bukkit. They now ask hasReceivers, which counts sub-buses.
• signals-bukkit: the Bukkit handler of a signal stays registered for good, and built and dispatched a value for every event even with no listener connected (every PlayerMoveEvent, for one). It now skips events nobody can receive, like the other two bridges.
• Javadoc: GebBridge.registerDispatcher now says that a bus keeps one dispatcher per event type and a new one replaces the old one, and unregisterDispatcher that only the same instance is removed. SignalBus.fire now says that GEB does not catch a listener's exception, so it reaches the caller. SignalBus(IBus) now says that buses sharing a GEB bus see each other's values. All three were checked against GEB 0.5.4.

Added

• Signal.next() and Signal.next(Predicate): a CompletableFuture that completes with the next (matching) value. The listener disconnects when the future completes or is cancelled; a throwing predicate fails the future instead of reaching the code that fires.
• Signal.connectOn(Executor, Consumer) and the ConnectionGroup variant: run a listener on an executor, to hop to a thread. A task queued before its connection was disconnected is skipped.
• SignalBus.hasReceivers(Class), SignalBus.hasReceivers(SignalKey) and Signal.hasReceivers(): whether firing could reach a listener, counting sub-buses. GebBridge.hasSubBuses() backs it.
• GebBridge.dispatcher(IEventDispatcher) and GebBridge.loadDispatchers(ClassLoader), each with a ConnectionGroup variant: register dispatchers and get a Connection that unregisters them. On the shared bus, dispatchers registered with registerDispatcher or loadAndRegisterDispatchers stay behind when the plugin that registered them reloads. loadDispatchers is all or nothing: a broken service file unregisters what was loaded.
• signals-bukkit: BukkitSignals.mainThread(), an Executor for the server's main thread, to use with connectOn for off-thread events such as players().chat(). Not for Folia.
• 24 new signals-core tests (72 in total, was 48): the exception contract of fire, hasReceivers (including a regression test for the sub-bus bug), next (value, predicate, cancel, failing predicate, concurrent fires), connectOn (order, skipped tasks, inline, group, null checks), dispatcher connections (replace, replaced dispatcher kept, rollback, group, null checks), sub-bus tracking and two buses on one GEB bus.

Changed

• GebBridge.loadAndRegisterDispatchers now delegates to loadDispatchers: same behaviour, except that a broken service file no longer leaves the dispatchers read before it registered.
• README: next, connectOn, mainThread, the dispatcher connections, a warning about clear() on a shared bus, and the sub-bus notes. The GEB Direct Use example now cleans up in onDisable.
• Version is now 0.2.4-SNAPSHOT.