-
-
Notifications
You must be signed in to change notification settings - Fork 5
Null response without an error #4
Comments
What kind of schematic are you using? MCEdit or Sponge? |
I tried both types and also renamed them both to .schematic |
Are you able to send a screenshot of the schematic open in NBTExplorer? |
Schematic 1 is a Sponge schematic, try loading it using |
Yes the first one is Sponge, the second one had a .nbt thing at the end. Ill try the new SpongeSchematic()#read later. Thanks |
How exactly did you know it didn't work? |
When I read the nbt via fileinputstream, it caused my whole completable future to exit und stop working, even my debug messages after the loop wouldn't print out. |
I will need the schematics to reproduce this. |
Yes, i downloaded a random schematic, here it is: https://workupload.com/file/RNfUqkkMXZc |
Okay, I'll look into this sometime tomorrow. |
Thanks ^^ |
The schematic you provided has loaded on my machine, but the block palette is slightly off. |
Ah okay, I have no more ideas why it isn't loading and exiting my whole completable furutre. Do you maybe have an idea where the error which I send you is coming from? |
It may be caused by the fact you are not on the 1.18 branch of Minestom. |
That could be true, I'm using the latest version of the main branch (-SNAPSHOT) |
Any news on the bug? |
I'm not sure, I was able to read and build the schematic perfectly fine. I did discover a different bug but it was unrelated to your issue. |
Describe the bug
So when you trying to load up a schematic via Scaffolding.fromFile or via the FileInputStream the response is always null. There is no exception too which would be thrown. BTW my entire completeable future is beeing closed but i have no idea what why and whats caused it...
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It should throw an error and should load when the schematics are right, load them up.
Screenshots
1.
2. (Debug)
(- Please ask for a full code snippet)
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: