New Direwolf 1.6.4 v1.0.3 Pack - ID Conflicts

  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord

Too_Cheesy

New Member
Jul 29, 2019
6
0
0
I updated my Direwolf20 1.6.4 pack from version 1.0.2 to 1.0.3 this morning and i got this.

Untitled.png


Does anybody have a solution or can they point me in the right direction if possible.
I tried looking through the configs but i couldn't find the mod that uses the ids.
 
D

Deleted member 38496

Guest
From the changelog:

"Forestry - this will cause some mismatched ID messages. Ignore them."
 
  • Like
Reactions: Too_Cheesy

Too_Cheesy

New Member
Jul 29, 2019
6
0
0
From the changelog:

"Forestry - this will cause some mismatched ID messages. Ignore them."
Can you point me in the direction of the changelog as i cant seem to find it, and thanks for the reply !!!!

EDIT: And no i didnt read the patch notes, i didnt know where they where. I am really sorry for posting when there was a clear solution out there already. Could you give me a link please
 

thib92210

New Member
Jul 29, 2019
34
0
0
Go to your "%appdata%" folder, then go to "ftblauncher" and "ModPacks" and delete the "Direwolf20_1_6_4" folder.
Then, go to your FTB Launcher installation folder (the one you chose in the "OPTIONS" tab in the launcher) and delete the "Direwolf20_1_6_4" folder. Then go to the launcher and download the latest version of the pack. This should resolve everything.

CAUTION : If you have some world saves to backup before doing this, go to the second folder I told you to delete, go to "minecraft" -> "saves" and backup your world saves.
 

Too_Cheesy

New Member
Jul 29, 2019
6
0
0
Go to your "%appdata%" folder, then go to "ftblauncher" and "ModPacks" and delete the "Direwolf20_1_6_4" folder.
Then, go to your FTB Launcher installation folder (the one you chose in the "OPTIONS" tab in the launcher) and delete the "Direwolf20_1_6_4" folder. Then go to the launcher and download the latest version of the pack. This should resolve everything.

CAUTION : If you have some world saves to backup before doing this, go to the second folder I told you to delete, go to "minecraft" -> "saves" and backup your world saves.

Trying that now mate. Will post back in 5mins
 

Too_Cheesy

New Member
Jul 29, 2019
6
0
0
Trying that now mate. Will post back in 5mins

Yea that did not work mate. I went to ftblauncher in appdata (i have unhidden the hidden folders) so i don't have to search for "%appdata%". Then to the modpacks folder and deleted the direwolf 1.6.4 modpack. Then i went to the root of my C: drive to where i have the actual ftb launcher and the actual downloaded modpacks. I deleted it from there too.

So basically its a fresh install.
Then i copied the backed up version of my world into the newly generated saves folder of my new dw20 modpack.
And i still get it. So i am now choosing to ignore it. Hopefully there wont be any significant backlash.
But thanks to all that helped. It was very much appreciated.

I also found the info for the changelog here for anybody who finds this thread...

http://forum.feed-the-beast.com/threads/direwolf20-1-6-4-changelog.35698/#post-494880

And check Direwolf's twitter, its where i found the link, just google it. Cheers.
 

thib92210

New Member
Jul 29, 2019
34
0
0
Yeah the IDs are not the same, but the save folder contains IDs of blocks, not their names, making them impossible to retriview (or maybe if you replace all the old IDs with the new ones -_-)
 

Cratoz

New Member
Jul 29, 2019
1
0
0
when logging into a server i cant ignore the id problems. dont know how to get around this.

any suggestions?
 

thib92210

New Member
Jul 29, 2019
34
0
0
The server is not running the same version of the modpack.
Make a backup of your version, delete the folders (the one in "ftblauncher" and the one in the installation folder) and install the proper verison
 

Zarjak

New Member
Jul 29, 2019
1
0
0
when logging into a server i cant ignore the id problems. dont know how to get around this.

any suggestions?
I have this exact same problem, I understand the Id mis-match isn't going to hurt anything but upon logging onto my server(Which is running 1.0.3 like my client) I am meet with the same Id mis-matches but I am unable to ignore them logging onto my own server.
 

thib92210

New Member
Jul 29, 2019
34
0
0
Do the same stages I described for the client (delete stuff etc…) to update your server. This must be the same issue as for the client
 

UniZero

Popular Member
Oct 3, 2012
3,406
310
124
Scotland, UK
Go to your "%appdata%" folder, then go to "ftblauncher" and "ModPacks" and delete the "Direwolf20_1_6_4" folder.
Then, go to your FTB Launcher installation folder (the one you chose in the "OPTIONS" tab in the launcher) and delete the "Direwolf20_1_6_4" folder. Then go to the launcher and download the latest version of the pack. This should resolve everything.

CAUTION : If you have some world saves to backup before doing this, go to the second folder I told you to delete, go to "minecraft" -> "saves" and backup your world saves.

I would not instruct people to download the latest version I would always say leave it on the recommeded one as per jadedcat's video here which was about mod dupes.
 

thib92210

New Member
Jul 29, 2019
34
0
0
For the moment, the recommendent one is actually the latest one since they are fixing a lot of issues, it is always better to keep the latest one.
But in the future, it will be better to use the recommanded pack indeed !
 

Yosomith

New Member
Jul 29, 2019
344
0
0
I updated my Direwolf20 1.6.4 pack from version 1.0.2 to 1.0.3 this morning and i got this.

View attachment 8700

Does anybody have a solution or can they point me in the right direction if possible.
I tried looking through the configs but i couldn't find the mod that uses the ids.

This kind of thing is pretty normal to see when you update as sometimes mod developers do change things from time to time. From what I've seen it's usually harmless.
 

UniZero

Popular Member
Oct 3, 2012
3,406
310
124
Scotland, UK
This kind of thing is pretty normal to see when you update as sometimes mod developers do change things from time to time. From what I've seen it's usually harmless.

One of the updates mentioned about going back to previous config's which may give mismatch errors but it should be ok.