PaperMC / PaperMC/Velocity

Spectator mode has errors when using 1.17.1 server under build#454

Open
#1,470 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

type: bug
Dominant language
Java
Stars
2.3k
Forks
960
Avg merge
5d 10h
Merged PRs (30d)
2

Description

Expected Behavior

When using velocity to connect to the backend server, in spectator mode, you can use the spectator mode to pass through blocks and use the inventory to quickly teleport normally.

Actual Behavior

In spectator mode, you cannot pass through blocks or use the inventory to fast teleport.

Steps to Reproduce

With velocity build#454, 1.17.1fabric server, and Fabric Loader 0.14.25, use the corresponding client version to enter the server, switch to spectator mode, try to pass through the block, and try to use the inventory to quickly teleport when there are multiple people on the server. These can be reproduced.

Plugin List

without any plugin

Velocity Version

velocity 3.4.0 build#454

Additional Information

I suspect that the game mode data on the server side of the old version (1.17.1) was not forwarded to the client by velocity normally.
In addition, my issue is machine translated, I apologize for the difficulty in reading.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with Velocity build#454, a 1.17.1 Fabric server, Fabric Loader 0.14.25, and the matching client. Trace how spectator-mode data is forwarded between the proxy and the older backend, then verify that passing through blocks and inventory-based teleporting work normally with multiple players.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, networking
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.