I am using Redstone Flux (Thermal Expansion) for testing.

Currently, my block will connect to fluxducts and accepts energy (tested with simpleSystem.out, it even saves it on reload), but refuses to send energy into a cable, machine or otherwise.

 

Here is the TileEnity/block/EnergyStorage and ForgeWrapper for my custom energy implementation.

Edited June 10, 20196 yr by cj3636

What version. Override getCapability (and hasCapability if you’re on an outdated version) and return your energy storage

On 6/7/2019 at 8:36 PM, Cadiboo said:

What version. Override getCapability (and hasCapability if you’re on an outdated version) and return your energy storage

1.12.2 

This is the code I have gotten to now:

 

TileEntity

EnergyStorage

ForgeWrapper

 

I was following CjMinecraft's tutorial seen here on GitHub

Still have the same issue; the block will connect to RF, receive RF, but refuses to send it.

You call setMaxTransfer(0) in deserialise.

Also, what is the use of ForgeWrapper?

Edited June 10, 20196 yr by Cadiboo

2 minutes ago, Cadiboo said:

You call setMaxTransfer(0) in deserialise.

Also, what is the use of ForgeWrapper?

I'm not 100% sure, but the tutorial explained it was necessary to convince other power api's that the block was Forge Energy compatible?

40 minutes ago, Cadiboo said:

You call setMaxTransfer(0) in deserialise.

Also, what is the use of ForgeWrapper?

I touched up the code a bit. I still have the same issue and for the life of can not figure out why!

The block receives energy just fine, but refuses to send it.

 

Relevant code in my repo on GitHub.

 

Thank you for your help so far!

5 hours ago, cj3636 said:

I'm not 100% sure, but the tutorial explained it was necessary to convince other power api's that the block was Forge Energy compatible?

You do that by returning an IEnergyStorage from getCapability