Jump to content
Currently supported: All versions

Eclipse can't find the '.project' file for Minecraft

pinkyboy9102

By pinkyboy9102
in ForgeGradle

 Share

Recommended Posts

pinkyboy9102 Tree Puncher

pinkyboy9102

Posted
Posted

Hi all,

 

Before 1.7.10 forge was released, I used the older, non-gradle version of forge to code. Recently I decided to update my mods but then decided it would be better to start from scratch instead of all the effort, so I followed some basic tutorials on setting up forge gradle. I have run all the commands correctly and the builds were all successful, but when I attempt to link my Eclipse to the 'eclipse' folder in the forge source folder, it just has minecraft as a package with no drop down and says:

 

'The project description file (.project) for 'Minecraft' is missing.  This file contains important information about the project.  The project will not function properly until this file is restored.'

 

I have looked around but can't find solutions anywhere. Help would be GREATLY appreciated!

 

Many thanks,

pinkyboy9102

 

EDIT: Nevermind, I just re-ran 'gradlew setupDecompWorkspace eclipse' then double-clicked the empty package and it...un-emptied

  • 1 month later...
  • 3 months later...
  • 3 months later...
nedreud Tree Puncher

nedreud

Posted
Posted

I ended up with this exact same error. I'd been happily following Wuppy's new tutorials for 1.8 (http://www.wuppy29.com/minecraft/modding-tutorials/forge-modding-1-8/) and decided in my infinite wisdom to rename the location of my root Forge folder from c:\minecraft-1.8 to c:\forge-1.8 (I'm on Windows).

 

Well, after doing that the project sort of loaded but it couldn't find any of my source files. More frustrating was that it was still broken after renaming the folder back to c:\minecraft-1.8!

 

Cue several hours of totally deleting all directories and instances of Forge and Eclipse, including those pesky .gradle and .eclipse folders on your user and AppData directories. Still no joy. Completely rebuild using 

gradlew cleancache --refresh-dependencies setupDecompWorkspace eclipse

. Nope, still not working. I even tried setting up Forge 1.7.

 

But then I had an epiphany. I'm a NodeJS developer for a living and use the Git Bash console for git actions (it's a MINGW32 console). I re-ran the 

gradew

command in the Git Bash terminal, which took a few minutes longer than from the standard CMD terminal, and voila! All working again.

  • 7 months 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.

×
 Share
Go to topic listing

Announcements



  • Recently Browsing

    • No registered users viewing this page.

  • Posts

    • bkbenji
      OpenAL.dll issue (causing crash)

      By bkbenji · Posted

      Is there a fix for this issue? I have tried reinstalling OpenAL.dll, switching Java versions, and even muting my game when it launched, but all of these attempts have resulted in my game crashing nonetheless. I have been dealing with this issue for approximately a week straight. I have not changed any sound settings, so I am very confused. Full Code: https://gnomebot.dev/paste/mclogs/beEBzpm "4/16/2025 12:16:30 AM 1000 Error Faulting application name: javaw.exe, version: **.**.**.**, time stamp: 23 0xd75c3041 24 Faulting module name: OpenAL.dll, version: **.**.**.**, time stamp: 0x647635a125 Exception code: 0xc0000409 26 Fault offset: 0x00000000000a2b05 27 Faulting process id: 0x10A0 28 Faulting application start time: 0x1DBAE81D04A6F2F 29 Faulting application path: C:\Users\********\curseforge\minecraft\Install\java30 \java-runtime-delta\bin\javaw.exe 31 Faulting module path: C:\Users\********\curseforge\minecraft\Install\natives\n32 eoforge-21.1.148\OpenAL.dll 33 Report Id: 28552180-f359-40cc-adeb-08dada7e99d8 34 Faulting package full name: 35 Faulting package-relative application ID:" Any sort of insight would be greatly appreciated, it's giving me a headache.
    • Calcifer
      I can't get this modpack running.

      By Calcifer · Posted

      I'm new to this, if that wasn't obvious. My friend and I are trying to make a modpack for 1.19.2. I've made a modpack previously with 0 issues before and many of the same mods. However, I can't seem to find the issue when trying to load up his new modpack.   Any help would be greatly appreciated.
    • SPROUTBAKES
      blocks addon

      By SPROUTBAKES · Posted

      BLOCK
    • PhysicalJP
      Minecraft modpack crashing on create world.

      By PhysicalJP · Posted

      Im trying to make a customized modpack for just myself using the atm9 modpack as a base. It was working till recently, when curseforge force updated all the mods in the pack. Currently every time I get to the main menu I try and create a world in single player and it just says saving world. then generates a crash report.    Crash Report: https://pastebin.com/xXESPfJs   Latest Log Part 1: https://pastebin.com/Cb2VpUyr  Part 2: https://pastebin.com/9SWVn4Dx
    • Thargor
      Minecraft Crashing upon joining save/server or when placing specific blocks

      By Thargor · Posted

      Okay, for him the config file looked like this: flywheel-client.toml: #Select the backend to use. Set to "DEFAULT" to let Flywheel decide. backend = "DEFAULT" #Enable or disable instance update limiting with distance. limitUpdates = true #The number of worker threads to use. Set to -1 to let Flywheel decide. Set to 0 to disable parallelism. Requires a game restart to take effect. #Range: -1 ~ 12 workerThreads = -1 #Config options for Flywheel's built-in backends. [flw_backends]     #How smooth Flywheel's shader-based lighting should be. May have a large performance impact.     #Allowed Values: FLAT, TRI_LINEAR, SMOOTH, SMOOTH_INNER_FACE_CORRECTED     lightSmoothness = "SMOOTH" There was no "INSTANCING", so we changed "DEFAULT" to "OFF", but this didn't help. Changing it to "INSTANCING" didn't work as well.

  • Topics

×
×
  • Create New...

Important Information

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

  I accept