Viscord - Discord/Fluxer Server to Server

5.2.1 — loader-boundary fix

Fixes the class of failure that was killing modded Forge servers. Discord work no longer runs on the JDK common ForkJoinPool, so Forge stops logging Could not find parent network/vonix/viscord/shadow/javacord/api/entity/message/MessageBuilderBase ... in classloader jdk.internal.loader.ClassLoaders$AppClassLoader / An error occurred building event handler on every start.

• Delayed Discord work now runs on Viscord's own executor, whose threads carry the game class loader, and BotClient.sendEmbed pins the context class loader around the Javacord send.
• Components V2 log noise is now suppressed by logger level (Configurator.setLevel(String, Level)) instead of a log4j-core AbstractFilter subclass. A mod-loader class extending log4j-core links Filter's MessageSupplier overloads outside the MC-BOOTSTRAP module layer — the shape of the LinkageError: loader constraint violation ... MessageSupplier raised from EventBus.handleException, which converts any listener exception into a server crash.
• Shaded jars no longer contain META-INF/services/org.apache.logging.log4j.*; mergeServiceFiles() used to publish Javacord's PropertySource descriptor pointing at a relocated mod class.

Server-side only. No config keys, commands, or linked-account data changed.

Full notes: https://github.com/Vonix-Network/Viscord-Architectury/releases/tag/v5.2.1