The Java API

The Java API is the dev.tehoclient.api package. It is platform-neutral: every adapter implements it, so the same code runs on Paper, a proxy, Minestom or a modded server. Platform helpers such as BukkitTeho only translate platform types.

#Getting the API

TehoApi api = TehoApi.get();

TehoApi.get() throws IllegalStateException when the Teho API is not running on this server. If Teho support is optional for your plugin, use TehoApi.find(), which returns an Optional<TehoApi>.

#TehoPlayer

A TehoPlayer is one player's session on your server. It hangs one API off each feature.

TehoPlayer teho = api.player(uuid).orElseThrow();
teho.notify(notification);
teho.waypoints().set(waypoint);
teho.hud().timer(timer);
teho.staff().grant(grant);

It also tells you about the session:

#How calls behave

Sends return boolean. true means the frame was queued. false means the player did not negotiate the capability, or you turned the feature off in config.yml. It never throws for an unsupported feature.

Builders validate early. Ids are required, and limits such as a sidebar's 32 rows or a hologram's 16 lines throw IllegalArgumentException in build(), so you find mistakes in development instead of in a player's log.

Requests return CompletableFuture. Anything that waits for the client, such as screenshots, client info, proofs and clips, completes when the reply arrives. Players can decline, so always check granted() or valid().

teho.info().request("Matchmaking", ClientInfo.Field.INPUT, ClientInfo.Field.PERFORMANCE)
        .thenAccept(info -> {
            if (info.has(ClientInfo.Field.INPUT) && info.input() == ClientInfo.Input.CONTROLLER) {
                queue.joinControllerPool(teho.uniqueId());
            }
        });

A future completes on whichever thread delivered the client's reply, and that differs between platforms. Schedule back onto the thread that owns the world or player before you change game state.

State is remembered. Rules, staff grants, waypoints, cooldowns, timers and other state are kept per player in the SDK and re-sent after a re-handshake, so you only set them once.

#Colours

Methods that take rgb ignore the top byte. Methods that take argb treat a value with a zero alpha byte as opaque, so 0x4DA9FF and 0xFF4DA9FF mean the same thing, and you only need the alpha byte for translucent colours such as 0x804DA9FF.

#Item ids

Wherever an item is accepted, such as cooldown icons, bars or holograms, a bare id gets the minecraft: namespace, so "ender_pearl" and "minecraft:ender_pearl" are equivalent.

#A listener without platform events

TehoListener has a default no-op method for every callback, so implement only what you need. It is handy in shared code that runs on more than one platform.

TehoApi.get().addListener(new TehoListener() {
    @Override
    public void onReady(TehoPlayer player) {
        player.hud().timer(Timer.stopwatch("session", "Session", 0));
    }

    @Override
    public void onKey(TehoPlayer player, String keybind, boolean pressed, long heldMs) {
        if (pressed && keybind.equals("party")) {
            openPartyMenu(player);
        }
    }
});