jarrett

Thanks! I've been reading conflicting info on what version of MC introduced resource packs. Are they available in 1.5.2?

I'd like to read some arbitrary files related to my mod. Specifically, these will be images and JSON config files. (I'm aware of the Forge config file format, but it's not suitable for my use case. So JSON it is.) These will not be save-specific files. I.e. they should be global to the Minecraft installation. So I'm thinking they would go somewhere in minecraft/config/NameOfMyMod. First, is this OK? Second, is there an API method I can call which will return the path to my mod's config folder? Once I have that path, I'll be able to read and parse the JSON data. Third, will it be possible use images in the config folder as textures? If not, is there any way to achieve something similar? Essentially, I want my mod to be able to use user-supplied textures. I'd rather not force users to open the .jar file and put them there. If necessary, I'd be willing to read the image data from the files myself, and pass that image data to an API method. I'm targeting MC 1.5.2.

I think he's asking whether you can: [*]Extend the reactor tile entity class [*]Cause your subclass to be instantiated instead of the reactor base class, in all cases where Minecraft would normall instantiate it. Crafting, on chunk load, etc.. I wish I could answer that. I've actually been wondering the same thing. I came up with the following ideas, but I don't know if they'll work. They're just hypothetical. [*]Override the reactor crafting recipe so it instantiates your extended reactor. [*]Take over the reactor's block ID. Perhaps this would solve the problem of updating reactors that existed before the addon was installed. If you're messing with the tile entity data, you'll need to be able to detect and read the original data.

The problem Yesterday, I downloaded the Forge 7.8.1.738 source for Minecraft 1.5.2. install.sh failed trying to access scala-library.jar with this error: scala-library.jar; cannot read zip file I was able to resolve the error, and I'm posting my fix for others who have the same problem. Why the problem occurs Here's my diagnosis of the underlying issue. The install script downloads a number of .jar files. When it tries to download scala-library.jar, the server returns a 404 page. But, the script doesn't detect this, and instead saves the HTML of the 404 page into scala-library.jar. Later, when something tries to read the .jar file as if it's a Java archive, it crashes, because the file contains HTML instead of valid .jar data. That's why it says "cannot read zip file." (Java archives are encoded in zip format.) The solution You need to give Forge a valid copy of scala-library.jar. I was able to obtain a copy from here: http://www.scala-lang.org/download/ Download the main Scala package from that page. Extract the archive and look in the lib subfolder. You should see scala-library.jar there. Be sure you get a version of Scala that's compatible with Forge. As of this writing, that's Scala 2.10.2. Later versions may work, but I can't promise that. Start with a freshly extracted copy of Forge. Run install.sh and let it fail. Copy your valid version of scala-library.jar (the one you got from scala-lang.org) into forge/mcp/lib, replacing the invalid version. Run install.sh again. It will ask you if you want to overwrite MCP. Say yes. For me, that resolved the issue, and install.sh succeeded. As a side note, the EAC mentions that you can download the .jars from forgeessentials.com. I tried this first, but the scala-library.jar from there appeared to be corrupted. I didn't spend much time investigating this error, because I was able to work around it by just downloading the file from scala-lang.org.

I have solved my problems. I'd like to post my experiences for the benefit of anyone else who is having similar problems. I've had astyle installed all along. But it appears that 6.4.1.436 cannot detect an installed astyle under some circumstances. I'm not sure exactly what triggers this error, but it happened to me. Thus far, 6.4.1.436 is the only build for which this error occurs for me. I've tested a number of builds, but certainly not anywhere near all of them. I never did figure out what was going on there, but that's OK, because I didn't have to. My solution was to switch to a later build, specifically, 6.4.2.448. This appears to be the last build for MC 1.4.5, which is why I chose it. Interestingly, the Releases forum topic for 1.4.5 doesn't point to this build. Instead, it points to 6.4.1.436, which is the one that gave me problems. I don't know what to make of that. Is 6.4.1.436 the officially supported build? Is 6.4.2.448 OK to use? I don't know the answers to these questions, but maybe someone more knowledgeable could fill in the gaps. In any case, I'm sticking with 6.4.2.448, unless someone advises me to do otherwise. It works for me, and I'm able to deploy my finished mod to a 1.4.5 instance running in MultiMC.

Looking at it again, I don't think the line I called "curious" is very curious after all. I misunderstood it to mean it was seeing astyle installed. But now I believe it means that it just found the astyle config file in the Forge distribution. So I guess that's not really odd after all. But any thoughts on why install.sh isn't seeing astyle? If worst comes to worst, I'll dig into the Python script and see where it's looking. But I'm hoping that maybe somebody knows a quick fix off the top of their head.

Well the weird thing is, astyle is installed. For verification: $ which astyle /usr/local/bin/astyle But thanks for pointing out the line where it says it couldn't find astyle. I didn't notice that before. I think that does get us closer to the root of the problem. How does Forge look for astyle? Does it just search the $PATH? Or is there some specific place it looks? If the latter, I could always symlink from there. Here's another line in the console output I find curious: # found ff, ff patches, srgs, name csvs, doc csvs, param csvs, renumber csv, astyle config Also, in case it wasn't clear before, I have successfully installed other versions of Forge on this computer. I even have a working mod. It's really just this particular Forge version that's giving me trouble.

Sorry, could you clarify what you mean by the console log? If you're referring to the output on the OS X terminal when running install.sh, here it is: http://pastebin.com/dKa0kd1n If you're referring to the log generated when the Minecraft client boots, unfortunately I haven't even gotten that far yet. The error occurs when installing the Forge dev environment via install.sh. Because I can't get past that step, it's not possible for me to boot the client either. In any case, I'd be totally fine with using a different Forge release, if that would be an easy solution. I'd be happy with any Forge version that enables me to target MC 1.4.5. Would you recommend a different build? Thanks so much for your help. It is much appreciated.

Yep, here's the complete log: http://pastebin.com/9mBWqWcq

Update: Problem solved. See my comment later in the thread for the solution. I'm attempting to develop a mod for 1.4.5. (The mod is written and working in 1.4.7, but I'm now trying to support 1.4.5 for compatibility with IC2.) Based on this page, I believe that I should be using Forge 6.4.1.436. I downloaded the source for that version. When running install.sh, I get this error: 81 errors 13 warnings ================== Client recompile failed, correct source then rerun updatemd5 The error message is actually much longer than what I've pasted, and includes 81 errors and 13 warnings, all seemingly coming from the Java compiler. The exact steps I performed were: [*]Download source [*]Extract zip file [*]Set permissions on install.sh [*]Run install.sh Should I be doing something different to make this version of Forge install? Or is there a different Forge source version I should download to target MC 1.4.5?