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


Forge Modder
  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by Awesome_Spider

  1. Don't register the item in init and the renderer in preinit, this will probably cause a nullpointer exception.
  2. Hmm. Not sure why they would tell you to do that. Just call setUnlocalizedName instead. Not sure if that's why it's not showing up.
  3. Why are you overriding getUnlocalizedName? You have to set the unlocalizedName by calling setUnlocalizedName.
  4. Basically, add a PropertyFacing property to your block, make your blockstate have states for each facing value, and in each you would rotate it using a "y" value (an angle) in each blockstate when it is facing a certain way. Also, make it point to a model called "orientable" instead of "cube_all". Hope this helps.
  5. I wanted basically the same question answered a while ago. You may find it helpful to look here.
  6. Yes, that should too. Is your registryName and Unlocalized name lowercase as well?
  7. And the item name has to be lower case.
  8. That's because you have to put the modid in "layer0" as well.
  9. umm... Just use the quick fix your IDE suggests? Edit: Sorry, I replied too late.
  10. When I look at NBTTagCompound#getTagList there is a parameter for the key and an int for the type. What would I put for the type?
  11. Ok. My library publishes to my maven repo, but when I try to add it as a dependency in my mod's build.gradle, it still doesn't show up. Any ideas?
  12. I tried that and it gave me an error. Error:(3, 0) Could not find method jar() for arguments [build_848yu15mitzovn826g9z2l9b1$_run_closure1@6e302bcd] on root project '1.11' of type org.gradle.api.Project. Was I supposed to edit any of the strings? Here is my build.gradle:
  13. I am trying to set/get a list or string array (doesn't matter which) to an ItemStack's nbt and there doesn't seem to be any method in NBTTagCompound to do that. Would I have to create a custom tag for this?
  14. Here is the build.gradle for the lib: buildscript { repositories { jcenter() maven { url = "http://files.minecraftforge.net/maven" } } dependencies { classpath 'net.minecraftforge.gradle:ForgeGradle:2.2-SNAPSHOT' } } apply plugin: 'net.minecraftforge.gradle.forge' //Only edit below this line, the above code adds and enables the nessasary things for Forge to be setup. version = "1.11-1.0.0" group= "wiseowl5.owlcore" // http://maven.apache.org/guides/mini/guide-naming-conventions.html archivesBaseName = "owlcore" sourceCompatibility = targetCompatibility = "1.6" // Need this here so eclipse task generates correctly. compileJava { sourceCompatibility = targetCompatibility = "1.6" } minecraft { version = "1.11-" runDir = "run" // the mappings can be changed at any time, and must be in the following format. // snapshot_YYYYMMDD snapshot are built nightly. // stable_# stables are built at the discretion of the MCP team. // Use non-default mappings at your own risk. they may not allways work. // simply re-run your setup task after changing the mappings to update your workspace. mappings = "snapshot_20170127" // makeObfSourceJar = false // an Srg named sources jar is made by default. uncomment this to disable. } dependencies { // you may put jars on which you depend on in ./libs // or you may define them like so.. //compile "some.group:artifact:version:classifier" //compile "some.group:artifact:version" // real examples //compile 'com.mod-buildcraft:buildcraft:6.0.8:dev' // adds buildcraft to the dev env //compile 'com.googlecode.efficient-java-matrix-library:ejml:0.24' // adds ejml to the dev env // the 'provided' configuration is for optional dependencies that exist at compile-time but might not at runtime. //provided 'com.mod-buildcraft:buildcraft:6.0.8:dev' // the deobf configurations: 'deobfCompile' and 'deobfProvided' are the same as the normal compile and provided, // except that these dependencies get remapped to your current MCP mappings //deobfCompile 'com.mod-buildcraft:buildcraft:6.0.8:dev' //deobfProvided 'com.mod-buildcraft:buildcraft:6.0.8:dev' // for more info... // http://www.gradle.org/docs/current/userguide/artifact_dependencies_tutorial.html // http://www.gradle.org/docs/current/userguide/dependency_management.html } processResources { // this will ensure that this task is redone when the versions change. inputs.property "version", project.version inputs.property "mcversion", project.minecraft.version // replace stuff in mcmod.info, nothing else from(sourceSets.main.resources.srcDirs) { include 'mcmod.info' // replace version and mcversion expand 'version':project.version, 'mcversion':project.minecraft.version } // copy everything else, thats not the mcmod.info from(sourceSets.main.resources.srcDirs) { exclude 'mcmod.info' } } idea { module { inheritOutputDirs = true } }
  15. Well, for question number two I know that some mod authors do either or. Some have a client proxy, server proxy, and common proxy, while some only have the client and common, in which case the client inherits the common. The client code would in this case be the only code that would need to be executed separate, so there would be no point in having a separate server proxy class I think.
  16. Can you show the code for the class where the packet is registered (not just the method you used for this)? Edit: Sorry, I didn't see your post.
  17. Where did you register your packet? Edit: Oh wait, I see it now.
  18. Ok, I am away from my code at the moment, I'll show that when I get home.
  19. I got the dependence y in forge worked out now, now all I need is access to my library in my code.
  20. Good to know. I'll change it over when I get the time.
  • Create New...

Important Information

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