This is a read-only snapshot of the ComputerCraft forums, taken in April 2020.
coranos's profile picture

ITurtlePeripheral removed from CC 1.48?

Started by coranos, 25 December 2012 - 03:48 PM
coranos #1
Posted 25 December 2012 - 04:48 PM
I just tried to run CC 1.4.8 and I see this class was removed:
dan200.turtle.api.ITurtlePeripheral;

I used the update() to do work inside my peripheral, why was it removed?
Lyqyd #2
Posted 25 December 2012 - 05:21 PM
Moved.
GopherAtl #3
Posted 25 December 2012 - 06:54 PM
from looking at the new API, it looks like you would just implement your IHostedPeripheral, which extends IPeripheral and which has an update method, and ITurtleUpgrade, which has methods to return the IHostedPeripheral.
Cloudy #4
Posted 25 December 2012 - 09:15 PM
Yeah, use some common sense when looking at the new API download - it is obvious we haven't removed it, as turtles still have peripherals :P/>
coranos #5
Posted 26 December 2012 - 06:20 AM
Common sense would put the removal in a change log, or add @deprecated so peripheral developers would get a warning rather than a hard compiler error.

The API also doesn't match the way mcp 725 decompiles the classes. (NBTTagCompound is in net.minecraft.src, not net.minecraft.nbt).

I'm not complaining, just documenting for the next guy that gets confused.

If it was obvious, I wouldn't have asked :)/>
immibis #6
Posted 26 December 2012 - 04:36 PM
The API also doesn't match the way mcp 725 decompiles the classes. (NBTTagCompound is in net.minecraft.src, not net.minecraft.nbt).
It's actually a Forge change, not an MCP change.
If you use BON instead of the API download, you'll always get the latest API and names that match everything else.
Cloudy #7
Posted 27 December 2012 - 08:43 AM
Common sense would put the removal in a change log, or add @deprecated so peripheral developers would get a warning rather than a hard compiler error.

The API also doesn't match the way mcp 725 decompiles the classes. (NBTTagCompound is in net.minecraft.src, not net.minecraft.nbt).

I'm not complaining, just documenting for the next guy that gets confused.

If it was obvious, I wouldn't have asked :)/>

We thought the updated API would have been enough. However we will remember for the future.