Choonster

NEI Integration requires NEI, but you don't have it installed.

Search for "loading screen" in the EAQ.

I don't quite understand this. I thought the event handler method was called based on the method prototype. Doesn't the forge bus only look for methods that take event parameters for that bus, and similarly for the FML bus? Why would forge bus fire the LivingDropsEvent for example? The Forge and FML buses will be references to the same object (see how the FML bus is initialised here). If you register two instances of the same class on a bus, both instances will receive the event when it's fired.

A NullPointerException means you tried to access a field or call a method of a null value. The exception was thrown on line 270 of CraftingManager , which is this: aitemstack[i1] = ((ItemStack)hashmap.get(Character.valueOf(c0))).copy(); The only possible cause of the exception would be hashmap.get returning null , which means that there was a character in the recipe's shape string that you didn't specify an ingredient for. In future, mod development-related questions belong in Modder Support. You would have gotten help a lot quicker if you posted this there.

One or more of the mods you have installed (ExtraCells and possibly others) requires Applied Energistics to run.

TooManyItems is trying to load a client-only class on the server, this is an error with the mod. Make sure you're running the latest version for 1.7.10, then report this to the author (though it looks like it may not be maintained any more). It looks like you may have put some mods in minecraft.jar, don't do this. Forge mods (including the Forge version of TMI) are designed to be loaded from their own JARs in the mods folder. Edit: I'm not that familiar with TMI. If it's meant to be a client-only mod, don't install it on the server.

To generate custom terrain in your biome, override BiomeGenBase#genTerrainBlocks to populate the Block and byte (metadata) arrays. I have an example of a biome that generates Nether Brick instead of Stone here. In your case, you'd want to call the super method to generate the default terrain and then replace some Stone with your ore(s).

The installer downloaded joptsimple 4.6, but the Forge JAR's Class-Path manifest attribute is telling Java to look for 4.5. I think this is caused by Forge's build.gradle using the 1.8 JSON for the Class-Path manifest attribute instead of the 1.8.8 JSON. This is the offending line.

I had a look at Chisel's 1.7.10 CTM code and it's pretty complex. For each face, it checks for connections to all eight blocks surrounding the face and chooses the appropriate sub-icon from to render in each quarter of the face. It's probably possible in 1.8, but it will be tricky to implement using the standard blockstate/model system. You'll probably need a model composed of eight 8x8x8 cubes (a full block is 16x16x16) and a property for each corner of each face with seven possible values: not connected connected on side A, connected on side B connected on side A and B, connected on side A and diagonal, connected on side B and diagonal connected on side A, B and diagonal The value of this property will determine which texture you use for the corner. The individual cubes only need to have their outside faces defined, the inside faces don't need to be rendered. Forge's blockstates format will come in handy here. Using a custom model class may make things easier, but I don't know much about the system.

I don't know much about the system myself, but Forge has some examples here: code, assets

I tried running a server with Forge 1.7.10-10.13.4.1558-1.7.10 and the mods you listed (except Better Furnaces) and couldn't reproduce this error. I tried WorldEdit-Forge 6.0-beta-01 (from Curse) and 6.1.1-SNAPSHOT-dist (seems to have been downloaded by the other WorldEdit version), I couldn't find 6.0.1. I didn't download Better Furnaces because Chrome thinks the download linked in its Minecraft Forum thread is malicious. Try removing Better Furnaces and see if it works then.

I'm new to forge and gradle. I am not sure how to approach this solution because I don't know how to do anything "from" Gradle. Is there a particular file I should open up and edit from the forge source files? Put the code in your build.gradle script and set the environment variable it uses. This will likely only fix the warning, not the error.

Most blocks store the value of each of their properties in the metadata, which is saved with the world; but some blocks have properties whose values are only determined at runtime and aren't saved in the metadata. The individual connection properties of BlockFence are an example of these unsaved properties: they're not stored in the metadata, they're only determined by calling Block#getActualState . This returns an IBlockState with each connection property set based on blocks adjacent to the fence at the specified position ( BlockFence#canConnectTo ). Minecraft calls this method before choosing the model to render at each position (though it's also called in a few other places), allowing you to choose the model based on information only available at specific positions like neighbouring blocks or values from a TileEntity . I don't have any examples of connected textures using this system, but I do have a few other blocks that use it: BuildCraft-like pipes that connect to adjacent pipes: [url=https://github.com/Choonster/TestMod3/tree/dc884dbe20a1fa803ef4d7be2fd7d3babfda3d8d/src/main/java/com/choonster/testmod3/block/pipe]Block[/url] classes, blockstates file Coloured rotatable blocks with values stored in a TileEntity : Coloured Rotatable: [url=https://github.com/Choonster/TestMod3/blob/dc884dbe20a1fa803ef4d7be2fd7d3babfda3d8d/src/main/java/com/choonster/testmod3/block/BlockColoredRotatable.java]Block[/url] , [url=https://github.com/Choonster/TestMod3/blob/dc884dbe20a1fa803ef4d7be2fd7d3babfda3d8d/src/main/java/com/choonster/testmod3/tileentity/TileEntityColoredRotatable.java]TileEntity[/url] , blockstates file Coloured Multi Rotatable: [url=https://github.com/Choonster/TestMod3/blob/dc884dbe20a1fa803ef4d7be2fd7d3babfda3d8d/src/main/java/com/choonster/testmod3/block/BlockColoredMultiRotatable.java]Block[/url] , [url=https://github.com/Choonster/TestMod3/blob/dc884dbe20a1fa803ef4d7be2fd7d3babfda3d8d/src/main/java/com/choonster/testmod3/tileentity/TileEntityColoredMultiRotatable.java]TileEntity[/url] , blockstates file

The two lines are completely unrelated. The first is just a warning (not an error) that you're targeting an older version of Java but using the classes from the current compiler, this means that your code will only use language features from the old version but may still use classes or methods introduced in a newer version (which means your code may crash at runtime when run on the old version of Java). See this page and the pages linked by it for more details. This StackOverlflow answer explains how to set the path from Gradle. The second is the start of the actual compilation error.

Make sure the client and server both have the same setting configured for RailCraft's Residual Heat feature. Also make sure they have the same mods installed (apart from client- or server-only mods), it looks like the server is missing BuildCraft Compat.

Update BuildCraft.

If you update CodeChickenLib to 1.1.2.132 or newer and CodeChickenCore to 1.0.5.36, they should use the paths provided by ForgeGradle itself to find MCP mappings.

The resolution in that thread was to delete vecmath.jar in System > Library > Extensions, but I can't find such a file. I do have hidden files visible, so I'm pretty sure it's not hiding out somewhere in the folder. Is there any other solution you might know of? I'm afraid I can't help you any further. That was the only discussion of this error I've seen.

I managed to extend my previous example with a face rotation property: [url=https://github.com/Choonster/TestMod3/blob/dee37427c6851507b30409e995dce21ee150c33c/src/main/java/com/choonster/testmod3/block/BlockColoredMultiRotatable.java]Block[/url] , [url=https://github.com/Choonster/TestMod3/blob/dee37427c6851507b30409e995dce21ee150c33c/src/main/java/com/choonster/testmod3/tileentity/TileEntityColoredMultiRotatable.java]TileEntity[/url] , blockstates file Having a block with so many possible combinations of properties makes me glad that Forge's blockstates format exists. This should be pretty similar to what you're looking for, alexfadeev.

I'm obviously not the OP, but I managed to make a relatively simple block that stores its facing (just the standard EnumFacing values) in its TileEntity . You can see the implementation here: [url=https://github.com/Choonster/TestMod3/blob/da28151e33cd2f3bb9f7db1478e862fab629f220/src/main/java/com/choonster/testmod3/block/BlockColoredRotatable.java]Block[/url] , [url=https://github.com/Choonster/TestMod3/blob/da28151e33cd2f3bb9f7db1478e862fab629f220/src/main/java/com/choonster/testmod3/tileentity/TileEntityColoredRotatable.java]TileEntity[/url] , blockstates file Getting the facing synced correctly between all players was a bit tricky, but I just needed to call World#markBlockForUpdate when rotating the block to send the TileEntity update packet and when receiving the packet to update the model with the new facing.

You can link to specific lines on Github either by appending #L<line> to the URL or just clicking on the line. You can also link to a range of lines using #L<start>-L<end> at the end of the URL. In addition, you can link a range of lines by clicking a line number and then shift-clicking another line number.

The OP is overriding Block#isAir , which is what World#isAirBlock uses.

Does that show as an error for you? IDEA will let me compare a Block and IBlockState or any other interface without complaint (probably because a subclass could implement that interface), but not a Block and any other class (because a class can only extend one class).

Soul Shards: Reborn is trying to use a client-only class on the server. Report this to the author.

If you do end up writing some documentation on the system, you may want to consider making a pull request to Forge's Read the Docs site.