Jump to content

shadowfacts

Forge Modder
  • Posts

    588
  • Joined

  • Last visited

Everything posted by shadowfacts

  1. Correct me if I'm wrong, but I believe FG's scanning of dependencies for ATs was only added in FG2.
  2. Ok. OP, copy the TiCon access transformer into src/main/resources/TCon_at.cfg
  3. Yes. Sticking "PAYED IF HELPED" in your titles isn't a good way to learn. Be patient, not everybody can spend all day on forums helping people. We have real lives too. P.S. "paid" is the past tense of "pay", not "payed".
  4. When your mod block is placed, you call World#setBlock for all of the blocks in your structure.
  5. I'm having trouble understanding your mangled version of "English". Could you please rephrase it? Once we understand what you're trying to say, we'll probably be able to help you better.
  6. coolAlias' suggestion is the correct method. Tells us what you tried (show your code) and tell us went wrong and we'll probably be able to help you.
  7. ItemStack has an NBTTagCompound field.
  8. Each item doesn't have its own data. Each ItemStack has it's own data. In the game, there is only ever 1 instance of each item.
  9. Depends, do you mean your own cauldron block or the Vanilla one? Making your own would be the easiest way to accomplish this. Your block would have a TileEntity that stored an ItemStack[] which would be your inventory, then in your block, you would perform the appropriate checks in onEntityCollidedWithBlock, then add the EntityItem's item stack to the TE's inventory and kill the EntityItem.
  10. Use an OreDictionary recipe (ShapedOreRecipe and ShapelessOreRecipe), you can then use OreDictionary names instead of items/blocks/itemstacks directly. GameRegistry.addRecipe(new ShapedOreRecipe(YourItems.output, "# #", "###", "###), '#' "ingotCopper");
  11. No, a .jar file is a .zip file with a different extension. Try renaming a .jar to .zip, you can then open it up with whatever extraction program you like. OP, the error specifically happens when FML is trying to parse your mod metadata (the mcmod.info) file. Can you post that?
  12. 1. Does the mcmod.info file exist? 2. Can you show the whole log? 3. Heh, nice ironic username
  13. No, a missing texture is not going to cause an NPE. OP, the problem is you're adding things to a list that is null, before you add anything to your lists you need to initialize them with an empty ArrayList.
  14. You can put the deobfsucated version of your dependency in the libs folder of your root project, the whole thing will then be included in eclipse (you'll need to re-run gradle eclipse).
  15. I'm going to guess that this is on an obfuscated server. How are you compiling your mod? If it's not by using gradle build, your mod won't get reobfuscated.
  16. Are you sure that inventory isn't null when getStackInSlot is called? In your TE you are setting it to null at line 77 and line 86, I think you mean to be setting inventory[par1] to null, not inventory.
  17. The Class is the is class of entity you want to retrieve and the AxisAlignedBB (axis aligned bounding box) is the region from which you want to retrieve entities.
  18. Jabelar has a very good tutorial which explains how to do this. It is for 1.7.10, so you may need to make a couple alterations, but for the most part, everything should be the same.
  19. Also, there are examples of an EnergyStorage, energy TileEntity, and an energy item.
  20. You could also add the compiled library mod jar as a compile time dependency and just not shade it.
  21. *.iml, *.iws, and *.ipr
  22. I'm not sure about the first method, but the easiest way is probably to shade your dependency. This is the official tutorial. You will only be able to shade your library mod into your actual mod if the library mod doesn't have an @Mod class.
  23. Unless you include your core mod via Gradle (easiest would be using a compiled jar and potentially shading it), Gradle has no idea if they exist.
  24. Nobody is just going to write code for you. We will give you the tools you need to learn and write your own code. This is the explanation of events that I wrote.
×
×
  • Create New...

Important Information

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