#(Insom96) CIT-Number in Tablist and over NPC heads

35 messages · Page 1 of 1 (latest)

sand eagle
#

I have the problem that every NPC has a unique CIT-Number. They are always seen in tablist and/or over every single NPC head. How can I disable this?

cloud stormBOT
#

(Insom96) CIT-Number in Tablist and over NPC heads

cloud stormBOT
#

Hi I'm AutoThreadBot! Don't mind me, I'll just be adding the helper team to this thread so they can see it. A human will get to you soon.
You can block this bot if you don't want to see these messages, I won't mind.
<@&525394568410038282>

austere wing
#

!update

smoky lintelBOT
#
Update Paper

Paper is a higher-performance alternative to Spigot that is 100% compatible with the equivalent Spigot version. It's much easier to update than Spigot itself, and carries a lot of performance and quality-of-life benefits.

Latest Paper builds are at https://papermc.io/downloads.

(If you would prefer to use a Spigot build, refer to !update spigot).

austere wing
#

but if it doesn't fix the issue, can you paste a startup log please?

#

!Logs

smoky lintelBOT
# austere wing !Logs
Info: logs

Please post your full latest log file.

Background Info: One of the most helpful tools to identifying the source of a problem is your server logs file! Logs contain all sorts of important information like server and plugin versions, any error messages, and a lot more important information (More Info).

How To: Your log can be found in the logs folder within your server folder. The most recent log is a text file labeled latest.log. To get help using these logs, please open that file in a text editor and copy all of the text, then open https://paste.denizenscript.com/New/Log and paste the text into the box on the page. Then click "Submit" and copy the URL and paste that back into this channel.

Please do not upload the file to Discord or to other pastebin services, use the log pastebin linked above.

sand eagle
#

git-Paper-328 MC 1.19.3
latest working citizens version for 1.19.3 installed

austere wing
#

can take a look at logs, but if you have the latest versions then you may need to update to 1.19.4 - that's a fixed bug we've patched already

sand eagle
#

ok but I only have 1.19.3 on my servers and on spigotmc stands that this will not work

weary socket
#

If you don’t want to provide logs or update, can’t help sorry

inner valveBOT
#
Thread Closing Reminder

Has your issue been resolved, or your question been answered?
If so, please use the </resolved:1028673926114594866> command to close your thread.
Or </invalid:1028673926898909185> if it's not possible to resolve.

If not yet resolved, please reply below to tell us what you still need.

(Note that if there is no reply for a few days, this thread will eventually close itself.)

#

@sand eagle

sand eagle
#

@weary socket if u are not interested in reading what i wrote last. I ended with a question whats not answered yet

#

@austere wing started with excellent support and u start with your own type of let me call it „special“ support. What a nice way to shutdown ur supportlevel

weary socket
#

@sand eagle I read that you’re using 1.19.3, so I guess I’ll wait for logs then?

sand eagle
#

No I asked if the bug is fixed if I use the newest version on my 1.19.3 server even if it says that its not supported

weary socket
#

@sand eagle citizens does not support 1.19.3

austere wing
inner valveBOT
#
Thread Closing Reminder

Has your issue been resolved, or your question been answered?
If so, please use the </resolved:1028673926114594866> command to close your thread.
Or </invalid:1028673926898909185> if it's not possible to resolve.

If not yet resolved, please reply below to tell us what you still need.

(Note that if there is no reply for a few days, this thread will eventually close itself.)

#

@sand eagle

sand eagle
#

U can close the ticket

chrome frigate
#

You can close it, please read the message above

inner valveBOT
#
Thread Closing Reminder

Has your issue been resolved, or your question been answered?
If so, please use the </resolved:1028673926114594866> command to close your thread.
Or </invalid:1028673926898909185> if it's not possible to resolve.

If not yet resolved, please reply below to tell us what you still need.

(Note that if there is no reply for a few days, this thread will eventually close itself.)

#

@sand eagle