Currently once you get binmat, there is no way to disable it again. Even if you don't set an autobrain, your user will still enter binmat when hacked if there is GC. This has been an issue for a while, but usually people ignore it. Have binmat and don't want to play? Just don't hold an ante, easy enough. But, here is a use-case where just *having* binmat is bad. Authentication systems often expire authorization for users based on last action (14 and 30 days being common "idle for this long -> expire auth" times). But if you retire a user with binmat, an enemy can send it GC for an ante then binmat it to keep it's last action recent-enough to avoid auto-expiry. Sure sure, "just manually remove it", but this isn't viable for a corp. An ally might disappear for a while and their users auto-retire with no one telling you, etc. being able to track with some accuracy if a user is truly active is important, and binmat means we can't actually tell meaningful activity: anyone who knows the loc can force activity remotely. What would work would be something like... binmat.c{disable:true}. If set, your user would act as if they didn't have binmat when breached. You could then set disable to false to turn binmat back on (or enable:false/true perhaps might make more sense) ( note: this could obviously be changed by a scam script, but since a scam can already change your autobrain, disabling isn't really anything *new*. setting the autobrain to scriptdoesntexist is just as bad )