#(mefizo) ????????????

21 messages · Page 1 of 1 (latest)

topaz mortarBOT
#

(mefizo) ????????????

#

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.

hallow breach
#

why

#

Task evwery 1 tick

#

xd

storm wind
#

That's internal workings of Citizens, all of Minecraft itself is based around ticking (running code every tick) - every single entity, mob goal, world, redstone machine, etc. are updated basically every single tick

#

If you are experiencing any actual performance issues, please post a spark report

#

!spark

gaunt grailBOT
# storm wind !spark
Info: spark

The "timings" system within Spigot/Paper is incredibly inaccurate for use with Citizens, and cannot be used to diagnose any issues related to Citizens. It notably blames Citizens for a significant amount of entity-related lag (that isn't in any way caused by Citizens).

For accurate timings, you need a Java profiler. There are a variety of profiler options (WarmRoast, YourKit, VisualVM, ...), but the simplest to use on a Spigot server is a plugin named "Spark" that embeds WarmRoast, which you can find here: https://www.spigotmc.org/resources/spark.57242/.

To get a spark report, type /spark profiler start, then replicate lag issues (for no more than about a minute), then /spark profiler stop, and post the link it gives you.

hallow breach
#

nice shit, plugin for npcs stealng 23% xD

storm wind
#

Timings is entirely inaccurate (for Citizens at least), there's a reason Paper is planning on replacing it

#

^ spark is a more accurate tool for checking these sort of issues, if you can get a spark report we can look into it for you

#

(Spark is what Paper is planning on replacing timings with actually)

hallow breach
#

ok thanks for help

frail epochBOT
#

@hallow breach

Thread Close Blocked

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>.

#

@hallow breach

Thread Close Blocked

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>.

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

#

@hallow breach

hallow breach
#

nie pinguj mnie

#

cwelu