Back to Basics, Battlefield 1
Product: Battlefield 1 Platform:Microsoft XBOX One Summarize your bug Back to Basics allowing cheaters/ guns not meant for the game mode How often does the bug occur? Every time (100%) Steps: How...
Forum Discussion
Absolutely. Don't know how this slipped by Dice, but the servers are full of people shooting automatic pistols and revolver rifles at each other. Totally kills the point of Back to Basics.
This is tracked, I believe. Cause of the bug would be the fact that Pilot/Tanker weapons have recently become available for Assault/Support, but they were not adjusted for B2B, as, before introduction of those guns to Support/Assault, there was no need to disable them (as planes and tanks were blocked anyway). I imagine that being the reason why pistol carbines, Frommer Auto and sawed-off slipped into this mode.
Please excuse my ignorance. What does tracked mean? Does that mean Dice is aware and will fix it soon? I really hope they do before it becomes unfeatured. Back to Basic servers are almost always empty, and it's my favorite mode. Really the only reason I came back to BF1 this week.
When you hear that the bug is tracked, it means that it's known and, at very least, the Quality Assurance team is investigating. It doesn't always mean that it will be fixed in the future - fix might be heavily delayed in two cases:
a) If there is no reliable way of reproducing the bug/the fix is particularly complicated in terms of changes that have to be applied. Revive bug or Operations end screen bug are two good examples. Those often are high on priority list, but simply are way more challenging than typical bugs
b) If bug priority is low. It's the most common if the bug has very low severity (especially when it's easy to bypass). Let's think about it logically: if you have, let's say, 3 bugs that heavily hurt the game and 3 that barely do anything, you would obviously prioritize the major ones.
On this one, I believe it's more on the major issue side, so I could see it being fixed soon-ish if BF1 patches continue (maybe in the next update if we get one, who knows) - cause of the issue is known and quite straightforward. While I know it was technically detected before update from July 31st, I'm fairly sure that it wasn't fixed mostly because it was spotted when certification process for the update already was very advanced.
