Crafting Tools


Adds hotkeys to craft items from your cursor, quickbar or nearby ghost items NEW: craft nearby upgrade requests if not in inventory FIX: craft merged chests

Utilities
a month ago
1.1 - 2.0
2.58K

g Duplicate key binding

a month ago

In Factorio 2.0 Alt+G is assigned to Green wire conntection mode
so if you press it it will craft the item under the cursor AND switch to Green wire conntection mode

Solution: reassign your key bindings

a month ago
(updated a month ago)

Sorry, but I don't have that key bind. I use Ctrl - G and your cursor craft is the only thing assigned to that. Alt-G works great for green wire.
ctrl-g works great for crafting regular items in my inventory, but when it runs out and turns into a ghost, i get that error. No recipe for _ 1 _ .

I re-read my original post and realized I didn't explain very clearly and I'm sorry for that.

a month ago

as long as i don't know for which recipe it brings this message, there is not much i can do

a month ago

If I start the game with only this mod enabled, every recipe from the logistics section returns the error: wooden and iron chests, basic belt, burner inserter and stone brick.
Then items from intermediate products all return the same error: iron and copper plate and iron gear wheel.
Combat items too: firearm magazine and light armor.

If I enable other recipes then some recipes stop erroring, but it isn't predictable, in some cases most magazine recipes will return this error, but in other attempts they work alright.

a month ago
(updated a month ago)

@Evio I don't quite understand what you're referring to, or what you're actually doing

a month ago
(updated a month ago)

I'm using this mod exactly the way I've been using it for a couple years except that it now it says No recipe for __1__ when trying to craft many recipes, while holding a ghost, same issue satans_empathy was talking about.

You may want to test these issues instead of just dismissing.

(The mod Cursor Craft isn't exhibiting that error when crafting with a ghost in hand, although it gives the wrong error message when there aren't enough materials to craft)

a month ago

You may want to test these issues instead of just dismissing.

what makes you think that?
I have done something about it and I'm not getting this message, after removing the duplicate keybinding.
If you continue to raise this error message, then I need to know exactly what you are doing so that I can reproduce it for myself

a month ago

what makes you think that?

Because “I don't quite understand what you're referring to, or what you're actually doing” right after being told exactly what was being done.

If you continue to raise this error message, then I need to know exactly what you are doing so that I can reproduce it for myself

The update you published after your last reply fixes this so it looks like you actually found what it was... perhaps the comparing item.name instead of item bit in control.lua?

I don't think the error will happen again now but I won't be sure until I re-enable de mod in the server.

Thanks for the fix.

a month ago

yes found, item.name is not a name. and item.name.name is strange to read and unsafe ;-). I have rewritten this whole stuff

a month ago

Now I'm having this issue though, when using the shortcut to craft ghost in hand when there's no ghost in hand:

The mod Crafting Tools (3.2.5) caused a non-recoverable error.
Please report this error to the mod author.

Error while running event Kux-CraftingTools::cursor-craft-1 (ID 214)
__Kux-CraftingTools__/features/CraftingHotkeys/control.lua:100: attempt to index field 'cursor_ghost' (a nil value)
stack traceback:
        __Kux-CraftingTools__/features/CraftingHotkeys/control.lua:100: in function <__Kux-CraftingTools__/features/CraftingHotkeys/control.lua:93>
a month ago

Thanks @Evio - I didn't find any items that didn't give that error, but I didn't go through the list checking each one. Now, I get the same error you mention here, making it a bit more difficult to test as we'd have to load a new world for each item being tested, as long as it keeps giving the error.

Sorry for my delay in reply @kuxynator, work gets hectic sometimes. Either way, thanks for starting to look into it!

a month ago

should be fixed. hopfully

New response