Draco18s

Ugh. Getting the super return, substringing it, and concatenating it.... It's almost like there'd be an easier way to do that.

Yeah, it's just superfluous code. It is technically a bug, but one that doesn't mean anything.

Go find MovingPositionedSound and then go find it's super class. Which is unsurprisingly called...PositionedSound.

It's a new system, but it's not that hard to understand and there are several tools out there (like McCrayfish Model Creator) that make things easier.

I apologize, I thought that json was poinging at one of the block models you created. Undo that, that's the item model. There might be a problem there as well, but I can't see it. That said, there's still the same problem: Your olportal_ew.json file (and the other one) has a "portal": texture definition, but the elements uses "#olportal" so these are not hooked up to each other.

Change "all": "chemmix:blocks/olportal" To "olportal": "chemmix:blocks/olportal"

"texture": "#olportal" "all": "chemmix:blocks/olportal" ...seriously? You defined a variable called "olportal" and then said "set the variable 'all' to [texture]"

Double click on a class to open it and look at the object hierarchy window.

A Minecraft modding tutorial wouldn't help you with the problems you have. You need to have a stronger understanding of OOP first.

Everything in the cpw package moved to net.minecraftforge. Rather than typing out imports, let your IDE do it for you. Remove all your import lines, then hover over each object one after the other and import the right thing (or hit ctrl-O). Also, do not do Main instance = new Main() , that "new Main()" portion is unnecessary and will be overwritten by Forge when it instantiates your mod.

If you want it to glow in the dark, you can do that with baked models.

There's two gradle commands. Did you run both?

"Skipped" means that the file needing to be downloaded is already current. It's not an issue.

AH HAHAHAHAHA This will never work. If someone is cheating, they can decompile your mod and make it report whatever the fuck they want. Only one thing is ever true about a client/server interaction: Assume the client is always lying.

You done gone fucked up. Start over by reinstalling Forge.

I think it needs to extend a Capability object/interface of some sort, but that would be a valid interface for the custom one, yes. You'd then need to implement it. I'm away from dev, so I can't check.

Do not strip that off! Unlocalized names are GLOBAL, if you add an item with the unlocalized name "item.thingy.name" (or I should say, that's what shows up when you go to put it into your localization file) and localize it to "Awesome Hat" and then another mod comes along and creates an item with an unlocalized name of "item.thingy.name" localized to "Neat Wand" guess what? Both items in-game will display with the same name, depending on which mod loads second. Instead, if both mods left their mod ID in the unlocalized name, this would not happen.

getRegistryName().toString() ResourceLocations aren't implicitly converted to strings.

ModelLoader does not exist on the dedicated server. Do you understand why the proxy system exists?

Shame it will still crash a dedicated server because it has client-side-only code in a common place.

Alot is Better than You at Everything

Proxy files are mandatory: you need one (client) to register the item renderers.

You can use a 1 power explosion if you want it to do less damage. That's irrespective of the particle effects. If you're having a problem with the particles, go dig into the doExplosion methods and search out what it does to make them.

Please read this: http://meta.stackexchange.com/questions/66377/what-is-the-xy-problem You have asked Question X when your problem is Y. You need to spawn particles.

I don't understand your goal.