Prevent l0g from picking targets with BINMAT enabled

[bowkill-hackmud]

A binmat game(s) can be intentionally sandbagged by a defender to wait out the short ~3min lock stack rotation window. If a l0g has a loc_count of 3 or higher, it becomes improbable (or impossible?) to win enough games as an attacker to breach the l0g's target list before a rotation happens forcing the attacker to start over. This leaves the only practical approach to cracking a high loc_count l0g to be flooding the target with attacker-controlled users for "self breaching" (i.e. a pay-to-win strategy).

As a result, similar to l0g avoiding targets that contain a l0g to prevent chaining, l0g should avoid targets with binmat to prevent defender controlled time delays exceeding the maximum stack rotation window.

[Helloman892]

I feel that this forces picking BINMAT or l0g_wr1t3r, and therefore disincentivises both depending on outlook. Not sure if that's a good thing, but throwing the criticism in.

[1shira]

issue: this could potentially make whole defense networks entirely ineffective. it's a breaking change and at present after this change the only way to get back a defense net that works with l0g you would have to retire the users with binmat.

[bowkill-hackmud]

I agree, made a follow-up suggestion giving users the ability to manually disable binmat. https://github.com/orgs/comcode-org/discussions/33