Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
What error are you getting from Transfer Broker?
I don't think Harmony 2.0.4-4 was broken by the DLC update, but it does not manage errors thrown by the various broken mods, and as a result it look like it is broken itself. So it's lacking, but not technically broken.
As was pointed out at Colossal's firefighting thread, they made this mess themselves, by not releasing an early beta of the game for the modders to update their mods to. Knowing that their workshop is so fragile, yet releasing a big update publicly without any coordination with the workshop authors, is very negligent of Colossal.
That same carelessness is reflected in how Harmony 2.0.4-4 is released, without testing, without a plan, completely lacking discipline. It's that lack of discipline that I wanted to address by creating the redesigned version, and it's paying dividends.
Thank you for your support!
Thank you also for pointing out the TB version issue, I will deal with it ASAP
Details:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object
at TransferBroker.TransferBrokerMod.CheckAppVersion () [0x00000] in <filename unknown>:0
at TransferBroker.TransferBrokerMod.OnEnabled () [0x00000] in <filename unknown>:0
at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (object,object[],System.Exception
I getting an error too. What should I do? Thanks for your support
I apologize for the error. It means TB has found that it is not safe for it to work with the new transfer mechanics introduced by the update, and requires support for the new stuff to be added. I'm fighting a few fires ATM, but will publish an update ASAP.
also see the detailed explanation here
Thanks for your quick response!