Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Player Heads with "profile" item component don't work properly #10776

Closed
Ooogods opened this issue May 23, 2024 · 4 comments
Closed

Player Heads with "profile" item component don't work properly #10776

Ooogods opened this issue May 23, 2024 · 4 comments
Labels
resolution: cannot reproduce Paper team is unable to replicate the issue. type: bug Something doesn't work as it was intended to. version: 1.20.6 Game version 1.20.6

Comments

@Ooogods
Copy link

Ooogods commented May 23, 2024

Expected behavior

When you give yourself a player head with the item component "profile", it should give you the player head with the skin of the indicated component value and the texture should stick with the given player head.

Observed/Actual behavior

The texture is visible in the inventory at first. But whenever you interact with it (place it on the ground, throw the item etc.), some of the player heads lose its skin texture and convert to one of the default skin textures. The issue occurs in some skins but the texture sticks properly for the other ones. I observed that which skins are sticking is inconsistent across my two servers.

Steps/models to reproduce

  1. Use a give command to get a player head with a profile component (for ex. /give @p minecraft:player_head[minecraft:profile="test"])
  2. When you get the skull, the skin should be visible.
  3. Throw the item on the ground, or place it.
  4. The correct skin disappears and converts to one of the default skins.
  5. If it works properly, try with another skin name.

Plugin and Datapack List

No plugins.
No datapacks.

Paper version

This server is running Paper version 1.20.6-90-master@b149584 (2024-05-22T17:30:13Z) (Implementing API version 1.20.6-R0.1-SNAPSHOT)
You are running the latest version

Other

I also tested it on a spigot server if it's an important detail. It doesn't work properly on Spigot too but the problem is not exactly the same and it's highly inconsistent.

@Ooogods Ooogods added status: needs triage type: bug Something doesn't work as it was intended to. labels May 23, 2024
@papermc-sniffer papermc-sniffer bot added the version: 1.20.6 Game version 1.20.6 label May 23, 2024
@kennytv
Copy link
Member

kennytv commented May 23, 2024

Cannot reproduce

@lynxplay
Copy link
Contributor

lynxplay commented Jun 1, 2024

Closing this as no further comment regarding replication steps was provided.
If you have working replication steps on latest paper without plugins, post them here and we can reopen this 👍

@lynxplay lynxplay closed this as not planned Won't fix, can't repro, duplicate, stale Jun 1, 2024
@lynxplay lynxplay added resolution: cannot reproduce Paper team is unable to replicate the issue. and removed status: needs triage labels Jun 1, 2024
@Xenapte
Copy link

Xenapte commented Jul 17, 2024

I can confirm this on my side. It seems to be a vanilla issue caused by slow internet connections; my server has bad internet speed to mojang's skin servers - the skin also failed to generate for me until I tried using a proxy to speed it up. Somehow this wasn't a problem before 1.20.6.

@electronicboy
Copy link
Member

This is generally a spigot issue, you need to call update() on the profile and then create the itemstack and do whatever in the response if you want to ensure that you properly populate the skull info, otherwise, spigot having made that async means that you enter a pretty tight race condition

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
resolution: cannot reproduce Paper team is unable to replicate the issue. type: bug Something doesn't work as it was intended to. version: 1.20.6 Game version 1.20.6
Projects
Status: Invalid
Development

No branches or pull requests

5 participants