Jump to content

[1.16.5] How do i store simple NBT data on an item?


Alexmaster75

Recommended Posts

The idea is simple; under this phrase there's what should i do in minecraft but for context, this item it's a nuclear fuel and i want to create a reactor to put the fuel in; so, the fuel has 2 NBT tags: (1) it's for the damage, so in time the reactor subtracts 1 unit of damage; (2) it's the enrichment percentage, so you put uranium ingots into a machine, the player selects from 1 to 100 the percentage, then the machine, with a proportion, deletes the required uranium and creates this fuel, with the value selected by the player in it. So what is the purpose of this? It's in base of the value of the fuel, that the reactor decides how would the reactivity be, the burn rate, the heat generated, ecc.

 

-> A machine sets the variable in the item created at the moment to what the player has set (because it's a percentage it must be from 1 to 100 but that's secondary)

-> The item now has this value and nothing more (other that the maxDamage() value that has been set in the registry item class)

-> The item can be putted in another machine where the value gets read for processing (this damn item should be a kind of fuel, so the maxDamage it's used to be removed 1 unit every time it's been used in time)

 

That's it, the item it's just a container of 2 NBT values and nothing more, and i can't find anything, not even on these forums, mostly because it's all from 2011 to 2017, at least where i researched; so or i am a dumbass that should not even try modding, or i can't find anything

 

 

For now this is the code i come up with:

 

package net.alexmaster75.etg.item.custom;

import net.minecraft.item.Item;
import net.minecraft.item.ItemStack;
import net.minecraft.nbt.CompoundNBT;
import javax.annotation.Nullable;

public class EnrichedUraniumFuel extends Item {
    public EnrichedUraniumFuel(Properties properties) {
        super(properties);
    }

    @Nullable
    @Override
    public CompoundNBT getShareTag(ItemStack stack) {
        final int EnrichmentPercent = 0;
        CompoundNBT nbt;
        nbt = super.getShareTag(stack);
        return nbt;
    }
}

 

Edited by Alexmaster75
Link to comment
Share on other sites

Hi!

CompoundNBT works like this:

1. you get the Compound from super

2. you add things to it (there are methods for this)

3. you store it by returning it to the function

But I think you are in the wrong function. I'm not sure, however, I think you need to do this in a special method called only once

Sorry if my Posts are weird sometimes, I just try to help and learn as much as I can :D

Also: PLEASE use SPOILERS for logs!

Link to comment
Share on other sites

 

19 minutes ago, Luis_ST said:

define does not work, show what you have tried

11 hours ago, Alexmaster75 said:

 

 

package net.alexmaster75.etg.item.custom;

import net.minecraft.item.Item;
import net.minecraft.item.ItemStack;
import net.minecraft.nbt.CompoundNBT;
import javax.annotation.Nullable;

public class EnrichedUraniumFuel extends Item {
    public EnrichedUraniumFuel(Properties properties) {
        super(properties);
    }

    @Nullable
    @Override
    public CompoundNBT getShareTag(ItemStack stack) {
        final int EnrichmentPercent = 0;
        CompoundNBT nbt;
        nbt = super.getShareTag(stack);
        return nbt;
    }
}

 

I tried this, the registration of the item it's just a registry of all the items, here's what:

package net.alexmaster75.etg.item;

import net.alexmaster75.etg.ETG;
import net.alexmaster75.etg.item.custom.EnrichedUraniumFuel;
import net.minecraft.item.Item;
import net.minecraftforge.eventbus.api.IEventBus;
import net.minecraftforge.fml.RegistryObject;
import net.minecraftforge.registries.DeferredRegister;
import net.minecraftforge.registries.ForgeRegistries;

public class ModItemsMain {

    public static final DeferredRegister<Item> ITEMS =
            DeferredRegister.create(ForgeRegistries.ITEMS, ETG.MOD_ID);
  
  
  
  	public static final RegistryObject<Item> ENRICHED_URANIUM_FUEL = ITEMS.register("enriched_uranium_fuel",
            () -> new EnrichedUraniumFuel(new Item.Properties().group(ModItemMainGroup.MAIN_GROUP).maxDamage(2000)));
  
  
  	public static void register(IEventBus eventBus) {
        ITEMS.register(eventBus);
    }

}

I excluded all the other items just for the sake of the context

Edited by Alexmaster75
Link to comment
Share on other sites

8 hours ago, Alexmaster75 said:

i tried and it doesn't work, primarily i'm not getting where exactly i should code that piece in

post the code which use the code mentioned by D7 (ItemStack#getOrCreateTagElement), it is also possible that the method is called ItemStack#getOrCreateTag depends on the mappings you use

Link to comment
Share on other sites

3 hours ago, Luis_ST said:

post the code which use the code mentioned by D7 (ItemStack#getOrCreateTagElement), it is also possible that the method is called ItemStack#getOrCreateTag depends on the mappings you use

package net.alexmaster75.etg.item.custom;

import net.alexmaster75.etg.ETG;
import net.minecraft.item.Item;
import net.minecraft.item.ItemStack;
import net.minecraft.nbt.CompoundNBT;

import javax.annotation.Nullable;

public class EnrichedUraniumFuel extends Item {
    public EnrichedUraniumFuel(Properties properties) {
        super(properties);
    }

    @Nullable
    @Override
    public CompoundNBT ItemStack#getOrCreateTagElement(ETG.MOD_ID) {
        super(EnrichedUraniumFuel);
        return super.getShareTag(stack);
    }
}

Am i dumb?

Link to comment
Share on other sites

package net.alexmaster75.etg.item.custom;

import net.minecraft.item.Item;

public class EnrichedUraniumFuel extends Item {
    public EnrichedUraniumFuel(Properties properties) {
        super(properties);
    }

    public String getOrCreateTagElement(String enrichedPercentage) {
        return enrichedPercentage;
    }

}

Should resemble this?

Link to comment
Share on other sites

i'm trying to access that method from, i don't even remember, i found this "https://nekoyue.github.io/ForgeJavaDocs-NG/javadoc/1.16.5/net/minecraft/item/ItemStack.html" but i don't know if it is correct or anything; i didn't take any java class irl but i don't think calling this method should be this complicated, or the more logical thing would be that i'm just stupid and i'm not getting such a simple idea

Link to comment
Share on other sites

29 minutes ago, diesieben07 said:

I would advise you to just look at the code in your IDE

where is it, it's obviously more logical looking in the IDE and i swear that was the first thing i did, but didn't find it

It would be way more easy understand from the file that from examples online

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.