#(xxyyxx) Citizens2 causes sleep action bar message to spam false numbers
26 messages · Page 1 of 1 (latest)
(xxyyxx) Citizens2 causes sleep action bar message to spam false numbers
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.
Thread is now a Bug thread. This indicates a core code bug that a developer must resolved, not an error message or other support topic. Please do not misuse the Bug label. Use </helpthread:1028674284870180883> to switch the thread back to a normal help thread if you are not 100% confident it is a code bug.
Not sure if this is a problem with the plugin itself or my config? i don't think its the config though because i used only the provided commands to make my npcs
Seems like it's something on our end
also, i think using something like 51% percentsleep gamerule causes the night to skip even if not enough real players are sleeping
@woeful mango need your config.yml
The npc is being added to the player list
Sometimes can happen with other plugins - does this happen with only citizens on server
@woeful mango
I dont use any other npc plugins
I mean any other plugins, not just other npc plugins
Ah my bad. I am using a custom suite of 25+ plugins (made by myself) but im not sure how any of these would cause the npcs to be added to player list?
Is there anything specifically i should look out for?
If you can tell me any known conflicts that could cause this issue, it’d help me narrow it down to potential causes
@woeful mango maybe just try once with no other plugins? might help narrow it down
@full apex good news. I have confirmed that this is an issue with sentinel, not citizens
removing the sentinel plugin fixes this issue
@woeful mango
Thread was closed either automatically by timeout or by the Discord manual close button. If closing was intentional, please use </resolved:1028673926114594866> or </invalid:1028673926898909185>.
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.)
@woeful mango