Jump to content

Special Ability Tools


kenoba10

Recommended Posts

if(brokenBlock != null)
{
	ItemStack result = FurnaceRecipes.smelting().getSmeltingResult(new ItemStack(brokenBlock, 1, meta));

	if(result != null)
	{
		EntityItem drop = new EntityItem(world, par2, par3, par4, result);
		world.spawnEntityInWorld(drop);
		return false;
	}
}

Thanks but when I break it with the pick the first time i break that ore type I get an ingot and the ore, the rest of the then I just get the ore back

 

That makes sense. The problem with the ore is the fact that what a block drops is set inside the block's class. And to my knowledge, there is no way to void that block drop. But I guess you could do a hackish type job by using gamerules... By that I mean set block drops to false and then back to true again once it dropped the item.

 

As to it only working once... I am not sure :/

How would I set blcok drops to false??

Link to comment
Share on other sites

  • Replies 73
  • Created
  • Last Reply

Top Posters In This Topic

I have no flippin idea :D

 

I was just saying what I would do, but that would require me to learn how they work. So I would suggest reading through how they are set and such.

I am Mew. The Legendary Psychic. I behave oddly and am always playing practical jokes.

 

I have also found that I really love making extremely long and extremely but sometimes not so descriptive variables. Sort of like what I just did there xD

Link to comment
Share on other sites

I have no flippin idea :D

 

I was just saying what I would do, but that would require me to learn how they work. So I would suggest reading through how they are set and such.

I'm giving up on the auto smelting pickaxe idea I'll think of something else for my pickaxe. Thanks for the help though

Link to comment
Share on other sites

Awww...!! I liked the idea. Maybe I will figure it out and make a small mod out of it xD

I am Mew. The Legendary Psychic. I behave oddly and am always playing practical jokes.

 

I have also found that I really love making extremely long and extremely but sometimes not so descriptive variables. Sort of like what I just did there xD

Link to comment
Share on other sites

It was my idea thats Copy Right I was gonna do that already

Thaumcraft 2 had the Pickaxe of the Core, so I guess you actually stole it from him.

well that pickaxe had like a 33 % chance of dropping a native ore cluster and crap it wasnt auto smelting

Link to comment
Share on other sites

point is you don't have copyright over "auto smelting pickaxe" tons of people has this idea before you and im SURE other mods have done it before (example: IC2 mining laser automaticly smelt things)

how to debug 101:http://www.minecraftforge.net/wiki/Debug_101

-hydroflame, author of the forge revolution-

Link to comment
Share on other sites

well that pickaxe had like a 33 % chance of dropping a native ore cluster and crap it wasnt auto smelting

Yes, it was auto-smelting. Crouching allowed you to mine without dropping the smelted ore, and right clicking spawned a guide wisp, but I can assure you that by default it was auto-smelting.

Link to comment
Share on other sites

well that pickaxe had like a 33 % chance of dropping a native ore cluster and crap it wasnt auto smelting

Yes, it was auto-smelting. Crouching allowed you to mine without dropping the smelted ore, and right clicking spawned a guide wisp, but I can assure you that by default it was auto-smelting.

Oh I don't know that much about Thaumcraft really maybe thats the pickaxe of the core in ThaumCraft 3 that I was thinking if that makes it not copying

Link to comment
Share on other sites

nobody cares if you copy something as generic as this. It would only be cheap if you were making another item called the Mining laser and it would have the same feature as the one in IC2 and EVEN if you were doign that, almost nobody would actually care. if you want to make a auto-smelting pickaxe just DO IT. its so generic

how to debug 101:http://www.minecraftforge.net/wiki/Debug_101

-hydroflame, author of the forge revolution-

Link to comment
Share on other sites

nobody cares if you copy something as generic as this. It would only be cheap if you were making another item called the Mining laser and it would have the same feature as the one in IC2 and EVEN if you were doign that, almost nobody would actually care. if you want to make a auto-smelting pickaxe just DO IT. its so generic

I stopped making it because I ran in to problems I couldnt find out how to solve nobody knew such as how to prevent the default block drop

Link to comment
Share on other sites

Happy birthday:

@Override
public boolean onBlockStartBreak(ItemStack itemstack, int i, int j, int k, EntityPlayer player)
{
	World world = player.worldObj;
	int blockID = world.getBlockId(i, j, k);
	int meta = world.getBlockMetadata(i, j, k);

	NBTTagList ench = itemstack.getEnchantmentTagList();
	int level = 0;
	if(ench != null)
	{
		for (int x = 0; x < ench.tagCount(); x++)
		{
			NBTTagCompound nbt = (NBTTagCompound) ench.tagAt(x);
			int id = nbt.getInteger("id");
			if (id == Enchantment.fortune.effectId)
			{
				level = nbt.getInteger("lvl");
			}
		}
	}
	ArrayList<ItemStack> items = Block.blocksList[blockID].getBlockDropped(world, i, j, k, meta, level);
	if(items == null || items.size() == 0)
	{
		return false;
	}
	for (ItemStack item : items)
	{
		if (FurnaceRecipes.smelting().getSmeltingResult(item) == null)
		{
			return false;
		}
		ItemStack smelted = FurnaceRecipes.smelting().getSmeltingResult(item).copy();

		world.playSoundEffect(i + 0.5F, j + 0.5F, k + 0.5F,
				Block.blocksList[blockID].stepSound.getBreakSound(),
				(Block.blocksList[blockID].stepSound.getVolume() + 1.0F) / 2.0F,
				Block.blocksList[blockID].stepSound.getPitch() * 0.8F);

		world.setBlock(i, j, k, 0);
		if(!world.isRemote)
		{
			float var6 = 0.7F;
			double var7 = world.rand.nextFloat() * var6 + 1.0F - var6 * 0.5D;
			double var9 = world.rand.nextFloat() * var6 + 1.0F - var6 * 0.5D;
			double var11 = world.rand.nextFloat() * var6 + 1.0F - var6 * 0.5D;
			EntityItem entityitem = new EntityItem(world, i + var7, j + var9, k + var11, smelted);
			world.spawnEntityInWorld(entityitem);
		}
		itemstack.damageItem(1, player);
	}

	return true;
}

Link to comment
Share on other sites

Happy birthday:

@Override
public boolean onBlockStartBreak(ItemStack itemstack, int i, int j, int k, EntityPlayer player)
{
	World world = player.worldObj;
	int blockID = world.getBlockId(i, j, k);
	int meta = world.getBlockMetadata(i, j, k);

	NBTTagList ench = itemstack.getEnchantmentTagList();
	int level = 0;
	if(ench != null)
	{
		for (int x = 0; x < ench.tagCount(); x++)
		{
			NBTTagCompound nbt = (NBTTagCompound) ench.tagAt(x);
			int id = nbt.getInteger("id");
			if (id == Enchantment.fortune.effectId)
			{
				level = nbt.getInteger("lvl");
			}
		}
	}
	ArrayList<ItemStack> items = Block.blocksList[blockID].getBlockDropped(world, i, j, k, meta, level);
	if(items == null || items.size() == 0)
	{
		return false;
	}
	for (ItemStack item : items)
	{
		if (FurnaceRecipes.smelting().getSmeltingResult(item) == null)
		{
			return false;
		}
		ItemStack smelted = FurnaceRecipes.smelting().getSmeltingResult(item).copy();

		world.playSoundEffect(i + 0.5F, j + 0.5F, k + 0.5F,
				Block.blocksList[blockID].stepSound.getBreakSound(),
				(Block.blocksList[blockID].stepSound.getVolume() + 1.0F) / 2.0F,
				Block.blocksList[blockID].stepSound.getPitch() * 0.8F);

		world.setBlock(i, j, k, 0);
		if(!world.isRemote)
		{
			float var6 = 0.7F;
			double var7 = world.rand.nextFloat() * var6 + 1.0F - var6 * 0.5D;
			double var9 = world.rand.nextFloat() * var6 + 1.0F - var6 * 0.5D;
			double var11 = world.rand.nextFloat() * var6 + 1.0F - var6 * 0.5D;
			EntityItem entityitem = new EntityItem(world, i + var7, j + var9, k + var11, smelted);
			world.spawnEntityInWorld(entityitem);
		}
		itemstack.damageItem(1, player);
	}

	return true;
}

I'm gonna take a guess you decompiled Thaumcraft 2 and this is the pickaxe of the core code? It works though Thanks so much!

Link to comment
Share on other sites

I had it working in one of my mods, but it probably is roughly the same idea. As people have said, a smelting pickaxe is a pretty general thing, it's not likely to have many differences, if any, among themselves.

Link to comment
Share on other sites

I had it working in one of my mods, but it probably is roughly the same idea. As people have said, a smelting pickaxe is a pretty general thing, it's not likely to have many differences, if any, among themselves.

Thanks everything works

Link to comment
Share on other sites

I had it working in one of my mods, but it probably is roughly the same idea. As people have said, a smelting pickaxe is a pretty general thing, it's not likely to have many differences, if any, among themselves.

Do you know of any way I could make it so that it can't autosmelt things that an axe breaks and things that a shovel breaks?

Link to comment
Share on other sites

About the auto smelting pickaxe, i am not sure if you already gotten it working or gave up on it. But what if you checked wether it is being mined by that certain pickaxe before it drops the ingot/ore. So in your idDropped() method or whatever it is called you would have some checks to find out what broke the ore? and if it is the pickaxe drop the ingot else just drop the ore.

Link to comment
Share on other sites

  • 1 year later...

after Block. where it says blockList, blockList is underlined red and it doesnt go to anyhing that i can change it to, and ench.tagAt(x); says to add cast to "ench". help is greatly appreciated

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.