#(Mocsek) Why is it when i try to create an npc in 1.19.3 it says "That is not a valid number"?

1 messages · Page 1 of 1 (latest)

lost wedgeBOT
#

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>

proper fern
#

!logs

lavish yokeBOT
# proper fern !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.

proper fern
#

!checklog

lavish yokeBOT
#
Server Version

Paper version git-Paper-448 (MC: 1.19.3)-- (:warning: Outdated build, behind by 71... Current build is 519)

Plugin Version(s)

Citizens v2.0.30-SNAPSHOT (build 2824) -- (:warning:Outdated build, behind by 235)

Checked For

@proper fern

UUID Version

0 (:triangular_flag_on_post: Hacked or Invalid ID)

Java Version

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

Other Noteworthy Plugin(s)

WorldGuard v7.0.7+216b061

Problematic Plugin(s)

PlugMan v2.1.7 - :warning: Plugin Managers are dangerous and will cause unpredictable issues. Remove it.

Possibly Relevant Plugin(s)

TAB v3.3.2 - This plugin adds Below_Name scoreboards to NPCs.
ViaVersion v4.6.2 - Mixed client vs server versions can sometimes cause packet-related issues.

Potentially Bad Line(s)

[19:30:47] [Server thread/INFO]: Mocsek: Reload complete. :warning: NEVER reload your server. If you change plugin files, you MUST RESTART your server properly.
[19:23:53] [ServerMain/INFO]: Environment: authHost='https://authserver.mojang.com/', accountsHost='https://api.mojang.com/', sessionHost='https://api.minehut.com/mitm/proxy', servicesHost='https://api.minecraftservices.com/', name='properties' :warning: Free server providers cannot be properly supported. Refer to https://wiki.citizensnpcs.co/Frequently_Asked_Questions#I_have_a_free_server_.28Aternos.2C_Minehut.2C_....29_but_there.27s_problems.
Caused by: com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1 path $ :warning: Log contains error messages.

proper fern
#

!patchversions

lavish yokeBOT
# proper fern !patchversions
Info: patchversions

We support only the latest patch-version of Minecraft for any recent main version (and Mojang, Spigot, Paper, etc. all generally also follow the same rule).

"Patch version" means the last number in a version label, for example in 1.18.2, the main version is 1.18, and the patch version is .2.
So if 1.18.2 is the latest patch version, then 1.18.1, and 1.18(.0) are all outdated patch versions, and therefore are unsupported.

Note that we do still support recent older main versions (such as 1.17 and 1.16) so long as you are on the latest patch-version of those main versions (like 1.17.1 and 1.16.5).

proper fern
#

Should update to 1.19.4 and the latest Citizens version

#

And also, never use /reload, it can and will break things - should always properly restart

#

1.19.3 is an outdated unsupported patch-version - is there any reason you can't update?

#

Well, should update then - staying on the latest version is always a good idea

#

Can either make a backup of your server, or download a copy of it and test updating locally

marble craterBOT
#
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.)

#

@halcyon kestrel