MCreator Overrides Locked JSON files with mutliple Item States

Started by Mindthemoods on

Topic category: Troubleshooting, bugs, and solutions

Last seen on 20:43, 20. Aug 2024
Joined May 2022
Points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • MCreator plugins:
  • Comments:
MCreator Overrides Locked JSON files with mutliple Item States

I've been trying out the new item states interface to add a visual ammunition cue to some ranged items in MCreator 2023.4- to render the ranged items correctly, I'm locking the mod elements and adding custom display settings to the JSON model. I've done this successfully with other items before, but MCreator doesn't appear to treat the JSON files as locked if the item includes multiple item states, and resets them whenever the mod is compiled. (Not consistently though- sometimes it appears to work as intended?) I'm not entirely sure this is a bug, and long story short, wondering if there's a better way to do this. (Besides just fixing all the JSON files last before exporting).

Hi! Files should be locked…
Tue, 01/02/2024 - 18:56

Hi! Files should be locked when they are locked so this is likely a bug. Would you mind opening a bug report at https://github.com/MCreator/MCreator/issues? But please try to figure out under what circumstances your changes are overwritten. In other words, what steps to take to make locked ME code change

Last seen on 20:43, 20. Aug 2024
Joined May 2022
Points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • MCreator plugins:
  • Comments:
It's strange, but I'm really…
Tue, 01/02/2024 - 19:50

It's strange, but I'm really having trouble replicating it. The locked elements are duplicates of another element, (the first is named energy_blaster, the second is energy_blaster_1, and the third is energy_blaster_2.) Whenever energy_blaster is unlocked, energy_blaster_2 becomes convinced it's unlocked, and reverts to the energy_blaster texture. But using identical naming conventions for identical new elements doesn't produce the same issue. I'm just going to assume it's something weird on my end, but thanks for responding!