Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

EEPROMS/ Lua Bios copying in BC adv crafting tables #1044

Closed
n00b7 opened this issue Apr 9, 2015 · 5 comments
Closed

EEPROMS/ Lua Bios copying in BC adv crafting tables #1044

n00b7 opened this issue Apr 9, 2015 · 5 comments

Comments

@n00b7
Copy link

n00b7 commented Apr 9, 2015

bug

Hello, I am using
(forge 1291 for 1.7.10)
Open Computers v1.5.6.13
Buildcraft v6.4.8

I think that I have discovered a bug, so i was going to let you know about it.

When i put a eeprom or a Lua bois into an advanced crafting table from BuildCraft. I put the Eeprom or Lua bois into the top of the table. (material crafting area) (the amount doesnt seem to matter.) and I have more stacks down in the slots below. It will make/add more copies of itself if you continue to move the stacks around.

I don't know if this is an issue with BuildCraft or Open computers,
but i am going to post this in both places.

Thank you for taking the time to look at this error. :)
@n00b7 n00b7 changed the title EEPROMS copying in BuildCraft advanced crafting tables EEPROMS/ Lua Bios copying in BC adv crafting tables Apr 9, 2015
@fnuecke
Copy link
Member

fnuecke commented Apr 10, 2015

Strange. Will try to look into this tomorrow.

@n00b7
Copy link
Author

n00b7 commented Apr 11, 2015

Buildcraft 6.4.9 and 6.4.10 fix this issue

@n00b7 n00b7 closed this as completed Apr 11, 2015
@n00b7 n00b7 reopened this Apr 11, 2015
@n00b7
Copy link
Author

n00b7 commented Apr 11, 2015

i reopend this because it could happen with buildcraft 7.0.0 beta

@Vexatos
Copy link
Contributor

Vexatos commented Apr 11, 2015

@asiekierka probably already fixed it for BC 7 as well.

@fnuecke
Copy link
Member

fnuecke commented Apr 11, 2015

Oh, it is? Cool then. And yes, I'd very strongly assume those changes will also be in 7. If not you can re-open it when it comes out and you see the issue re-appearing. Although, seeing as it seems to have been an issue in BC, it'd make more sense to open it on BC's issue tracker, then?

@fnuecke fnuecke closed this as completed Apr 11, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@fnuecke @Vexatos @n00b7