Just letting everyone know that I've added native support for TE3 machines into Tinker's Construct directly!
IC2 and Mekanism still require this mod though.
But if you used this mod just because of TE3 you won't need to anymore when the next version of TiC comes out.
I'll release an update soon to remove TE3 support from this mod
Unless you are using this with Tinker's Construct's version that already has the cobalt/ardite dusts you must use version 1.1.1 or below.
By your crash log I can tell that the version of TiC you have does not come with the dusts
I updated my FTB Monster server to 1.1.0 as well as my client. I think I have dealt with all the issues that i could possibly deal with MCPC and Essentials and stuff, but my client keeps crashing on load http://pastebin.com/7eJc7bAD
I think the error is pointing at a conflicting ID with AOBD. I've searched for possible answers and I see multiple crash reports in pastebin the last few days with the same error, but no resolutions. Maybe you can tell me how to fix it please?
Pretty sure it's an id conflict. But there's no way I can sort that out for you. You'll have yo go through through the mods and find it yourself unfortunatelly ):
But you shouldn't update the version that the Monster pack has, AOBD updates change very little, if they didn't think it was worth updating it's probably because they already have the version with all the features they need.
Actually now I am really confused as I see the item ID in the config file as 31743. I was able to log in SSP and did an ID data dump and the item id shows as 31999. What am I missing?
Pretty sure it's an id conflict. But there's no way I can sort that out for you. You'll have yo go through through the mods and find it yourself unfortunatelly ):
I can understand that...the question, however, would be if you had any ideas what mod would use the id you use. I don't know much about it so I may be asking for something completely crazy If so please forgive me.
But you shouldn't update the version that the Monster pack has, AOBD updates change very little, if they didn't think it was worth updating it's probably because they already have the version with all the features they need.
I didn't do any manual updates, just moved server to 1.1.0 from 1.0.9 so had to download new pak for client and server.
Actually now I am really confused as I see the item ID in the config file as 31743. I was able to log in SSP and did an ID data dump and the item id shows as 31999. What am I missing?I can understand that...the question, however, would be if you had any ideas what mod would use the id you use. I don't know much about it so I may be asking for something completely crazy If so please forgive me.I didn't do any manual updates, just moved server to 1.1.0 from 1.0.9 so had to download new pak for client and server.
That's quite strange... it could be a ID de-sync between client and server. Maybe their server ID is one but their client ID and something else. In that case you'd have to report it to the FTB team.
Backup your world, delete the server and client and then download them new and see if the problem persists.
About what mod uses the ID, there's simply no way of me knowing it since any mod worth anything gives the players the ability to change IDs, and I know for a fact that the FTB team messes with IDs of pretty much every mod they use, there's no way of me knowing what ID they are giving for each item.
That's quite strange... it could be a ID de-sync between client and server. Maybe their server ID is one but their client ID and something else. In that case you'd have to report it to the FTB team.
Backup your world, delete the server and client and then download them new and see if the problem persists.
About what mod uses the ID, there's simply no way of me knowing it since any mod worth anything gives the players the ability to change IDs, and I know for a fact that the FTB team messes with IDs of pretty much every mod they use, there's no way of me knowing what ID they are giving for each item.
Hey man I am getting this on start up
2014-03-18 13:07:34 [OFF] [ForgeModLoader] Logging level for ForgeModLoader logging is set to SEVERE 2014-03-18 13:07:38 [SEVERE] [ForgeModLoader] The mcmod.info file in MAG-Technomancy 0.3.0a.zip cannot be parsed as valid JSON. It will be ignored argo.saj.InvalidSyntaxException: At line 14, column 21: Expected 't' to be followed by [[r, u, e]], but got [[h, a, u]]. at argo.saj.SajParser.aJsonValue(SajParser.java:153) at argo.saj.SajParser.arrayString(SajParser.java:79) at argo.saj.SajParser.aJsonValue(SajParser.java:198) at argo.saj.SajParser.aFieldToken(SajParser.java:137) at argo.saj.SajParser.objectString(SajParser.java:114) at argo.saj.SajParser.aJsonValue(SajParser.java:194) at argo.saj.SajParser.arrayString(SajParser.java:79) at argo.saj.SajParser.parse(SajParser.java:58) at argo.jdom.JdomParser.parse(JdomParser.java:36) at cpw.mods.fml.common.MetadataCollection.from(MetadataCollection.java:44) at cpw.mods.fml.common.discovery.JarDiscoverer.discover(JarDiscoverer.java:53) at cpw.mods.fml.common.discovery.ContainerType.findMods(ContainerType.java:42) at cpw.mods.fml.common.discovery.ModCandidate.explore(ModCandidate.java:71) at cpw.mods.fml.common.discovery.ModDiscoverer.identifyMods(ModDiscoverer.java:137) at cpw.mods.fml.common.Loader.identifyMods(Loader.java:353) at cpw.mods.fml.common.Loader.loadMods(Loader.java:484) at cpw.mods.fml.client.FMLClientHandler.beginMinecraftLoading(FMLClientHandler.java:183) at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:473) at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:808) at net.minecraft.client.main.Main.main(SourceFile:101) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at net.minecraft.launchwrapper.Launch.launch(Launch.java:131) at net.minecraft.launchwrapper.Launch.main(Launch.java:27) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.multimc.onesix.OneSixLauncher.launch(OneSixLauncher.java:214) at org.multimc.EntryPoint.listen(EntryPoint.java:139) at org.multimc.EntryPoint.main(EntryPoint.java:53) 2014-03-18 13:07:39 [SEVERE] [ForgeModLoader] The mcmod.info file in MISC-FIX-AOBD v1.3.0.jar cannot be parsed as valid JSON. It will be ignored argo.saj.InvalidSyntaxException: At line 6, column 14: Invalid character at start of value [â]. at argo.saj.SajParser.aJsonValue(SajParser.java:201) at argo.saj.SajParser.aFieldToken(SajParser.java:137) at argo.saj.SajParser.objectString(SajParser.java:114) at argo.saj.SajParser.aJsonValue(SajParser.java:194) at argo.saj.SajParser.arrayString(SajParser.java:79) at argo.saj.SajParser.parse(SajParser.java:58) at argo.jdom.JdomParser.parse(JdomParser.java:36) at cpw.mods.fml.common.MetadataCollection.from(MetadataCollection.java:44) at cpw.mods.fml.common.discovery.JarDiscoverer.discover(JarDiscoverer.java:53) at cpw.mods.fml.common.discovery.ContainerType.findMods(ContainerType.java:42) at cpw.mods.fml.common.discovery.ModCandidate.explore(ModCandidate.java:71) at cpw.mods.fml.common.discovery.ModDiscoverer.identifyMods(ModDiscoverer.java:137) at cpw.mods.fml.common.Loader.identifyMods(Loader.java:353) at cpw.mods.fml.common.Loader.loadMods(Loader.java:484) at cpw.mods.fml.client.FMLClientHandler.beginMinecraftLoading(FMLClientHandler.java:183) at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:473) at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:808) at net.minecraft.client.main.Main.main(SourceFile:101) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at net.minecraft.launchwrapper.Launch.launch(Launch.java:131) at net.minecraft.launchwrapper.Launch.main(Launch.java:27) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.multimc.onesix.OneSixLauncher.launch(OneSixLauncher.java:214) at org.multimc.EntryPoint.listen(EntryPoint.java:139) at org.multimc.EntryPoint.main(EntryPoint.java:53)
2014-03-18 13:07:34 [OFF] [ForgeModLoader] Logging level for ForgeModLoader logging is set to SEVERE 2014-03-18 13:07:38 [SEVERE] [ForgeModLoader] The mcmod.info file in MAG-Technomancy 0.3.0a.zip cannot be parsed as valid JSON. It will be ignored argo.saj.InvalidSyntaxException: At line 14, column 21: Expected 't' to be followed by [[r, u, e]], but got [[h, a, u]]. at argo.saj.SajParser.aJsonValue(SajParser.java:153) at argo.saj.SajParser.arrayString(SajParser.java:79) at argo.saj.SajParser.aJsonValue(SajParser.java:198) at argo.saj.SajParser.aFieldToken(SajParser.java:137) at argo.saj.SajParser.objectString(SajParser.java:114) at argo.saj.SajParser.aJsonValue(SajParser.java:194) at argo.saj.SajParser.arrayString(SajParser.java:79) at argo.saj.SajParser.parse(SajParser.java:58) at argo.jdom.JdomParser.parse(JdomParser.java:36) at cpw.mods.fml.common.MetadataCollection.from(MetadataCollection.java:44) at cpw.mods.fml.common.discovery.JarDiscoverer.discover(JarDiscoverer.java:53) at cpw.mods.fml.common.discovery.ContainerType.findMods(ContainerType.java:42) at cpw.mods.fml.common.discovery.ModCandidate.explore(ModCandidate.java:71) at cpw.mods.fml.common.discovery.ModDiscoverer.identifyMods(ModDiscoverer.java:137) at cpw.mods.fml.common.Loader.identifyMods(Loader.java:353) at cpw.mods.fml.common.Loader.loadMods(Loader.java:484) at cpw.mods.fml.client.FMLClientHandler.beginMinecraftLoading(FMLClientHandler.java:183) at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:473) at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:808) at net.minecraft.client.main.Main.main(SourceFile:101) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at net.minecraft.launchwrapper.Launch.launch(Launch.java:131) at net.minecraft.launchwrapper.Launch.main(Launch.java:27) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.multimc.onesix.OneSixLauncher.launch(OneSixLauncher.java:214) at org.multimc.EntryPoint.listen(EntryPoint.java:139) at org.multimc.EntryPoint.main(EntryPoint.java:53) 2014-03-18 13:07:39 [SEVERE] [ForgeModLoader] The mcmod.info file in MISC-FIX-AOBD v1.3.0.jar cannot be parsed as valid JSON. It will be ignored argo.saj.InvalidSyntaxException: At line 6, column 14: Invalid character at start of value [â]. at argo.saj.SajParser.aJsonValue(SajParser.java:201) at argo.saj.SajParser.aFieldToken(SajParser.java:137) at argo.saj.SajParser.objectString(SajParser.java:114) at argo.saj.SajParser.aJsonValue(SajParser.java:194) at argo.saj.SajParser.arrayString(SajParser.java:79) at argo.saj.SajParser.parse(SajParser.java:58) at argo.jdom.JdomParser.parse(JdomParser.java:36) at cpw.mods.fml.common.MetadataCollection.from(MetadataCollection.java:44) at cpw.mods.fml.common.discovery.JarDiscoverer.discover(JarDiscoverer.java:53) at cpw.mods.fml.common.discovery.ContainerType.findMods(ContainerType.java:42) at cpw.mods.fml.common.discovery.ModCandidate.explore(ModCandidate.java:71) at cpw.mods.fml.common.discovery.ModDiscoverer.identifyMods(ModDiscoverer.java:137) at cpw.mods.fml.common.Loader.identifyMods(Loader.java:353) at cpw.mods.fml.common.Loader.loadMods(Loader.java:484) at cpw.mods.fml.client.FMLClientHandler.beginMinecraftLoading(FMLClientHandler.java:183) at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:473) at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:808) at net.minecraft.client.main.Main.main(SourceFile:101) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at net.minecraft.launchwrapper.Launch.launch(Launch.java:131) at net.minecraft.launchwrapper.Launch.main(Launch.java:27) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.multimc.onesix.OneSixLauncher.launch(OneSixLauncher.java:214) at org.multimc.EntryPoint.listen(EntryPoint.java:139) at org.multimc.EntryPoint.main(EntryPoint.java:53)
It means that both me and the author of MAG-Technomancy 0.3.0a.zip have used special characters on one of the file mcmod.info file. Which is what holds that short mod description you see in the Mods menu in-game. Nothing of vital importance. Can be safely ignored.
I get the following messages in the log when I have AOBD installed:
[SEVERE] [ForgeModLoader] The mcmod.info file in AOBD v1.3.0.jar cannot be parsed as valid JSON. It will be ignored
And another, unrelated one:
[WARNING] [Another One Bites The Dust] Mod Another One Bites The Dust is missing a pack.mcmeta file, things may not work well
These does not seem to cause any issues, but I am sure there is a reason for these messages to exist.
PS: I am using AOBD 1.3.0
First warning means I've used a special character on that file. The mod description won't show up properly inside the mods menu (if you look in it it will probably say the mod AOBD is missing its mcmod.info file. The mod will still work just fine as that file's only use it to provide the text for that menu.
The second menu is related to resource packs. It also doesn't stop anything and several mods just don't bother with it. I can guarantee that you can safely ignore that warning as well
That's quite strange... it could be a ID de-sync between client and server. Maybe their server ID is one but their client ID and something else. In that case you'd have to report it to the FTB team.
Backup your world, delete the server and client and then download them new and see if the problem persists.
About what mod uses the ID, there's simply no way of me knowing it since any mod worth anything gives the players the ability to change IDs, and I know for a fact that the FTB team messes with IDs of pretty much every mod they use, there's no way of me knowing what ID they are giving for each item.
D= If you remember let me know :3 Suggestions are always welcome :3Also.. if anyone could help me with this straw poll:
strawpoll.me/1142067
Glad to hear it Enjoy
IC2 and Mekanism still require this mod though.
But if you used this mod just because of TE3 you won't need to anymore when the next version of TiC comes out.
I'll release an update soon to remove TE3 support from this mod
Unless you are using this with Tinker's Construct's version that already has the cobalt/ardite dusts you must use version 1.1.1 or below.
By your crash log I can tell that the version of TiC you have does not come with the dusts
Thank you for letting me know I'm glad to see you guys like it
That's great to hear Have fun with it
Have you tried processing cobalt/ardite/aluminium on the mekanism machines?
What version of Mekanisn, AOBD and TIC do you have?
Also, make sure you don't have an id conflict...
cool:3
Thank you Glad you like it
I think the error is pointing at a conflicting ID with AOBD. I've searched for possible answers and I see multiple crash reports in pastebin the last few days with the same error, but no resolutions. Maybe you can tell me how to fix it please?
Thanks!
But you shouldn't update the version that the Monster pack has, AOBD updates change very little, if they didn't think it was worth updating it's probably because they already have the version with all the features they need.
That's quite strange... it could be a ID de-sync between client and server. Maybe their server ID is one but their client ID and something else. In that case you'd have to report it to the FTB team.
Backup your world, delete the server and client and then download them new and see if the problem persists.
About what mod uses the ID, there's simply no way of me knowing it since any mod worth anything gives the players the ability to change IDs, and I know for a fact that the FTB team messes with IDs of pretty much every mod they use, there's no way of me knowing what ID they are giving for each item.
Hey man I am getting this on start up
2014-03-18 13:07:34 [OFF] [ForgeModLoader] Logging level for ForgeModLoader logging is set to SEVERE
2014-03-18 13:07:38 [SEVERE] [ForgeModLoader] The mcmod.info file in MAG-Technomancy 0.3.0a.zip cannot be parsed as valid JSON. It will be ignored
argo.saj.InvalidSyntaxException: At line 14, column 21: Expected 't' to be followed by [[r, u, e]], but got [[h, a, u]].
at argo.saj.SajParser.aJsonValue(SajParser.java:153)
at argo.saj.SajParser.arrayString(SajParser.java:79)
at argo.saj.SajParser.aJsonValue(SajParser.java:198)
at argo.saj.SajParser.aFieldToken(SajParser.java:137)
at argo.saj.SajParser.objectString(SajParser.java:114)
at argo.saj.SajParser.aJsonValue(SajParser.java:194)
at argo.saj.SajParser.arrayString(SajParser.java:79)
at argo.saj.SajParser.parse(SajParser.java:58)
at argo.jdom.JdomParser.parse(JdomParser.java:36)
at cpw.mods.fml.common.MetadataCollection.from(MetadataCollection.java:44)
at cpw.mods.fml.common.discovery.JarDiscoverer.discover(JarDiscoverer.java:53)
at cpw.mods.fml.common.discovery.ContainerType.findMods(ContainerType.java:42)
at cpw.mods.fml.common.discovery.ModCandidate.explore(ModCandidate.java:71)
at cpw.mods.fml.common.discovery.ModDiscoverer.identifyMods(ModDiscoverer.java:137)
at cpw.mods.fml.common.Loader.identifyMods(Loader.java:353)
at cpw.mods.fml.common.Loader.loadMods(Loader.java:484)
at cpw.mods.fml.client.FMLClientHandler.beginMinecraftLoading(FMLClientHandler.java:183)
at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:473)
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:808)
at net.minecraft.client.main.Main.main(SourceFile:101)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:131)
at net.minecraft.launchwrapper.Launch.main(Launch.java:27)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.multimc.onesix.OneSixLauncher.launch(OneSixLauncher.java:214)
at org.multimc.EntryPoint.listen(EntryPoint.java:139)
at org.multimc.EntryPoint.main(EntryPoint.java:53)
2014-03-18 13:07:39 [SEVERE] [ForgeModLoader] The mcmod.info file in MISC-FIX-AOBD v1.3.0.jar cannot be parsed as valid JSON. It will be ignored
argo.saj.InvalidSyntaxException: At line 6, column 14: Invalid character at start of value [â].
at argo.saj.SajParser.aJsonValue(SajParser.java:201)
at argo.saj.SajParser.aFieldToken(SajParser.java:137)
at argo.saj.SajParser.objectString(SajParser.java:114)
at argo.saj.SajParser.aJsonValue(SajParser.java:194)
at argo.saj.SajParser.arrayString(SajParser.java:79)
at argo.saj.SajParser.parse(SajParser.java:58)
at argo.jdom.JdomParser.parse(JdomParser.java:36)
at cpw.mods.fml.common.MetadataCollection.from(MetadataCollection.java:44)
at cpw.mods.fml.common.discovery.JarDiscoverer.discover(JarDiscoverer.java:53)
at cpw.mods.fml.common.discovery.ContainerType.findMods(ContainerType.java:42)
at cpw.mods.fml.common.discovery.ModCandidate.explore(ModCandidate.java:71)
at cpw.mods.fml.common.discovery.ModDiscoverer.identifyMods(ModDiscoverer.java:137)
at cpw.mods.fml.common.Loader.identifyMods(Loader.java:353)
at cpw.mods.fml.common.Loader.loadMods(Loader.java:484)
at cpw.mods.fml.client.FMLClientHandler.beginMinecraftLoading(FMLClientHandler.java:183)
at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:473)
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:808)
at net.minecraft.client.main.Main.main(SourceFile:101)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:131)
at net.minecraft.launchwrapper.Launch.main(Launch.java:27)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.multimc.onesix.OneSixLauncher.launch(OneSixLauncher.java:214)
at org.multimc.EntryPoint.listen(EntryPoint.java:139)
at org.multimc.EntryPoint.main(EntryPoint.java:53)
It means that both me and the author of MAG-Technomancy 0.3.0a.zip have used special characters on one of the file mcmod.info file. Which is what holds that short mod description you see in the Mods menu in-game. Nothing of vital importance. Can be safely ignored.
First warning means I've used a special character on that file. The mod description won't show up properly inside the mods menu (if you look in it it will probably say the mod AOBD is missing its mcmod.info file. The mod will still work just fine as that file's only use it to provide the text for that menu.
The second menu is related to resource packs. It also doesn't stop anything and several mods just don't bother with it. I can guarantee that you can safely ignore that warning as well
Thanks Gany, that did it!