Elytrium / Elytrium/LimboFilter

[BUG] Geyser standalone

Open
#107 1 comment 0 reactions 0 assignees View on GitHub
bug
Dominant language
Java
Stars
172
Forks
52
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
If you use standalone Geyser and connect through it to the server, you don't get the code sheet (although messages and the rest of the plugin work fine). However, if you don't join via standalone Geyser and instead connect directly through the proxy (Velocity with geyser as a plugin), you do get the sheet with the code, and everything works correctly.
(I edited to include this second part for clarification.)

**To Reproduce**
1. Create a geyser standalone
2. Connect from it with bedrock

**Expected behavior**
The sheet should appear in your hand like when you enter the server and you have geyser.jar in velocity.

**Screenshots**
https://imgur.com/a/hTOYg0M

**Server Info (please complete the following information):**
I have the limbo plugins taken from this discord message from "Nugget": https://discord.com/channels/775778822334709780/869912613696442439/1354471193914245287
LimboApi is a bit bellow with 2/3 messages.

[velocity-dump-2025-04-05-14-45-52.json](https://github.com/user-attachments/files/19615163/velocity-dump-2025-04-05-14-45-52.json)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the standalone Geyser path with Bedrock and compare it with connecting through Velocity with Geyser as a plugin. Use the attached velocity dump and the listed Limbo plugin setup while tracing why the code sheet is absent; done means the sheet appears in the player's hand in standalone mode as it does through Velocity.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.