Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 02/06/20 in all areas

  1. In ServerPlayNetHandler::processEntityAction But if you call that setElytraFlying method from PlayerEntity does that have the desired effect? The setFlag method is protected, but all setElytraFlying appears to do is set it. I don't see any additional checks after it is called. It won't fully replicate the behavior of Elytra, but my guess is that it is in charge of the flying part.
    1 point
  2. The only reason you'd want two methods is if you plan to pass strings sometimes and resource locations other times, but you aren't planning on doing that, are you? (In terms of different kinds of registries, its already a generic method that supports everything you need)
    1 point
  3. I updated my build.gradle forge/mappings version yesterday, this is what my line looks like: And it worked no problemo. Good luck!
    1 point
  4. Forge Version: 31.1.0 Minecraft Version: 1.15.2 Downloads: Changelog: (Direct) Installer: (AdFocus) (Direct) MDK: (AdFocus) (Direct) Intro: This is the first recommended build for 1.15.x! This would of been out a few weeks ago, but Mojang decided to release 1.15.2, so we figured it'd be best to hold off until that version stabilized. As you may have read, we dropped 1.12 support a few weeks ago and now concentrate on 1.14.4 and 1.15.2 until 1.16 drops. 1.15.x brought many changes to the rendering engine and incorporated some parts of the new rendering engine known as "Blaze3D", but this release was still a lot faster than 1.14.x, thanks to the mod loading and launching rewrite we started in 1.13 being complete. Also thanks again through all the contributors for this release that helped to fix bugs and bring new features to forge. Changelog: New: Removed and cleaned up old code Remove third-party vecmath library in favor of using the new minecraft functionality Allow logos in the mod screen to be scaled differently Allow models to override be overridden when using OBJ models Make more Data Generator stuff usable by modders Add support for custom nether portal frame blocks Added new Click Input Event Added entity nameplate rendering event Added support for gui_light model option Re-implemented the ITeleporter interface to allow moders to control dimensional teleporting more easily Allow mods to more easily specify a custom texture for chests Add support for sending fluid stacks over the network more easily Add support for fluid overlay rendering for custom fluids Fixes: Fixed incorrect item lighting Fixed broken stairs and fence rendering Fixed keybindings not saving Fixed items being too small when dropped Fixed mod list screen Fixed capability data not being transferred when returning from the end Fixed incorrect warning screen caused by removed vanilla sounds Fixed game crash with modded entities Fixed bucket rendering Fixed crash when parsing custom obj models Fixed items not being colored correctly with custom colors Fixed items rendering too dark Fixed many other rendering related issues Fixed particles not rendering correctly due to wrong GL state Fixed incorrect item lighting Fixed crash when using certain fonts Fixed crash when building quads for rendering Fixed dyes tag not automatically finding new dyes Fixed Big Mushrooms not generating Fixed Raw Mouse Input Event Fixed fullbright lighting Fixed Fish Bucket not being usable by mods Fixed breaking overlay Fixed Widget Foreground Color not allowing pure black Fixed entities turning on a spot Fixed RenderType loosing it's mapping for registry replacements Fixed extended version of getLightValue not being used everywhere Fixed Wakeup Event not being called at the correct spot Fixed mod resources ordering Fixed Player Changed Dimension event providing the wrong dimension Fixed Keybinds modifier not working correctly Fixed Chunk Data Load Event not fireing Fixed small typos in forge config Fixed restoring blur mipmaps Fixed Right Click Block not being called on client and server Fixed crash on new java 8 versions in development environments Fixed a bunch of events not having the new rendering context Fixed Attacks/Punches not registering Fixed functionality for rails to have different maximum speeds Fixed registry desync, causing entities or sounds to be mixed up when connecting to a server Fixed compression system used by the installer to make downloads smaller.
    1 point
  5. You need to set the render layer using RenderTypeLookup#setRenderLayer within your FMLClientSetupEvent to make blocks transparent. It takes in two parameters: the block and the RenderType. The RenderTypes are as follows: Solid - field_228615_R_ Cutout Mipped - field_228616_S_ Cutout - field_228617_T_ Translucent - field_228618_U_ Translucent (No Crumbling) - field_228619_V_ Leash - field_228620_W_ Water Mask - field_228621_X_ Glint - field_228622_Y_ Entity Glint - field_228623_Z_ Lightning - field_228624_aa_ What you are looking for is either cutout mipped or cutout so use either RenderType#field_228616_S_ or RenderType#field_228617_T_ to accomplish this.
    1 point
  6. IDE: IntelliJ IDEA Forge Version: 1.14.4 - 28.1.0 I'm able to develop and test the mod without any issue in the IDE with the runClient task. I know that I need to package the external libraries with the mod as told in the forge documentation so I use the Jar-in-Jar approach. Placing the JAR in the mods folder, loading the world and entering the chat command to start the mod crashes the game and gives me the following error: The game crashed whilst exception in server tick loop Error: java.lang.NoClassDefFoundError: com/microsoft/signalr/HubConnectionBuilder I have placed the JAR (signalr-3.0.0.jar) and Meta (signalr-3.0.0.jar.meta) files in the resources/META-INF/libraries directory. Here are the Meta file contents: Maven-Artifact: com.microsoft.signalr:signalr:3.0.0 Here is an excerpt from my build.gradle file where I define dependencies and manifest attributes: dependencies { minecraft 'net.minecraftforge:forge:1.14.4-28.1.0' implementation 'com.microsoft.signalr:signalr:3.0.0' } jar { manifest { attributes([ "Specification-Title": "mymod", "Specification-Vendor": "glorious", "Specification-Version": "1", "Implementation-Title": project.name, "Implementation-Version": "${version}", "Implementation-Vendor" :"glorious", "Implementation-Timestamp": new Date().format("yyyy-MM-dd'T'HH:mm:ssZ"), "ContainedDeps" : "signalr-3.0.0.jar", ]) } } Which creates the following MANIFEST.MF (ends with empty line): Manifest-Version: 1.0 Implementation-Title: MinecraftMod Implementation-Version: 1.0 Specification-Vendor: glorious Specification-Title: mymod Implementation-Timestamp: 2019-11-05T18:29:41+0000 ContainedDeps: signalr-3.0.0.jar Specification-Version: 1 Implementation-Vendor: glorious I'm not sure what I could be missing here, any help is appreciated. EDIT: Problem solved I went back to Gradle Shadow and tried a different approach, here are my changes to build.gradle: buildscript { ... dependencies { classpath group: 'net.minecraftforge.gradle', name: 'ForgeGradle', version: '3.+', changing: true classpath 'com.github.jengelman.gradle.plugins:shadow:4.0.4' } } apply plugin: 'net.minecraftforge.gradle' apply plugin: 'com.github.johnrengelman.shadow' ... dependencies { minecraft 'net.minecraftforge:forge:1.14.4-28.1.0' shadow 'com.microsoft.signalr:signalr:3.0.0' } shadowJar { project.configurations.shadow.setTransitive(true); configurations = [project.configurations.shadow] classifier '' // Replace the default JAR } reobf { shadowJar {} // Reobfuscate the shadowed JAR } jar { manifest { attributes([ "Specification-Title": "mymod", "Specification-Vendor": "glorious", "Specification-Version": "1", "Implementation-Title": project.name, "Implementation-Version": "${version}", "Implementation-Vendor" :"glorious", "Implementation-Timestamp": new Date().format("yyyy-MM-dd'T'HH:mm:ssZ") ]) } } The key here was the line: project.configurations.shadow.setTransitive(true); Although the setTransitive() method summary says transitive is true by default it didn't seem to work without explicitly specifying. Thanks to user Choonster for their build.gradle file from this forum post. Thanks to user KhogaEslam for their comment on this github issue. I hope this helps anyone having the same issue.
    1 point
×
×
  • Create New...

Important Information

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