Jump to content

[1.6.1] Block that creates 'larger block'


KeeganDeathman

Recommended Posts

Okay, so I want to make it so that when you place a block and then activate it, it places some dummy blocks around it in 1 3x3 square having the original block the center, and also having a model render over it so that it has a texture. Any help on this?

[shadow=gray,left][glow=red,2,300]KEEGAN[/glow][/shadow]

Link to comment
Share on other sites

Not sure why you locked your old post to be honest, you pretty much had it :P

 

As mentioned before, you'll need this tutorial: http://minalien.com/tutorial-multi-block-structures-in-minecraft/

 

Then, make one of the blocks (the one you place) a rendered Tile Entity. Without the above tutorial, you'd have the 3x3 block visible, but can walk through it.

 

Make a block, call it "Gag Block" or something, and make it so it's solid, but can't be seen. Those are the other blocks that will be placed when you place the model block. Does that make sense?

width=463 height=200

http://s13.postimg.org/z9mlly2av/siglogo.png[/img]

My mods (Links coming soon)

Cities | Roads | Remula | SilvaniaMod | MoreStats

Link to comment
Share on other sites

Not sure why you locked your old post to be honest, you pretty much had it :P

 

As mentioned before, you'll need this tutorial: http://minalien.com/tutorial-multi-block-structures-in-minecraft/

 

Then, make one of the blocks (the one you place) a rendered Tile Entity. Without the above tutorial, you'd have the 3x3 block visible, but can walk through it.

 

Make a block, call it "Gag Block" or something, and make it so it's solid, but can't be seen. Those are the other blocks that will be placed when you place the model block. Does that make sense?

 

Yeah sorta, So I need to make a base block, that has a render tilenetity that renders the model, and the gag blocks?

[shadow=gray,left][glow=red,2,300]KEEGAN[/glow][/shadow]

Link to comment
Share on other sites

I'm not sure about rending a model over the whole thing, but to have it add blocks on activation, you want something like this in your block's class:

public boolean onBlockActivated(World par1World, int par2, int par3, int par4, EntityPlayer par5EntityPlayer, int par6, float par7, float par8, float par9)
{
	par1World.setBlock(par2, par3+1, par4, Registration.celestialBlock.blockID, 0, 2);
        return true;
}

This creates a single block directly above the activated block.

Link to comment
Share on other sites

I'm not sure about rending a model over the whole thing, but to have it add blocks on activation, you want something like this in your block's class:

public boolean onBlockActivated(World par1World, int par2, int par3, int par4, EntityPlayer par5EntityPlayer, int par6, float par7, float par8, float par9)
{
	par1World.setBlock(par2, par3+1, par4, Registration.celestialBlock.blockID, 0, 2);
        return true;
}

This creates a single block directly above the activated block.

If a model is bigger than 1x1x1 it will just render outside the block, without any sort of collision to it.

So, he'd use his existing model with the code you put there. That code has to place invisible blocks, so the model will still show and have collision too. Only issue he'll have then is the mode will de-render when the original block is out of the screen - I have no idea how to fix that.

width=463 height=200

http://s13.postimg.org/z9mlly2av/siglogo.png[/img]

My mods (Links coming soon)

Cities | Roads | Remula | SilvaniaMod | MoreStats

Link to comment
Share on other sites

hmmm, thanks for the tip on placing the blocks, now, for the model de-rendering, Ill look it up, think i saw it somewhere before.

I might just make some more blocks, about 6, and have them have the textures of the model on them, the model isn't to special, just a box the size of the 3x3 square, with a texture. It would be take up some ids, but it would still work.

[shadow=gray,left][glow=red,2,300]KEEGAN[/glow][/shadow]

Link to comment
Share on other sites

If your model is based of the centre block, adding this to your blocks class should do the trick.

 

@Override
public AxisAlignedBB getCollisionBoundingBoxFromPool(World world, int x, int y, int z)
{
    return AxisAlignedBB.getBoundingBox(x - 1, y - 1, z - 1, x + 1, y + 1, z + 1);
}

Link to comment
Share on other sites

If your model is based of the centre block, adding this to your blocks class should do the trick.

 

@Override
public AxisAlignedBB getCollisionBoundingBoxFromPool(World world, int x, int y, int z)
{
    return AxisAlignedBB.getBoundingBox(x - 1, y - 1, z - 1, x + 1, y + 1, z + 1);
}

 

Thanks, now how about rendering the model?

[shadow=gray,left][glow=red,2,300]KEEGAN[/glow][/shadow]

Link to comment
Share on other sites

thanks for helping me expand my collison box, and I was wondering if you know how to load a tile entity, when the block is right clicked?

Replying here instead just in case someone else runs across this needing the same answers.

 

 

To your block class add (your block will need to extend BlockContainer or implement ITileEntityProvider before its available)

@Override
public TileEntity createNewTileEntity(World world)
{
    return new TileEntityLargeBlock(); //Rename to your tile entity 
}

 

 

This will create the tile entity as soon as the block is in the world, but you didn't want it to render until your right clicked so in your tile entity add

public boolean shouldRender = false;

 

Back to your block class

@Override
public boolean onBlockActivated(World world, int x, int y, int z, EntityPlayer entityPlayer, int face, float posX, float posY, float posZ)
{
  TileEntity tile = world.getBlockTileEntity(x, y, z);  // Once again rename to your tile entity.
  if (!(tile instanceof TileEntityLargeBlock)) {
    return false; // If for some reason your block does not have the correct tileentity you don't want it to create the false blocks, as nothing will hide them.
  }

  // run any pre-generation code you have here.  eg. making sure there is space for the false blocks.

  ((TileEntityLargeBlock)tile).shouldRender = true;

  // create your false blocks here as they are now hidden
  return true;
}

 

 

The last thing to do is in your renderer, simply check if shouldRender is true before rendering, if not leave without rendering anything.

 

 

 

You can change the other code I gave you too,

@Override
public AxisAlignedBB getCollisionBoundingBoxFromPool(World world, int x, int y, int z)
{
    TileEntity tile = world.getBlockTileEntity(x, y, z);  // Once again rename to your tile entity.
    if (tile instanceof TileEntityLargeBlock  && ((TileEntityLargeBlock)tile).shouldRender) {
        return AxisAlignedBB.getBoundingBox(x - 1, y - 1, z - 1, x + 1, y + 1, z + 1);
    }
    return super.getCollisionBoundingBoxFromPool(world, x, y, z);
}

 

Link to comment
Share on other sites

thanks for helping me expand my collison box, and I was wondering if you know how to load a tile entity, when the block is right clicked?

Replying here instead just in case someone else runs across this needing the same answers.

 

 

To your block class add (your block will need to extend BlockContainer or implement ITileEntityProvider before its available)

@Override
public TileEntity createNewTileEntity(World world)
{
    return new TileEntityLargeBlock(); //Rename to your tile entity 
}

 

 

This will create the tile entity as soon as the block is in the world, but you didn't want it to render until your right clicked so in your tile entity add

public boolean shouldRender = false;

 

Back to your block class

@Override
public boolean onBlockActivated(World world, int x, int y, int z, EntityPlayer entityPlayer, int face, float posX, float posY, float posZ)
{
  TileEntity tile = world.getBlockTileEntity(x, y, z);  // Once again rename to your tile entity.
  if (!(tile instanceof TileEntityLargeBlock)) {
    return false; // If for some reason your block does not have the correct tileentity you don't want it to create the false blocks, as nothing will hide them.
  }

  // run any pre-generation code you have here.  eg. making sure there is space for the false blocks.

  ((TileEntityLargeBlock)tile).shouldRender = true;

  // create your false blocks here as they are now hidden
  return true;
}

 

 

The last thing to do is in your renderer, simply check if shouldRender is true before rendering, if not leave without rendering anything.

 

 

 

You can change the other code I gave you too,

@Override
public AxisAlignedBB getCollisionBoundingBoxFromPool(World world, int x, int y, int z)
{
    TileEntity tile = world.getBlockTileEntity(x, y, z);  // Once again rename to your tile entity.
    if (tile instanceof TileEntityLargeBlock  && ((TileEntityLargeBlock)tile).shouldRender) {
        return AxisAlignedBB.getBoundingBox(x - 1, y - 1, z - 1, x + 1, y + 1, z + 1);
    }
    return super.getCollisionBoundingBoxFromPool(world, x, y, z);
}

 

oh my god thank you thank you thank you!

 

I'll edit this post if telling you if it worked!

 

EDIT: Well now when i right click it does nothing.

Heres my code:

BlockTowerFloorBase:

package codelyoko;

import net.minecraft.block.Block;
import net.minecraft.block.material.Material;
import net.minecraft.entity.player.EntityPlayer;
import net.minecraft.src.ModLoader;
import net.minecraft.tileentity.TileEntity;
import net.minecraft.util.AxisAlignedBB;
import net.minecraft.world.IBlockAccess;
import net.minecraft.world.World;

public class BlockTowerFloorBase extends Block
{

public BlockTowerFloorBase(int id, Material par1Material)
{

	super(id, par1Material);
	this.setCreativeTab(Lyoko.tabLyoko);

}

@Override
public TileEntity createTileEntity(World world, int metadata)
{
	return new TileEntityTowerFloor();
}

public boolean onBlockActivated(World par1World, int par2, int par3, int par4, EntityPlayer par5EntityPlayer, int par6, float par7, float par8, float par9)
{
	TileEntity tile = par1World.getBlockTileEntity(par2, par3, par4);  // Once again rename to your tile entity.
	if (!(tile instanceof TileEntityTowerFloor)) {
		return false; // If for some reason your block does not have the correct tileentity you don't want it to create the false blocks, as nothing will hide them.
	}
	par1World.setBlock(par2+1, par3, par4, Lyoko.TowerFloorGagBlock.blockID, 0, 2);
	par1World.setBlock(par2+1, par3, par4+1, Lyoko.TowerFloorGagBlock.blockID, 0, 2);
	par1World.setBlock(par2+1, par3, par4-1, Lyoko.TowerFloorGagBlock.blockID, 0, 2);
	par1World.setBlock(par2, par3, par4+1, Lyoko.TowerFloorGagBlock.blockID, 0, 2);
	par1World.setBlock(par2, par3, par4-1, Lyoko.TowerFloorGagBlock.blockID, 0, 2);
	par1World.setBlock(par2-1, par3, par4+1, Lyoko.TowerFloorGagBlock.blockID, 0, 2);
	par1World.setBlock(par2-1, par3, par4, Lyoko.TowerFloorGagBlock.blockID, 0, 2);
	par1World.setBlock(par2-1, par3, par4-1, Lyoko.TowerFloorGagBlock.blockID, 0, 2); 
	ModLoader.openGUI(par5EntityPlayer, new GUITowerFloorCreated());
	return true;
}




@Override
public AxisAlignedBB getCollisionBoundingBoxFromPool(World world, int x, int y, int z)
{
	return AxisAlignedBB.getBoundingBox(x - 1, y - 1, z - 1, x + 1, y + 1, z + 1);
}

//This will tell minecraft not to render any side of our cube.
public boolean shouldSideBeRendered(IBlockAccess iblockaccess, int i, int j, int k, int l)
{
	return false;
}

//And this tell it that you can see through this block, and neighbor blocks should be rendered.
public boolean isOpaqueCube()
{
	return false;
}

}

 

EDIT: Opps, forgot to implement ITileEntityProvider. Hehe :)

Now it just loads when i place the block, not even waiting for me to right click it!

[shadow=gray,left][glow=red,2,300]KEEGAN[/glow][/shadow]

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • rp.crazyheal.xyz mods  
    • I'm developing a dimension, but it's kinda resource intensive so some times during player teleporting it lags behind making the player phase down into the void, so im trying to implement some kind of pregeneration to force the game loading a small set of chunks in the are the player will teleport to. Some of the things i've tried like using ServerLevel and ServerChunkCache methods like getChunk() dont actually trigger chunk generation if the chunk isn't already on persistent storage (already generated) or placing tickets, but that doesn't work either. Ideally i should be able to check when the task has ended too. I've peeked around some pregen engines, but they're too complex for my current understanding of the system of which I have just a basic understanding (how ServerLevel ,ServerChunkCache  and ChunkMap work) of. Any tips or other classes I should be looking into to understand how to do this correctly?
    • https://mclo.gs/4UC49Ao
    • Way back in the Forge 1.17 days, work started for adding JPMS (Java Platform Module Support) to ModLauncher and ForgeModLoader. This has been used internally by Forge and some libraries for a while now, but mods (those with mods.toml specifically) have not been able to take advantage of it. As of Forge 1.21.1 and 1.21.3, this is now possible!   What is JPMS and what does it mean for modders? JPMS is the Java Platform Module System, introduced in Java 9. It allows you to define modules, which are collections of packages and resources that can be exported or hidden from other modules. This allows for much more fine-tuned control over visibility, cleaner syntax for service declarations and support for sealed types across packages. For example, you might have a mod with a module called `com.example.mod` that exports `com.example.mod.api` and `com.example.mod.impl` to other mods, but hides `com.example.mod.internal` from them. This would allow you to have a clean API for other mods to use, while keeping your internal implementation details hidden from IDE hints, helping prevent accidental usage of internals that might break without prior notice. This is particularly useful if you'd like to use public records with module-private constructors or partially module-private record components, as you can create a sealed interface that only your record implements, having the interface be exported and the record hidden. It's also nice for declaring and using services, as you'll get compile-time errors from the Java compiler for typos and the like, rather than deferring to runtime errors. In more advanced cases, you can also have public methods that are only accessible to specific other modules -- handy if you want internal interactions between multiple of your own mods.   How do I bypass it? We understand there may be drama in implementing a system that prevents mods from accessing each other's internals when necessary (like when a mod is abandoned or you need to fix a compat issue) -- after all, we are already modding a game that doesn't have explicit support for Java mods yet. We have already thought of this and are offering APIs from day one to selectively bypass module restrictions. Let me be clear: Forge mods are not required to use JPMS. If you don't want to use it, you don't have to. The default behaviour is to have fully open, fully exported automatic modules. In Java, you can use the `Add-Opens` and `Add-Exports` manifest attributes to selectively bypass module restrictions of other mods at launch time, and we've added explicit support for these when loading your Forge mods. At compile-time, you can use existing solutions such as the extra-java-module-info Gradle plugin to deal with non-modular dependencies and add extra opens and exports to other modules. Here's an example on how to make the internal package `com.example.examplemod.internal` open to your mod in your build.gradle: tasks.named('jar', Jar) { manifest { attributes([ 'Add-Opens' : 'com.example.examplemod/com.example.examplemod.internal' 'Specification-Title' : mod_id, 'Specification-Vendor' : mod_authors // (...) ]) } } With the above in your mod's jar manifest, you can now reflectively access the classes inside that internal package. Multiple entries are separated with a space, as per Java's official spec. You can also use Add-Exports to directly call without reflection, however you'd need to use the Gradle plugin mentioned earlier to be able to compile. The syntax for Add-Exports is the same as Add-Opens, and instructions for the compile-time step with the Gradle plugin are detailed later in this post. Remember to prefer the opens and exports keywords inside module-info.java for sources you control. The Add-Opens/Add-Exports attributes are only intended for forcing open other mods.   What else is new with module support? Previously, the runtime module name was always forced to the first mod ID in your `mods.toml` file and all packages were forced fully open and exported. Module names are now distinguished from mod IDs, meaning the module name in your module-info.java can be different from the mod ID in your `mods.toml`. This allows you to have a more descriptive module name that doesn't have to be the same as your mod ID, however we strongly recommend including your mod ID as part of your module name to aid troubleshooting. The `Automatic-Module-Name` manifest attribute is now also honoured, allowing you to specify a module name for your mod without needing to create a `module-info.java` file. This is particularly useful for mods that don't care about JPMS features but want to have a more descriptive module name and easier integration with other mods that do use JPMS.   How do I use it? The first step is to create a `module-info.java` file in your mod's source directory. This file should be in the same package as your main mod class, and should look something like this: open module com.example.examplemod { requires net.minecraftforge.eventbus; requires net.minecraftforge.fmlcore; requires net.minecraftforge.forge; requires net.minecraftforge.javafmlmod; requires net.minecraftforge.mergetool.api; requires org.slf4j; requires logging; } For now, we're leaving the whole module open to reflection, which is a good starting point. When we know we want to close something off, we can remove the open modifier from the module and open or export individual packages instead. Remember that you need to be open to Forge (module name net.minecraftforge.forge), otherwise it can't call your mod's constructor. Next is fixing modules in Gradle. While Forge and Java support modules properly, Gradle does not put automatic modules on the module path by default, meaning that the logging module (from com.mojang:logging) is not found. To fix this, add the Gradle plugin and add a compile-time module definition for that Mojang library: plugins { // (...) id 'org.gradlex.extra-java-module-info' version "1.9" } // (...) extraJavaModuleInfo { failOnMissingModuleInfo = false automaticModule("com.mojang:logging", "logging") } The automatic module override specified in your build.gradle should match the runtime one to avoid errors. You can do the same for any library or mod dependency that is missing either a module-info or explicit Automatic-Module-Name, however be aware that you may need to update your mod once said library adds one. That's all you need to get started with module support in your mods. You can learn more about modules and how to use them at dev.java.
    • Faire la mise à jour grâce à ce lien m'a aider personnellement, merci à @Paint_Ninja. https://www.amd.com/en/support 
  • Topics

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.