FAQ

Is it free?

Yes. ExyliaKillCam is free and open source, under the GNU General Public License v3.0. Download it from GitHub releases; the source is in the same repository. There is no licence key and nothing to buy.

Why does the killcam not show exactly what I saw?

Because it is recorded on the server, and the server never knew what your screen showed. A client predicts its own movement and is corrected afterwards, so a player on a bad connection may have watched a hit land that the server decided had missed — or the other way round. The killcam shows the server's answer: where everybody really was and which hits really counted. Field of view, view bobbing and the camera tilt on taking damage were never on the server either, so they are not in a killcam.

That is the right answer for a killcam, even when it is not the popular one. See What is not in it on ExyliaLib's replays page.

A player died and got no killcam

Check, in order: that PacketEvents is installed; that they have exyliakillcam.use; that a player killed them (or a mob, with deaths.mobs on); that the world is not in deaths.disabled-worlds; that no duel, event or queue was holding them; that their mode is not OFF (ASK only offers it in chat); and that they respawned within a minute of the death. A player who had just joined, or a server that just started, may not have enough recorded yet.

Does it cost much memory?

The recording is ExyliaLib's black box, one for the whole server: a few seconds of frames around every player, about seconds-before plus three, never written anywhere until a death asks for them. Each death then keeps one recording, with its ground, per player — only the last one — until killcam.rewatch-minutes has passed (checked every minute) or the player leaves. Lower rewatch-minutes or recording.radius on a very busy server.

What happens when a player quits?

A player who leaves while watching is put back where they were before leaving, by ExyliaLib, so they log in where they respawned. Their kept death is dropped: /killcam after rejoining has nothing to show.

What happens on a reload?

/killcam reload reads the files again and reopens the recording with the new settings. Killcams being watched carry on, and deaths already kept can still be watched. The recording starts filling again, so a death in the first seconds after a reload may have a shorter clip, or none.

When the plugin stops — the server shuts down, or the plugin is disabled — everybody watching is put back where they were first.

Does it work on Folia?

Yes. Every step runs on the thread that owns the player or the place, and ExyliaLib's recording and stages work per region.

Does it change the real world?

No. The fight is laid down on ExyliaLib's temporary world, on a plot of its own, and the bodies are packets only the viewer sees. The place where the fight happened is never touched, and the fight goes on for everybody else while the victim watches.

The kill effect did not play at the end

It needs ExyliaKillEffect 1.9.0 or newer and kill-effects.replay on. Only the effect that really played on that death is shown, so a kill without one shows none — and a viewer whose ExyliaKillEffect particles are on NONE or SELF_ONLY sees none either.

Is there an API?

No public API, events or placeholders.

Where do I get help?

On the Exylia Discord: discord.exylia.net. Bug reports and feature requests are also welcome as issues on the GitHub repository.