Skip to content
Gjum edited this page Jul 8, 2017 · 5 revisions

Table of Contents

Introduction

JukeAlert provides an easy-to-use means by which one can record player activity within an 11 block radius.

Tutorial

Creating Snitches

To create a snitch reinforce a jukebox or a noteblock. This will create an active snitch block. Jukeboxes snitches will save logs and notify you whenever someone enters the 11 block radius of the snitch, whereas noteblock snitches only notify.

Recommendation: It is highly recommended to properly name your snitches with /janame to make your own life easier when trying to determine the general location of the snitch.

Access to a snitch can be controlled with Citadel groups. By reinforcing the snitch to a group with /ctr group group-name, any member and above on the group will receive snitch notifications.

Note: If you are receiving a snitch notification and are unsure what group that snitch is part of then use /jalookup x y z to find out.

Checking Snitches

Jukebox snitches keep a log of activity near them. If you're a member of the group that the snitch is reinforced to, you can check the log by walking within the radius of the snitch typing /jainfo. This will show the first page of snitch logs, (with the newest entries at the top). If you want to view older entries, censor locations, or filter the entries, /jainfo has optional parameters:

/jainfo [<page number> or 'next'] [censor] [action=<action type>] [player=<username>]

  • <page number> or next - these let you view older entries. You can either specify a specific page number (e.g. /jainfo 3 to view page 3) or use the keyword next (i.e. /jainfo next to view the next page).

  • censor - censor coordinates in the logs. For example, if an uncensored line is Player32 Block Break 54 [31, 3, 37], using /jainfo censor will display it as Player32 Block Break 54 [*** *** ***]. This is useful for posting evidence of crimes on forums.

  • action=<action type> - filter by action type. For example, /jainfo action=kill will only show entries where a player or animal has been killed. Note that action types with a space in them will need to be wrapped in double quotes, (e.g. /jainfo action="block break").

  • player=<username> - filter by player name. For example, /jainfo player=Raider337 will only return log entries for Raider337. Note that this is case insensitive and will also display partial matches, so you don't have to type out the full username, (e.g. /jainfo player=raider will return all entries for Raider337 as well as any other player with 'raider' in their name).

These parameters can be used together and in any order.

Type of Snitches

Name Functions Time before cull
Jukebox Notifies of entry and saves logs Two weeks
Noteblock Notifies of entry Four weeks

Note: Both snitch types have the same 11 block radius.

Cull Time

Snitches stop being active if a moderator or owner does not walk within the radius of the snitch after enough time has passed. Once a snitch reaches hours before cull, then it will stop being active on the next server restart if it isn't updated. To prevent a snitch being culled, a moderator or owner (anyone with LIST_SNITCHES permission) in the same group as the snitch must walk within the radius of the snitch. This resets the time before that snitch will be culled. This is also called refreshing or updating a snitch. Members cannot refresh or update a snitch.

Type /jalist [page-number] to see which snitches are close to being culled. This command requires moderator or owner rank in the citadel group. The list is sorted by lowest to highest cull time. This allows you to easily check which snitches need to be updated.

Lever Triggering

Jukebox Snitches can have additional functionality added to them such that they can cause nearby levers to trigger. This is not default snitch behavior and the owner or moderator of a snitch can opt-in a snitch by using the command /jaToggleLevers 1 and can opt it out (later) by using the command /jaToggleLevers 0 when in nearby proximty to their snitch. Once a snitch has been opted into lever triggering, levers that are on the blocks adjacent to the jukebox sides will be triggered by people not on the snitch group as follows:

Direction Trigger
North Player enters snitch radius or logs into snitch
South Player opens chest within snitch radius
East Player places block within snitch radius
West Player breaks block within snitch radius

When these events trigger, the associated lever will enable briefly and disable shortly thereafter. This is approximately 750ms but will vary directly depending on the amount of server lag. Levers that are already enabled due to user action will not flicker as a result of a juke alert lever toggle event, but said lever will disable in the same approximate 750ms.

Citadel Ranks and JukeAlert

As mentioned in the citadel rank section, different ranks on a group have different powers when it comes to a JukeAlert.

Owners and moderators can create, refresh, change the group the snitch is on, and see the snitches in the group with /jalist.

Members can use /jainfo and /jalookup to check the snitch and see what group it is part of and will receive snitch notifications. However, they can't refresh a snitch to keep it from being culled nor can they see the snitch on /jalist.

Owner can create snitches, add moderators


List of Commands

Name Command
Display JukeAlert Help /jahelp
Display first page of snitch logs in chat /jainfo
Display specified page of snitch logs in chat /jainfo [page-number]
Display snitches in chat /jalist
Display next page of snitches /jalist [page-number]
Name the snitch /janame []
Use the coordinates to look up the citadel group the snitch is on /jalookup [world]
Displays group ignore list /jamute
Add/remove group to/from ignore list until server restart /jamute [group-name]
Add/remove all groups to/from ignore until server restart /jamute [*]
Clear snitch logs in the snitch /jaclear
Opt in or opt out a snitch from the lever triggering functionality /jaToggleLevers 1 or 0

<> = mandatory [] = optional