Migration from StrikePractice

Import arenas, kits, gates, and rollback data from StrikePractice or ShyamStrikeCore into ShyamDuels.

Before You Migrate

Back up your StrikePractice plugin folder and ShyamDuels plugins/ShyamDuels/ folder.
Install ShyamDuels on a test server first if possible.
Ensure FAWE is installed and arena worlds are accessible.
Stop the server or ensure no players are in active matches during import.

Migration Command

/shyamduels migrate strikepractice

Permission: shyamduels.admin. The migrator reads its source from plugins/ShyamDuels/migrator/StrikePractice/ (drop your StrikePractice kits.yml, arenas.yml, and config.yml there), or falls back to an installed StrikePractice plugin's own data folder. ShyamStrikeCore's door-animation.yml is read from plugins/ShyamDuels/migrator/ShyamStrikeCore/.

What Gets Imported

Data	Details
Kits	Inventory, armor, effects, icons, build whitelists, match-start potion flags.
Arenas	Corners, spawns, center, build mode, FFA flag, linked kits, world name.
Gates	Complex door gate regions copied into `data/complex-door-data/`.
Schematics	Re-saved per arena via FAWE (`FaweUtils.saveSchematic(arena)`) - not a raw file copy.
FFA config	`ffa-reset-delay` (minutes) × 60 → `ffa.reset-interval-seconds`; `ffa-countdown` 0 → `ffa.skip-countdown: true`, else `ffa.countdown-seconds: [n..1]`; FFA kit names inferred by stripping a trailing `ffa`; `build=true` with empty whitelist → `OAK_PLANKS`.
Gate sources	Tri-path: bundled `complex-door-data` → live folder → `data/`; worlds must contain `level.dat` (Multiverse `worlds` searched). Gate/door keys: `door-animation.enabled/animation_ticks/fence_material/delay_seconds/gate.*`.
GUI order	Kit/arena menu order written to `data/order.yml`.

After Migration

Run /arena list and /kit list to verify imports.
Run /shyamduels gate list if you used StrikePractice gates.
Check build mode pairs: set matching /arena build and /kit build values (Build Mode).
Teleport to each arena and confirm corners/spawns align with the physical build.
Run a test queue match and FFA join on imported maps.
Reload configs if you edited YAML manually: use the matching /shyamduels reload-* command (e.g. reload-config, reload-gui, reload-messages).

Arena cloning

If you enable arenas.cloning after migration, build templates only in the base Arenas world, not in clone worlds. See Arena Cloning.

Manual Cleanup

The migrator logs warnings for skipped or partial imports. Common follow-up tasks:

Re-save arena corners if schematic paths differ between plugins.
Re-link kits with /arena addkit if a kit name changed during import.
Reconfigure FFA display names/icons with /arena setdisplayname and /arena seticon.
Verify gate eject points with a test duel (Gate Setup).