diff --git a/docs/floodgate/api.md b/docs/floodgate/api.md
index 9ebe82e..50a42d6 100644
--- a/docs/floodgate/api.md
+++ b/docs/floodgate/api.md
@@ -7,7 +7,7 @@ Floodgate has an API to extend what is possible and allow servers to get informa
This page will contain information about class FloodgateApi.
See the sidebar for more information about other parts of the API.
-### Accessing the Floodgate API
+### Accessing the Floodgate API {#accessing-the-floodgate-api}
See [here](/geyser/getting-started-with-the-api) for how to include the Floodgate API in your project.
@@ -29,7 +29,7 @@ To see full, detailed documentation, see the [javadocs](https://repo.opencollab.
:::
-#### We'll highlight a few to get you started quickly:
+#### We'll highlight a few to get you started quickly: {#well-highlight-a-few-to-get-you-started-quickly}
`FloodgateApi#isFloodgatePlayer(UUID)`
Used to check if the given UUID of an **online** player is a Bedrock player.
@@ -48,5 +48,5 @@ Click [here](/floodgate/linking/) to get more information about the PlayerLink c
Used to send a form to the Bedrock player with the given UUID.
Click [here](/geyser/forms/) to get more information about Forms.
-### Using the API on backend servers
+### Using the API on backend servers {#using-the-api-on-backend-servers}
In order to successfully use the API on backend Spigot servers when using a proxy, `send-floodgate-data` must be set to `true` on the proxy Floodgate's config, and the `key.pem` file must be identical between all Floodgate instances.
diff --git a/docs/floodgate/features.md b/docs/floodgate/features.md
index 7309b9c..8da7f26 100644
--- a/docs/floodgate/features.md
+++ b/docs/floodgate/features.md
@@ -2,7 +2,7 @@
title: Features
---
-## Whitelist command
+## Whitelist command {#whitelist-command}
Floodgate 2.0 has a whitelist command, `fwhitelist`, that should be used for adding or removing Floodgate players to whitelist.json. The username prefix doesn't need to be included.
`fwhitelist add Tim203`
@@ -12,7 +12,7 @@ You can also specify a UUID: `fwhitelist add 00000000-0000-0000-0009-01f64f65c7c
The permission node is `floodgate.command.fwhitelist`.
-## What is skin uploading?
+## What is skin uploading? {#what-is-skin-uploading}
Skins of Bedrock player should be visible to Java players on servers with Floodgate 2.0 installed.
If they aren't, it's most likely that the skin uploading queue has grown too large and can take a while to upload your skin.
diff --git a/docs/floodgate/index.md b/docs/floodgate/index.md
index ec31434..8e2ea6f 100644
--- a/docs/floodgate/index.md
+++ b/docs/floodgate/index.md
@@ -4,11 +4,11 @@ permalink: /floodgate/
---
# Floodgate
-## What is Floodgate?
+## What is Floodgate? {#what-is-floodgate}
Floodgate is a hybrid mode plugin that allows Minecraft: Bedrock Accounts to join Minecraft: Java Edition servers without needing a Minecraft: Java Edition account.
This is something you install in addition to Geyser. Unlike Geyser, Floodgate can only be installed as a plugin on Spigot (including Paper and forks), Bungeecord, Velocity, and as a mod on Fabric servers, and can only be utilized on servers that have it installed.
-## What has Floodgate 2.0 to offer?
+## What has Floodgate 2.0 to offer? {#what-has-floodgate-20-to-offer}
Floodgate 2.0 is a rewrite of Floodgate 1.0, with various bugfixes and improvements. It also introduces new features: being able to [see Bedrock player skins on Java edition](/floodgate/features/#what-is-skin-uploading),
being able to [use Bedrock forms](/geyser/forms/), link your account once and login on every server that has [Global Linking](/floodgate/linking/#what-is-global-linking) enabled,
and the [Global Api](/geyser/global-api).
diff --git a/docs/floodgate/issues.md b/docs/floodgate/issues.md
index 6b6e9da..4ac9a2e 100644
--- a/docs/floodgate/issues.md
+++ b/docs/floodgate/issues.md
@@ -5,54 +5,54 @@ title: Issues
# Known Issues & Caveats
If an issue you're experiencing is not listed here, please consider joining the Geyser [Discord](http://discord.geysermc.org/).
-## Running commands
+## Running commands {#running-commands}
In some instances, like if you have the `username-prefix` set to `*`, you may need to wrap the Bedrock player's username in quotes; for example: `/tp "*BedrockPlayer"`. Setting the prefix to `.` should also fix this.
-## If you wish to use IP forwarding, please enable it in your BungeeCord config as well!
+## If you wish to use IP forwarding, please enable it in your BungeeCord config as well! {#if-you-wish-to-use-ip-forwarding-please-enable-it-in-your-bungeecord-config-as-well}
It is likely you have enabled `send-floodgate-data` in your Floodgate config but either Floodgate isn't installed on the target server, or your floodgate key isn't the same between the installs of the plugin (please copy them so they all use the same key).
-## `java.lang.IllegalStateException: Cannot reply to EncryptionRequestPacket without profile and access token.`
+## `java.lang.IllegalStateException: Cannot reply to EncryptionRequestPacket without profile and access token.` {#javalangillegalstateexception-cannot-reply-to-encryptionrequestpacket-without-profile-and-access-token}
Make sure the server has Floodgate installed and started up correctly. Otherwise, see if the next line fixes your error.
-## `javax.crypto.AEADBadTagException: Tag mismatch!`
+## `javax.crypto.AEADBadTagException: Tag mismatch!` {#javaxcryptoaeadbadtagexception-tag-mismatch}
If Geyser and Floodgate are on the same server, shut down your server, delete the `floodgate` plugin folder, delete any key file in the Geyser folder, and restart your server.
If Geyser and Floodgate are not on the same server and you had to copy the key file, this could also be an error related to uploading through FTP. Using ASCII will not work here, and you need to make sure you're on binary when uploading. We recommend using [WinSCP](https://winscp.net) if you need to use FTP.
-## java.lang.NumberFormatException: For input string: ""
+## java.lang.NumberFormatException: For input string: "" {#javalangnumberformatexception-for-input-string-}
You're trying to log in without an Xbox account. Floodgate requires an Xbox account to authenticate the Bedrock player.
-## Geyser-Floodgate:51777 lost connection: Internal Exception: java.lang.NumberFormatException: For input string: "SfqdXv36" (or a similar error)
+## Geyser-Floodgate:51777 lost connection: Internal Exception: java.lang.NumberFormatException: For input string: "SfqdXv36" (or a similar error) {#geyser-floodgate51777-lost-connection-internal-exception-javalangnumberformatexception-for-input-string-sfqdxv36-or-a-similar-error}
Set `ip-forwarding` in your BungeeCord to `true`.
-## "Please connect through the official Geyser" disconnect message
+## "Please connect through the official Geyser" disconnect message {#please-connect-through-the-official-geyser-disconnect-message}
Ensure that Floodgate and Geyser are both up-to-date.
-## Prefix is not changing on the server after changing it in the config.
+## Prefix is not changing on the server after changing it in the config. {#prefix-is-not-changing-on-the-server-after-changing-it-in-the-config}
Between the Paper builds of 1.15.2-355 and 1.16.5-505, there was a bug where Floodgate players who had already connected to the server would not have their prefixed changed. Paper builds 1.16.5-506 and later fix this issue.
Ensure that you removed the `usercache.json` file from the server root directory and restart your server.
-## Issues with LuckPerms and prefixes
+## Issues with LuckPerms and prefixes {#issues-with-luckperms-and-prefixes}
Set `allow-invalid-usernames` to `true` in LuckPerms' config.
-## Failed to verify username! (with Paper)
+## Failed to verify username! (with Paper) {#failed-to-verify-username-with-paper}
To completely mitigate this issue, disable `perform-username-validation` in the [unsupported settings of the `config/paper-global.yml` file](https://paper.readthedocs.io/en/latest/server/configuration.html#unsupported_settings) (`paper.yml` in the root server folder on servers below 1.19). Using Floodgate on the backend servers will also mitigate this issue.
-## Error with Forge or Fabric Bukkit Hybrid
+## Error with Forge or Fabric Bukkit Hybrid {#error-with-forge-or-fabric-bukkit-hybrid}
At this time, there is no way to run Floodgate on servers that mix Forge and Bukkit or Fabric and Bukkit (For example: Magma, Mohist, and Cardboard/Bukkit4Fabric) - most hybrids do not support the complicated procedures we need to do in order to allow Bedrock players to connect (for the technically minded: these server softwares typically don't support NMS).
If you wish to use Floodgate in combination with hybrid servers, we recommend putting these servers behind a BungeeCord or Velocity proxy, and running Floodgate on the proxy.
-## After enabling global linking in offline mode, player data is not synced between Java and Bedrock players.
+## After enabling global linking in offline mode, player data is not synced between Java and Bedrock players. {#after-enabling-global-linking-in-offline-mode-player-data-is-not-synced-between-java-and-bedrock-players}
This occurs in offline mode because the UUID of the Java account linked to the Bedrock account does not match the online mode UUID returned by Floodgate's global linking server.
diff --git a/docs/floodgate/linking.md b/docs/floodgate/linking.md
index 5604d8a..2b59be3 100644
--- a/docs/floodgate/linking.md
+++ b/docs/floodgate/linking.md
@@ -2,7 +2,7 @@
title: Linking
---
-## What is Global Linking?
+## What is Global Linking? {#what-is-global-linking}
Instructions and information about how to link can also be found here: [https://link.geysermc.org/](https://link.geysermc.org/)
@@ -37,7 +37,7 @@ Once you saved the config and restarted your server you should be using Global L
If you don't want to use Global Linking, you can disable `enable-global-linking` in the Floodgate config.
-## Local Linking
+## Local Linking {#local-linking}
You can also set up a local linking database on your server. Local linking can work with Global Linking at the same time. Link entries in your local database will override entries in the Global Linking Server.
Note that you only have to follow these steps on your proxy (BungeeCord or Velocity), if you have one.
diff --git a/docs/floodgate/setup/proxy-servers.mdx b/docs/floodgate/setup/proxy-servers.mdx
index c66a97c..91f4041 100644
--- a/docs/floodgate/setup/proxy-servers.mdx
+++ b/docs/floodgate/setup/proxy-servers.mdx
@@ -8,7 +8,7 @@ Additionally, it will display Bedrock edition skins properly.
3. Change `auth-type` in Geyser's config to `floodgate`.
4. Restart the server.
-### Installing Floodgate on servers behind the proxy
+### Installing Floodgate on servers behind the proxy {#installing-floodgate-on-servers-behind-the-proxy}
This is only needed when you want to use the Floodgate API on your backend server(s) behind a proxy.
diff --git a/docs/geyser/anticheat-compatibility.md b/docs/geyser/anticheat-compatibility.md
index 4ff7273..8cd9d87 100644
--- a/docs/geyser/anticheat-compatibility.md
+++ b/docs/geyser/anticheat-compatibility.md
@@ -9,7 +9,7 @@ This is a community-compiled list and does not indicate any endorsement from Gey
:::
-### AntiCheat compatibility reports
+### AntiCheat compatibility reports {#anticheat-compatibility-reports}
Full Compatibility (Checks Bedrock Players Accurately)
diff --git a/docs/geyser/api.md b/docs/geyser/api.md
index ceb0309..526f1cb 100644
--- a/docs/geyser/api.md
+++ b/docs/geyser/api.md
@@ -4,16 +4,16 @@ title: Geyser API
Geyser has an API to extend what is possible with Geyser, and to allow you to interact with Geyser in your own plugins, mods, or extensions.
-### Where can I use the Geyser API?
+### Where can I use the Geyser API? {#where-can-i-use-the-geyser-api}
You could use the Geyser API in:
- A plugin for Paper/Spigot, Velocity, Waterfall/BungeeCord, etc.
- A mod for Fabric or NeoForge
- A Geyser Extension
-### Accessing the Geyser API
+### Accessing the Geyser API {#accessing-the-geyser-api}
See [here](/geyser/getting-started-with-the-api) for how to include the Geyser API dependency in your project.
-### Documentation
+### Documentation {#documentation}
The Geyser API offers events to subscribe to, or information on whether a player is joining through Geyser, and gives you the ability to enhance what is possible with Geyser (i.e. register custom items).
(soon, blocks and entities too).
@@ -24,7 +24,7 @@ It can be used easily in Geyser Extensions, see [here](/geyser/extensions) for d
Note: To see full, detailed documentation, see the javadocs.
-#### [GeyserApi](https://github.com/GeyserMC/Geyser/blob/master/api/src/main/java/org/geysermc/geyser/api/GeyserApi.java):
+#### [GeyserApi](https://github.com/GeyserMC/Geyser/blob/master/api/src/main/java/org/geysermc/geyser/api/GeyserApi.java): {#geyserapi}
The GeyserApi interface serves as a central access point to various functionalities provided by the Geyser API, providing methods to e.g. interact with player connections.
It extends the [Base API](https://github.com/GeyserMC/api/blob/master/base/src/main/java/org/geysermc/api/GeyserApiBase.java) interface, which provides basic information about individual players.
@@ -40,7 +40,7 @@ Most [API methods have a simple explanation](https://github.com/GeyserMC/Geyser/
Since the Geyser API extends the Base API that is shared across Floodgate and Geyser, you can also use the [methods from the Base API](https://github.com/GeyserMC/api/blob/master/base/src/main/java/org/geysermc/api/GeyserApiBase.java).
-#### We'll highlight a few to get you started quickly:
+#### We'll highlight a few to get you started quickly: {#well-highlight-a-few-to-get-you-started-quickly}
`GeyserApi#isBedrockPlayer(UUID)`
Used to check if the given UUID of an **online** player is a Bedrock player.
@@ -60,38 +60,38 @@ Click [here](/geyser/forms/) to get more information about Forms.
`GeyserApi#onlineConnectionsCount()`
Used to get the amount of online Bedrock players.
-### Short Overview of the Geyser API
+### Short Overview of the Geyser API {#short-overview-of-the-geyser-api}
-#### [Cumulus](https://github.com/GeyserMC/Cumulus/tree/master/src/main/java/org/geysermc/cumulus)
+#### [Cumulus](https://github.com/GeyserMC/Cumulus/tree/master/src/main/java/org/geysermc/cumulus) {#cumulus}
While technically not directly in the Geyser API, the Cumulus library is also provided by the Geyser API.
It allows you to send Bedrock edition forms to players. See [Cumulus](/geyser/forms/) for more information.
-#### [Events](https://github.com/GeyserMC/Geyser/tree/master/api/src/main/java/org/geysermc/geyser/api/event)
+#### [Events](https://github.com/GeyserMC/Geyser/tree/master/api/src/main/java/org/geysermc/geyser/api/event) {#events}
The event package contains all the events that Geyser fires. See [here](/geyser/events) for detailed information on how to listen to Geyser events.
-#### [Command](https://github.com/GeyserMC/Geyser/tree/master/api/src/main/java/org/geysermc/geyser/api/command)
+#### [Command](https://github.com/GeyserMC/Geyser/tree/master/api/src/main/java/org/geysermc/geyser/api/command) {#command}
This package contains classes and interfaces related to commands in Geyser, which allows [Geyser Extensions](/geyser/extensions) to register custom commands.
-#### [Entity](https://github.com/GeyserMC/Geyser/tree/master/api/src/main/java/org/geysermc/geyser/api/entity)
+#### [Entity](https://github.com/GeyserMC/Geyser/tree/master/api/src/main/java/org/geysermc/geyser/api/entity) {#entity}
The Entity package contains classes and interfaces related to entities in Geyser, like the GeyserPlayerEntity interface,
which represents a player entity in Geyser. This interface extends the GeyserEntity interface, while providing additional functionality specifically for player entities,
like currently, showing emotes.
-#### [Item](https://github.com/GeyserMC/Geyser/tree/master/api/src/main/java/org/geysermc/geyser/api/item)
+#### [Item](https://github.com/GeyserMC/Geyser/tree/master/api/src/main/java/org/geysermc/geyser/api/item) {#item}
The item package contains classes and interfaces related to items in Geyser. You can create custom items and register them using the Geyser API.
See [here](/geyser/custom-items) for detailed information on how to register custom items.
-#### [Block](https://github.com/GeyserMC/Geyser/tree/master/api/src/main/java/org/geysermc/geyser/api/block)
+#### [Block](https://github.com/GeyserMC/Geyser/tree/master/api/src/main/java/org/geysermc/geyser/api/block) {#block}
The block package contains classes and interfaces related to blocks in Geyser. You can create custom blocks using this package, and register them in using the [GeyserDefineCustomBlocksEvent](https://github.com/GeyserMC/Geyser/blob/master/api/src/main/java/org/geysermc/geyser/api/event/lifecycle/GeyserDefineCustomBlocksEvent.java).
See [here](/geyser/custom-blocks) for detailed information.
-#### [Network](https://github.com/GeyserMC/Geyser/tree/master/api/src/main/java/org/geysermc/geyser/api/network)
+#### [Network](https://github.com/GeyserMC/Geyser/tree/master/api/src/main/java/org/geysermc/geyser/api/network) {#network}
The network package contains basic information about the remote server via the
[RemoteServer](https://github.com/GeyserMC/Geyser/blob/master/api/src/main/java/org/geysermc/geyser/api/network/RemoteServer.java)
interface, such as the server's IP address and port, and the protocol version of the remote server. Or the auth type.
You can also get the port/IP that Geyser listens to via the [BedrockListener](https://github.com/GeyserMC/Geyser/blob/master/api/src/main/java/org/geysermc/geyser/api/network/BedrockListener.java) interface.
-#### [Pack](https://github.com/GeyserMC/Geyser/tree/master/api/src/main/java/org/geysermc/geyser/api/pack)
+#### [Pack](https://github.com/GeyserMC/Geyser/tree/master/api/src/main/java/org/geysermc/geyser/api/pack) {#pack}
The pack package contains classes and interfaces related to resource packs in Geyser. You can create custom resource packs and send them to individual sessions before they log in using the [SessionLoadResourcePacksEvent](https://github.com/GeyserMC/Geyser/blob/master/api/src/main/java/org/geysermc/geyser/api/event/bedrock/SessionLoadResourcePacksEvent.java).
If you wish to send a resource pack to all sessions, you can use the [GeyserLoadResourcePacksEvent](https://github.com/GeyserMC/Geyser/blob/master/api/src/main/java/org/geysermc/geyser/api/event/lifecycle/GeyserLoadResourcePacksEvent.java).
@@ -101,6 +101,6 @@ This allows you to load a Bedrock resource pack from a file path:
ResourcePack pack = ResourcePack.create(PackCodec.path(path));
```
-#### [Extension](https://github.com/GeyserMC/Geyser/tree/master/api/src/main/java/org/geysermc/geyser/api/extension)
+#### [Extension](https://github.com/GeyserMC/Geyser/tree/master/api/src/main/java/org/geysermc/geyser/api/extension) {#extension}
This package provides the necessary components to create and manage extensions.
For a more detailed explanation of extensions, see [here](/geyser/extensions).
diff --git a/docs/geyser/commands.md b/docs/geyser/commands.md
index c909e25..efd60d1 100644
--- a/docs/geyser/commands.md
+++ b/docs/geyser/commands.md
@@ -13,7 +13,7 @@ on the proxy server to assign permissions to players. Assigning permissions on t
:::
-## Geyser commands & their permissions
+## Geyser commands & their permissions {#geyser-commands--their-permissions}
| Command | Permission | Description |
|:--------------------------------------:|:------------------------------:|:-------------------------------------------------------------------:|
@@ -29,7 +29,7 @@ on the proxy server to assign permissions to players. Assigning permissions on t
| `geyser version` | `geyser.command.version` | Shows the current Geyser version and checks for updates. |
| `geyser tooltips` | `geyser.command.tooltips` | Toggle showing Advanced Tooltips (F3 + H on Java) |
-## Other Permissions
+## Other Permissions {#other-permissions}
Besides commands, there are other permissions that are used to guard specific Geyser features.
@@ -37,6 +37,6 @@ Besides commands, there are other permissions that are used to guard specific Ge
|--------------------------|------------------------------------------------------------------------------------------------------------|
| `geyser.settings.server` | Allow players to use the [game settings menu](/img/wiki/game_menu.png). (Also requires player to have op.) |
-## Floodgate commands and permissions
+## Floodgate commands and permissions {#floodgate-commands-and-permissions}
For Floodgate commands, see [here](/floodgate/commands/).
diff --git a/docs/geyser/common-issues.md b/docs/geyser/common-issues.md
index 25493ad..6ef4e70 100644
--- a/docs/geyser/common-issues.md
+++ b/docs/geyser/common-issues.md
@@ -15,7 +15,7 @@ For Floodgate issues see: [Floodgate: Known Issues/Caveats](/floodgate/issues/).
* If you don't use a reverse proxy such as TCPShield make sure that `enable-proxy-protocol` is set to false.
To fix "Unable to connect to world" with no console errors, see [here](/geyser/fixing-unable-to-connect-to-world/).
-## If the server doesn't show up in the friends list
+## If the server doesn't show up in the friends list {#if-the-server-doesnt-show-up-in-the-friends-list}
* *If using Windows 10, iOS, or Android*: try adding the server to the Servers list in-game.
* *If using Xbox One*: try connecting with [BedrockConnect](/geyser/using-geyser-with-consoles/).
@@ -31,14 +31,14 @@ See [here](/geyser/fixing-unable-to-connect-to-world/) for fixing "Unable to Con
:::
-### `java.net.BindException: Address already in use: bind` on startup.
+### `java.net.BindException: Address already in use: bind` on startup. {#javanetbindexception-address-already-in-use-bind-on-startup}
This means something (likely another instance of Geyser) is running on the port you have specified in the config. Please make sure you close all applications running on this port. If you don't recall opening anything, usually restarting your computer fixes this.
-### [...]` has been compiled by a more recent version of the Java Runtime (class file version 60.0)`
+### [...]` has been compiled by a more recent version of the Java Runtime (class file version 60.0)` {#-has-been-compiled-by-a-more-recent-version-of-the-java-runtime-class-file-version-600}
See this link for updating to Java 17: https://paper.readthedocs.io/en/latest/java-update/index.html.
-### Hosting provider will not immediately open up UDP.
+### Hosting provider will not immediately open up UDP. {#hosting-provider-will-not-immediately-open-up-udp}
These steps only apply for the standalone version of Geyser.
This usually has something to do on your host's end. Most commonly, it's because they do not open up ports over the UDP protocol, which is what Minecraft: Bedrock Edition uses, opposed to Minecraft: Java Edition using TCP.
@@ -58,7 +58,7 @@ This option will most likely not help if you are getting "Unable to Connect to W
***If you are using a plugin version:*** in your Geyser config, set your remote address to `127.0.0.1`. If that does not work, check your startup log for a message about Docker, and use that address in the remote address
-### Cannot reply to EncryptionRequestPacket without profile and access token
+### Cannot reply to EncryptionRequestPacket without profile and access token {#cannot-reply-to-encryptionrequestpacket-without-profile-and-access-token}
There are two causes of this message:
@@ -70,21 +70,21 @@ This message can occur with a Floodgate setup. Usually, it means that a misconfi
If you have your configuration set up like this, put simply, it won't work. If authentication for the Java server is set to online, it is expected Geyser is configured the same way. The server requires a valid Minecraft: Java Edition account, and if you aren't logging into one with Geyser, then you will be unable to join the server. If your configuration is set up properly and you're still getting this issue, it could be that your credentials are invalid.
-### Connection Refused: \
+### Connection Refused: \ {#connection-refused-insert-ip-andor-domain}
Connection Refused usually means that a Java server could not be found on that port, or the server denied access to the connection on a network level.
The latter can happen with anti-DDOS plugins such as TCPShield, but otherwise ensure that the server you're trying to connect to is spelled correctly in the config, is up and is port forwarded correctly.
If you're updating from an old build of Geyser, set your remote address to `auto` and try again.
-### Floodgate Misconfiguration
+### Floodgate Misconfiguration {#floodgate-misconfiguration}
See [this page](/floodgate/setup/) for more information.
-### Missing profile key. This server requires secure profiles.
+### Missing profile key. This server requires secure profiles. {#missing-profile-key-this-server-requires-secure-profiles}
See [this page](/geyser/secure-chat/).
-### Mojang Resetting Account Credentials
+### Mojang Resetting Account Credentials {#mojang-resetting-account-credentials}
This is unfortunately something we have no control over, and is most likely the case when you're running Geyser as a plugin on a server host or joining a friend far away from your location. If you're running Geyser locally, this should not happen to you, but what we recommend for servers is a plugin we make called [Floodgate](https://github.com/GeyserMC/Floodgate), which allows for Bedrock clients to join your server without needing a Java Edition account. Take a look [here](/floodgate) for more information.
# "Invalid IP address!" from Bedrock
@@ -129,5 +129,5 @@ And so on.
If your players can't connect from the lobby to another backend server, check console.
-### Plugins that can cause issues
+### Plugins that can cause issues {#plugins-that-can-cause-issues}
* `HamsterAPI`
diff --git a/docs/geyser/creating-a-startup-script.md b/docs/geyser/creating-a-startup-script.md
index f4dc0fd..d283270 100644
--- a/docs/geyser/creating-a-startup-script.md
+++ b/docs/geyser/creating-a-startup-script.md
@@ -12,7 +12,7 @@ In order for this to work, you MUST have Java 17 (or higher) installed!
Once you have downloaded and placed Geyser into its own folder, you will need to create a startup script; similar to how you'd run a Bukkit/Spigot/Paper server.
-### Windows
+### Windows {#windows}
* Create a new text file in the same location as the Geyser-Standalone jar file, and call it `run.bat`. Open this with a text editor (preferably Notepad++), and insert the text below:
```batch title="run.bat"
@@ -23,7 +23,7 @@ pause
* Double-click the **run.bat**, and Geyser should start up. Geyser will generate all the needed files.
-### macOS
+### macOS {#macos}
* Create a text file called **run.command**, and open it with a text editor such as TextEdit or TextMate. Type the text below into the **run.command** file:
```sh title="run.command"
@@ -35,7 +35,7 @@ java -Xms1024M -jar Geyser-Standalone.jar
* Open Terminal, and type in `chmod a+x` **(Do NOT press return!)**, and drag your *run.command* file into the Terminal.
* Press return on your keyboard, and Geyser will start up. Geyser will generate all the needed files.
-### Linux
+### Linux {#linux}
* Create a file called *run.sh*, and open it with a text editor. Type the text below into your `run.sh` file:
```sh title="run.sh"
diff --git a/docs/geyser/current-limitations.md b/docs/geyser/current-limitations.md
index 36b69b2..3f0f2d1 100644
--- a/docs/geyser/current-limitations.md
+++ b/docs/geyser/current-limitations.md
@@ -7,7 +7,7 @@ title: Current Limitations
With Geyser being a protocol translator between two different games with two different codebases, there are a handful of limitations that Geyser is unfortunately unable to handle.
Despite Minecraft Bedrock and Java being quite close in comparison, there are some vast differences in many areas.
-## Unfixable
+## Unfixable {#unfixable}
The following things cannot be fixed without changes to Bedrock or the Java protocol in general. As of now, they are not fixable in Geyser.
@@ -32,7 +32,7 @@ The following things cannot be fixed without changes to Bedrock or the Java prot
- Saddled camels unmoveable/unrideable on bedrock.
- Bedrock edition players cannot see the changes to fence block states made by the Java Debug Stick.
-## Fixable With GeyserOptionalPack
+## Fixable With GeyserOptionalPack {#fixable-with-geyseroptionalpack}
The following changes **are supported** with the [GeyserOptionalPack](/other/geyseroptionalpack/), which is a Bedrock resource pack you can install for additional functionality for features Bedrock does not natively support:
- Custom armor stand poses
diff --git a/docs/geyser/custom-blocks.md b/docs/geyser/custom-blocks.md
index 29af0c2..8e12a18 100644
--- a/docs/geyser/custom-blocks.md
+++ b/docs/geyser/custom-blocks.md
@@ -8,7 +8,7 @@ To setup custom blocks in geyser, you have to choose how you are going to regist
It should be noted that blocks and their associated components are not very stable. Mojang tends to make changes to these much more often than they do for items. This means that any components Geyser allows you to register are liable to break in future versions of Bedrock.
-## Enabling custom blocks
+## Enabling custom blocks {#enabling-custom-blocks}
Before beginning, ensure that `add-non-bedrock-items` is set to `true` in your `config.yml` file.
@@ -21,13 +21,13 @@ Before beginning, ensure that `add-non-bedrock-items` is set to `true` in your `
add-non-bedrock-items: true
```
-## JSON mappings
+## JSON mappings {#json-mappings}
The JSON mappings use a similar structure to that of behavior packs registering blocks. The equivalent components are listed in the [Minecraft: Bedrock Edition Creator Documentation](https://learn.microsoft.com/en-us/minecraft/creator/reference/content/blockreference/examples/blockcomponents/blockcomponentslist).
Custom mappings files that register blocks or items should be placed in the `custom_mappings` folder. This folder is created when you start your server. It is located in the same folder as the `Geyser-Standalone.jar` file for standalone and inside your Geyser data folder for a plugin. If you do not have this folder, ensure you are on the latest version of Geyser.
-### Example mappings file
+### Example mappings file {#example-mappings-file}
```json
{
@@ -80,7 +80,7 @@ Custom mappings files that register blocks or items should be placed in the `cus
}
```
-### Schema
+### Schema {#schema}
The following details the schema for the mappings file. Only the `name` field is strictly required. All other fields are optional.
@@ -317,7 +317,7 @@ The following details the schema for the mappings file. Only the `name` field is
-## Geyser extensions
+## Geyser extensions {#geyser-extensions}
In this example, we will create a custom block that overrides the vanilla redstone dot. This block will be placed on top of a block and will emit a visible redstone signal when powered.
diff --git a/docs/geyser/custom-items.md b/docs/geyser/custom-items.md
index 27682df..dd81e70 100644
--- a/docs/geyser/custom-items.md
+++ b/docs/geyser/custom-items.md
@@ -6,7 +6,7 @@ title: Custom items with Geyser
To setup custom items in geyser, you have to choose how you are going to register your items. The easiest is [using a json file](#json-mappings) but you can also [use a Geyser extension](#geyser-extensions).
-## JSON mappings
+## JSON mappings {#json-mappings}
1. Start your server, and you should have a folder called `custom_mappings` that is created. That would be with the folder of `Geyser.jar` file for standalone and inside your Geyser data folder for a plugin.
2. Create a `.json` file, it can be any name you like and as many files as you like. You don't need to make one file per item. Here is the structure of the file:
@@ -73,9 +73,9 @@ To setup custom items in geyser, you have to choose how you are going to registe
}
```
-## Geyser extensions
+## Geyser extensions {#geyser-extensions}
-### Extending a vanilla item
+### Extending a vanilla item {#extending-a-vanilla-item}
1. Create your custom item options or registrations, to which you can add any of the following. They can be stacked, so that all of the specified types need to match, but you **do NOT need all of them.**
```java
@@ -108,7 +108,7 @@ public void onGeyserPreInitializeEvent(GeyserDefineCustomItemsEvent event) {
}
```
-### Non vanilla (modded) items with Geyser extensions (for example to use with Fabric)
+### Non vanilla (modded) items with Geyser extensions (for example to use with Fabric) {#non-vanilla-modded-items-with-geyser-extensions-for-example-to-use-with-fabric}
1. Create your item data:
```java
@@ -126,7 +126,7 @@ public void onGeyserDefineCustomItemsEvent(GeyserDefineCustomItemsEvent event) {
}
```
-## Resource pack
+## Resource pack {#resource-pack}
1. Setup a basic bedrock resource pack. If you need help, you can find it [here](https://wiki.bedrock.dev/guide/project-setup.html#rp-manifest).
2. Make a `textures` folder.
diff --git a/docs/geyser/custom-skulls.md b/docs/geyser/custom-skulls.md
index b87254b..73dc11a 100644
--- a/docs/geyser/custom-skulls.md
+++ b/docs/geyser/custom-skulls.md
@@ -8,7 +8,7 @@ Unlike Java Edition, Bedrock does not have native support for custom skull items
To setup custom skulls in geyser, you have to choose how you are going to register your blocks. The easiest is [using custom-skulls.yml](#custom-skullsyml), but you can also [use a Geyser extension](#geyser-extensions).
-## Enabling custom skulls
+## Enabling custom skulls {#enabling-custom-skulls}
To enable custom skulls, you must set `add-non-bedrock-items` to `true` in the `config.yml` file. This will enable the generation of the custom resource pack and the translation of custom skulls to custom blocks. You can then add custom skulls to the `custom-skulls.yml` file.
@@ -21,7 +21,7 @@ To enable custom skulls, you must set `add-non-bedrock-items` to `true` in the `
add-non-bedrock-items: true
```
-## custom-skulls.yml
+## custom-skulls.yml {#custom-skullsyml}
The configuration file `custom-skulls.yml` is present in Geyser's configuration folder and is laid out as follows:
@@ -59,15 +59,15 @@ skin-hashes:
To add a skull, you need to choose any of the four methods, and add a new entry. The following sections will explain each method:
-### Player usernames
+### Player usernames {#player-usernames}
Skulls can be registered in this section via player usernames. These will be updated when Geyser starts. As a result, they may change if the player's username or skin changes.
-### Player UUIDs
+### Player UUIDs {#player-uuids}
Skulls can be registered in this section via player UUIDs. These will be updated when Geyser starts. As a result, they may change if skin changes.
-### Player profiles
+### Player profiles {#player-profiles}
Skulls can be registered in this section via the texture string found in the NBT of custom player heads. Unless the value is changed manually, these will not be updated when Geyser starts. As a result, they will not change if the player's username or skin changes. The data is simply base64 encoded JSON. For instance, the example given in the config decodes as follows:
@@ -94,13 +94,13 @@ If on a paper server, this data can be obtained for a skull by holding the item
[05:58:07 INFO]: minecraft:player_head{display: {Name: '{"text":"Test"}'}, SkullOwner: {Properties: {textures: [{Value: "ewogICJ0aW1lc3RhbXAiIDogMTY1NzMyMjIzOTgzMywKICAicHJvZmlsZUlkIiA6ICJjZGRiZTUyMGQwNDM0YThiYTFjYzlmYzkyZmRlMmJjZiIsCiAgInByb2ZpbGVOYW1lIiA6ICJkYXZjaG9vIiwKICAidGV4dHVyZXMiIDogewogICAgIlNLSU4iIDogewogICAgICAidXJsIiA6ICJodHRwOi8vdGV4dHVyZXMubWluZWNyYWZ0Lm5ldC90ZXh0dXJlL2E5MDc5MGM1N2UxODFlZDEzYWRlZDE0YzQ3ZWUyZjdjOGRlMzUzM2UwMTdiYTk1N2FmN2JkZjlkZjFiZGU5NGYiLAogICAgICAibWV0YWRhdGEiIDogewogICAgICAgICJtb2RlbCIgOiAic2xpbSIKICAgICAgfQogICAgfQogIH0KfQ"}]}, Id: [I; -229048314, -553040501, -1407961158, 465313087]}}
```
-### Skin Hashes
+### Skin Hashes {#skin-hashes}
Skulls can be registered in this section via the hash of the skin on Minecraft's skin server. This is found at the end of the URL. For example, in the URL `http://textures.minecraft.net/texture/a90790c57e181ed13aded14c47ee2f7c8de3533e017ba957af7bdf9df1bde94f` the hash is `a90790c57e181ed13aded14c47ee2f7c8de3533e017ba957af7bdf9df1bde94f`.Unless the value is changed manually, these will not be updated when Geyser starts. As a result, they will not change if the player's username or skin changes.
This can be obtained by decoding the base64 data obtained from a player profile.
-## Geyser extensions
+## Geyser extensions {#geyser-extensions}
In this example, we will register a custom skull from a player profile. We will use the player profile from the example above.
@@ -135,6 +135,6 @@ public class RegisterCustomSkull implements Extension {
}
```
-## Scraping custom skulls from a world
+## Scraping custom skulls from a world {#scraping-custom-skulls-from-a-world}
Custom skulls can be extracted from an existing world for easy implementation via mappings or API using the tool [HeadExtractor](https://github.com/davchoo/HeadExtractor) made by Amberichu. See the linked repository for usage instructions.
diff --git a/docs/geyser/events.md b/docs/geyser/events.md
index 9435625..c52eb2f 100644
--- a/docs/geyser/events.md
+++ b/docs/geyser/events.md
@@ -7,7 +7,7 @@ Geyser has a powerful event system that allows you to listen to events that are
Full documentation can be found [here](https://github.com/GeyserMC/Geyser/tree/master/api/src/main/java/org/geysermc/geyser/api/event).
-## Event Categories
+## Event Categories {#event-categories}
To use events in a Spigot/Paper plugin or a Fabric mod, you need to register the Geyser Event Bus as a listener and then subscribe to the events you want to listen to.
Extensions can use the @Subscribe annotation.
@@ -21,7 +21,7 @@ Events are categorized into the following categories:
To see all the events in the respective categories, click on the links above.
-## Usage Examples:
+## Usage Examples: {#usage-examples}
Each method that you want to subscribe to an event needs to be annotated with the @Subscribe annotation (from the GeyserMC events package).
```java
@@ -92,7 +92,7 @@ public class ExamplePlugin extends JavaPlugin implements EventRegistrar {
GeyserApi.api().eventBus().subscribe(this, GeyserEvent.class, this::yourMethod);
```
-## Event Priority
+## Event Priority {#event-priority}
Events can have a priority, which is used to determine the order in which the listeners are called. The default priority is NORMAL.
To (optionally) set the priority of your event listener, you can add the priority to the `@Subscribe` annotation:
```java
diff --git a/docs/geyser/extensions.md b/docs/geyser/extensions.md
index c51769c..54ffe30 100644
--- a/docs/geyser/extensions.md
+++ b/docs/geyser/extensions.md
@@ -8,7 +8,7 @@ Geyser Extensions are the equivalent of "plugins", but specifically for the Geys
This brings the advantage of them being platform-agnostic, meaning that you won't have to worry about supporting all platforms individually.
Additionally, they will be, by design, only applied for Bedrock players joining via Geyser.
-## What can Geyser Extensions do?
+## What can Geyser Extensions do? {#what-can-geyser-extensions-do}
Extensions can fully utilize the Geyser API to add additional functionality to Geyser.
See [Geyser API docs](/geyser/api/) for info on what is currently possible.
@@ -22,7 +22,7 @@ To name a few examples:
The underlying Geyser API is steadily expanding, creating more and more opportunities.
-## Which Geyser Extensions exist?
+## Which Geyser Extensions exist? {#which-geyser-extensions-exist}
At the moment, extensions are still a new system, so there is only a small list of known extensions for Geyser.
However, new extensions are always being created!
@@ -30,12 +30,12 @@ However, new extensions are always being created!
There is an [official list](https://github.com/GeyserMC/GeyserExtensionList) of available extensions you can check out.
If you have an extension you'd like to see on this list, feel free to open a PR!
-## Installing Extensions
+## Installing Extensions {#installing-extensions}
To install an extension, simply put the extension .jar file into Geyser's 'extensions' folder.
Then, restart Geyser (or the server Geyser runs on).
-## Creating Geyser Extensions
+## Creating Geyser Extensions {#creating-geyser-extensions}
The easiest way to create an extension would be utilizing [this official template](https://github.com/GeyserMC/GeyserExampleExtension/).
Simply create a new repository from the template, customize the `extension.yml` & `settings.gradle` files, and get started making the extension.
@@ -58,7 +58,7 @@ Explanations for the individual fields:
- api: The Base API version your extension targets.
- authors: The author(s) of the extension. To add more than one entry, separate entries with a comma.
-## Creating the main class
+## Creating the main class {#creating-the-main-class}
The main class, the entrypoint for the extension, needs to [implement the 'Extension' interface provided by Geyser](https://github.com/GeyserMC/GeyserExampleExtension/blob/master/src/main/java/org/geyser/extension/exampleid/ExampleExtension.java#L12).
That way, Geyser recognizes the extension, and gives you access to important methods - such as 'logger()', to get your extensions logger.
@@ -84,7 +84,7 @@ and register them in the event. You can find an example for custom items [here](
To build your extension, run the Gradle build task, and install the extension.
-## Creating commands with Geyser Extensions
+## Creating commands with Geyser Extensions {#creating-commands-with-geyser-extensions}
To create a command, you would need to use the "Commands" package in the Geyser API. Brief rundown:
- [Command.java](https://github.com/GeyserMC/Geyser/blob/master/api/src/main/java/org/geysermc/geyser/api/command/Command.java)
This interface represents a command in Geyser - to make one, you can use the CommandBuilder. You can register it with the
@@ -126,12 +126,12 @@ Here, it would send "Hello World" to the source that ran the command.
Since we also set aliases, you could also run `/exampleid example` or `/exampleid ex` for the same command.
To provide args, simple run `/exampleid examplecommand [args]` - replacing [args] with the arguments you want to pass to the command.
-## Listening to Events
+## Listening to Events {#listening-to-events}
See [here](/geyser/events) for documentation. You do not need to register the event listener, Geyser will do that for you.
---
-## Facing troubles with extensions?
+## Facing troubles with extensions? {#facing-troubles-with-extensions}
- Make sure you are using the latest version of Geyser - older versions might not have the latest API changes.
- Add debug prints.
diff --git a/docs/geyser/faq.mdx b/docs/geyser/faq.mdx
index b26b3fe..11f5519 100644
--- a/docs/geyser/faq.mdx
+++ b/docs/geyser/faq.mdx
@@ -5,7 +5,7 @@ title: Frequently Asked Questions
import { Questions, Q, A } from "../../src/components/Questions";
import { Versions } from '../../src/components/Versions'
-### General Questions
+### General Questions {#general-questions}
Here you can find answers to frequently asked questions about Geyser - if you have a question that isn't answered here, feel free to ask in our [Discord](https://discord.gg/GeyserMC)!
@@ -246,7 +246,7 @@ Here you can find answers to frequently asked questions about Geyser - if you ha
-### Additional Questions
+### Additional Questions {#additional-questions}
These additional frequently asked questions are not related to Geyser gameplay.
diff --git a/docs/geyser/fixing-unable-to-connect-to-world.md b/docs/geyser/fixing-unable-to-connect-to-world.md
index 048f18c..c0f6186 100644
--- a/docs/geyser/fixing-unable-to-connect-to-world.md
+++ b/docs/geyser/fixing-unable-to-connect-to-world.md
@@ -18,25 +18,25 @@ If you are not using a Minecraft server hosting provider, carry on.
geyser connectiontest <ip>:<port>, and see what it suggests to try.
-### Java Edition players can't connect!
+### Java Edition players can't connect! {#java-edition-players-cant-connect}
This **should not be** a Geyser problem. Geyser does not modify server behavior. Floodgate does modify the login structure, but only for Bedrock players.
Contact your hosting provider or look elsewhere for fixing this connection issue.
-### Connecting fails after updating Geyser
+### Connecting fails after updating Geyser {#connecting-fails-after-updating-geyser}
If this occurred after updating a plugin version of Geyser, ensure that you shut off your server, swapped the Geyser jar, and then started up your server.
Incase you reset your configuration file, check out the [setup guide](/geyser/setup/) again.
-### There are errors in my console!
+### There are errors in my console! {#there-are-errors-in-my-console}
Please read through the [common issues page](/geyser/common-issues/). If there is another error not documented there, join us on our [Discord](https://discord.geysermc.org).
-### Try restarting the server and game
+### Try restarting the server and game {#try-restarting-the-server-and-game}
Especially on mobile devices, sometimes just restarting Minecraft fixes the issue.
-### Is it the server or the client?
+### Is it the server or the client? {#is-it-the-server-or-the-client}
Run your Java server IP and Bedrock address here: https://mcsrvstat.us/. It's a great way of determining if the server is reachable in the first place.
Additionally, check if you can see a connection attempt in the server console. If you can't, it's likely a network issue.
@@ -45,38 +45,38 @@ For console players specifically: If only they can't join, while other Bedrock p
# General troubleshooting steps
-### Ensure you're connecting on the right IP and Port
+### Ensure you're connecting on the right IP and Port {#ensure-youre-connecting-on-the-right-ip-and-port}
You should be connecting with the Java server IP and the Bedrock port (set in the Geyser config). If you port forwarded 19132, for example, you should specify port 19132 when connecting from Bedrock.
-### I'm using a hosting provider or VPS!
+### I'm using a hosting provider or VPS! {#im-using-a-hosting-provider-or-vps}
Please read [this page on supported hosting providers](/geyser/supported-hosting-providers/) to see if there are extra configuration steps required for your hosting or server provider.
Some VPS/KVM providers may require further setup, such as OVH, SoYouStart, and Oracle Cloud. Please read this [note](/geyser/port-forwarding/#issues-with-specific-vpskvm-providers) for more information.
-### Issues using Docker or Pterodactyl
+### Issues using Docker or Pterodactyl {#issues-using-docker-or-pterodactyl}
Make sure you assign the port to pterodactyl, and on docker, to the docker compose file. See our [port-forwarding](/geyser/port-forwarding/#using-docker-or-pterodactyl) page for fixes.
# Port forwarding issues
Your server does need to be port forwarded to allow connections from outside the local network. See [our port-forwarding guide](/geyser/port-forwarding/) for more information.
-### Using TCP in DNS options/port forwarding instead of UDP
+### Using TCP in DNS options/port forwarding instead of UDP {#using-tcp-in-dns-optionsport-forwarding-instead-of-udp}
Minecraft: Java Edition uses TCP for connecting; Minecraft: Bedrock Edition uses UDP. Port forwarding your Bedrock Edition port with only TCP will not work, it has to be UDP. Forwarding your Bedrock Edition port with `TCP/UDP` (both protocols) should also work but is not recommended unless Java Edition and Bedrock Edition is sharing the same port.
-### Bedrock port is less than 10000
+### Bedrock port is less than 10000 {#bedrock-port-is-less-than-10000}
Historically, having a Bedrock port that is a lower number will cause issues. Setting it to 10000 or above seems safe.
-### Bedrock players can connect *after* hitting the server on a TCP port (e.g. on Java or a website on the same server), OR only people who also play on Java Edition can join from Geyser
+### Bedrock players can connect *after* hitting the server on a TCP port (e.g. on Java or a website on the same server), OR only people who also play on Java Edition can join from Geyser {#bedrock-players-can-connect-after-hitting-the-server-on-a-tcp-port-eg-on-java-or-a-website-on-the-same-server-or-only-people-who-also-play-on-java-edition-can-join-from-geyser}
This is likely a firewall issue on your server. Try the following workaround:
Attempt to connect to the Bedrock IP and port through a web browser - for example, `http://test.geysermc.org:19132`. It won't work, but then try connecting through Bedrock, and it should work.
Specific host fixes for OVH/SoYouStart can be found [here](/geyser/port-forwarding/#issues-with-specific-vpskvm-providers).
-### Changing the `bedrock` `address` in the Geyser config.
+### Changing the `bedrock` `address` in the Geyser config. {#changing-the-bedrock-address-in-the-geyser-config}
Except for a few specific hosting providers, you generally do not need to change this part of the Geyser config.
However, in rare instances, it does fix issues - for example, when Windows has multiple network adapters (check by running `ipconfig` in cmd),
@@ -84,13 +84,13 @@ it can help to set the `address` to the local IP of the adapter you want to use.
# Using a hosting provider or other location
-### Pterodactyl
+### Pterodactyl {#pterodactyl}
If you get this error while using the Pterodactyl Panel, try editing the Geyser config and changing the port to something besides `19132` (e.g. `25566`).
# Hosting Geyser on another computer on the same network
-### Can only connect from the same computer and not anywhere else
+### Can only connect from the same computer and not anywhere else {#can-only-connect-from-the-same-computer-and-not-anywhere-else}
Your firewall is likely in the way. Try adding an exception to Java, or disable the firewall for testing purposes.
@@ -100,7 +100,7 @@ Minecraft offers a vanilla Bedrock server [here](https://www.minecraft.net/downl
# Using Geyser on the same computer
-### Windows 10/11
+### Windows 10/11 {#windows-1011}
_This only affects people trying to join Geyser from Windows 10/11 Edition with Geyser hosted on the same computer._
diff --git a/docs/geyser/forms.md b/docs/geyser/forms.md
index 62ba37b..0672acd 100644
--- a/docs/geyser/forms.md
+++ b/docs/geyser/forms.md
@@ -17,7 +17,7 @@ We'll discuss them one by one starting with the easiest and ending with the leas
After that, you get an overview of every single component.
Then we'll talk about sending the form, receiving a response and doing advanced stuff.
-## ModalForm
+## ModalForm {#modalform}
While this is the easiest form type it's also the least customisable.
You have a title, description (content) and two buttons.
@@ -34,7 +34,7 @@ ModalForm.builder()
.button2("Button 2")
```
-## SimpleForm
+## SimpleForm {#simpleform}
While this one is less easy than ModalForm is, it also has more customizability.
It's still limited to a title, content and buttons, but these buttons can also have images and do not have a minimum and maximum of two.
@@ -51,7 +51,7 @@ SimpleForm.builder()
.button("Button with path image", FormImage.Type.PATH, "textures/i/glyph_world_template.png")
```
-## CustomForm
+## CustomForm {#customform}
While the CustomForm is the last one on our list (and thus the least easy one), it also has the greatest customizability.
This form exists of a title, content and a list of different components e.g. label, slider and input.
@@ -70,7 +70,7 @@ CustomForm.builder()
.slider("Text", 0, 10, 1, 5)
```
-## Sending a form
+## Sending a form {#sending-a-form}
After you decided which form type you want to use and finished filling in the actual content, it's time to send the Form to the Bedrock player.
You can do that by calling the API and send a form to the player's UUID and the form:
@@ -93,7 +93,7 @@ player.sendForm(
);
```
-## Receiving a response from the client
+## Receiving a response from the client {#receiving-a-response-from-the-client}
It's nice and all that we can send forms to a client, but we also want to be able to get a response from a client and being able to handle them.
We can do that using one (or multiple) result handers. The most used result handlers are: `validResultHandler(BiConsumer