#(Darwin) strange error on .to_cuboid[]
56 messages · Page 1 of 1 (latest)
(Darwin) strange error on .to_cuboid[]
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've been here long enough to know better than to make threads like this
you know what information we need
have no idea
what do you mean?
How do you replicate this?
If i'm on a blank testing server, how could i trigger it?
It's just a random bug. I have no idea how to replicate it
It's worked fine all day and now just poof. And it's not
The only thing a can tell, samosbor is not a default world
- createworld samosbor generate_structures:false worldtype:FLAT "settings:{"structures":{"structures":{}},"layers":[{"block":"minecraft:air","height":1}],"biome":"minecraft:samosbor_void","flat_world_options":{}}"
It's just a random bug. I have no idea how to replicate it
then it's problem solving time. What does the error message say?
(it's literally what you copied above)
World unloaded?
Does this problem occur with any other worlds or just this one?
I bet it will fix itself after restart
But it should be addressed, since it's a critical thing
as you can see in debug
it's impossible to 'address' without having any consistent way to replicate
it doesn't matter when creating cuboid, but chunks are loaded
everything has a cause
as in, it'll still through the error if you're in the world?
This happened after I made samosbor world not default
So I think it's partially unloaded somehow
Maybe after several destroy adjusts
yes
by happened I mean it worked even with non default world. but suddenly stopped after several uses
huh?
<location[-1,1,0,samosbor].to_cuboid[<location[-12,5,-11,samosbor]>]>
works fine
with
-1,1,0,samosbor -1,0,1,samosbor 0,0,0,samosbor
it's working
but with -1,0,0,samosbor it's not
how is this possible?
I restarted the server, and as I said, it's working now
https://paste.denizenscript.com/View/124135
Well, there's very little we could do without a way to replicate the issue - did you create the world in the same server run you tried using that tag in maybe? and then after a restart it works fine?
I triggered it several times on a test server
but I still don't understand why this happens
https://paste.denizenscript.com/View/124137
https://paste.denizenscript.com/View/124138
Cuboidtag doesn't even require world to exist
Tag parse results for <location[0,0,0,lasagna].to_cuboid[<location[5,5,5,lasagna]>]>: https://paste.denizenscript.com/View/124139
cu@lasagna,0,0,0,5,5,5
@analog rover <location[-1,0,0,samosbor].to_cuboid[<location[-12,5,-11,samosbor]>]>
Tag parse results for <location[-1,0,0,samosbor].to_cuboid[<location[-12,5,-11,samosbor]>]>: https://paste.denizenscript.com/View/124141
cu@samosbor,-12,0,-11,-1,5,0

Yeah. How world can be unloaded if it doesn't have to exist
You can see in my logs
I send in random order this commands
` - adjust <world[test]> destroy
- createworld test generator:denizen:void
- narrate <location[0,0,0,test].to_cuboid[<location[5,5,5,test]>]>`
and error just suddenly appears sometimes. And sometimes does not
But if it appeared one time, this tag will be broken until /ex reload
Is it specifically with to_cuboid? what if you just construct a location?
Steps to reproduce:
- createworld test generator:denizen:void
- narrate <location[0,0,0,test].to_cuboid[<location[5,5,5,test]>]>
if no error
- adjust <world[test]> destroy
repeat
Content of Server Log Paste #124162: Unnamed Server Log Paste... pasted 2024/06/27 23:24:15 UTC-07:00, Paste length: 52357 characters across 484 lines, Content: [14:18:32] [ServerMain/INFO]: Environment: Environment[sessionHost=https://sessionserver.mojang.com,...
More investigation:
When in bugged state
<location[1,1,1,test].to_cuboid[<location[5,5,5,test]>]> won't work
<location[1,1,1,test].to_cuboid[5,5,5,test]> will work
Also
<location[1,1,1,test].to_cuboid[<location[6,6,6,test]>]> works
I can't understand this bug. Is there is something wrong with Static Tag Processor?
@sullen violet these errors seem to happen because the Bukkit Location has an empty reference to a world (but not null), I.e. it had a world instance that was GCed away? might be static tag processing caching a location instance that later loses it's world?
there's a whole dedicated system to catch and fix that
it looks like spigot actively fucked that system in an update at some point with an unloadedness check that will have to be aggressively bypassed now :(
should be fixed ref #commit-log
(#commit-log message)
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.)
@bronze shuttle
looks like it's stable now 🙀