I'm gonna quote my comment from the other thread, since it seems relevant here:
A glitch, in most cases, is not a broken game mechanic, as OP says it is. Especially when you're talking about getting under the map. That's just an accident, plain and simple. OP, you seem to be using the self-applied term "game mechanic" as carte blanche to do whatever you want. When it's a glitch that gives an unfair advantage, there's a specific name for that. It's called an exploit.
Just because it's part of the game doesn't mean it's meant to be used. The developers clearly never intended for us to get out of bounds and into otherwise-inaccessible areas of the map. Tracking down and patching every single exploit is impossible, when a developer has corporate overlords focused on getting new content made for people to spend money on. The same people who make new content are generally the ones who patch glitches and exploits. There's only so much they can do, and only so much time they had available to work on BF4 before moving on to the next game, or even simply the next DLC for BF4.
You're also assuming they even know about these glitches and exploits. I've been playing BF4 since shortly after its release, and while I'm generally aware of the existence of many of those glitches and exploits, I don't know how to do more than a handful. Personally, I actually don't remember how to do any of them, and I've only ever used them to go after other people who were using them for an unfair advantage. The idea of a game is to have a level playing field where everything that is meant to be doable is reasonably obvious and easily learned. People shouldn't have to go down a rabbit hole on YouTube or something to learn how to "play the game as intended." If you have to go down such a rabbit hole to figure out how to get outside the map, that's not intended gameplay.
It can be very difficult to track down and learn how all the glitches and exploits are done. Unless their use is extremely widespread, it's simply not worth the time for the devs to try and learn about them all, and then take the time to patch them. It's like whack-a-mole. You're never going to find them all within a reasonable period of time, and no sane boss is going to pay you to spend days or weeks on YouTube just to figure out what the glitches are, when there's always going to be another glitch that gets uncovered after you patch what you do find, and when there are more pressing things, like intended game mechanics that actually are broken and not functioning as intended, with significant impacts to the entire player base.
Let's take another approach to this. Super Mario 64 or The Legend of Zelda: Ocarina of Time speed runs (or really, any other game of your choice, but Super Mario 64 and Ocarina of Time are particularly spectacular examples). Go watch one. It shouldn't take more than a few minutes. It's absolutely crazy stuff. Can you watch one of those, and honestly say that everything used there is an intended game mechanic? Absolutely not.
Now, there's a slight difference, in that you can't exactly remotely push out post-release patches to a cartridge-based game released in the '90s, but the same basic rules apply to the pre-release development process. You patch what you and the testers find and what can be easily taken care of within the time available before release. Everything else is still in the game, but it's not intended to be in the game. It's just there, and clearly not meant to be used.
Now, it sounds like there's some obvious hipocrisy in how BF4DB is run, and some people who should have enforcement actions taken against them, but aren't. That's a separate issue, that you're right to be upset over, OP. But the simple fact here is that you cheated. Exploits like this are considered cheating by the community at large, plain and simple. You don't have to inject third-party code into the game for something to be considered chea
