Sadly enough it's not allowed in the way I wanted to implement it anyway, as ruled by staff (even though I don't agree with the ruling, I will still follow it). There likely is still a single method left that would be allowed, but it's technically way more complex. I'll do a little explanation and try to not be too technical.
In the past we could force the action by manipulating some stuff (sometimes the url you visited when clicking, or just faking the confirm button which Torn then accepted) or all information was available in the page structure (known as the DOM, as HTML). For more recent stuff, like all crime 2.0 crimes, this is no longer the case. The information is now only available hidden way down in a tree-structure of javascript beneath the DOM. It's available for us to use, but it's very hard to find in the first place. Once we know where it lives, we get to the next hurdle. While extensions have 99% of the access of on-page scripts (which is also kind of where userscripts live), we hit that 1% area in this case. As a result, userscripts can do this way easier than us. Yes it's possible for us to work around, but we are talking a very major effort. Due to this, we've yet to release (and be allowed to keep; we had a burglary filter which was deemed illegal....) any feature for crimes.
TLDR; new technology used by Torn makes our lives way harder
