"Chain Class format" based numbering breaks, causing duplicate numbers

[Ash Pesante]

When using the following settings: * Chain Class format: 1 * Chain Map Node Reference: Signature ID ...with the desire to create an automated, incremental hole numbering system using just the gray number (1, 2, 3, 4, etc), occasionally the numbers will be reset (ie, "1,2,3,4,5" becomes "1,1,3,4,5").

This seems to occur most when updating holes throughout the chain, and possibly when overwriting wormhole sigs with the connection. As it doesn't consistently occurs, I will attempt to reproduce using manual adding methods.

[Ash Pesante]

Manually adding chain connections and updating them (without travelling between them) did not cause the issue, leading me to believe it may be due to moving through the chain and updating that way.

[Josh Glassmaker]

I am not sure if this is an easy fix or a flaw - I am in the process of redesigning this feature completely and vastly improving it along with the auto-mapper that may be the root cause. If anyone else spots the mistake in the code I can bug fix it but otherwise I am going to try and push for the redesign - it is a ways off yet since the core of Tripwire is getting rewritten as well.