You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Keep getting a registry problem with tesla-core-lib #47
I am trying to install industrial foregoing which required tesla core lib. No matter what version of tesla core I download. Server starts up fine, but anyone that joins gets the message below. On single player the mods are working fine. It seems to only be on the server side having the issue. I have even uninstalled and wiped the server and only launched it with tesla core lid and forgelin on it... same issue. So I do not believe its any of the other mods conflicting with it.
I suspect a version and/or config mismatch between the clients and the server. I suspect that one side is using 1.0.15.13 and the other side is using something older, due to this change in particular: b056d95#diff-9e6f26eae9370cf4016296713ff9607a
I had this problem too, it seems to come from the defaults in the teslacorelib config file being improperly generated on occasion. You can fix it by looking at the debug in your log folder to find what things specifically are causing the problem, and edit teslacorelib.cfg (in your config folder) to register the proper things.
Activity
[-]Keep getting a problem with tesla-core-lib[/-][+]Keep getting a registry problem with tesla-core-lib[/+]josephcsible commentedon Nov 23, 2018
I suspect a version and/or config mismatch between the clients and the server. I suspect that one side is using 1.0.15.13 and the other side is using something older, due to this change in particular: b056d95#diff-9e6f26eae9370cf4016296713ff9607a
bkepps commentedon Dec 31, 2019
I had this problem too, it seems to come from the defaults in the teslacorelib config file being improperly generated on occasion. You can fix it by looking at the debug in your log folder to find what things specifically are causing the problem, and edit teslacorelib.cfg (in your config folder) to register the proper things.