Jump to content
Please read the rules and FAQ before starting a new topic
Currently supported: All versions

1.6.4 valid hash for compiling

creeperkila21

By creeperkila21
in Support & Bug Reports

 Share

Recommended Posts

creeperkila21 Tree Puncher

creeperkila21

Posted
Posted (edited)

Hi, I am currently developing for a 1.6.4 modded forge server and I can not seem to find a valid hash for 1.6.4

  

================ Forge ModLoader Setup Start ===================
Checking MCP zip (may take time to download)
Download of mcp8.11.zip failed hash check, deleting 1ecfa789fcf4d2ad5e6dcaeda336c55e 2d7a759309b5cc10ca29caa0b10f3bfc
Press any key to continue . . .

This is the error I get.

 

Here is the current 1.6.4 hash I am currently using.

  

[1.6.4]
client_md5 = 2e5044f5359e82245551167a237f3167
server_md5 = abcf286a14f7aee82e8bf89270433509
mcp_ver    = 8.11
mcp_url    = http://mcp.ocean-labs.de/files/archive/mcp811.zip
mcp_md5    = 2d7a759309b5cc10ca29caa0b10f3bfc

 

What client_md5 should I use and what server_md5 should I use ? I am creating a client side mod and a server side mod, so I do need both.

 

I may also need a new MCP_URL as that website, Ocean-Labs, is currently down for construction.

 

Thank you for the help.

Edited by creeperkila21
Link to comment
Share on other sites
LexManos Reality Controller

LexManos

Posted
Posted

1) Those are the correct hashes, if you get something else then you're getting an incorrect file. That's the POINT of the hashes...

2) Stop modding for 1.6.4, you won't get support here. Seriously dude... Its been years, update.

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Consider supporting the team on Patreon

Link to comment
Share on other sites
  • 2 years later...
DaemonUmbra Reality Controller

DaemonUmbra

Posted
Posted

MCP is dead and was only used for versions that are absolutely ANCIENT now.

Also, please don't necropost.

This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy.

 

As the most common issue I feel I should put this outside the main bulk:

The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge.

If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan.

 

For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety.

Spoiler

Logs (Most issues require logs to diagnose):

Spoiler

Please post logs using one of the following sites (Thank you Lumber Wizard for the list):

https://gist.github.com/: 100MB Requires member (Free)

https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$)

https://hastebin.com/: 400KB

Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads.

 

What to provide:

...for Crashes and Runtime issues:

Minecraft 1.14.4 and newer:

Post debug.log

Older versions:

Please update...

 

...for Installer Issues:

Post your installer log, found in the same place you ran the installer

This log will be called either installer.log or named the same as the installer but with .log on the end

Note for Windows users:

Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension

 

Where to get it:

Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs.

 

Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch:

Spoiler
  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it).
  4. Now launch the pack through that profile and follow the "Mojang Launcher" instructions above.

Video:

Spoiler

 

 

 

or alternately, 

 

Fallback ("No logs are generated"):

If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft

 

Server Not Starting:

Spoiler

If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output.

 

Reporting Illegal/Inappropriate Adfocus Ads:

Spoiler

Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad.

Lex will need the Ad ID contained in that URL to report it to Adfocus' support team.

 

Posting your mod as a GitHub Repo:

Spoiler

When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub.

When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository.

 

  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. Run the following commands:
    1. git init
    2. git remote add origin [Your Repository's URL]
      • In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git
    3. git fetch
    4. git checkout --track origin/master
    5. git stage *
    6. git commit -m "[Your commit message]"
    7. git push
  4. Navigate to GitHub and you should now see most of the files.
    • note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

 

Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing


×
×
  • Create New...

Important Information

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

  I accept