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

[Bug] NPC Nametag Visibility #1414

Closed
MrSwalbert opened this issue Feb 18, 2018 · 10 comments
Closed

[Bug] NPC Nametag Visibility #1414

MrSwalbert opened this issue Feb 18, 2018 · 10 comments

Comments

@MrSwalbert
Copy link

When you type "/npc name" the nametag is meant to disappear. It doesn't.

@fullwall
Copy link
Member

Can you please post your config?

@MrSwalbert
Copy link
Author

@MrSwalbert
Copy link
Author

I am also using NameTagEdit. Could this be possibly interfering?

@CoffeeAC
Copy link

Im having the same problem and im using ColouredTags (effects tag above you & tablist) im thinking it is interfering

@MrSwalbert
Copy link
Author

MrSwalbert commented Feb 18, 2018

NTE is definitely hooking in as the prefix above the NPC is set to the NTE prefix. The problem I have is that when a player logs out, the NTE prefix disappears from that player's NPC and it resets to a default nametag.

I want to disable the Citizens nametags and use normal holograms.

@JohOply
Copy link

JohOply commented Feb 19, 2018

I have the problem too
I use build 1504

/npc name seems work correctly with non-player type, and if the NPC name is unique
So the bug appear when multiple NPC have same name

Also NPC name stay visible when I use "F1", whereas non-player NPC's name disappear like normal player

@mcmonkey4eva
Copy link
Member

Might be fixed in newest version?
Were some recent related commits.
If it isn't, please reply below and I'll re-open this.

@ygtdmn
Copy link

ygtdmn commented May 10, 2018

It didn't fix. I was using NameTagEdit as well. I removed NameTagEdit but nametags are still showing. Server version: 1.8
@mcmonkey4eva

@mcmonkey4eva
Copy link
Member

@uniodex Update your server. There's no valid reason to run 1.8 on a server... use 1.12.2 latest, and add in backport plugins (ViaBackwards for supporting old clients, there are combat backdaters if you want that to be old style as well, etc.)

@ygtdmn
Copy link

ygtdmn commented May 10, 2018

Well no time to update right now. I will update it in summer after my exams are finished. But since you add 1.8.8 support i thought you will give support for 1.8.8.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants