(rojer_klass) The Npc stops sitting after restarting the server or updating chunks.
#(rojer_klass) The Npc stops sitting after restarting the server or updating chunks.
steady templeBOT
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>
pastel forge
calm sigilBOT
!logcheck https://paste.denizenscript.com/View/108931
pastel forge
definitely start by updating citizens
night jay
definitely start by updating citizens
Just installed Citizens-2.0.31-b3036 the problem has not disappeared.
calm sigilBOT
+++ Info pluginconflict: https://wiki.citizensnpcs.co/Plugin_Conflict
brave flicker
An easy test would be just, temporarily remove everything but Denizen and Citizens and see if you can still replicate it
(Can use a test server/local copy, ofc)
night jay
An easy test would be just, temporarily remove everything but Denizen and Citize...
Ok, I'll try it.
night jay
An easy test would be just, temporarily remove everything but Denizen and Citize...
No conflicts. The same problem at empty server
and new log for these two plugins
https://paste.denizenscript.com/View/108933
limpid nebula
No conflicts. The same problem at empty server
did it break from sitting during this log, or only after the restart?
also, can you enable debug-mode in Citizens/config.yml and retest and post a log from there
(making sure either way that the log contains the time when it stopped sitting properly)
most sitting failures will output an error via Denizen, but there's also some internal debug as it tries to make sitting happen via the Citizens debugger
night jay
did it break from sitting during this log, or only after the restart?
It broke during this log. I went a long distance from the sitting NPC, and then returned to him and saw that the NPC was standing. Although the plugin believed that he was sitting.
Okay I’ll enable debug-mode latter today and show you logs
night jay
also, can you enable `debug-mode` in `Citizens/config.yml` and retest and post a...
https://paste.denizenscript.com/View/108972
The npc I showed here has an ID 119 "Старец". But this problem is relevant for all sitting NPCs (Although, some (not many) of them work correct).
line 4303 [21:17:36] -> I select the NPC and use commands to stand and sit down to display the sitting animation, cuz when the server started, NPC was standing inside the block as in the photo above.
line 5899 [21:18:27] -> I walked away from the sitting NPC, and when I returned the NPC was "standing" again. And I entered the /npc stand and /npc sit commands again to play the sitting animation. I think there must be a problem somewhere here. Perhaps it appears with the update of the chunk in which the NPC is located.
limpid nebula
https://paste.denizenscript.com/View/108972
The npc I showed here has an ID 119...
so, here's what I can tell you right now
A: Obviously, what you're seeing there is not intended behavior, NPC's shouldn't be standing back up
B: there's nothing in your logs to explain what's gone wrong. All debug looks completely normal, it even spawns a valid seat for the NPC when it loads (line 3845 in that log) and nothing goes wrong when doing so. In fact, that chair never despawns either, according to the log.
C: I tested locally to be safe, tried to build the shape structure and all as you in case it mattered, spawned an NPC, /npc sit, flew away, made sure the chunk unloaded, then flew back
and it's still fine
calm sigilBOT
!checklog https://paste.denizenscript.com/View/108972
limpid nebula
D: you're basically up to date on everything, other than an unusual version of Java and on 1.18.2 (vs I'm on 1.19.4) but I don't really expect either of those two be necessarily at fault (unless there's some new bug with 1.18.2? I doubt it but we don't really actively test for it)
and you're testing without other plugins involved
so... what exactly went wrong is really hard to determine here
Possible theories are
1: 1.18.2 has a bug? Could try updating to 1.19.4
2: something is corrupt related to your Citizens saves / config. You have hundreds of NPCs on that server, so, clearly using a well-worn save file there. Might try resetting configs to see if the result is different?
3: Your world file looks a bit well-worn too, I notice errors in that log related to broken playerdata. There's also possibly gamerules or something. You might see if testing with a blank world makes a difference?
4: Could also try with a reset to spigot/paper configs? Not sure what in them could mess with anything here but it's possible I suppose?
5: Possibly even some combination of those?
basically tldr is, what you're seeing shouldn't happen, and doesn't on a clean server, but there's no obvious reason why, so only thing left available is to try to figure out what part of your server is different from a normal empty server that's causing the change.
If we can find out what difference caused it, we can hopefully work from there to actually fix it. (Or at least to reapply whatever the one actual change needed is to your actual full server)
night jay
Possible theories are
1: 1.18.2 has a bug? Could try updating to 1.19.4
2: somet...
Okay, I get you. Give me some time. I will run all the tests you have listed and try to find out what is the cause of this error. (I doubt about the version, since it was also observed on 1.15.2 (as far as I remember, but it was a long time ago)). It seems to me that the problem may really be hiding in the saves/config and corrupted files of my world. I'll let you know when I get the test result.
Also, I want to note that while I was looking for a solution to this error, I came across 2 people who faced the same problem. But the solution was never found. One of the people wrote about this problem in your discord, but in the citizens channel.
I hope we can find out what is the problem and help others avoid similar situations.
limpid nebula
There was a bug that caused this a few years ago that's since been resolved, so examples of it or threads about it from years ago aren't relevant to a current issue
(if it reappeared it would show in logs, as there's messages for anything like it now)
Actually, one possible case I can think of that might explain it: if your NPC has some other trait on it that is trying to teleport it or unmount or anything
if the NPC is ripped off its seat by a separate trait, that wouldn't be logged directly
night jay
@limpid nebula I have completed all the tests you mentioned. The only test in which the error has disappeared is the change of the paper to a new version (paper-1.19.4-516). Apparently, the problem is in 1.18.2. Either in the Minecraft version itself, or in paper-388 1.18.2
However paper-388 is the latest release for 1.18.2.
I do not know what to do. Switching to another version is very problematic for me.
night jay
There _was_ a bug that caused this a few years ago that's since been resolved, s...
Also, I found that this is fixed through the seletion NPC and the /npc despawn /npc spawn commands. However, this is a temporary solution, since then the problem will come back again.
woeful remnantBOT
@night jay