Toasts

A toast is the popup in the top right when a player earns an advancement. Vanilla only produces one by granting a real advancement, which then sits in the player's advancement list forever.

Toasts toasts = new Toasts(plugin, scheduler);

toasts.builder()
        .icon(Material.DIAMOND)
        .title(Text.mini("<gold>Objective complete"))
        .description(Text.mini("<gray>You found the vault"))
        .frame(AdvancementFrame.GOAL)
        .show(player);

The module registers a temporary advancement, grants it, and removes it again, so nothing persists.

icon(ItemStack) uses a full item rather than a bare material, so a custom-model-data icon works.

Building without showing

Toast toast = Toast.builder()
        .icon(Material.EMERALD)
        .title(Text.mini("<green>Sold"))
        .build();

toasts.show(toast, player);
String json = toast.toJson();

Useful when the same toast is shown to many players, or when you want to inspect the generated advancement JSON.

Real advancements

Advancements.grant(player, advancement);
Advancements.revoke(player, advancement);

For the case where you do want the advancement to stick. Both return whether anything changed.

How it works, and why that matters

The module registers a one-criterion synthetic advancement through the data-pack loader, awards that criterion so the client animates the toast, then revokes and unregisters it a couple of ticks later. No packets and no NMS.

The keys are namespaced by your plugin name and carry a per-instance random prefix, so two Toasts instances, or one re-created across a reload, can never mint the same key and collide on the advancement registry.

The player-touching revoke runs on the player's own region thread and the registry removal hops onto the global region, which is why the service takes a Scheduler and never uses a Bukkit one.