Blood Magic

Blood Magic

Mods
94M Downloads

1.16.4 - Standard Item Filter not sustaining amounts.

Dracious opened this issue ยท 1 comments

commented

Issue Description:

I created my own custom modpack using the create mod, and I also threw blood magic in. When I try to input the amount of items I'd like to filter into a Standard Item filter its not keeping the amount I put in. It just reverts to the default blank space.

What happens:

I enter in the amount of items I want to filter, I back out of the filter. Place the filter into my node only to find that the filter didn't keep the amount I entered.

What you expected to happen:

I expected the filter to sustain the item amount I entered.

Steps to reproduce:

  1. Grab a standard item filter
  2. Right click standard item filter in hand place item type you want inside then enter in the amount of items you want to filter.
  3. Exit filter gui, then re-open to check if saved.

Affected Versions (Do not use "latest"):

  • BloodMagic: 3.1.13-39
  • Minecraft: 1.16.5
  • Forge: 36.2.34
commented

Hi, just to check - the GUI for these filters can be a little bit finnicky, so can you confirm that you're following the steps below exactly?

  1. open the GUI for the standard item filter
  2. insert a ghost item into a slot. (this should highlight that slot with a border)
  3. type a number into the # field with the slot still highlighted
  4. close and re-open the filter
  5. either click on the previously selected item, or mouse over it.

the # field will appear empty until you clock on the item you're filtering, then it should change to show the selected value for that field. Similarly, the mouseover text for the filtered item should say 'ghost item amount: 1', and the mouseover text for the filter itself should say 'allow: 1x Stone' (or 'deny:', for whichever values and items you're filtering)

I've just tested this using MC 1.16.4 as it's what i had available, but the same version of Blood Magic, and was unable to recreate this bug. I don't think there were any changes between .4 and .5 that would cause this to happen, but it is possible. I just hope it's either user error or some really arcane cross-mod incompatibility, because i'm not a programmer, just a documenteer-er. :p

If you can recreate this bug while following these steps exactly, please let us know and we'll look into things further.