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

MartinTheDragon

Members
  • Content Count

    14
  • Joined

  • Last visited

Community Reputation

0 Neutral

About MartinTheDragon

  • Rank
    Tree Puncher

Converted

  • Gender
    Male
  • Location
    Austria

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. By all means, I didn't want to hurt you or your feelings in any way. I was just wondering and asking if things could have been made differently, and as it seems, they sadly could not have. You misinterpreted my post. I of course appreciate the work all of you do. I just didn't know any better.
  2. Well, the developers of ForgeGradle clearly failed at this then. Was it really necessary to use the internal Gradle API?
  3. Build fails with > Failed to notify project evaluation listener. > org.gradle.internal.nativeintegration.services.FileSystems.getDefault()Lorg/gradle/internal/nativeplatform/filesystem/FileSystem; when I use a Gradle version above 4.9. (6.2.2) I checked, my buildscipt should be alright. This only happens when I apply the ForgeGradle plugin. I'm using Kotlin Script, but that shouldn't be the problem (the script works fine with Gradle 4.9). Of course, I could always just stay on that older version, but that would have several disadvantages. The most important one being that
  4. That is a way of doing it, but you would have to set so many parameters for every material you create. And if you just set the durability for the material and not for the tool itself, are you using a multiplier for the tool?
  5. Well, you could use a gray texture for your tool and then color it in the corresponding color of the material you chose with your enum. So you would have to make an enum with a constructor that has a color as an argument. Then you could for each material you have in your enum register all the tools automatically with the texture colored in the color of the material. At least that is how I would do it.
  6. I guess I should have checked earlier. It does save locale data in a list.
  7. You mean like that? (I am using Kotlin) override fun addInformation(stack: ItemStack, worldIn: World?, tooltip: MutableList<ITextComponent>, flagIn: ITooltipFlag) { if (worldIn != null && worldIn.isRemote) { var i = 0 val list = emptyList<ITextComponent>().toMutableList() while (true) { val translationKey = "${this.translationKey}.lore$i" val tmp = I18n.format(translationKey) if (tmp == translationKey) break else { list.add(StringTextComponent(
  8. I have created an item that reads the tooltip/lore defined in a language file, and it does that once every minute because it is subscribed to the ClientTickEvent. But I wondered if there was an event for when the language is being changed so I could read the file again instead of every minute. Or is there something else that would do that and I just need to hook it up to that?
  9. As I said, the problem is that it doesn't exist anymore. Do I have to implement some sort of interface?
  10. I've been trying to create an item that can be put into a furnace as fuel instead of an ingredient, but I can't find out how. In 1.12.2, you just had to override the method which returns the burntime. Now this method doesn't exist anymore.
×
×
  • Create New...

Important Information

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