error

[FurnaceUpgrades] The CanStackItem, CanCombineDroppedItem hook's was unsubscribed due to conflicts with the 'Loottable' plugin

1 hour ago, NHGaming said:

[FurnaceUpgrades] The CanStackItem, CanCombineDroppedItem hook's was unsubscribed due to conflicts with the 'Loottable' plugin

Hey, its not a error, just a warning so, its let you know that its not using furnace upgrades stacks and only using Loottable config Stacks

Everything should work perfectly, ignore that message

so basically now, we are forced to set furnace stack size to 1 in loottable, thats not a fix, thats a workaround. you could do a reverse dictionary check like i showed you and it wont conflict with anything

1 hour ago, tacman1981 said:

so basically now, we are forced to set furnace stack size to 1 in loottable, thats not a fix, thats a workaround. you could do a reverse dictionary check like i showed you and it wont conflict with anything

can you give that info again, i might have missed it

 if (source == null || target == null)
                return null;
                
                if (!_furnacesData.ContainsKey(source.uid.Value) || !_furnacesData.ContainsKey(target.uid.Value))
                {
                    return null;
                }
return false;


this is months old now, I've had zero issues ever since I changed the check into this, obviously I haven't updated since this, because every update since has just broke it again. I haven't updated since December when I made this change and it works perfectly, stopped conflict spam and prevented the items inside furnace from creating new unstackable cooked items. it may need the same check for the mixing table, which is a weird addition for a furnace plugin

6 hours ago, tacman1981 said:

 if (source == null || target == null)
                return null;
                
                if (!_furnacesData.ContainsKey(source.uid.Value) || !_furnacesData.ContainsKey(target.uid.Value))
                {
                    return null;
                }
return false;


this is months old now, I've had zero issues ever since I changed the check into this, obviously I haven't updated since this, because every update since has just broke it again. I haven't updated since December when I made this change and it works perfectly, stopped conflict spam and prevented the items inside furnace from creating new unstackable cooked items. it may need the same check for the mixing table, which is a weird addition for a furnace plugin

where you put this?

        private object CanStackItem(Item source, Item target)
        {
            if (source == null || target == null)
                return null;
                
                if (!_furnacesData.ContainsKey(source.uid.Value) || !_furnacesData.ContainsKey(target.uid.Value))
                {
                    return null;
                }

            return false;
        }