Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Fluorescent Flamingo

  • Content Count

  • Joined

  • Last visited

Everything posted by Fluorescent Flamingo

  1. Yesterday Eclipse suddenly stopped working for me, and I don't know why. I didn't mess around with anything, and I've never had this problem before in years of using the software. When I try to close the program it gives this error: An error has occurred. See error log for more details. Could not initialize class com.sun.org.apache.xml.internal.serializer.Encodings Upon checking the error log: I can't close Eclipse at all without using Task Manager now. This is only the most visible of many bugs and errors that have suddenly popped up
  2. You need to create your own class (preferably enum, it’ll be easier) and let it implement IItemTier as an interface. You’ll need to override all the methods of IItemTier in your new class - look at what the vanilla one does, and just replicate its functionality. Then you can just use your MyModItemTier.SOME_MATERIAL in the constructor of your new tool Items.
  3. I only just noticed the existence of a whole sub-folder full of recipe advancements. Having added plenty of custom recipes which apparently work just fine, I am now wondering if it's essential to create recipe advancements for them all too - is it functionally required or does it just have some effect on the recipe book? Also, why do all the recipe advancements for complex, multi-item recipes unlock depending only on a single ingredient?
  4. I'm trying to create an item that uses the standard 2D sprite model in the inventory, but for handheld rendering uses a different model. This item isn't a block. The only vanilla example of this is, I believe, the trident, but I can't figure out how to hook into the code for that in ItemRenderer. I thought it was as simple as adding another model called, e.g. "special_item#inventory.json", but no. After some searching I've found loads of old forum threads on how to achieve this in previous versions, such as 1.12, or 1.8 (here), but it seems the relevant methods (ModelLoader#setCust
  5. Ohhh.... so the code is a development tool for Mojang and modders to use, to avoid having to manually write the JSONs? That's very good to know.
  6. Hello everyone, After browsing the code for the Block and Item Tags system, and successfully having implemented my own item tag, something has me confused. Tags, and recipes, are defined in JSON files but there's a duplicate implementation of all of this in the actual code. In the BlockTagsProvider class, all those same vanilla tags which exist as JSONs are created dynamically, and the same for the Forge Tags in ForgeBlockTagsProvider. Ditto for items. And each of the hundreds of JSON crafting recipes are also duplicated in the code of RecipeProvider! Why do
  7. Ah. I wouldn't claim it's agonising, but it becomes a bit tedious if you have quite a long list of blocks. And we programmers like to avoid code reuse wherever possible, don't we? My first thought was a method like this: private static RegistryObject<Item> registerBlockItem(RegistryObject<Block> block, ItemGroup group) { return ITEMS.register(block.get().getRegistryName().getPath(), () -> new BlockItem(block.get(), new Item.Properties().group(group))); } but of course it failed because the RegistryObject's value doesn't exist at that point.
  8. Just wondering, is there a less intensive way to generate BlockItems from Blocks than manually declaring the whole block list in item form? In earlier versions you declared your Block, and when you registered it automatically created the associated ItemBlock. Now you have to declare all the Blocks and BlockItems separately, maintaining two lists of the same thing. It seems like the sort of thing that could be automated away with a convenience method.
  9. Thanks very much for both of your replies. I found out that I had a broken JDK installation, so I installed a new one and pointed to it in the gradle.properties, and then I was able to run gradlew eclipse as normal!
  10. EDIT: SOLVED by fixing my Java JDK installation. Gradle was trying to use an old Java version that didn't exist, so I downloaded the newest Java 8 JDK, and added the line 'org.gradle.java.home=C:/Program Files/AdoptOpenJDK/jdk-' to my gradle.properties file. Hi everyone, In trying to setup Forge for 1.15.2 (Eclipse) I keep running into the same problem. This is what I've done: Downloaded the Forge MDK (latest version, 1.15.2 - 31.1.27 - though I also tried with the Recommended version) Extracted all the files into my deve
  • Create New...

Important Information

By using this site, you agree to our Privacy Policy.