100%/40% attribute increase chance bug

Game mode: [Online private, modded]
Type of issue: [Bug]
Server type: [PvE]
Region: [EU]

As soon as you place a thrall that comes with a 100% chance of increase in an attribute, further thralls come with only a 40% chance in that same attribute.

I saw this while placing a bunch of bearers, the first one had a chance of increasing strength of 100%, ALL the following thralls had only 40% in strength.
But the first four bearers all had a 100% chance attribute (one had two attributes with a 100% chance), thus the last one (#5) had 40% in every attribute.

Placing four bearers and getting 100% five times seems to me more buggy than unbelievably lucky.
That the 100% prevents other thralls from getting more than 40% is a bug for sure.

A server-restart fixes this, thralls placed after server restart are not prevented from having attribute increase chances of more than 40%.
Unless one of the new thralls has 100%, then the bug is active until the next server-restart.

And it may(!) be restricted to the type ot thrall. I placed thralls after the server-restart that were OK, but then I placed a bearer and he got 100% in survival, the next bearer got 40%, but another thrall that was not a bearer and which I placed some time later got 70% in survival.

Please provide a step-by-step process of how the bug can be reproduced. The more details you provide us with the easier it will be for us to find and fix the bug:

  1. Place thralls (seems to be more prevalent with bearers, at least to me…) until you get one with a 100% chance in an attribute.
  2. Place more thralls of the same type and look at the attribute in which the first one got the 100%, it will be 40% then.
  3. Place thralls of that type after server-restart and see that they get normal attribute increase chances, unil a new thrall with 100% appears. Go to 2.
1 Like

I think it was reported before and said to be fixed internally: 40% Growth Rate Bug - so, here’s hoping that the fix may roll out soon.

1 Like

I know, but that thread is closed already. I wanted to add some additional information, so that people affected by that bug know that a server restart fixes it temporarily, until we get the hotfix.

1 Like

Hey there,

This issue should be addressed in our newest patch:


This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.