Cosmetics and text

Translations, textmojis, custom messages, chat formats, particles, effects and sounds.

Textmojis #

Textmojis (/manage/textmojis, permission textmojis.manage). Staff add, edit and delete words that players can swap for a text face in chat. shrug → ¯\_(ツ)_/¯ is there from the start.

  • What counts as a match: a whole word, inside a message or on its own, with a space or the edge of the message on both sides. Capitals don't matter. shrug and Shrug match; shrugged and shrug. don't.
  • /shrug always works, whatever the player's settings. Typed as a command, it sends the rest of the line as a chat message (/shrug oh well becomes ¯\_(ツ)_/¯ oh well). Inside a chat message, /shrug is swapped too.
  • Plain shrug is only swapped for players who turn on Auto-replace textmojis (portal Settings, or /settings in-game). It's off by default, so nobody's normal sentences change without asking.
  • Commands win: a global command, or any other server command with the same name, stays that command. Plain-word swapping still works for that word.
  • Alongside chat: swaps happen after the mute check and the chat filter, and the message log keeps what the player typed. /shrug goes through the normal chat path, so mutes, the filter and the chat format apply to it too. Staff with network.chatfilter.bypass still get textmojis.
  • Survival dialogues: a typed answer to a dialogue is never swapped, so a word stays what the dialogue expects.
  • Servers fetch GET /server/textmojis?version=… every 60 seconds (chat_filter_interval) and swap locally, with no API call per message. A change on the panel also tells servers to fetch straight away (textmoji_refresh). The last list is saved, so textmojis keep working after a restart or while the panel is down.

Chat format spacing #

Chat format spacing. {rank}, {badge}, {level} and {crew} have no spaces of their own (e.g. &7[&b12&7]): the format puts the spaces in, like the default {rank} {badge} {level} {name}&8: &f{message}. When a part is empty, the spaces it leaves become one and none are left at the start, so [Admin] Bob never turns into Bob or [Admin] Bob. Rank prefixes are saved without spaces too. Formats and prefixes saved before this were converted so chat looks the same. {rank} is the chat prefix of the player's main rank (Players → Ranks); no permissions plugin is needed.

Name tags and the tab list #

Name tags and the tab list. Each player's rank, badge, level and crew show above their head and on their line in the tab list, on every server (Pit, Survival, lobby). network/Cosmetics/NameTags.sk does it. The look is set with game rules (Servers → Groups → edit, and each server can override them), so Pit and Survival can differ:

  • Rank, badge and level above heads (on) and Name tag format ({rank} {name} {level} {crew}).
  • Rank, badge and level in the tab list (on) and Tab list format ({rank} {badge} {name} {level} {crew}).
  • Sort the tab list by rank (on): highest rank weight first (Players → Ranks), then by name.

The placeholders are the chat format's ({rank}, {badge}, {level}, {crew}, {premium}, {name}), plus {lvl} for the level number alone (e.g. {rank} {name} &7Lv.{lvl}). {level} is the level of the game mode the player is on: Pit's level on Pit, the Survival level on Survival, and nothing in the lobby. As in chat, the space next to an empty part is dropped. The name takes its rank colour, or gold with Premium. A format without {name} has the name added at the end.

  • Above the head the game only shows a scoreboard team's prefix and suffix around the name, so each player gets a team of their own: what's before {name} is the prefix and the rest is the suffix. Pit runs 1.8, which allows 16 characters on each side, counting colour codes. Parts are left out on the side that's too long, in this order: badge, crew, Premium, level. As a last resort the text is cut. Modern servers allow 64.
  • Scoreboards. Players read teams from the scoreboard they're on, and the sidebar gives each player a scoreboard of their own (network/Players/Sidebar.sk, and SkBee's on Pit). So each player's team is put on the main scoreboard and on every online player's own one. A new sidebar board gets every team straight away, and a check every 2 seconds catches boards made by anything else. Without this, name tags would vanish as soon as someone got a sidebar.
  • Updates. A team is changed only when what it shows changes. That happens on join; on a rank change, a badge change, a save loading or a staff edit (Network_RefreshName); on a Pit kill or level up; and every 10 seconds for crews, Survival levels and new formats from the panel. Team names start with nt and the rank order, which is how the tab list is sorted. The rank weight is sent with the player's rank (weight, stored as {network::rankweight::<uuid>}).
  • Hidden players. The network has no vanish or disguise of its own. A player hidden with Bukkit's hidePlayer (as vanish plugins do) is already kept out of the tab list and out of sight by the game.

Chat colours #

Chat colours. The colour of a player's chat messages, picked in /settings (Chat colour menu) or on the portal (Settings → Chat colour). Grey is everyone's; staff choose which colours exist and which ranks come with each (Settings → Chat colours, black is off by default). Others are unlocked by a store package (Unlock a chat colour, taken back on refunds or when it ends) or given by staff, for good or for some days (player page → Settings and pets). The colour goes in front of {message} in the chat format on every server, Pit included.

Translations #

Translations (/manage/translations, permission translations.manage). The search box on that page finds any text across every section, by English, translation or key. Choose the languages, then type the words for each: Item Shop and loadout items, preset loadouts, pets, badges, menu text, your own keys, pet, job, Tag skill, server and event descriptions, job tasks, every game message and menu in the scripts (the Game: sections) and what the panel tells players (the Panel replies: sections). Pick a section at a time; "Show only what's left to translate" hides what's done. A {word} is a value such as a name or price and can go anywhere in the sentence; saving warns if one was lost. The colour and tag a line starts with are added for you. Anything without a translation shows in English. Servers download changes within a minute (Translations.sk), and the Item Shop, pets, loadouts and lobby menus show each player's language. Players choose theirs with /language or in portal Settings. The old Japanese shop text was carried over. In your own scripts: Tr(player, "custom.your.key", "English"). For script messages with values: send Trf({_p}, "msg.area.name", "&aYou paid {amount}.", "amount=%{_amount}%") to {_p}, then run php artisan translations:scan to list new msg. keys in config/game_text.php (a test fails if it's out of date). New panel messages go in config/panel_text.php as templates; FriendService::notify and the message of server API replies about a player are matched against them. Change the English wording (link at the top of Translations, /manage/translations/english, same permission): search for an in-game message (the msg. keys) and type your own English instead of the scripts' text, e.g. the mana bar. It's saved as an English row, which servers use before the built-in text, and other languages fall back to it where they have no translation. Clearing a box, or typing the original back, goes back to the original. Saving warns if a {value} was lost, and changes are in the audit log (translations.english). Not translated: staff-only tools (/network, /networkupdate, survival admin commands), and text everyone shares at once (Tag's boss bar, leaderboard holograms, pet name tags, health bars).

Finding and filling in translations #

Finding and filling in translations (same page). The big Translation group box picks what to translate and shows how many are left in each. Show all untranslated lists what's left from every group at once, 300 at a time. Auto-translate what's showing fills in untranslated text with the Google Cloud Translation API and saves it, up to 300 texts a press. It's off until someone with settings.manage adds an API key under Settings → Auto translate (stored encrypted). Google bills by the character, the text is sent to Google only when the button is pressed, and {values} and & colour codes are kept out of the translation. A result that loses a {value} is left untranslated.

Anything Google translated shows a red Auto Translated label, so a bad translation is easy to find. The label goes when someone changes the text, or ticks "It's right, remove the mark" and saves. The Filter box next to the group box shows everything, only untranslated, or only Auto Translated, for one group or for all groups.

Custom messages #

Custom messages (Cosmetics and text → Custom messages, /manage/custom-messages, permission custommessages.manage; network/Chat/CustomMessages.sk). Staff make join, quit and death messages for players to choose. Each has a type, which can't change afterwards, a name players see when choosing, and one line of text with & colours and the values {player}, {rank} (their rank prefix) and {server}. A death message can also have a second line for when another player made the kill, which can use {killer}; deaths with no player killer (falls, mobs, the void) use the first line. A value that doesn't exist is refused when saving. The page shows each message in colour and how many players use it.

Everyone starts on Default: the server's normal message, which is the game's own, or survival's [+] name line. Nothing changes for a player until they choose. They choose or go back to Default in-game with /custommessages (also in the /settings menu) or under Settings on the portal. The choice is saved on the panel, so it shows in both places, is sent to their server straight away if they're online, and comes with their profile on every other server they join. Servers keep the last choice and the list, so messages keep working while the panel is down, but changing one needs the panel.

New and edited messages reach every server within about 15 seconds. They are network-wide, and open to everyone: there is no rank or store lock. Deleting a message puts its players back on Default. The Join and leave messages and Death messages rules still win: where one is off, nobody's message of that kind shows. Message names can be translated (the Custom messages section under Translations), but the line in chat is one shared text, so it shows as staff wrote it for everyone. Script editor projects can read a player's choice with Net_CustomMessage and Net_CustomMessageText. This needs both the core and network folders updated; until core is, servers don't get the list and everyone stays on Default.

Particle effects #

Staff build particle effects on the panel (Cosmetics and text → Particle effects, permission particles.manage) and every server can play them by their key. Cosmetics, skills and events attach an effect by its key.

  • Building one. An effect is a stack of up to 8 layers. Each layer is a shape (ring, filled circle, helix, spiral, sphere, dome, line, burst, wings, star, heart, or a cloud on one spot) drawn with one particle, with its colour and dust size, radius, height, points, turns and strands, an offset and tilt, spin and rise speed, particle speed and spread, and when it starts, how long it lasts and how often it's drawn. Animations: show the whole shape, draw it point by point, a moving trail, grow outwards or shrink in. At most 600 points across all layers.
  • Presets. "Start from a preset" on the edit page (and "Start from the Beam preset" on the list, /manage/particles/create?preset=beam) swaps the layers for a ready-made effect to change. Beam is the combat scripts' beam step as layers: a bright end rod core drawn forward 10 blocks from eye height, a coloured dust glow, a spark spiral wound round it and sparks scattering along it as it fades; it turns with the player. Presets live in ParticleEffect::PRESETS (presetLayers($key) fills in every field); add more there.
  • Live preview. The edit page shows the effect in 3D next to a player figure, animated the way it plays in-game (20 ticks a second). Drag to turn, scroll to zoom, tick "Walk in a circle" to see it follow and turn with a moving player. It also shows how long the effect lasts, the most particles it draws in one tick, and layers that don't show on 1.8.
  • Options. "Turn with the player" keeps forward the way the player or mob faces (wings stay on the back). "Repeat until stopped" is for auras. Off: servers don't get it.
  • Starter effects (all on): halo, flame_helix, angel_wings, kill_burst, heart_pop, summon_circle, frost_nova, vortex, void_zone (the Void Zone class skill's dark circle; loops until the skill stops it).
  • In-game. network/Cosmetics/Particles.sk downloads the effects every minute (GET /api/v1/server/particles?version=, only sent when they changed) and keeps the last copy for restarts. Scripts use Particles_Play(key, location) and Particles_PlayOn(key, entity) (both return an id, "" if not played), Particles_Stop(id), Particles_StopOn(entity) and Particles_Has(key). An effect on a player or mob follows them and stops when they die or leave.
  • Server load. The panel works out every point, so servers only turn and move them. Each server draws at most particles_per_tick particles a tick in total (in config-*.sk: 250 on Pit, 400 on lobby and survival; the rest wait a frame) and plays at most 48 effects at once.
  • Versions. Particles are modern Paper names. On 1.8 (Pit) each maps to its old name (coloured dust keeps its colour); the few with no 1.8 match (totem, soul, glow, cherry leaves, sculk soul) are skipped there.
  • Testing. /pfx play <key> plays it on you, /pfx here <key> where you stand, /pfx stop, /pfx list, /pfx reload (alias /particlefx, permission network.particles).

Mention sounds #

When someone's name is in a chat message (any case), they hear a sound (network/Cosmetics/Sounds.sk, called from the chat handler in network/Panel/Events.sk after mutes and the chat filter, so blocked messages don't ping anyone). Staff add mention sounds next to kill and death sounds (Cosmetics and text → Sounds), free or Premium-only, and choose the default everyone hears until they pick their own (or none). Two come ready: Ping (free, the default) and Bell (Premium). Players pick theirs in /sounds (the bottom section; "The normal sound" goes back to the default) or in their portal settings, and turn it off with the setting "Sound when someone says my name".

Kill and death effects #

Particle effects players unlock for their kills and deaths, and back effects they wear, owned network-wide (Cosmetics and text → Kill and death effects, permission kill_effects.manage).

  • Offering one. Pick a particle effect (ones that repeat until stopped aren't allowed, they'd never end), whether it's a kill or death effect, and how players get it: free, bought with global coins (a price), Player Premium only (usable while they have Premium), a store package (buying that package gives it for good, a refund takes it back) or given by staff. Staff-only effects are listed only to players who have them; store ones while the package is on sale.
  • Back effects. A third kind: a repeating effect that stays on the player's back the whole time they play, turning with them (pick a particle effect with "Repeat until stopped" and "Turn with the player"; kill and death effects can't use repeating ones, back effects must). It comes back within 2 seconds after a death or world change, and hides in spectator mode. Two starters, both free: Clock (upright) (clock_back): a clock face on the back with a red second mark that ticks round the hours once a second, and Clock (flat) (clock_flat): a clock lying flat behind the player whose minute hand sweeps round every 12 seconds.
  • Mob kills. A tick box on the page makes kill effects also play when a player kills a mob (off by default). Servers check it every minute.
  • Players pick one kill, one death and one back effect (or none, the default) in /effects (aliases /killeffect, /deatheffect) or on the portal (Play → Kill and death effects), which plays each one in 3D on Preview. In /effects, click to use, click twice to buy, right click to see it played on you.
  • In-game (network/Cosmetics/KillEffects.sk, every server): when a player kills another player, the killer's kill effect plays where the victim fell and the victim's death effect plays there too. Effects play through network/Cosmetics/Particles.sk, so 1.8 (Pit) skips layers with no 1.8 particle. A Premium pick stops the moment Premium ends; a pick that's turned off or taken shows nothing.
  • Staff give or take effects on a player's page (Settings tab). Every change is in the audit log.
  • Starters (on): back effects Clock (upright) and Clock (flat) (free); kill effects Blood burst (kill_burst, free), Frost nova (frost_nova, 2,500 coins), Heartbreaker (heart_pop, Premium); death effects Smoke and flame (flame_helix, 1,500 coins), Summoning circle (summon_circle, Premium).
  • API: POST /api/v1/server/kill-effects (config, list, buy, select). Picks come with the login profile (kill_effects: kill, death, back and their _premium flags) and with profile updates when they change.

Kill and death sounds #

Game > Sounds (sounds.manage) lists the sounds players can pick, each with its modern and 1.8 name, volume, pitch, and Premium only. The examples start off, and nobody has a sound until they pick one, in /sounds or their portal settings (network/Cosmetics/Sounds.sk).