Quintinius

Oh, I've got that far - my mod builds fine, and I can even compile it and run it (alongside RTG) in a normal Forge installation without any problems. What I'm having trouble with is getting RTG to run in the deobfuscated development environment. Sorry, I could probably have made that clearer in the first place.

I tried a few more mods as well, and got similarly inconsistent results - WorldEdit, for example, crashes with similar errors, but Chisel doesn't. And I can't see what RTG, JEI and WorldEdit have in common that Chisel and HWYLA don't. Not sure what you mean by this. Is it part of the same problem? If not, you might be better off starting a new thread for it.

You will need to add an entity AI to attack the current target, and one to target the nearest hostile mob. Have a look at EntityWolf#initEntityAI for a good example of how that works. As far as I can see, though, vanilla doesn't have an entity AI for targetting the nearest hostile mob, so you will need to create it yourself. EntityAINearestAttackableTarget is close, but only accepts one type of targetable Entity. You can tell if a given type of Entity is hostile because it will implement the IMob interface.

I'm trying to develop a mod that depends on Realistic Terrain Generation (RTG) for terrain generation algorithms. My understanding is that, to load an external mod in the development environment, I can just place RTG's release jar into the /run/mods directory of my Eclipse workspace. According to some other forum threads I found, there used to be a problem with compatibility between obfuscated and deobfuscated versions of external mods, but apparently this has been changed in a recent version of Forge so that mods can be loaded whether or not they are obfuscated. Unfortunately, when I try this with RTG, Minecraft crashes after postinitialisation with a NoClassDefFoundError. This happens whether or not I include its API in the /src/api source folder. I'm pretty sure it's not a problem with RTG, because there are already other mods that do the same thing - and with the same version of both Forge (12.18.2.2099) and RTG (4.1.2.4) - apparently without any problems. I don't really understand FML well enough to be able to tell how, though, and I couldn't find any similar threads on the forums. Can anybody help? Here's the stack trace:

So, you're using the latest build.gradle, but it's still not working? I've got no idea what the problem might be, then, sorry. I'll take "Solved" out of the title though, so maybe someone else will stop by.

Unfortunately, that didn't work - setupDecompWorkspace overwrote it with the original dev.json (and then threw up the same error) - but I did find the actual problem! It turns out that, as of build 1583, Forge requires ForgeGradle 2.1 - but that hasn't been released yet, so you have to set up build.gradle to use the latest snapshot of ForgeGradle. It's possible to do this manually, but I suspect the easiest way for most people will be to download the most recent MDK from the Forge homepage, extract the MDK's build.gradle file and copy everything above the line starting "version =" into the same place in the mod's build.gradle, replacing everything that was there before. Mystery solved!

I've tried updating my build.gradle to reference 1.8.9-11.15.1.1722 and am getting this error when I run ./gradlew setupDecompWorkspace: > ################################################# ForgeGradle 2.0-SNAPSHOT https://github.com/MinecraftForge/ForgeGradle ################################################# Powered by MCP unknown http://modcoderpack.com by: Searge, ProfMobius, Fesh0r, R4wk, ZeuX, IngisKahn, bspkrs ################################################# :deobfCompileDummyTask :deobfProvidedDummyTask :getVersionJson :extractUserdev ~/.gradle/caches/minecraft/net/minecraftforge/forge/1.8.9-11.15.1.1722/userdev/dev.json could not be parsed :extractUserdev FAILED FAILURE: Build failed with an exception. * What went wrong: A problem occurred configuring root project 'Name of Mod'. > java.io.FileNotFoundException: Inherited json file (1.8.9) not found! Maybe you are running in offline mode? * Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. BUILD FAILED And here is the relevant part of the log when run with the --debug flag: 23:23:10.696 [DEBUG] [net.minecraftforge.gradle.util.delayed.DelayedBase] Resolving: {CACHE_DIR}/{API_GROUP_DIR}/{API_NAME}/{API_VERSION}/userdev/dev.json 23:23:10.707 [DEBUG] [net.minecraftforge.gradle.util.delayed.DelayedBase] Resolved: ~/.gradle/caches/minecraft/net/minecraftforge/forge/1.8.9-11.15.1.1722/userdev/dev.json 23:23:10.710 [DEBUG] [net.minecraftforge.gradle.util.delayed.DelayedBase] Resolving: {CACHE_DIR}/versionJsons 23:23:10.711 [DEBUG] [net.minecraftforge.gradle.util.delayed.DelayedBase] Resolved: ~/.gradle/caches/minecraft/versionJsons 23:23:10.765 [ERROR] [org.gradle.api.Project] ~/.gradle/caches/minecraft/net/minecraftforge/forge/1.8.9-11.15.1.1722/userdev/dev.json could not be parsed The first file mentioned, dev.json, is exactly identical to the current one in the Forge repo, and although I admit I actually have no clue how Gradle works, the error messages seem to indicate that it runs aground on line 6 of that file when trying to read/parse ~/.gradle/caches/minecraft/versionJsons/1.8.9.json. Unfortunately, beyond that, I've run out of ideas, and nobody else seems to have had this problem either. (Figures.) I'm probably just doing something really stupidly wrong, but nevertheless, any help is gratefully appreciated.