LexManos

Yes, we fix a bug related to interacting with iron doors. We have for years, get over it.

Possibly, either way you should tell the mod author to update.

Give the exact page, and link you clicked to download. Screenshots help Just checked the files page everything is fine. Edit: Seems adfocus is having a caching issue, just use the direct downloads.

CCC has no valid uses for devs in 1.8+ Stop using it.

There is no crash here.

Known and fixed bug, update Forge.

"Pay us and we'll remove the need for credentials on your launcher!" Really... really not a cracked launcher!?!?

We do not support 1.6.4, you should update or do your own research. 1.7.10 is feasible, 1.8 is where we currently are at. 1.9 is just around the corner.

Make sure you have access to the internet, also post the logs. The EAQs exist for a reason.

{ "forge_marker" : 1, "defaults": { "textures" : { "texture": "blocks/quartz_ore" }, "model": "pressure_plate_down" }, "variants": { "power": { 0: {"model": "pressure_plate_up"}, 1: {}, 2: {}, 3: {}, 4: {}, 5: {}, 6: {}, 7: {}, 8: {}, 9: {}, 10: {}, 11: {}, 12: {}, 13: {}, 14: {}, 15: {} } } } Something like that should work, haven't tested it but it's the idea. 1.9 expands things to have predicates which can make this a little better but we'll see when it actually goes live and we see what we can deal with. Or, if you use POWERED as a unlisted property in getActualState and then filter out the power you can do this: { "forge_marker" : 1, "defaults": { "textures" : { "texture": "blocks/quartz_ore" }, "model": "pressure_plate_down" }, "variants": { "powerd": { "true": {}, "false": {"model": "pressure_plate_up"} } } }

Sadly you have to follow the basic rules that are put in place for blocks. The reason it 'bugs' out in Forge is because we treat stairs {and slabs, and other blocks} correctly allowing for the proper sides that are solid to be detected as solid. This is what allows us to let torches stay on the sides of stairs, or to have mods have covers that are treated as solid. Things like that. There may be a way to trick it into not doing this by making the solid block you're placing against not have any cull faces but that would be a waste for the rest of the world. I would just say, even tho that model looks cool, you need to keep some semblance of the same shapes as vanilla. Else your torches would look weird when placed on them as well. Remember that Minecraft knows about the blocks in code, and nothing about resources can change what the game thinks the blocks are shaped as.

Inequalities and stuff like that don't work. You have to specify all your variants. This isn't magic you have to tell it what states your block has.

Yes, every permutation of every property gets a blockstate created for it thus all your 'invalid' states STILL exist and take up memory. Even if they are not put into the ID mapping. Admittedly as BlockState implementation is a small class, that's not much memory for you, wasting maybe ~500 bytes. But waste is waste. As for why they don't use mTs/sTm in networking. state = MAP[(ID<<16) | meta] is thousands of times faster then state = MAP[iD].mTs(meta)

Take these with a rain of salt code-style wise as they are patches but: Furnaces Chests BrewingStands This is my original test code which shows my intention of how modders should so it with Caps that Forge/They don't provide {Doing it this way gives soft-dependencies} https://github.com/LexManos/MinecraftForge/blob/Capabilities/patches/minecraft/net/minecraft/tileentity/TileEntityFurnace.java.patch#L58 This shows my original test code which creates, and queries a TE for it's capability: https://github.com/LexManos/MinecraftForge/blob/Capabilities/src/test/java/net/minecraftforge/test/capabilitytest/TestCapabilityMod.java#L27-L62 It's not to difficult. Someone write better docs.

You should not be using POWERED then, as in memory you're taking up twice as much room as you need to because you have 'invalid' states in the IBlockState table. In your renderer you should just have a >0 check. Or, as others have suggested use IUnlistedProperty and fill it in in getActualState. Beyond that, depending on how you register your class things could get odd with the metadata. What state does that pass in that is 'invalid'?

This stuff is fairly simple, and we have examples in Forge.... Not sure why people are getting so confused.

The log file will give you more information. Most likely you are having issues decompressing the libraries because you don't have enough ram. You can fix this by reading the EAQs on how to add extra ram. Or you could go to maven central and download/install the scala libraries manually.

Run the installer jar file as described in the eaq, or the video in my signature and post the logs from the console window. If you cant figure that our youll want to go reinstall java and then run the jarfix in the eaqs.

Yes, the resoure location should be your mod id : some internal name you want

That is horrible... that should not be the case. Show the rest of your class.

No, istorgae is for the default implementation of serialization. If youre attaching to another entitiy that is not your own and you want tonstore data, your icapapbilityprovider must implement inbtserializeable.

If only your te had a way for people to edit the integer... perhaps a method that when given an integer assigns it to the internal value.. setting it if you will....

It does this by attempting to download the file but saying to there server "this is the one i have dont send me anything if its the same as yours" Which is really specific to how their host is setup and considering most othere hosts arnt configured for that they just send the file... mojang really needs to switch over to normal maven .sha1/.md5 structure u.u Anyways yes, it just looks like its downloading forge but we just give them a 404.

Not for installing the client.

Yes, the logs from that run.