Quark

Quark

143M Downloads

[1.19.2] Cannot Enter World With Blazeandcave Advancement Pack 1.15.3

Lucipo opened this issue ยท 5 comments

commented

Crash log: https://pastebin.com/VxnydwX7

MC Version: 1.19.2

Quark version: Quark-3.4-389

Issue: Any world that has the Bacap datapack ( https://www.planetminecraft.com/data-pack/blazeandcave-s-advancements-pack-1-12/ ) installed within it gives the errors in the log near the bottom as soon as it starts to load advancements. This did not happen on previous versions, it only started once I updated Quark to the latest version (about 3 weeks outdated beforehand)

Loading regular worlds works fine and removing quark lets me load worlds w/ bacap datapack enabled.

commented

Using Quark-3.4-388 lets me enter the world, mustve been something that changed between versions

commented

That seems to be caused by an advancement added by that datapack. It is somehow adding one with a trigger on block which has an empty block set of valid target blocks. This is wrong bur also Quark is not accounting for a possible null here. I'll fix but datapack author should probably fix too altho vanilla allows that so its more of a logic issue on their end

commented

The log doesn't say unfortunately I only see there was a trigger which targeted a null set of blocks (maybe was an empty tag I haven't checked). Fix will be next update somewhat soon

commented

That seems to be caused by an advancement added by that datapack. It is somehow adding one with a trigger on block which has an empty block set of valid target blocks. This is wrong bur also Quark is not accounting for a possible null here. I'll fix but datapack author should probably fix too altho vanilla allows that so its more of a logic issue on their end

Hi, I'm part of the Blaze and Cave community and do you perhaps know which advancement / file causes the issue?
It would cut out a lot of work tracking it down.
The datapack was only intended to run in vanilla and fabric/quilt, but we are open to fix compatibility issues if possible.

commented

should have been taken care of in new update