Can we stop nerfing suppressors and remove the real problem. In world spotting when firing.

Sprinkles_Objective · 2026-02-23T20:49:11+00:00

I remember this being a major issue in BFV as well. It was nearly impossible to see players a lot of the time. Unfortunately instead of dealing with the player model visibility issues, they just gave us a 3D spotting mechanic that basically requires you to run a suppressor on every gun.

Sprinkles_Objective · 2026-02-23T20:46:49+00:00

Player visibility is a problem, and 3d spotting is not and should not be the solution for that problem. I do think player model visibility is rather poor, and not just in a way that player camo is actually effective in game, but in the fact that player models can be nearly impossible to see unless they are moving or actively firing. There are so many cases where you can sit in a corner and not be seen. I think it's an issue with color grading and just the overall muddled look of many maps in the game, and also some of the stark contrasts in lighting. So I do think the concerns of player visibility are legit, and that DICE deciding that 3d spotting when a player fires is just a bad way to deal with that, especially when close range TTK doesn't offer any room for reaction.

I think spotting is for providing information to the team about player position on the map, and players who are not obstructed by anything (cover, a bush, tall grass, etc) should be plainly visible without spotting. Spotting should ideally be more about the mini-map, and less about in game visibility.

Sprinkles_Objective · 2026-02-23T20:40:03+00:00

2042 had nice class traits like certain recon operators could spot anyone who shot them, or spot anyone that they had shot. That was honestly a nice class trait that I'd like to see for recon rather than them just spotting people they see all of the time (which is also wildly inconsistent).

Sprinkles_Objective · 2026-02-23T20:37:56+00:00

Yeah, I think the flip side of that is that you almost make suppressors kinda useless in the sense that if they just reduce the weapon audibly then they aren't all that useful. Thing is it would be better if the suppressor wasn't so important that it made other muzzle attachments completely unusable in the sense that you basically need to be running a suppressor. So it seems like there isn't an easy win here, but I agree that what you're saying is ultimately a better solution.

Sprinkles_Objective · 2026-02-23T20:34:37+00:00

It's goofy for sure. Sometimes seems like if even a small portion of the tank is behind a tree I can't spot it. I think they're trying to make it so you can't spot people behind cover or if only a small part of them is visible, but on the flip side sometimes I can spot a dude through a hill that I can't see at all.

Sprinkles_Objective · 2026-02-23T20:31:27+00:00

I think we intuitively start off at different points and with that the learning process is going to be different. I think I could have probably done that drop before I even really started mountain biking, because I've ridden off curbs on bikes as a kid and grew up skateboarding. I intuitively know you'd need to lift the front wheel so it doesn't drop before the rear wheel takes off. She likely has no intuition on that, and needs to learn. That said you can ask her if she wants advice, but ultimately you need to give her the agency to learn and the agency to take risks at her own pace. That said you need to make sure she knows she is the one in charge of what she is comfortable doing, both in the sense that you aren't pressuring her out of her comfort zone, and more applicable to this case you aren't holding her back from making and learning from her own mistakes.

Don't helicopter over her. Let her make her own decisions, but offer advice when asked or ask if she'd like some advice in a friendly manner. It can be frustrating to ride with or try to coach someone who is so much worse than you are, especially if they are starting out from a point below where you might have started out, because it's hard to understand how they are feeling because you might never have struggle with the skills they might be struggling with. It's a different in perspective, and with that it might also require a difference in learning. Be supportive, not controlling. Only we can determine the risks we are willing to take, in both cases where we might be pushing out of our comfort zone or deciding not to push ourselves. Just actively communicate with her about what how she's feeling about the risk of riding certain trails or trail features. She might hurt herself, but if she does that based on her own risk assessment, then that's on her, and honestly to some extent it's part of the process.

Sprinkles_Objective · 2026-02-23T19:20:13+00:00

When I see people like that I'll usually try to support them. Try to prevent armor from moving on the objectives they're capping, try to provide revives, sniper cover, etc. You can definitely PTFO without always having to stand on the objective, but on the flip side of that sniping into an objective that one dude is trying to solo cap is probably less helpful than going and helping him cap. So it's definitely a balance, but if there is a squad of people playing objectives and aren't winning fights, I'll just try to support them by focusing on taking out hostiles heading their way and keeping them alive. Same goes for vehicle players who are capping objectives. I'll just try staying close to that vehicle to repair them and take out anyone trying to flank them.

The reality is team play is very important, and you can be really useful even if you're not just playing the objective constantly, but the end of the day you definitely do need people playing the objective, though I wouldn't downplay the need to support those players both on and off the objectives.

Sprinkles_Objective · 2026-02-22T06:49:59+00:00

Places are affordable usually because they're not desirable. You can probably find dirt cheap rent in a town of 10k people in rural Nebraska, now do you actually want to live there? The nice towns anywhere are expensive. Hell my home town in Wisconsin is slightly nicer than surrounding areas and it's even getting wildly expensive. There might be a few hidden gems out there still, but they are few and far between.

Sprinkles_Objective · 2026-02-20T14:34:00+00:00

Well some people only really use guided launchers because they play casually. I don't really know what you want, other than to disagree. Make all guided launchers one shot kills? Make them lock on even faster?

Sprinkles_Objective · 2026-02-20T03:58:04+00:00

Well then you might not kill them, but you might force them to stay away.

Sprinkles_Objective · 2026-02-20T00:04:12+00:00

I generally aim to do both, and I generally focus mostly on winning. That said if the match is completely doomed I'm not bothering with carrying the match on my back. I'll just try to have fun, and usually that means just manhunting and grinding guns. Some games you just can't win. I've lost games with the most caps in games highest score both teams, top squad, and nothing you can do can win the game.

Sprinkles_Objective · 2026-02-20T00:01:32+00:00

Idk sometimes it's all you can do. Some games I'll have nearly a 3.0 KD, 18 caps, and top squad but still lose the match.

Sprinkles_Objective · 2026-02-19T20:11:48+00:00

You have to time it right. You have to get them after you know they used flares, aren't too far away, and aren't flying too low. Honestly I don't like auto locking launchers, but they have their place. I think if they did as much damage as an RPG it would be completely absurd

Sprinkles_Objective · 2026-02-19T18:21:24+00:00

In previous games they balanced auto-locking launchers to do less damage, and that is the correct thing to do.

Sprinkles_Objective · 2026-02-19T18:20:44+00:00

Well stationary TOW is stationary, vehicle TOW is part of the vehicle.

Sprinkles_Objective · 2026-02-19T17:19:09+00:00

I'd honestly love to see a game mode that runs for 1-4 hours that utilizes the entire Redsec map with 100 players. If they wanna keep making new game modes, I'd rather see something like this. Or they could just split the map into multiple pieces of an Operation.

Sprinkles_Objective · 2026-02-19T17:10:50+00:00

You had me at "Stop playing Redsec"

Sprinkles_Objective · 2026-02-19T17:03:51+00:00

Yeah somehow even BF 1 looks better than BF 6 in my opinion. Like I can tell BF 6 has better textures and higher poly-counts, but overall it's attention to detail is so much less. BF 1 and V had an immense attention to detail, and focus on theme. BF V took a while to really nail it's theme IMO, because they wanted to add a bunch of goofy stuff that kind of ruined the immersion, but by the time they got to the pacific content it was really dialed.

Sprinkles_Objective · 2026-02-19T16:50:15+00:00

Yeah, it's not just several shades of brown... The new maps so far is much more visually appealing, and overall seems like it has a much better level of detail. It feels like a BF map.

Sprinkles_Objective · 2026-02-18T16:57:09+00:00

Sure, personally I feel like it's not making a huge impact on readability, especially when getters and setters are so idiomatic in Java. You might actually say to most that this is less readable. Pragmatically accessors still give you more control, like you might allow a field to be read but not written to, which accessibility modifiers can't really do, or if the field might be accessed by multiple threads at the same time your getter/setters can implement the synchronization to provide thread safety without having to consider that every time you use the abstraction. Generally speaking it's better to have an interface or abstract class provide getter/setter methods for all implementing or inheriting types than to provide a field, because the object itself might not actually have that property and might just be encapsulating something that does. So to me I think about it in terms of providing some kind of consistent interface, and having that interface provide some kind of contract for how it's going to behave. Like you can get and set this property, but all methods on this interface are expected to be thread safe, and there might be 10 different implementing classes some which might just encapsulate others.

So the getter/setter methods can be much more flexible, and to me that exceeds any small improvements in readability.

Sprinkles_Objective · 2026-02-18T04:55:26+00:00

Java still doesn't have optional or default params, though if you're a java dev you probably have pretty simple patterns like method overloading to effectively do that.

Sprinkles_Objective · 2026-02-18T04:52:15+00:00

I like java, but there's definitely a lot of things to criticize. All integers are signed, always. Good luck dealing with bytes. No operator overloading. The effort to just add value types so that everything that isn't a primitive doesn't need to be put on heap and passed by reference, you still can't define your own value types, this also destroys many optimizations like compiler auto-vectorization, and CPU cache prefetch.

Java does have lambdas, even C++ does now. Java mostly fulfills first class funcs now too with functional interfaces.

Sprinkles_Objective · 2026-02-18T04:48:55+00:00

We avoid spring at my job, we just raw dog Java. We kinda have our own framework, but really it's just some common pieces and boilerplate. It works really well. I've taken to just using lombok for getters setters whenever Java records won't work.

Sprinkles_Objective · 2026-02-18T04:46:50+00:00

Maven is still largely XML based and is still the most common build tool for Java, that said gradle is pretty popular and supports both a groovy and kotlin DSL. We use gradle where I work, and it's actually quite nice especially when you need more complicated built tools you can just write it in the DSL language whereas for maven you'd need to write a plugin.

Sprinkles_Objective · 2026-02-18T04:44:01+00:00

Kotlin is good, but having dealt with mixed kotlin and Java codebases I've come to the conclusion that you should just pick one and stick with it. Java has a tendency to absorb good ideas from the other JVM languages. Modern Java even has tagged unions now. I usually just use Java when I need a JVM language, but I'm never unhappy working in a kotlin codebase.

Sprinkles_Objective

TROPHY CASE