search

OpenMods / OpenPeripheral

https://openmods.info
MIT License
67 stars 25 forks source link

Computercraft Error. message after trying to call mekanism peripherals. #261

Closed Feelthethunder closed 8 years ago

Feelthethunder commented 8 years ago

As the title says computercraft doesn't like to use the peripherals from mekanism. Specifically the energy cubes. I have tried everything and have all the latest versions of computercraft, mekanism, and openperipherals. After trying an advanced program, I boiled it down to a very very basic one and it still didn't work. Code:

local cube = peripheral.wrap("left") local energy = cube.getStored() print(energy)

The output of the program was Error. Without the () at the end of getStored I get a function: 38f62f8f error Yet when I use the lua script and use the command:

peripheral.getMethods("left")

I get all of the methods: getStored getOutput getMaxEnergy getEnergyNeeded

all of these peripherals come up with the same Error. message when I try to call them. If anyone can help and save me some more hair tearing out that would be appreciated. Thanks.

boq commented 8 years ago

This peripheral is not provided by OpenPeripheral - notice missing 'listMethods' and 'getAdvancedMethodsData'.

It looks like peripheral code provided by Mekanism itself is broken. I'm... not really sure what happened there, but it does not look like it was generated by sane compiler...

boq commented 8 years ago

It looks like it was already fixed in Mekanism. And yes, it was generated by compiler, just by very broken code...

Feelthethunder commented 8 years ago

Could you please explain what I must do to fix this then? I am still lost.

boq commented 8 years ago

"looks like it was already fixed in Mekanism."

So just wait for next release, where this fix aidancbrady/Mekanism#3014 is included.

Feelthethunder commented 8 years ago

Alright thanks for the help. Let the waiting game begin.

On Dec 5, 2015, at 2:52 AM, Bartek Bok notifications@github.com wrote:

"looks like it was already fixed in Mekanism."

So just wait for next release, where this fix aidancbrady/Mekanism#3014 is included.

— Reply to this email directly or view it on GitHub.