#Getting Server StackTrace
1 messages · Page 1 of 1 (latest)
Thanks for creating a thread! Be patient, and we will answer your question when we are able to. In the meantime...
• Check the FAQ by doing /faq to see if your question is already answered.
• Did you describe your issue thoroughly?
• Are relevant logs attached?
• Is your thread tagged appropriately?
• Ensure you've answered the questions outlined in our Post Guidelines.
When your question is answered, please close it with /close, or click the button. Thank you!
no offense to Paper, but their stack traces are a pain to harvest useful information from
anyways, i see two potential causes:
- ticking player, which could be caused by a huge variety of things (including simple lag), but extremely unlikely by terralith
- block state calls, which are potentially able to be caused by terralith, but the context seems unlikely
either way, i dont know. im not very good with understanding paper's errors. and while its possible terralith is the cause, unless the paper support team has a very good reason to believe so, i think its unlikely
its been a while since i last checked in with Paper's "compatibility politics", so take this next statement with a grain of salt. Paper has always been hostile towards datapacks. its possible that they didnt know what was causing your issue. they saw you had a datapack, and since they "dont support datapacks and """datapacks are bad!!!!!""" ", they just suggested Terralith oculd be the cause
but, again, i am unsure. its possible paper has warmed up to datapacks, and im giving an unfair statement. but its also possible im wrong and terraith is the cause. but i digress; ive been rambling a bit too much for what you need