Patch: Stop Auto-repair from repairing unfinished structures #4205
Comments
Kreuvf uploaded file Fix for auto-repair applying to unfinished structures |
vexed changed blocking which not transferred by tractive |
vexed changed blockedby which not transferred by tractive |
vexed commented Maybe it is late, and I am missing something, but, if you remove
Then it will always do it, would it not ? For the maximum value, we should CLIP that or something. |
Kreuvf commented The change will check that the status of the structure in question is not "under construction", which is the only status without auto-repair. Besides fixing the auto-repair bug this also fixes consistency inside the WZ world: if an unattended half-built structure vanishes over time, but has auto-repair as well, This is a quick fix, I know. On the other hand clipping the max. value does not seem like a clean solution to me as well. |
Per commented I believe the patch is erroneously reversed. Hence vexed's confusion. |
per changed status from |
per changed resolution from `` to |
per commented Stop Auto-repair from repairing unfinished structures. Patch by Kreuvf. Changeset: 8f7b9c8f07502c2e0cb86fd2c7d6085dfae1896d |
per commented Stop Auto-repair from repairing unfinished structures. Patch by Kreuvf. Changeset: 8f7b9c8f07502c2e0cb86fd2c7d6085dfae1896d |
1 similar comment
per commented Stop Auto-repair from repairing unfinished structures. Patch by Kreuvf. Changeset: 8f7b9c8f07502c2e0cb86fd2c7d6085dfae1896d |
resolution_fixed
type_patch (an actual patch, not a request for one)
| by KreuvfOnly tested with 3.1.0, but probably also existing in many other branches.
Problem: Auto-repair repairs structures while they are built. When finished, the structure has more bodypoints than its maximum value allows. This results in the first hit to reduce the current bodypoints to the maximum value allowed.
This patch add a check for the structure status != SS_BEING_BUILT. Patch tested with 3.1.0.
Issue migrated from trac:4205 at 2022-04-16 11:43:45 -0700
The text was updated successfully, but these errors were encountered: