Jump to content

Recommended Posts

Posted
  Quote

 

What...? I don't know where you got these instructions from, but they are wrong.

  1. Clone the repo.
  2. Open build.gradle in IntelliJ (i.e. import the gradle project).
  3. Run the setup gradle task.
  4. Refresh the gradle project in IntelliJ.

Done.

 

Expand  

 

I followed these steps, which I found elsewhere on this forum. I am able to make changes, run forge client, and see those changes. I am using IntelliJ IDEA Community 2019.2.4

 

However, I'm not able to "test with existing mods" as described in the docs for 1.13.x (which I think are the latest docs at the time of this writing).

 

The general idea from the docs and linked video is:

1. import another mod as a module in the project settings

2. add forge main as a module dependency in the new module

3. add the output path of the new module as a "JAR or Directory" runtime dependency in forge main

 

I have tried adding a mod of my own that works, as well as the example mod that comes with the forge mdk. In either case, forge client runs, the minecraft client starts. When I click the mods button from the minecraft title screen, I see only "Minecraft" and "Forge" in the list of mods. (which is troubling because I think I also expect FML).

 

There is an error in the output of running forge client: `Incompatible Java and native library versions detected.` That seems pretty significant, but I'm not sure 

 

Here is the output of running forge client:

 

9:21:24 p.m.: Executing task 'forge_client'...

> Task :forge:compileFmllauncherJava UP-TO-DATE
> Task :forge:processFmllauncherResources UP-TO-DATE
> Task :forge:fmllauncherClasses UP-TO-DATE
> Task :forge:compileJava UP-TO-DATE
> Task :forge:processResources UP-TO-DATE
> Task :forge:classes UP-TO-DATE
> Task :forge:downloadMCMeta UP-TO-DATE
> Task :forge:downloadAssets
> Task :forge:extractNatives UP-TO-DATE
> Task :forge:prepareRuns
> Task :forge:compileUserdevJava UP-TO-DATE
> Task :forge:processUserdevResources UP-TO-DATE
> Task :forge:userdevClasses UP-TO-DATE
> Task :forge:prepareForge_client

> Task :forge:forge_client
[21:21:28] [main/INFO]: ModLauncher running: args [--gameDir, ., --launchTarget, fmldevclient, --fml.mcpVersion, 20190829.143755, --fml.mcVersion, 1.14.4, --fml.forgeGroup, net.minecraftforge, --fml.forgeVersion, 28.1.90, --version, MOD_DEV, --assetIndex, 1.14, --assetsDir, /Users/zeigfreid/.gradle/caches/forge_gradle/assets, --username, Dev, --accessToken, ❄❄❄❄❄❄❄❄, --userProperties, {}]
[21:21:28] [main/INFO]: ModLauncher 4.1.0+62+5bfa59b starting: java version 1.8.0_131 by Oracle Corporation
[21:21:29] [main/INFO]: Added Lets Encrypt root certificates as additional trust
[21:21:29] [main/WARN]: Failed to find exploded resource mods.toml in directory 
[21:21:29] [main/INFO]: Launching target 'fmldevclient' with arguments [--version, MOD_DEV, --gameDir, ., --assetsDir, /Users/zeigfreid/.gradle/caches/forge_gradle/assets, --assetIndex, 1.14, --username, Dev, --accessToken, ❄❄❄❄❄❄❄❄, --userProperties, {}]
[21:21:30] [Client thread/INFO]: Setting user: Dev
[21:21:34] [Client thread/INFO]: LWJGL Version: 3.2.1 build 12
[21:21:34] [Client thread/INFO]: [org.lwjgl.system.Library:checkHash:467]: [LWJGL] [ERROR] Incompatible Java and native library versions detected.
Possible reasons:
	a) -Djava.library.path is set to a folder containing shared libraries of an older LWJGL version.
	b) The classpath contains jar files of an older LWJGL version.
Possible solutions:
	a) Make sure to not set -Djava.library.path (it is not needed for developing with LWJGL 3) or make
	   sure the folder it points to contains the shared libraries of the correct LWJGL version.
	b) Check the classpath and make sure to only have jar files of the same LWJGL version in it.
[21:21:34] [Client thread/INFO]: [org.lwjgl.system.Library:checkHash:467]: [LWJGL] [ERROR] Incompatible Java and native library versions detected.
Possible reasons:
	a) -Djava.library.path is set to a folder containing shared libraries of an older LWJGL version.
	b) The classpath contains jar files of an older LWJGL version.
Possible solutions:
	a) Make sure to not set -Djava.library.path (it is not needed for developing with LWJGL 3) or make
	   sure the folder it points to contains the shared libraries of the correct LWJGL version.
	b) Check the classpath and make sure to only have jar files of the same LWJGL version in it.
[21:21:34] [Client thread/INFO]: [org.lwjgl.system.Library:checkHash:467]: [LWJGL] [ERROR] Incompatible Java and native library versions detected.
Possible reasons:
	a) -Djava.library.path is set to a folder containing shared libraries of an older LWJGL version.
	b) The classpath contains jar files of an older LWJGL version.
Possible solutions:
	a) Make sure to not set -Djava.library.path (it is not needed for developing with LWJGL 3) or make
	   sure the folder it points to contains the shared libraries of the correct LWJGL version.
	b) Check the classpath and make sure to only have jar files of the same LWJGL version in it.
[21:21:35] [Client thread/INFO]: [org.lwjgl.system.Library:checkHash:467]: [LWJGL] [ERROR] Incompatible Java and native library versions detected.
Possible reasons:
	a) -Djava.library.path is set to a folder containing shared libraries of an older LWJGL version.
	b) The classpath contains jar files of an older LWJGL version.
Possible solutions:
	a) Make sure to not set -Djava.library.path (it is not needed for developing with LWJGL 3) or make
	   sure the folder it points to contains the shared libraries of the correct LWJGL version.
	b) Check the classpath and make sure to only have jar files of the same LWJGL version in it.
[21:21:35] [modloading-worker-1/INFO]: Forge mod loading, version 28.1.90, for MC 1.14.4 with MCP 20190829.143755
[21:21:35] [modloading-worker-1/INFO]: MinecraftForge v28.1.90 Initialized
[21:21:42] [Forge Version Check/INFO]: [forge] Starting version check at https://files.minecraftforge.net/maven/net/minecraftforge/forge/promotions_slim.json
[21:21:42] [Forge Version Check/INFO]: [forge] Found status: AHEAD Current: 28.1.90 Target: null
[21:21:45] [Client thread/INFO]: OpenAL initialized.
[21:21:45] [Client thread/INFO]: Sound engine started
[21:21:45] [Client thread/INFO]: Created: 512x512 textures-atlas
[21:21:46] [Client thread/INFO]: Created: 256x256 textures/particle-atlas
[21:21:46] [Client thread/INFO]: Created: 256x256 textures/painting-atlas
[21:21:46] [Client thread/INFO]: Created: 128x128 textures/mob_effect-atlas
[21:21:47] [Realms Notification Availability checker #1/INFO]: Could not authorize you against Realms server: Invalid session id
[21:21:52] [Thread-1/FATAL]: Forge config just got changed on the file system!
[21:22:18] [Client thread/INFO]: Stopping!
9:22:18 p.m.: Task execution finished 'forge_client'.

 

I noticed that in the dependencies list for forge main there are two entries for LWJGL:

 

Gradle: org.lwjgl:lwjgl:3.2.1

Gradle: org.lwjgl:lwjgl:3.2.2

 

I'm not sure how to follow the suggested actions a) and b) in the above output.

 

I'd really appreciate some guidance! I am adding events to hook into grass spreading, and the change itself is really straightforward. I feel like I could have a PR up soon, but I am not interested in pushing untested code.

 

Thanks!

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

    • Without Network protocol fix mod, I get kicked with a Network Protocol error when on LAN. Also, both of these issues are caused by a Null Pointer Exception/Screen cannot be null in a "Client Bound Player Combat Kill Packet".
    • You need a new "items" folder at  resources/assets/yourmodid/ there you add for every item model a .json file with the exact item/block name and fill it like this if it's an item: { "model": { "type": "minecraft:model", "model": "yourmodid:item/youritem" } } and so if its a block: { "model": { "type": "minecraft:model", "model": "yourmodid:block/youritem" } } There is also a generator for it you can do namy crazy things with it which replaces the previous hard coded Item Properties implementaion method (Bow pulling animation for example). https://misode.github.io/assets/item/
    • Hello! I'm playing a modpack (custom made) with some friends, and we have the server running on BisectHosting. We encountered a bug with an entity from The Box Of Horrors mod, that would crash the game whenever someone nearby it would log in. We tried to fix it by: 1) Editing the player.dat files to change the location of the affected players (something I had done successfully previously) 2) Updating the version of the mod we had (0.0.8.2) to the latest alpha version (0.0.8.3 However, after doing both of those, none of us are able to join the server, and we get the following errors: Server side: https://pastebin.com/J5sc3VQN Client side: Internal Server Error (that's basically all I've gotten) Please help! I've tried restoring the player data to how it was before I made the changes (Bisect allows you to restore deleted files) and deleting all of my player data files and I still get the same error. Deleting Box Of Horrors causes the error: Failed to load datapacks, cannot continue with server load.
    • Hey there! I'm trying to create a simple mod for Forge 1.21.1 that adds a few custom banner patterns that don't require any banner pattern items. To be completely honest, this is my first time modding for Minecraft, so after setting up the project in Intellij, I copied the parts of the source code from this mod on CurseForge that dealt with adding and registering banner patterns, including the lang and banner_pattern .json files. From what I understand, to add a banner pattern that doesn't require a banner pattern item, I only needed to create the registries for each pattern like in here and then register it in the main java class like here on Line 54. Additionally, in the lang/en_us.json file, add in the names for each respective banner color, and in the data/minecraft/tags/banner_pattern/no_items_required.json file, add each banner pattern that does not require a banner pattern item to make a banner. The project is able to compile when loading in Forge which makes me assume that the file structure I have is correct, but on loading a Minecraft world, this error appears in console and the loom is subsequently blank. [Worker-Main-1/ERROR] [minecraft/TagLoader]: Couldn't load tag minecraft:no_item_required as it is missing following references: *lists every added entry in no_item_required.json* The message clearly states something went wrong regarding when trying to load in the registries from the mod, but I have no clue what could be wrong with the code I have. Attached below are screenshots of what I currently have. Java Main Class Banner Registry Class File Structure Error in Console upon loading a Minecraft world What the loom shows without minecraft:no_item_required    The original mod I copied still functions completely, so if anyone can figure out why the registries for the mod I'm making isn't working, that would be greatly appreciated!    
    • Please someone help me to know how can I fix this generation error in the trees! I already uninstalled and reinstalled several mods in my modpack and can't figure out what is causing it.    
  • Topics

×
×
  • Create New...

Important Information

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