#(Ruben8383848) The lookclose perplayer command isnt working for me
60 messages · Page 1 of 1 (latest)
(Ruben8383848) The lookclose perplayer command isnt working for me
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>
!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.
@hollow heron
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.)
@hollow heron
Can this tread please stay open. I didnt try yet because I didnt have the time
Thread closed as invalid.
Wait thats my fault
Thread was manually reopened by @hollow heron.
.
We need your logs
!logcheck
Incorrect upload of log reuploaded to pastebin at https://paste.denizenscript.com/View/107578
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.
please follow the instructions
Content of Server Log Paste #107579: Unnamed Server Log Paste... pasted 2023/03/19 07:07:09 UTC-07:00, Paste length: 180028 characters across 1743 lines, Content: [00:00:16] [Craft Scheduler Thread - 1108 - BuycraftX/INFO]: [BuycraftX] Fetching all due players......
Is this good
Content of Server Log Paste #107579: Unnamed Server Log Paste... pasted 2023/03/19 07:07:09 UTC-07:00, Paste length: 180028 characters across 1743 lines, Content: [00:00:16] [Craft Scheduler Thread - 1108 - BuycraftX/INFO]: [BuycraftX] Fetching all due players......
@hollow heron no, you didn't post a startup log
Ok sorry it should work now
Content of Server Log Paste #107581: Unnamed Server Log Paste... pasted 2023/03/19 07:32:50 UTC-07:00, Paste length: 28859 characters across 281 lines, Content: [14:31:25] [ServerMain/INFO]: Building unoptimized datafixer[14:31:26] [ServerMain/INFO]: Environmen...
Content of Server Log Paste #107581: Unnamed Server Log Paste... pasted 2023/03/19 07:32:50 UTC-07:00, Paste length: 28859 characters across 281 lines, Content: [14:31:25] [ServerMain/INFO]: Building unoptimized datafixer[14:31:26] [ServerMain/INFO]: Environmen...
Paper version git-Paper-"4da844f" (MC: 1.19.3)
Citizens v2.0.30-SNAPSHOT (build 2960) -- (:warning:Outdated build, behind by 23)
@quasi plume
WorldGuard v7.0.7+216b061
Geyser-Spigot v2.1.0-SNAPSHOT - Bedrock clients are unsupportable. Please do all testing with a Java Edition client.
floodgate v2.2.0-SNAPSHOT (b74-4f36112)
[14:32:00] [Craft Scheduler Thread - 4 - DecentHolograms/WARN]: Caused by: while parsing a block mapping :warning: Log contains error messages.
@hollow heron you need protocollib installed
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.)
@hollow heron
Ok thanks
Thread closed as resolved.
I have
Thread was manually reopened by @hollow heron.
It still doesnt work
@hollow heron can you post your logs and a video of you doing it
@hollow heron you didn't type /npc look
!logcheck
Incorrect upload of log reuploaded to pastebin at https://paste.denizenscript.com/View/108122
Paper version git-Paper-"d5abb94" (MC: 1.19.4)
Citizens v2.0.31-SNAPSHOT (build 3002) -- (Outdated build, behind by 2)
@quasi plume
4 (:white_check_mark: Online)
WorldGuard v7.0.7+216b061, ProtocolLib v5.0.0-SNAPSHOT-b616
Geyser-Spigot v2.1.0-SNAPSHOT - Bedrock clients are unsupportable. Please do all testing with a Java Edition client.
floodgate v2.2.0-SNAPSHOT (b74-4f36112)
ViaVersion v4.6.2 - Mixed client vs server versions can sometimes cause packet-related issues.
[13:31:57] [Server thread/ERROR]: [Essentials] You are running an unsupported server version! :warning: Log contains error messages.
Ok thank you! Have a nice day !
@hollow heron so, it's working?
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.)
@hollow heron