Jump to content

Recommended Posts

Posted

I imported a project in the IntelliJ IDEA, using a tutorial.

But lines such as

import net.minecraft.init.Blocks;

import net.minecraftforge.fml.common.Mod;

import net.minecraftforge.fml.common.Mod.EventHandler;

import net.minecraftforge.fml.common.event.FMLInitializationEvent;

have red color.

 

So, what I need to do to fix this?

  • 2 weeks later...
Posted

Looks like you've not got the ForegBin src location setup correctly.

 

1) make sure you get the latest MDK and run two commands via terminal - first being "SetupDevWorkspace" as this will ensure all the gradle caches etc are aligned with that version and what not.

2) make sure you then run "gradle idea" as this should generate the IDEA files needed for you automatically.

3) Now, should that still fail, it could be a minor mapping issue in which case you go into Module Settings -> Dependencies. Add a dependency and locate your gradle cache directory (mine is C:\users\myname\.gradle\caches\minecraft\net\minecraftforge\forge\

4) There should be two directories with noting here, the first being "start" and second being "start". Add the Start directory by choosing just start and hit ok.

5) Then add another via the + in that same dialog, and this time navigate until you find forgeBin-1.8.x-XX.XX.X.XXXX.jar and choose it.

6) This should set you straight.

 

Failing this you've probably gone in a different direction that the IntilliJ IDEA herd in which case you probably should go back to the start and start with re-downloading the MDK into a clean directory, then run the above steps.

 

HTH.

Posted

I got the same issue too, I followed the tutorial exactly as it said, and it I'm getting errors saying that the MCP mapping is meant for 1.8.8, not 1.8.9 and it also just immediately ends instead of running like it was with 1.8

Main Developer and Owner of Zero Quest

Visit the Wiki for more information

If I helped anyone, please give me a applaud and a thank you!

Posted

I got the same issue too, I followed the tutorial exactly as it said, and it I'm getting errors saying that the MCP mapping is meant for 1.8.8, not 1.8.9 and it also just immediately ends instead of running like it was with 1.8

That's because each MCP mapping is for a specific version of Minecraft - you can't mix and match. The latest MCP mapping (i.e. current date) will probably always be for the latest Forge/Minecraft version, e.g. 1.8.9. If you are wanting to use an older Forge/Minecraft version, just keep turning back the date in your build.gradle's mappings setting until you get one that works.

mappings = "snapshot_20150617" // 1.8 mapping, specified by date rather than a specific MCP release
mappings = "stable_20" // specifically released stable 1.8.9 mapping, but you could change to 'snapshot_date' for more recent ones if you want

Posted

I didn't switch the gradle settings, I just deleted everything out of the folder and placed an older version of forge in the folder. The IDE looks like its reading the files now

Main Developer and Owner of Zero Quest

Visit the Wiki for more information

If I helped anyone, please give me a applaud and a thank you!

Posted

Also.. I'm trying to switch to the latest version by changing the version in build.gradle in IntelliJ, I run the commands and everything but when I run the game, it still says the previous version of forge

Main Developer and Owner of Zero Quest

Visit the Wiki for more information

If I helped anyone, please give me a applaud and a thank you!

Posted

You need to refresh your project from IDEA's Gradle window after running

setupDecompWorkspace

for a new version.

Please don't PM me to ask for help. Asking your question in a public thread preserves it for people who are having the same problem in the future.

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

    • When I first heard about Bitcoin back in 2018, I was skeptical. The idea of a decentralized, digital currency seemed too good to be true. But I was intrigued as I learned more about the technology behind it and its potential. I started small, investing just a few hundred dollars, dipping my toes into the cryptocurrency waters. At first, it was exhilarating to watch the value of my investment grow exponentially. I felt like I was part of the future, an early adopter of this revolutionary new asset. But that euphoria was short-lived. One day, I logged into my digital wallet only to find it empty - my Bitcoin had vanished without a trace. It turned out that the online exchange I had trusted had been hacked, and my funds were stolen. I was devastated, both financially and emotionally. All the potential I had seen in Bitcoin was tainted by the harsh reality that with decentralization came a lack of regulation and oversight. My hard-earned money was gone, lost to the ether of the digital world. This experience taught me a painful lesson about the price of trust in the uncharted territory of cryptocurrency. While the technology holds incredible promise, the risks can be catastrophic if you don't approach it with extreme caution. My Bitcoin investment gamble had failed, and I was left to pick up the pieces, wiser but poorer for having placed my faith in the wrong hands. My sincere appreciation goes to MUYERN TRUST HACKER. You are my hero in recovering my lost funds. Send a direct m a i l ( muyerntrusted ( @ ) mail-me ( . )c o m ) or message on whats app : + 1 ( 4-4-0 ) ( 3 -3 -5 ) ( 0-2-0-5 )
    • You could try posting a log (if there is no log at all, it may be the launcher you are using, the FAQ may have info on how to enable the log) as described in the FAQ, however this will probably need to be reported to/remedied by the mod author.
    • So me and a couple of friends are playing with a shitpost mod pack and one of the mods in the pack is corail tombstone and for some reason there is a problem with it, where on death to fire the player will get kicked out of the server and the tombstone will not spawn basically deleting an entire inventory, it doesn't matter what type of fire it is, whether it's from vanilla fire/lava, or from modded fire like ice&fire/lycanites and it's common enough to where everyone on the server has experienced at least once or twice and it doesn't give any crash log. a solution to this would be much appreciated thank you!
    • It is 1.12.2 - I have no idea if there is a 1.12 pack
  • Topics

×
×
  • Create New...

Important Information

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