#(AstroSquared) Destroying an NPC using the Dev API causes a warning

58 messages · Page 1 of 1 (latest)

deft bloom
#

I've been using npc.destory() to remove NPCs, but every time, it causes this error: (see attacted file). Is this a bug, or am I doing something wrong?

📎 error.txt
timber spruceBOT
#

(AstroSquared) Destroying an NPC using the Dev API causes a warning

timber spruceBOT
#

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>

long sundial
#

i think this is in our faq

#

!faq

final mulchBOT
long sundial
#

sec

#

yeah

#

is this what you meant? or do you mean removing them actively?

deft bloom
#

this doesn't happen when i shut down the server

long sundial
#

can you provide your code and a startup log?

#

!logs

final mulchBOT
# long sundial !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.

deft bloom
shrewd skiffBOT
#
Changed to Bug

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.

slender beacon
#

I’ll try and fix this soon

#

If you need a temporary workaround just disable glowing prior to destroy()

slender beacon
final mulchBOT
# slender beacon !logcheck https://paste.denizenscript.com/View/105948
Log Check Results
Server Version

Paper version git-Paper-387 (MC: 1.18.2)-- (Outdated build, behind by 1... Current build is 388)

Plugin Version(s)

Citizens v2.0.30-SNAPSHOT (build 2742) -- (:warning:Outdated build, behind by 159)

Checked For

@slender beacon

UUID Version

4 (:white_check_mark: Online)

Java Version

17 or newer (based on stack trace content) :white_check_mark:

Other Noteworthy Plugin(s)

ProtocolLib v4.8.0

Possibly Relevant Plugin(s)

ViaVersion v4.4.2 - Mixed client vs server versions can sometimes cause packet-related issues.
FastAsyncWorldEdit v2.4.10-SNAPSHOT-303;983e440 - This plugin has been known to break the plugin load order on many servers, due to usage of the 'loadbefore' directive in its 'plugin.yml'.

slender beacon
#

can you try updating first?

#

@deft bloom

shrewd skiffBOT
#
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.)

#

@deft bloom

deft bloom
#

I just woke up

deft bloom
#

also, i don't know why this is triggering as i never enabled glowing on any npcs and there are no mentions of setGlowing in my project

slender beacon
#

can you post the updated error then?

slender beacon
#

@deft bloom

deft bloom
#

I’ll be able to check after school

slender beacon
#

try new build

shrewd skiffBOT
#
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.)

#

@deft bloom

deft bloom
#

this is the closest thing that i found in my project relating to name visibility

image.png
slender beacon
#

So something in your code is breaking citizens

#

Are you despawning the entity during an event?

deft bloom
slender beacon
#

Ahh that’s probably why

slender beacon
#

update to new build

shrewd skiffBOT
#
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.)

#

@deft bloom

deft bloom
#

thanks, it works now without errors

shrewd skiffBOT
#
Resolved

Thread closed as resolved.

shrewd skiffBOT
#
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.)

#

@deft bloom

#
Resolved

Thread closed as resolved.

deft bloom
#

i already closed it?

white barn
#

Yeah, it was reopened by someone and I used the wrong command - meant to re-close it

deft bloom
#

okay