Sending Biomes via Packets

Constructing a Virtual Biome

A VirtualBiome is a wrapper for Biomes that is required for using the PacketHandler interface.

Example Usage

ExamplePlugin.java Java Copy

import dev.wyck.model.biome.CustomBiome;
import dev.wyck.keys.ResourceKey;
import dev.wyck.renderer.packet.PacketHandler;
import dev.wyck.renderer.packet.data.VirtualBiome;
import dev.wyck.wrapper.BiomeSettings;
import org.bukkit.Material;
import org.bukkit.plugin.java.JavaPlugin;

public class ExamplePlugin extends JavaPlugin {
  @Override
  public void onEnable() {
      CustomBiome customBiome = CustomBiome.builder()
          .resourceKey(ResourceKey.of("test", "custombiome"))
          .settings(BiomeSettings.defaultSettings())
          .fogColor("#FFFFFF")
          .foliageColor("#F5F2EB")
          .skyColor("#B99DFC")
          .waterColor("#F5F2EB")
          .waterFogColor("#000000")
          // Render all grass blocks as diamond blocks
          .replace(Material.GRASS_BLOCK, Material.DIAMOND_BLOCK)
          .register();

          VirtualBiome virtualBiome = VirtualBiome.builder()
              .biome(customBiome)
              .conditional(((player, chunkLocation) -> {
                  // Only show this biome to Jsinco
                  return player.getName().equals("Jsinco");
              }))
              // Set the priority of this phony biome, defaults to NORMAL
              .priority(PacketHandler.Priority.NORMAL)
              .build();
  }
}

Using the PacketHandler

Tip

The PacketHandler supports block replacements, which means that you can use it to show fake blocks in your custom biomes.

The PacketHandler is a biome renderer that injects biome data directly into packets sent to players. This means that the biome change is purely visual and does not affect gameplay elements such as mob spawns and is purely visual.

When to use the PacketHandler

• You want to show different biomes to different players in the same area.
• You want to use block replacements in your custom biomes.

Choosing an Injector

PacketHandlers require and injector in order to inject biome data into packets. Wyck supports three different injectors:

• Netty: Wyck’s built-in standalone injector that does not require any external dependencies. Works similarly to ProtocolLib.
• ProtocolLib: Injects block replacements and custom biomes into packets using ProtocolLib injectors.
• PacketEvents: Injects block replacements and custom biomes into packets using PacketEvents wrappers and injectors.

Example Usage

ExamplePlugin.java Java Copy

import dev.wyck.model.biome.CustomBiome;
import dev.wyck.renderer.packet.PacketHandler;
import dev.wyck.renderer.packet.data.VirtualBiome;
import net.kyori.adventure.key.Key;
import org.bukkit.plugin.java.JavaPlugin;

public class ExamplePlugin extends JavaPlugin {

  private PacketHandler packetHandler;

  @Override
  public void onEnable() {
      CustomBiome customBiome = ...;
      Key plains = Key.key("minecraft:plains");

      VirtualBiome virtualBiome = VirtualBiome.builder()
          .biome(customBiome)
          .biomeCondition(((player, snapshot) -> {
              // Replace all 'plains' biomes with this custom biome
              return snapshot.centerBiome().key().equals(plains);
          }))
          .build();

      this.packetHandler = PacketHandler.of(this) // Defaults to NETTY injector
          .appendBiome(virtualBiome)
          .register();
  }

  @Override
  public void onDisable() {
      this.packetHandler.unregister();
  }
}