6 replies to this topic

[coranos]

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]

Moved.

[GopherAtl]

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]

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

[coranos]

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]

coranos, on 26 December 2012 - 06:20 AM, said:

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]

coranos, on 26 December 2012 - 06:20 AM, said:

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.