I found the issue and we should both be embarrassed...you for the mistake and me for the amount of time it took for me to find it, I have submitted a Pull Request to your first repo with the fix and formatted the repo in the way that is intended from the MDK package.

 

The issue: Both of your proxies were the "common proxy", speaking of which, from the common issues thread:

Quote

1. The concept of a "common proxy" does not make sense. The whole point of @SidedProxy is to abstract over client specific and server specific behavior, the opposite of "common". Common code should go in your main mod class.

 

Your repo doesn't have your whole workspace in it, this can sometimes get in the way of reproducing errors, I would recommend using a git client to upload every file that it will let you (one of the files provided by Forge's MDK is a .gitignore file, this will automatically determine which files do not need to be uploaded, you will not need to do this manually).

"layer0": "items/test_item"

should be

"layer0": "scrmod:items/test_item"

 

1. Please update, 1.7.10 is ancient

2. That usually means you haven't followed the instructions correctly or there may be a file permission issue(move it somewhere else and try again).

Try these instructions:

 

Try removing MrTJPCore and the mods that depend on it, I don't know much about coremods but I've heard they can cause errors that don't always get traced back to the offending coremod.

Noticed this in the log at the beginning, again I'm not that knowledgeable about coremods but I'm very cautious about when they throw even a warning.

Quote

[01:39:20] [main/ERROR] [FML]: Coremod mrtjp.core.handler.CorePlugin: Unable to class load the plugin java.lang.ClassNotFoundException: mrtjp.core.handler.CorePlugin

 

Preferably use a site like Pastebin or GitHub's Gist service and then link to it here.

The entire config system for simplyjetpacks seems to be changed on GitHub, so we'll have to see what the next release does.

Can you post your crash report please?

This is where the exception is being thrown, I would suggest moving your simplyjetpacks config(including your custom jetpack) out of the minecraft installation, having the mod make a fresh one, then re-applying your changes manually with the moved copy as a guide.

I'm not seeing the same issue on my end, however I noticed you're missing all your gradle stuff in the repo, could you please add that.

There is also the fact that Google is enforcing SSL if people want to get Notifications in Chrome, they don't let you enable it on non-SSL sites.

I've seen some text editors insert symbols because the text encoding wasn't correct, double check that they're UTF-8.

Is the source code on github?

Have you tweaked the SimplyJetpacks configs? I'm seeing exceptions from the config loaders of SimpleJetpacks and JourneyMap.

The other person is connecting to the server... not to your client, the server would know more about the exchange than your client would.

Please excuse my dumbness sometimes

This looks like a client log, can you provide the server log? In regards to the file size issue, could you try using GitHub's gist service and see if it accept the full file?

20 minutes ago, Drake7890 said:

What do you mean full log? I copy-pasted the output log directly.

We mean the log file, not what you see in the console window, if you're using the vanilla launcher with forge on Windows you can open the run prompt (Windows Key + R) and type

%AppData%/.minecraft/logs

then click "run" and this will open the logs folder, what will help us most is the fml-client-latest.log file, and again, please use a site like pastebin rather than uploading the file.

1. This thread is almost 4 years old, if you have an issue please make a new thread.

2. If your issue is with a 1.7.10 version, please update or you will not get much help.

What I've done in the past to update the forge version is simply get the updated mdk and unzip it into the project, then run

gradlew setupdecompworkspace --refreshdependencies

 

Just run the installer, the only requirements for it to work are a working internet connection and java (which is a requirement for minecraft anyway).

Note that when I say "run" I do not mean unzip, I mean run it as a program, by double clicking, or from the command line like this if you have the jar version of the installer.

What do you mean by "archives of forge"? Are you looking for a zip that you can extract or unzip and have a working forge server?

Assuming you are running it through the command line, add -Xmx to specify the max you will give the server.

Note that this is the same method as a vanilla server

Example:

java -jar forge.jar -Xmx3G

will give the server a max of 3 Gigs to use

Please post your fml-client-latest.log

@lyghtningwither The Yggdrasil thing is a matter of how fast your client makes requests to Mojang's authentication servers, if you don't see the exception then your client is probably just giving enough time between the requests that the server's don't complain.

 

From what I've read elsewhere the client should catch that exception and basically say "Oh ok, I'll wait a bit and try again"