Hi.
I am using FE 1.7.10-1.4.4.1182 on my server with mods (forge 10.13.4.1558), but some crafteos mods are blocked, for example, unstable ingots and anything that requires them.
It does not work autonomus activator of Thermal Expansion.

I added the permissions to the group _ALL_ but it seems not help.
"fe.protection.craft.ExtraUtilities.unstableingot.*": "true", "fe.protection.exist.ExtraUtilities.unstableingot.*": "true", "fe.protection.inventory.ExtraUtilities.unstableingot.*": "true", "fe.protection.use.ExtraUtilities.unstableingot.*": "true",

Greetings.

I tried crafting an unstable ingot in dev env and it worked without any problem.
@Techjar does it crash when trying to craft that ingot in prod or what exactly is wrong here?

It doesn't crash.
The observed effect is the same as a desync between client and server recipe DB.
The crafted item appears in an output slot, but you can't retrieve it from there.
Happens when certain set of mods is present (the script I've linked above mentioning DragonAPI and/or Tinkers' Construct).

Yeah the problem is if anything inserts extra calls onto the stack in the crafting code path, it breaks, because like I said he's checking specific stack indices. It probably only breaks if you have at least 2 mods adding extra calls to the stack, as he checks 2 adjacent indices (probably in an attempt to fix this bug). It's not fixable from FE's side (though I guess you could use AnrDaemon's script), needs to be fixed in ExU. He should be doing a class check on inventoryCrafting.eventHandler.

The weird thing is it worked for me!
I could easily pull the stacks out...
I think it was in dev env though.

Try adding TiC?

@Techjar can you cross-link the ExU side of the issue please?

I mean, if there's an issue report on ExU side? If such thing ever exists.
Even closed-source projects often have public issue trackers.

I cannot as it isn't actually open source.

Try turning /p debug
and recording what happens when you try to craft. Also post your permissions.json file

@HeberonYT Did you solve your issue?

@fusiondesign Sorry to hear that, I got tired of so many problems and limitations with this mod.
The solution was to delete, and move to kcauldron to use the essentials plugin which is great, no problem and also get better performance without this mod.
I leave a summary of everything that does not work.
1- The plots do not work
2- Some recipes extra utilities are blocked
3- Some blocks do not work (activator autonomus)
4- Vip slots do not work
5- sudden Crash
6- Permission to deny colors and in chat format does not work.
7- not supported fastcraft
8- The graves do not keep all objects at death
9- Bad optimization, many checks, means low tps

Well, the main difference between forge essentials and bukkit essentials is bukkit essentials is far older and more mature. Forge Essentials has been working hard to catch up but it is still far behind essentials.

Our server has this issue as well. No command is logged when you go to grab the Unstable Ingots out of the vanilla crafting window. It will not allow you to pull out an unstable ingot using the normal Iron / Diamond recipe.

Can you give me more information about what mods you are using and what configs. If you are using a modpack please include a sharecode.

@HeberonYT

1. Nice to have a list of stuff that are the biggest show-stoppers for users
2. You are not forced to use every feature of FE 😉

As for those issues you mentioned:

1. Plots are still kinda under construction / half finished - there were not enough developers (1? 2?) to get this finished while at the same time taking care of the rest, too
2. see below
3. Probably a permission thing - there are generic permissions for fakeplayers which could block this
4. Should be checked as well - don't know if this ever had been reported
5. Well - if TF was installed on the server I can guess what happened - otherwise same thing - need crashlogs
6. same - needs to be reported + it helps to also remind us on issues that got inactive but are still imporant
7. rtfm - we have a proper guide on how to use fastcraft with FE together
8. From when was this? In there current version there shouldn't be any issue at all
9. FE has been optimized quite a lot - but what do you expect of the most powerful permission system for forge servers? Of course you will have a slight drop in TPS - though it can get serious if you do stuff like dropping 30+ quarries or something like that.

As for the unstable ingots: This is really a serious (and quite annoying) issue.
Even though I used Extra Utilities with FE on my own server as well (probably not hard to fix though) I heard this the first time.
It might be that it happens because I think extra utilities overwrites some of the recipe handler in MC which FE also does to handle crafting permissions.
Will need some investigation.

Could you try if it works with some mod crafting table?
For example a crafting backpack.

I just started a new server and have the same issue. Crafting the nuggets works fine. It's the unstable ingots with the iron that doesn't work. The private server I'm running is basically the DW20 pack with every mod updated and a few others thrown in for fun. A list of all the mods (even disabled ones) is here: http://pastebin.com/gnVr8nAR

Just tested and can confirm this also happens on my server.

So I got curious and looked into this. It's getting a stack trace and checking for a ContainerWorkbench at specific indices of the stack in it's recipe handler, so basically this can't be fixed from FE's side (unless you were to asm ExU). I believe this is the issue anyways, but I will investigate further. Can confirm that this is the issue.

Test is without FE. I'd be surprised, if it would work.
There's many ways to break ExU ingots crafting, but there's a way to fix it as well.
Grab this script and include it into your MT blob.

Wouldn't that allow you to craft the ingots anywhere though, including by automated means? Thereby defeating the purpose of the stable ingot (crazy complex ritual thing) and nugget recipes.

Try it? :) I didn't test it in autocrafters, though. Guess I'm too honest >.<
But given the comment at the top of that script, the issue is not limited to FE already.

As we moved to 1.12.2, is this still an issue? Closing this issue in 7 days if no response