Team Ping (with Sable structures compat)

Free use in modpacks is permitted.

Point at something. Press Y. Your team sees it.

That is the whole mod.

The marker appears where you were looking, with your name on it and how far away it is.
If it is off to the side or behind you, an arrow at the edge of the screen points at it.
After twenty seconds it fades by itself.

Nothing is written in chat. You get the marker, a short sound, and one line above the
hotbar. Chat stays chat.

I made this for playing on airships, where shouting coordinates over voice stops working
and “look over there” means nothing when there is three chunks away.

It knows what you are pointing at

You press the same key every time. The mod works out the rest.

• Ore — the marker names it, so your mates see Ancient Debris, not just a dot.
• A teammate — a blue Ally marker with their name on it.
• Anyone else — a red Enemy marker.
• A Create Aeronautics ship — a Vessel marker on the hull, named after the ship.
• Anything else — a plain marker. Blocks, the ground, a cloud, the sky.

Shift + Y marks danger instead. Red, and it sounds like it.

Waypoints that stay

Ctrl + Y leaves a waypoint instead of a marker. Those do not fade.

They are kept on the server, so they survive a restart, and your team sees them as well as
you. Someone who joins the team next week still sees the ones you placed today. Eight per
player, and Ctrl + Shift + Y opens the list.

Keys

All rebindable. Y is a popular key — if nothing happens, look at the controls screen
first. Do not like holding modifiers? There are separate keys for danger, waypoint and
take-down; they come unbound, bind them wherever you like.

What you need

NeoForge for 1.21.1, and nothing else. No Architectury, no Fabric API, no config
library to install alongside.

If you happen to have any of these, the mod picks them up on its own:

Both team systems count at the same time, because packs often hand out teams twice — a
party and a scoreboard team — and your marker should reach your mates either way.

Someone without the mod can still join a server that has it, and the other way round.
Tested inside a 165-mod pack, alongside Create, Sodium, Sinytra Connector and friends.

Settings

Two ordinary JSON files in config/. Ignore them both if the defaults suit you.

Yours: marker size, drawing through walls, edge arrows, sound volume, distance labels,
map markers on or off.

The server’s: how far you can mark (256 blocks), how often (once a second), how many
waypoints one player may keep (8), and which team system to trust.

For pack and mod authors

Use it in your pack, no permission needed, no credit required.

There is a small API in dev.teamping.api if you want to draw markers yourself — on your
own map, HUD or anywhere else. You do not have to filter by team; markers from other teams
never reach the client in the first place. The mod’s own map support goes through that
same API, so it is not a second-class path.

Licence and credits

MIT. Do whatever you like with it — use it, change it, ship it in a pack, take pieces
for your own mod. The only thing asked in return is that my name stays in the licence file.

Author: Argorice. Source and issues: https://github.com/Argorice/TeamPing

Thanks to the authors of XaeroPlus,
MapLink and
ping-to-map-xaeros, whose mods I read
while working out how to talk to Xaero’s maps, and to
sable-companion for a compatibility API
that made ship markers a short job instead of a long one. No code was copied from any of
them.

Available in English and Russian.