Page 1 of 1

[0.12.17][posila] Crafting cancelation = free resources

Posted: Sun Nov 22, 2015 1:43 pm
by nut
Hi, i found this bug, sorry if it's already reported, i searched a little and i didnt see anything similar.

This is how to reproduce the bug (ovbiously it work whit other numbers of items but this is an example)

1-pick 100 iron plate and 150 copper plate
2- craft 100 green circuits
3- cancel all the cables for the circuits
4-recraft all circuits you can

my remaining materials where: 100 green circuits and 138 copper plate (i should had 0 copper plates)

i recreated this 4 times whit a 100% succes chance

i didnt try any other objects, only whit green circuits

PD: congrats on the game, a friend told to me to try it a week ago and i am playing really a lot :D i'm about 1 or 2 hours left to make the rocket silo, and i'm enjoying this game a lot.

Re: [0.12.17] Crafting cancelation = free resources

Posted: Sun Nov 22, 2015 1:56 pm
by daniel34
I tried reproducing the bug with the steps you provided, but for me this works as intended. After I cancel the cables the already made cables go into my inventory and the rest I get back as copper plates. After crafting all 100 circuits I don't have any copper left.

Are you sure that you don't have any copper cables in your inventory already and the extra copper plates/circuits are not getting inserted into your inventory by the logistics bots?

Re: [0.12.17] Crafting cancelation = free resources

Posted: Sun Nov 22, 2015 2:13 pm
by nut
Image

Then i start to craft 100 circuits

Image

I cancell all the cables

Image

and before the remaining circuits ended crafting i crafted all circuits i can

Image

result

Image

Re: [0.12.17] Crafting cancelation = free resources

Posted: Sun Nov 22, 2015 3:11 pm
by joon
I noticed it as well with Crafting bug that the assembly machine didn't need any circuits. Probably has something to do with the cancellation of crafting.

Re: [0.12.17][posila] Crafting cancelation = free resources

Posted: Tue Nov 24, 2015 3:39 pm
by posila
Thanks for the report. This should be fixed in 0.12.19