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
Hah, kind of funny. Thanks for the report, ill get it fixed.
it might speed up the search for the problem mod(s).
The cause is most likely the fact that i raised the XP gain to the max amount in the mod settings.
Edit: in hindsight it was probably because i used dev mode to put both the wanderer and wayfarer trait on the same character
1) If mana shield is cast in lich form, it does not absorb damage.
2) If mana shield was active before the necromancer casts lich form, the spell remains functional and absorbs damage. However if it gets canceled and then reapplied, it doesn't absorb damage anymore, as in situation 1.
Here is the log:
Exception ticking Lidia (at (222, 0, 199)): System.NullReferenceException: Object reference not set to an instance of an object
at TorannMagic.AutoCast.CastOnSelf.Evaluate (TorannMagic.CompAbilityUserMagic casterComp, TorannMagic.TMAbilityDef abilitydef, AbilityUser.PawnAbility ability, TorannMagic.MagicPower power, System.Boolean& success) [0x0002c] in <6e56e84e66ef48e1a4f65b1ca11826e1>:0
at TorannMagic.CompAbilityUserMagic.ResolveAutoCast () [0x002ca] in <6e56e84e66ef48e1a4f65b1ca11826e1>:0
at TorannMagic.CompAbilityUserMagic.CompTick () [0x0048d] in <6e56e84e66ef48e1a4f65b1ca11826e1>:0
at Verse.ThingWithComps.Tick () [0x00024] in <0ee2c524c4be441e9b7f8bfcb20aca6f>:0
at (wrapper dynamic-method) Verse.Pawn.Verse.Pawn.Tick_Patch1(Verse.Pawn)
at Verse.TickList.Tick () [0x0015c] in <0ee2c524c4be441e9b7f8bfcb20aca6f>:0
Verse.Log:Error(String, Boolean)
Verse.TickList:Tick()
Verse.TickManager:Verse.TickManager.DoSingleTick_Patch3(TickManager)
Verse.TickManager:TickManagerUpdate()
Verse.Game:Verse.Game.UpdatePlay_Patch2(Game)
Verse.Root_Play:Verse.Root_Play.Update_Patch1(Root_Play)
Looking forward to a fix but for now, they're being sealed in a crytosleep casket since they are nearly useless.
EDIT: This seems to only happen when they have enough magic to cast "Reverse Time" (not 100% sure, but patterns are heavily pointing to it); once their magic is below the minimum needed, they perform work normally. A temporary fix is to make sure spells are constantly used to be below the threshold.
Check my post for a temporary workaround that I just found, until this can get fixed. If you can, keep Prediction active, don't put points into mana efficiency, and perhaps have them learn a few spells that reduce maximum mana or mana regen. If you can avoid learning the spell completely, you should be 100% fine.
I'm having this same problem, it must be related to 1.2. What I've found as a temporary fix is using dev. + god mode to reset their levels. On the plus side usable pawn on the down side gimped chronomancer.
The minion does not spawn, but the game slows down considerably.
Exception ticking Projectile_SummonMinion444956 (at (100, 0, 162)): System.MissingMethodException: void Verse.AI.Group.LordJob_DefendPoint..ctor(Verse.IntVec3)
at TorannMagic.Projectile_SummonMinion.Impact (Verse.Thing hitThing) [0x00344] in <6e56e84e66ef48e1a4f65b1ca11826e1>:0
at AbilityUser.Projectile_AbilityBase.ImpactSomething () [0x000f2] in <fec38be6254c4f0098db29424a6d7806>:0
at AbilityUser.Projectile_AbilityBase.Tick () [0x0003f] in <fec38be6254c4f0098db29424a6d7806>:0
at TorannMagic.Projectile_SummonMinion.Tick () [0x00001] in <6e56e84e66ef48e1a4f65b1ca11826e1>:0
at Verse.TickList.Tick () [0x0015c] in <7b345446a85d4ed599f9c604ae61854b>:0
Verse.Log:Error(String, Boolean)
Verse.TickList:Tick()
Verse.TickManager:DoSingleTick()
Verse.TickManager:TickManagerUpdate()
Verse.Game:UpdatePlay()
Verse.Root_Play:Update()
Exception ticking Projectile_SummonMinion444968 (at (88, 0, 155)): System.MissingMethodException: void Verse.AI.Group.LordJob_DefendPoint..ctor(Verse.IntVec3)
at TorannMagic.Projectile_SummonMinion.Impact (Verse.Thing hitThing) [0x00344] in <6e56e84e66ef48e1a4f65b1ca11826e1>:0
at AbilityUser.Projectile_AbilityBase.ImpactSomething () [0x000f2] in <fec38be6254c4f0098db29424a6d7806>:0
at AbilityUser.Projectile_AbilityBase.Tick () [0x0003f] in <fec38be6254c4f0098db29424a6d7806>:0
at TorannMagic.Projectile_SummonMinion.Tick () [0x00001] in <6e56e84e66ef48e1a4f65b1ca11826e1>:0
at Verse.TickList.Tick () [0x0015c] in <7b345446a85d4ed599f9c604ae61854b>:0
Verse.Log:Error(String, Boolean)
Verse.TickList:Tick()
Verse.TickManager:DoSingleTick()
Verse.TickManager:TickManagerUpdate()
Verse.Game:UpdatePlay()
Verse.Root_Play:Update()
Exception ticking Projectile_SummonMinion446381 (at (132, 0, 149)): System.MissingMethodException: void Verse.AI.Group.LordJob_DefendPoint..ctor(Verse.IntVec3)
at TorannMagic.Projectile_SummonMinion.Impact (Verse.Thing hitThing) [0x00344] in <6e56e84e66ef48e1a4f65b1ca11826e1>:0
at AbilityUser.Projectile_AbilityBase.ImpactSomething () [0x000f2] in <fec38be6254c4f0098db29424a6d7806>:0
at AbilityUser.Projectile_AbilityBase.Tick () [0x0003f] in <fec38be6254c4f0098db29424a6d7806>:0
at TorannMagic.Projectile_SummonMinion.Tick () [0x00001] in <6e56e84e66ef48e1a4f65b1ca11826e1>:0
at Verse.TickList.Tick () [0x0015c] in <7b345446a85d4ed599f9c604ae61854b>:0
Verse.Log:Error(String, Boolean)
Verse.TickList:Tick()
Verse.TickManager:DoSingleTick()
Verse.TickManager:TickManagerUpdate()
Verse.Game:UpdatePlay()
Verse.Root_Play:Update()
Their post and mine were before 1.2 released. I'm currently on 1.1 (waiting a week or so for more mods to update); I'm not sure how it works on 1.2, but it's not exclusive to that.
The bug is tied to an attempted autocast that isn't Prediction; I'm guessing they are trying to cast autocast a different spell which isn't properly coded for it. Pawn gets stuck trying to autocast every tick, and doesn't do anything. If you'd be up for it, you could help me try to crack down the exact culprit, and try each spell/skill one at a time until the bug pops up again. That'll make it easier for the author to fix this Chronomancer time loop.
please help