Eclipse messing with decompiled MC source?

[superminerJG 3]

MC 1.14.3 - Forge 27.0.25

 

When I open decompiled Minecraft source code, shows me this. I've already tried clicking the button higlighted in yellow in this image, reconfiguring, and doing it again. Do I need to do anything extra for this to work?

[Draco18s 2291]

Can you view other classes, or are all vanilla files showing that?

How did you set up your environment?

[superminerJG 3]

Here is my procedure:

1. Extracted Forge MDK into ...\Mods\Fluxed Machinery

2. gradlew eclipse

3. gradlew genEclipseRuns

4. Imported to Eclipse as Gradle Project from ...\Mods

Only these two

• ...\.gradle\caches\forge_gradle\minecraft_user_repo\net\minecraftforge\forge\1.14.3-27.0.25_mapped_snapshot_20190621-1.14.2\forge-1.14.3-27.0.25_mapped_snapshot_20190621-1.14.2.jar
• ...\.gradle\caches\forge_gradle\minecraft_user_repo\net\minecraftforge\forge\1.14.3-27.0.25_mapped_snapshot_20190621-1.14.2\forge-1.14.3-27.0.25_mapped_snapshot_20190621-1.14.2-launcher.jar

seem to be like this at the moment.

Edited July 9, 2019 by superminerJG
Forgot something :l

[PhilipChonacky 5]

2 hours ago, superminerJG said:

Here is my procedure:

1. Extracted Forge MDK into ...\Mods\Fluxed Machinery

2. gradlew eclipse

3. gradlew genEclipseRuns

4. Imported to Eclipse as Gradle Project from ...\Mods

I don't know if it make a difference, but you should run 'gradlew eclipse' after 'gradlew genEclipseRuns'

Also, the root of the Eclipse project would be the same folder where you extracted the MDK (...\Mods\Fluxed Machinery)

[Cadiboo 358]

gradlew genEclipseRuns should be run after gradlew eclipse.

[superminerJG 3]

[this is deleted]

Edited July 9, 2019 by superminerJG