PaperMC / PaperMC/Paper

Collidable

Open
#11,440 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status: unlikely type: bug version: 1.21.1
Dominant language
Java
Stars
12.7k
Forks
3.5k
Avg merge
3d 13h
Merged PRs (30d)
11

Description

Expected behavior

Using LivingEntity#setCollidable(boolean) should disable or enable collisions with the living entity.

Observed/Actual behavior

When setting collidable to false on Player, it collides with another entity no matter if it is set to false or true.

Steps/models to reproduce
  1. Spawn entity or obtain entity instance
  2. Get player instance
  3. Use setCollidable(false) on the player
  4. Collide with the entity :)
Plugin and Datapack List

[16:52:55 INFO]: Server Plugins (4):
[16:52:55 INFO]: Bukkit Plugins:
[16:52:55 INFO]: - FastAsyncWorldEdit, Multiverse-Core, ServerFramework, VoidGen

Paper version

[16:53:13 INFO]: Checking version, please wait...
[16:53:14 INFO]: This server is running Paper version 1.21.1-99-master@1bc02e6 (2024-09-25T02:41:02Z) (Implementing API version 1.21.1-R0.1-SNAPSHOT)
You are running the latest version
Previous version: 1.21.1-98-9b1ee0d (MC: 1.21.1)

Other

I was doing this when command is issued using Brigadier, though I don't think that could cause any issues.

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 behavior described for LivingEntity#setCollidable(boolean) on Paper 1.21.1-99, using a player and another entity as in the listed steps. Check whether both false and true produce the same collision result, and consider the Brigadier-issued command context noted in the report. Done means false disables the relevant collision and true restores it.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api
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.