GDLauncher
GDLauncher copied to clipboard
gorilla-devs
saving structure nbt not possible using GDL
Describe the bug I got a strange bug which makes it unable to export structures saved via structure blocks into the instance folder. The structure exported gets copied and can be inserted in the same world but no .nbt file is created and an error prompt in the log without any explanation gets printed. i talked before with @Kreezxil in discord and showed him my screen while trying many things out. he encouraged me to make a video about this cause.
To Reproduce Steps to reproduce the behavior:
- I use default path for minecraft instances in the GDL:
From there i can start a clean forge 36.2.8 installation or try my own pack Crashed on Gyrnolia. - Ingame (standard/flat world with cheats) i give myself a structure block via command, place down some vanilla blocks like a cubic 2x2x2 of sand and put sblocks at the volumetric corners: one set to "corner" mode and given a valid namestring like "forest", the other one set to "save" mode and given the same namestring
- hitting DETECT i get a confirmation about the selected area
- hitting SAVE i get a chat prompt "Unable to save structure"
- i go to the instance folder -> saves -> world -> there should be a folder called "generated" in which structures are saved. they are not. This procedure is the same for clean forge installation without any mods or addons and for a pack.
video https://youtu.be/r8w2_TmbZIQ i made a video where i show the steps of "to reproduce" in GDL (modpack & clean forge version) aswell as expected behavior in MultiMC launcher (with modpack). note the timestamps to skip loading times and i am really sorry about my crappy microphone :(
Expected behavior in step 4 should be a positive feedback from saving and step 5 should show a folder with the file of that structure i just exported.
Additional context
- I also tried a clean forge installation + my own pack in the MultiMC Launcher with no problems at all.
- I even removed write protection of all folders in my instance and all subfolders with no success.
- I started GDLauncher as Administrator and launched the instance with full permissions ... with no success.
- I also moved user data path to a clean drive (literally empty) and started clean forge / my pack from there: with no success.
- I reinstalled GDL once and tried all the above again. with no success.
Operating System:
- OS: Windows 10
- Java Version: [e.g. 8/16]
- Minecraft Version: 1.16.5
- Mod Loader: Forge 36.2.8 / 36.2.2 (tried .2 first and then updated with no success)
- GDL 1.1.15.beta-6
maybe related error further down in this github issue they discuss about instance pathes if i read it correctly. but i am not sure if its helpful cause i mostly don't understand what the ppl in this issue are talking about 😅
On a whim, do you have another computer that you can try the scenario on? preferably running the same OS.
Could you try doing this on the vanilla launcher? So we can confirm it’s a GDL bug
to be honest.. i didn't expect this outcome:
on my Laptop (same specs) i can replicate this issue. i had to install the beta-6 version of GDL cause of the forge not installing bug. after testing the structure issue i downgraded GDL to stable version and viola - the error is gone!
after that i tested downgrading GDL on my main pc and it works too.
Could you try doing this on the vanilla launcher? So we can confirm it’s a GDL bug
i kinda confirmed GDL bug by trying it on MultiMC?
to be honest.. i didn't expect this outcome:
on my Laptop (same specs) i can replicate this issue. i had to install the beta-6 version of GDL cause of the forge not installing bug. after testing the structure issue i downgraded GDL to stable version and viola - the error is gone!
after that i tested downgrading GDL on my main pc and it works too.
That’s definitely interesting. @killpowa any guesses on this?
I am facing the same issue; has anybody found a solution other than downgrading the launcher version?
Same Problem in version 1.1.29, im ATLauncher and Curseforge workt it fine
