public void updateTick(World world, int i, int j, int k, Random random)
{
int grown = mod_BushMod.cherryBushON.blockID;
super.updateTick(world, i, j, k, random);
if(world.getBlockId(i, j, k) == mod_BushMod.cherryBushOFF.blockID)
{
if(random.nextInt(1) == 0)
{
world.setBlockWithNotify(i, j, k, grown);
}
}
}First of all, this is code is defining the block that is going to be placed, which is 'grown' and the block is cherryBushOFF. I'll show you what I mean in one of the next steps.
int grown = mod_BushMod.cherryBushON.blockID;
I'm not sure what this is but you need it.
super.updateTick(world, i, j, k, random);
This code is saying if x, y, z co-ordinates equals mod_BushMod.cherryBushOFF.blockID it will continue and go to the next loop.
if(world.getBlockId(i, j, k) == mod_BushMod.cherryBushOFF.blockID)
This one is saying if random int out of 0 to 1 equals 0, it will place 'grown' at x, y, z co-ordinates.
if(random.nextInt(1) == 0)
{
world.setBlockWithNotify(i, j, k, grown);
}I hope this explains kinda of. You can change the co-ordinates to x, y + 1, z. This will place the block above.
4
You have literally installed your mods twice. Clean out the redundancies.
3
BaseModMp is part of ModloaderMP --an unrelated mod-- if I'm not mistaken.
Make sure you're starting from a clean jar and that you've removed any outdated mods from your mods folder.
2
Seems pretty self-explanatory to me. Either install what's being requested or remove the Smart Moving mod.
1
I'd suggest trying the instructions at the bottom of this post.
1
Why would you ask Risugami? You should ask Marglyph, the creator of Too Many Items. Though, I feel the answer might be a solid 'no'.
2
Not quite true. Forge does a half-decent job running Modloader mods with its compatibility layer. While, yes, there's no guarantee that an RML (Risu's ModLoader) mod will work 100% perfect in Forge, it's a far cry away from "incompatible".
1
The Old Versions link appears not to have a 1.4.7 version. I'd suggest following the suggestion at the bottom of this post.
It really can't be guaranteed that Forge will run the mod properly, much less enable it to work in SMP. I'd say a cautious "no" is a good answer but I'll let somebody more knowledgeable answer in my place. Or just try it out and see. YMMV (Your Mileage May Vary).
1
import net.minecraft.network.INetworkManager; import net.minecraft.network.packet.Packet; import net.minecraft.network.packet.Packet132TileEntityData; @Override public Packet getDescriptionPacket() { NBTTagCompound c = new NBTTagCompound(); c.setInteger( "blockID", this.blockID ); c.setInteger( "blockMeta", this.blockMeta ); return new Packet132TileEntityData( xCoord, yCoord, zCoord, 1, c ); } @Override public void onDataPacket( INetworkManager m, Packet132TileEntityData p ) { this.blockID = p.customParam1.getInteger( "blockID" ); this.blockMeta = p.customParam1.getInteger( "blockMeta" ); }1
The problem with Tinkers' Construct is that, at least from my general overview of it, the mod doesn't grant the player freedom, just adds a very thorough (and horribly designed, IMHO) crafting system with lots of different parts that have to be cobbled together.
If I did decide to pull a quasi TC, I'd be eliminating prefabrication in all its forms. You'd just be throwing materials onto the Blade Works and pulling out whatever the heck pops out on the other side.
The system would probably bring about another registry, the MaterialsRegistry class, which would allow registering items as hilt and blade materials and giving them proper "stats" that would be combined to create the final result. I assume I'd probably have to do a crap-tonne of render-passing to achieve the result sword sprites but I'm down with that.
Naturally, I would do a lot of fine-tuning to make the process simple yet powerful. At the moment, the only real utility of the system would be freeing the player to craft weapons almost entirely regardless their material supplies. However, the ultimate payout wouldn't be too great. You'd still want to focus on purer swords.
Additionally, this idea would result in an over-complication of the later alkahestry elements that allow modifying the sword's innate abilities and form.
Again, just something to toss around until either it's decidedly implementable or ultimately jossed.
1
I've basically FUBAR'd AltriaCraft trying to fix up the code, lol. Gonna be an interesting night. It's not exactly a walk in the park to condense so much sword stuff into one single ID and Item object.
However, the trade-off is pretty cool. Swords basically become infinitely malleable. If I so desired, I could easily pull a quasi Tinkers' Construct and allow the player near-free reign at forging weapons.
Thoughts?