Jump to content

2 issues with Eclipse, following "Basic Modding" tutorial


natron77

Recommended Posts

I am following the Basic Modding tutorial on the wiki (www.minecraftforge.net/wiki/Basic_Modding), trying to make a Forge mod for the first time.

Files I'm using: minecraftforge-src-1.4.7-6.6.1.524.zip, jdk1.6.0_39, Eclipse Europa 3.3.2

 

I installed Forge fine (install.cmd completed successfully)

 

When I launch Eclipse, and set the workspace to \forge\mcp\eclipse, I get these errors:

Project 'Minecraft' is missing required library: 'jars/bin/jinput.jar' Minecraft Build path

Project 'Minecraft' is missing required library: 'jars/bin/lwjgl_util.jar' Minecraft Build path

Project 'Minecraft' is missing required library: 'jars/bin/lwjgl.jar' Minecraft Build path

Project 'Minecraft' is missing required library: 'jars/bin/minecraft.jar' Minecraft Build path

Project 'Minecraft' is missing required library: 'lib/argo-2.25.jar' Minecraft Build path

Project 'Minecraft' is missing required library: 'lib/asm-all-4.0.jar' Minecraft Build path

Project 'Minecraft' is missing required library: 'lib/bcprov-jdk15on-147.jar' Minecraft Build path

Project 'Minecraft' is missing required library: 'lib/guava-12.0.1.jar' Minecraft Build

 

Additionally, if I try to follow the next step of the Tutorial (expand the Minecraft src package), the directory is empty.

Link to comment
Share on other sites

No problem, this is an odd one.  ???

 

Here, try this out:

 

-Right-click the project, select Properties

-Go to Java Build Path, Libraries tab

-Are any errors listed? Are the "missing" files there despite what it said earlier?

-If the JARs aren't there, manually add them from \mcp\jars\bin and \mcp\lib. If they are though, first remove them and then re-add them.

 

Let's see if this works out.

Link to comment
Share on other sites

Good, half the problem is fixed! ;D Now for the other half:

 

-Right-click the src you have highlighted in your image, select Properties

-What's the Location and Resolved Location looking like? It should be something like MCP_LOC\src\minecraft & C:\whatever\forge\mcp\src\minecraft respectively

-Click the "Edit..." button next to Location

-Verify that it's actually pointing to \forge\mcp\src\minecraft via "Folder..."

 

Fingers crossed!

Link to comment
Share on other sites

Good, half the problem is fixed! ;D Now for the other half:

 

-Right-click the src you have highlighted in your image, select Properties

-What's the Location and Resolved Location looking like? It should be something like MCP_LOC\src\minecraft & C:\whatever\forge\mcp\src\minecraft respectively

-Click the "Edit..." button next to Location

-Verify that it's actually pointing to \forge\mcp\src\minecraft via "Folder..."

 

Fingers crossed!

 

Both Location and Resolved location are Unknown, and there is no Edit button:

PTzq7W3.png

Link to comment
Share on other sites

*blinkblinks* ...Well, that explains the real problem. ???

 

While this is going on, which Eclipse are you using?

 

Let's tackle this another way then:

 

-Right-click src back in the Project Explorer, Build Path, Configure Build Path (We're going back to Java Build Path, this is just another way to do it for what we want right now)

-Because of what you showed before, the Source tab should be empty of any entries. Does "Add Folder..." and "Edit..." appear?

Link to comment
Share on other sites

Okay, that might actually be part of the problem... Europa is a 2007 release, meant for JRE 5. :(

 

We can go two routes at this point:

 

1.) Scrap Europa and download a newer version of Eclipse, see if it does the same thing with the workspace

2.) Continue working with this, see if we can get anywhere with this, I doubt this compiler is going to be helpful though

 

Assuming you want to continue on this, use Edit and there hopefully will be a "Browse..." button next to Linked Folder Location. Try to get it to match up with your intended directory if there is.

Link to comment
Share on other sites

  • 4 months later...
  • 4 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • I am not using hardcoded recipes, I'm using Vanilla's already existing code for leather armor dying. (via extending and implementing DyeableArmorItem / DyeableLeatherItem respectively) I have actually figured out that it's something to do with registering item colors to the ItemColors instance, but I'm trying to figure out where exactly in my mod's code I would be placing a call to the required event handler. Unfortunately the tutorial is criminally undescriptive. The most I've found is that it has to be done during client initialization. I'm currently trying to do the necessary setup via hijacking the item registry since trying to modify the item classes directly (via using SubscribeEvent in the item's constructor didn't work. Class so far: // mrrp mrow - mcmod item painter v1.0 - catzrule ch package catzadvitems.init; import net.minecraft.client.color.item.ItemColors; import net.minecraft.world.item.Item; import net.minecraftforge.registries.ObjectHolder; import net.minecraftforge.fml.event.lifecycle.FMLClientSetupEvent; import net.minecraftforge.fml.common.Mod; import net.minecraftforge.eventbus.api.SubscribeEvent; import net.minecraftforge.client.event.ColorHandlerEvent; import catzadvitems.item.DyeableWoolArmorItem; @Mod.EventBusSubscriber(bus = Mod.EventBusSubscriber.Bus.MOD) public class Painter { @ObjectHolder("cai:dyeable_wool_chestplate") public static final Item W_CHEST = null; @ObjectHolder("cai:dyeable_wool_leggings") public static final Item W_LEGS = null; @ObjectHolder("cai:dyeable_wool_boots") public static final Item W_SOCKS = null; public Painter() { // left blank, idk if forge throws a fit if constructors are missing, not taking the chance of it happening. } @SubscribeEvent public static void init(FMLClientSetupEvent event) { new Painter(); } @Mod.EventBusSubscriber private static class ForgeBusEvents { @SubscribeEvent public static void registerItemColors(ColorHandlerEvent.Item event) { ItemColors col = event.getItemColors(); col.register(DyeableUnderArmorItem::getItemDyedColor, W_CHEST, W_LEGS, W_SOCKS); //placeholder for other dye-able items here later.. } } } (for those wondering, i couldn't think of a creative wool helmet name)
    • nvm found out it was because i had create h and not f
    • Maybe there's something happening in the 'leather armor + dye' recipe itself that would be updating the held item texture?
    • @SubscribeEvent public static void onRenderPlayer(RenderPlayerEvent.Pre e) { e.setCanceled(true); model.renderToBuffer(e.getPoseStack(), pBuffer, e.getPackedLight(), 0f, 0f, 0f, 0f, 0f); //ToaPlayerRenderer.render(); } Since getting the render method from a separate class is proving to be bit of a brick wall for me (but seems to be the solution in older versions of minecraft/forge) I've decided to try and pursue using the renderToBuffer method directly from the model itself. I've tried this route before but can't figure out what variables to feed it for the vertexConsumer and still can't seem to figure it out; if this is even a path to pursue.  The vanilla model files do not include any form of render methods, and seem to be fully constructed from their layer definitions? Their renderer files seem to take their layers which are used by the render method in the vanilla MobRenderer class. But for modded entities we @Override this function and don't have to feed the method variables because of that? I assume that the render method in the extended renderer takes the layer definitions from the renderer classes which take those from the model files. Or maybe instead of trying to use a render method I should be calling the super from the renderer like   new ToaPlayerRenderer(context, false); Except I'm not sure what I would provide for context? There's a context method in the vanilla EntityRendererProvider class which doesn't look especially helpful. I've been trying something like <e.getEntity(), model<e.getEntity()>> since that generally seems to be what is provided to the renderers for context, but I don't know if it's THE context I'm looking for? Especially since the method being called doesn't want to take this or variations of this.   In short; I feel like I'm super super close but I have to be missing something obvious? Maybe this insane inane ramble post will provide some insight into this puzzle?
  • Topics

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.