stoupy51 / stardustfragment Goto Github PK

Is it implemented, planned or does not align with project philosophy?

I tried to add Stardust Fragment to a Fabric server alongside a few other datapacks (Mechanization, SimplEnergy and TCC). Both Stardust Fragment and SimplEnergy failed to load. I had the resource pack installed, but that wasn't the issue. The book, items and blocks were simply not working.

I also tested it in Vanilla with nothing but Stardust Fragment (and the resource pack) installed and it also did not work. I'm given a Written Book that says * Invalid book tag * when I open it. Although the datapack says in chat "Welcome and Thank you for using Stardust Fragment", it doesn't seem to be working.

When I check the log (full log: https://mclo.gs/VciBrgL), the following lines refer to the datapack. Note that SimplEnergy isn't installed, the only datapack is StardustFragment:

[10:52:00] [Render thread/WARN]: Found loot table element validation problem in {loot_tables:stardust:entities/celestial_dimension}.pools[0].entries[2]: Unknown loot table called simplenergy:i/simplunium_ingot
[10:52:00] [Render thread/WARN]: Found loot table element validation problem in {loot_tables:stardust:cave_base}.pools[0].entries[8]: Unknown loot table called simplenergy:i/simplunium_ingot
[10:52:00] [Render thread/WARN]: Found loot table element validation problem in {loot_tables:stardust:abandonned_cave_house}.pools[0].entries[6]: Unknown loot table called simplenergy:i/simplunium_ingot
[10:52:00] [Render thread/WARN]: Found loot table element validation problem in {loot_tables:stardust:cave_base}.pools[0].entries[9]: Unknown loot table called crazy_adventure:i/uranium_ingot
[10:52:00] [Render thread/WARN]: Found loot table element validation problem in {loot_tables:stardust:abandonned_cave_house}.pools[0].entries[9]: Unknown loot table called crazy_adventure:i/uranium_ingot
[10:52:00] [Render thread/INFO]: Loaded 7 recipes
[10:52:00] [Render thread/ERROR]: Couldn't load advancement global:stardust_fragment: Task Advancement{parentId=global:simplenergy, display=an@2bc32eaa, rewards=AdvancementRewards{experience=0, loot=[], recipes=[], function=dn$a@2a15e54}, criteria={always=aj@3fcbcea}, requirements=[[always]], sends_telemetry_event=false}
[10:52:00] [Render thread/INFO]: Loaded 1423 advancements
[10:52:00] [Render thread/WARN]: Not all defined tags for registry ResourceKey[minecraft:root / minecraft:block] are present in data pack: simplenergy:air, simplenergy:non_solid, stardust:non_solid

Version:
Stardust.Fragment.Resource.Pack.v3.4.x.zip
MechanizationResourcepack_v4.0.4.zip
Minecraft.v1.19.2

Problem:
Seems to be an issue with item frames.

The Pneumatic Exit-Point and Pneumatic Entry-Point from Mechanization use item frames.
The seeds like diamond seeds, stardust seeds, etc. from Stardust.Fragment also seem to use item frames.

Depending on the ordering of the resource packs, either the Mechanization item frames are replaced with stardust seed textures, or, mechanization item frames are fine, and stardust.fragment seeds are just regular-old item frame textures.

Awesome datapack btw! It's so freaking cool!

In the last public release of Stardust Fragment, if we spam the placement of a seed from stardust (for example, the legendary seed) on the wrong block (a block which isn't a lime concrete for the legendary seed), we can duplicate the seed.