Draco18s

It also allows other mods to do things with your blocks. Register them early!

Something didn't reobfuscate properly.

Hooray! You posted code! Boo! You didn't post the errors!

You're better off asking in the COG thread than the Forge forums this board is to help modders mod, not mod users use mods.

If by "libs" you mean "assets" and by "builds" you mean "reobf" then yes. You have to copy over your assets manually.

Correction: Vanilla will assign it.

(The modification needed is to fml.py which can be easily updated by downloading the last 1.6.4 version of the source and stealing its fml.py and adding it to the 1.6.2 source before installing). Haven't you heard? Reading is for chumps.

Hardly. Like it says on the top of the forum in BRIGHT FUCKING RED: You need to post the ForgeModLoader-client-0.log file.

While this is not technically wrong, the problem lies in where you've placed your texture (and changing the registration string isn't going to fix that, unless you get super lucky). In order to completely diagnose your problem I need to know where you're putting your texture file.

Packets coming from a player will pass a player entity to your packet handler. Its like magic: public void onPacketData(INetworkManager manager, Packet250CustomPayload packet, Player player) { }

1) You didn't say you updated the main post 2) I cannot assume that you updated the main post Now, I don't know anything about 1.7.2, but I'd try removing this: public Item func_149650_a(int p_149650_1_, Random p_149650_2_, int p_149650_3_) { return MoMinecraft.brokenObsidianItem; } Seems to me that vanilla code should be handling that...

No code: no help.

Did you register your entity? Did you create an item?

Find its static reference in the Block class, the wool / cloth block is done oddly.

Learn to read the code you are using please: Quote from DataWatcher.java: throw new IllegalArgumentException("Data value id is too big with " + par1 + "! (Max is " + 31 + ")"); And even some of those are already used: From http://www.minecraftforge.net/wiki/Datawatcher

http://lmgtfy.com/?q=minecraft+armor+model+tutorial

I do. https://github.com/Draco18s/Artifacts/blob/master/draco18s/artifacts/item/ItemArtifact.java (See how I check for null, and if null, I return a default non-null icon) I feel like I've got an array-based something somewhere, but I can't recall which mod that was offhand, much less which block or item.

This. I'm not even using 1.7 yet as the deobfuscation process is not even yet to the point when I started modding. And there were still common-use func_* calls. 1.7 not only has that problem, but a "everything is different now and the experienced modders are having trouble in places."

I can't without current code and current description of the problem. "It changed" is not a description. It's useless information that requires me to activate my psychic powers and the government hates it when I go rogue.

I honestly do not know what the problem is.

There suppose to be more of painting files. Like Model or something, cuz i havent seen any String on taking texture. EntityPainting uses an ENUM to describe paintings. The texture path is handled by the renderer, but the ENUM describes the painting name ("skull") as well as its UV position in the texture and width and height (UVWH are all full-block values, eg. 0,0 with width/height 1,1 would be a 1x1 painting located in the upper left of the texture, which at the default resolution would be 16x16 pixels).

You can use Loader.isModLoaded("IC2") in place of that reflection call. I wasn't aware of the Forge method when I did that.

Also: Tip: There are multiple ways to get rid of an item so it's no longer your active one. Tip #2: One of them involves Item Frames. An item that goes into a frame ceases to exist with no function calls or events. So unless your plan is to let the player have infinite* free infinity bows, this is an idea that is doomed to failure. Tip #3: The helmet no longer being worn / ceasing to exist will also need to be covered. *Pun not intended, but enjoyed. And only "inifinite-until-helmet-breaks" of course.

And if you put sanity checks in your getIcon function, you wouldn't have had the problem anyway.