The idea would indeed be nice. The thing with aiming projectiles isn't easily possible, because the dispenser interface doesn't support aiming/positions...
Posts by Aroma1997
-
-
Seems like the forums doesn't like too many http redirects...
I fixed the original post.
-
No. Quad rods produce more heat than you can dissipate with this reactor design. If you're looking for other, good reactor design, I would suggest you look at this thread.
-
I'm not a fan of this idea. Automating item dropping usually causes lots of lag. If you really want to do it, you can pull out the items using a hopper and drop them using a dropper.
-
Hmm interesting. We probably want to create different tiered kinetifc generators.
-
That is indeed a weird behaviour. Reworking the pump to make it more reliable is on my todo-list though.
-
It crashing there indicates that the item is indeed null. Make sure you're using the correct registry name.
-
Try printing out the itemstack as well to make sure the stack is not empty.
-
How do you generate more than 512EU/t
-
When are you registering these oredict entries? Make sure you register them after the items are actually registered in the respective mod.
-
I +1 this request.
-
If the nano suit already had all the properties of the hazmat suit, what would be the point of making a Q-Suit then?
-
It can in the new version, but before, it needed to be nbt, so it can be used for all kinds of different machines.
-
The Ore Washing plant needs to know how much water to drain. Therefore you need to give it that as an argument. You do that by using the following method:
JavaNBTTagCompount nbt = new NBTTagCompound(); nbt.setInteger("amount", 1000); Recipes.oreWashing.addRecipe(yourInputs, nbt, yourOutputs); -
Good luck.
-
i can just froward caps from a different te and not knowing what the cap is, can i do that w/ the EU API ?
I don't know why you would want to do that, but yes, of course you can do that.
easier to use??
than "hey TE do you have cap x on side y"
Asking the te "Do you have this capability" is as easy as asking the enet whether that block is a energy tile. Implementing the energy tile logic is easier with our api than if it was a capability.
but i dont think you/other change caps every tick
They don't. They shouldn't. But we need to check every tick to make sure. A TileEntity can switch between accepting energy and not accepting energy anytime. With the tileentity not notifying us, we need to ask every single tileentity every single tick.
so the cap needs to be told when caps are unloaded/destroyed ??
No, but we need to get notified because of the above problem.
-
that can be solved. TEs need to markdirty when they change cap
Not only our tes would need to do that, but also other people's tes. That would slow things down as well.
Another reason why there's no point of moving to capabilities is because our api is not less dynamic than capabilities and is easier to use.
-
-
-
