224207
That particular SigReason was a demonstration, but I'll remove it for you if you want me to.
So basically, despite it not being allowed for decoration, staff still make the code formatted in a way that allows everyone to change it? Why not just have a subroutine that links the SigReason code to a specific message? It'll be hard to change it to whatever a normal member wants then. Even better, make it set a flag when it is removed so it can test if a rule is still broken at the time of it's removal (or any time after that), so it can just reappear again like it was never edited out at all. Or just have pre-set messages that check for a violation in a rule and then type that, and add anything if more than one rule is broken. If it was like that, it'd made the jobs easier for the higher ups. As for punishments, if it was like what I just said, it could automatically inform a higher-up if that message appears a certain amount of times or higher, which could also be managed via flags. Isn't having that tag readily available to edit (partly) for members daring them to break the rules?
But most important of all: if it's specifically for signatures, why have it still work properly on posts, VMs, PMs, any text-generating device on here that isn't signatures? Just setting a flag and having it referenced to check for a value would surely be enough to prevent the SigReason code from being put anywhere else. If it can be posted anywhere else, does that actually make it a SigReason label?
I know it's an annoying amount of questions, but the answer for them would be interesting to know, so if any of you or the other mods/higher ups could answer, I'd appreciate it.
Just in case anyone's going to challenge my programming knowledge, however, despite me not having the best programming knowledge (in fact, nowhere near), I definitely don't have the worst, and I know enough about these things to know what does what.