MBedwars

ReplayCore includes the MBedwars adapter on modern Paper, Purpur and Folia and on the Spigot or Paper 1.8.8 legacy recorder. The detector accepts an enabled MBedwars or MBedWars plugin reporting version 1.0 or newer. The adapter starts only when it also finds recognised Bukkit event classes. This version gate does not certify every MBedwars release.

Modern recording needs the official PacketEvents plugin, version 2.13.0 or newer, installed beside ReplayCore. The 1.8.8 legacy recorder does not need PacketEvents. The adapter marks arena start and end, bed breaks and final kills when the corresponding events are available and recording is active.

Install and enable MBedwars and ReplayCore on the same server, then restart. Check the server log for 'ReplayCore mbedwars adapter activated using ... event binding(s).' An installed plugin alone does not prove that ReplayCore connected to its events. If the log says the integration is inactive, read its reason: absent or disabled plugin, old version, or no recognised event classes.

Run /replaycore status and confirm that recording is active. On modern servers, a missing, old or unready PacketEvents install stops recording even if the MBedwars adapter connected. Play a match, then check a completed replay for its markers. An active adapter alone does not prove that an event fired or reached the recording.

Markers do not automatically make one archive per match. Set recording.rotation.enabled: true and recording.rotation.mode: match to cut at match boundaries. On Folia, also set recording.rotation.folia-regionised: true; without it, rotation stays off and the archive finalises on shutdown. In the default threshold mode, match events add markers but do not cut a per-match archive.