Getting started

Installation

Downloading the plugin, ExyliaLib and PacketEvents, the files the first start writes, and how updates arrive.

Downloading

ExyliaKillCam is free. Every release is published on GitHub with the jar ExyliaKillCam.jar, which keeps the same name on every release.

Before you start

Plugin	What for
`ExyliaLib`	Required. The recording, the stage, the camera, the hotbar button, player settings, configuration and teleports.
`PacketEvents`	Required to show a killcam: the bodies in it are packets. Without it the plugin starts, but no killcam is ever shown.
`ExyliaKillEffect` 1.9.0+	Optional. The killer's kill effect plays again at the end of the killcam.

ExyliaLib is listed as soft, and is not downloaded

plugin.yml names ExyliaLib under softdepend on purpose, so the plugin can still start without it and say what is wrong. When ExyliaLib is missing, the console names the version it needs and where to download it (Modrinth or its GitHub releases), and ExyliaKillCam stays disabled until it is installed and the server restarts. Nothing is downloaded for you. When an ExyliaLib jar is already in plugins/ but failed to load, the console asks you to fix the library's own errors first.

Without PacketEvents

With ExyliaLib but no PacketEvents, deaths are still noticed but nobody is ever taken into a killcam: players in AUTO simply respawn, and /killcam answers "Killcams cannot be shown on this server. PacketEvents is missing." Install it next to ExyliaLib as the library's installation page explains.

Installing

Drop in the jars

Copy ExyliaKillCam.jar into plugins/, next to ExyliaLib and PacketEvents.

Start the server

The plugin writes its files and starts recording at once. There is nothing to set up.

Die once

See First steps.

Generated files

All of them live in plugins/ExyliaKillCam/.

File	Contents
`config.yml`	Language, the mode players start with, the length and shot of a killcam, which deaths get one, the recording and the kill effect. See Configuration.
`lang/<code>/messages.yml`	Every line the plugin sends: the title, the line above the hotbar, the summary, the offer and the refusals.
`lang/<code>/hotbar.yml`	The skip button shown on the hotbar while watching.

<code> is the language the plugin runs in: en, es, pt, fr, ru or tr, or ExyliaLib's own language while config.yml says default. Missing files are written again and new keys are added on every start; a changed default in hotbar.yml waits in /exylialib updates instead of overwriting your edit.

The plugin has no database of its own. The mode each player chose is kept by ExyliaLib's player settings, and recordings live only in memory.

Updating

ExyliaLib watches this plugin's GitHub releases. The plugin names its repository in plugin.yml (exylia-updates: Exylia-Plugins/ExyliaKillCam) and the oldest library it runs on (exylia-lib).

A new release is announced in the console and to admins. Nothing is downloaded on its own: /exylialib plugins downloads it, and it is applied on the next restart.
A new major version is only announced.
A release that needs a newer ExyliaLib waits until the library has updated.
plugin-updates in plugins/ExyliaLib/config.yml turns it off or tunes it.

To update by hand, replace the jar and restart. config.yml, messages.yml and hotbar.yml keep your edits.

Something missing on this page? Tell us on Discord