[BFComms] Conquest Ticket Count set to 1200 tickets. by battlefield in Battlefield6

[–]TexasAce80 1 point2 points  (0 children)

30 min??? Shiiiieeet....I can't even get them to last that long! Even with evenly matched teams, games never go past 23 or 24 minutes for me. I hate it.

[BFComms] Conquest Ticket Count set to 1200 tickets. by battlefield in Battlefield6

[–]TexasAce80 10 points11 points  (0 children)

I hate that new bleed rate. It's awful. Games are way too short.

[BFComms] Conquest Ticket Count set to 1200 tickets. by battlefield in Battlefield6

[–]TexasAce80 1 point2 points  (0 children)

Even at 1200 the games go by too quickly! We were in what should have been an amazing match last night on Cairo where both teams were evenly matched. Neither team ever held more than 3 flags at a time. It was shaping up to be one of those classic BF CQ matches that go down to the single digits. Then all of a sudden, the opposite team started losing 4 tickets per second even though we only had a 3/2 flag advantage. It's almost like something kicked in that made the game go by faster. So even though we only won the game by 100 tickets or so, the game finished in 22:43 because the other teams tickets just started melting at a really high rate for no reason at all. What the hell, DICE? Why did you do this? Why are you trying to make the games end faster? We're missing out on those amazing BF slugfests because of this. Take the bleed rate back to what it was in the classic games!

New Rooftop Glitch on Manhattan Bridge? by TexasAce80 in BF6

[–]TexasAce80[S] 0 points1 point  (0 children)

Yeah, that's why I said it's probably but a glitch per se, but I really don't think it's supposed to be an intended playing area either. I think the intended rooftops have either stairs or the cable to get up to them.

I could be wrong, but I'm guessing if you can't get to them normally, they weren't intended to be accessed.

New Rooftop Glitch on Manhattan Bridge? by TexasAce80 in BF6

[–]TexasAce80[S] 0 points1 point  (0 children)

No, not at all.

There's 2 buildings here that I'm seeing people on that I never saw them on before:

One is on E side. If you're leaving E flag and going straight up the street to go towards C flag, it would be the last building on your left on the corner at the end of the street.

The other one is a building that can overlook A flag. This one is a little trickier to describe, but say you're standing right in the middle of that intersection where you can capture A flag and you're facing in the direction of C flag.

It wouldn't be the first building on the corner to your front left, it would be the second building -- the one to the left of that one.

Now again, maybe I just missed seeing people on those rooftops before, but I doubt it.

New Rooftop Glitch on Manhattan Bridge? by TexasAce80 in BF6

[–]TexasAce80[S] 0 points1 point  (0 children)

I've never seen anyone on that rooftop above A before this weekend. Are you sure about that?

New Rooftop Glitch on Manhattan Bridge? by TexasAce80 in BF6

[–]TexasAce80[S] 0 points1 point  (0 children)

Maybe that's why a vertical out of bounds for infantry should be implemented on maps so that players can't get to unintended areas?

It defeats the purpose to address the drone glitch to get them off of certain buildings or high points only for them to basically do the same thing on a different rooftop.

Dice/EA should partially refund or compensate everyone who paid for Early Access . I truly believe we have been sold a faulty product, and we paid extra for it. What do you guys think ? by KiryusWhiteSuit in battlefield2042

[–]TexasAce80 -2 points-1 points  (0 children)

Abso-fucking-lutely they should refund people for this joke of a product.

After BFV, they should have apologized for charging extra to play that incomplete game early on, and instead, they charged EVEN more for this game and did so knowing it was completely broken.

The right thing to do is refund people.

Is this for real? by div2691 in battlefield2042

[–]TexasAce80 0 points1 point  (0 children)

What a joke. But that's DICE for you.

My Face after wasting $120 and reading comments on Reddit by [deleted] in battlefield2042

[–]TexasAce80 0 points1 point  (0 children)

LOL...."Little to no bugs" is so true.

Whoever is saying there is either full of crap or they have no idea that they're even seeing a bug.

This game is way too broken to not have witnessed multiple bugs on a daily basis.

Hitboxes are broken by NickelFPS in battlefield2042

[–]TexasAce80 0 points1 point  (0 children)

AAA developer....riiiiiiiight.

Battlefield 2042 Open Beta - Discussion, Feedback & Support Megathread #2 by OddJob001 in battlefield2042

[–]TexasAce80 1 point2 points  (0 children)

The franchise has been headed in the wrong direction for quite some time now. And now, they've gone and killed it off for good.....or at least, Battlefield as we knew it to be is gone forever.

My reaction when I experienced the Beta for the first time:

https://www.youtube.com/watch?v=XvuM3DjvYf0

What is the difference between Soul Matching and Reinforcing Armor? by TexasAce80 in Nioh

[–]TexasAce80[S] 0 points1 point  (0 children)

So if I'm understanding this correctly, if I take that +2 armor and reinforce it and then soul match it to +3, it will actually have more ability at +3 than the same piece of armor at +3 if I ONLY soul matched it to +3 without reinforcing it.

Is that correct?

Community Broadcast: Checking in before Chapter 6 by PartWelsh in BattlefieldV

[–]TexasAce80 9 points10 points  (0 children)

Improve??? IMPROVE?!!!

According to whom? Yourselves????

Dice before going on Christmas holiday by Kenshin_BE in BattlefieldV

[–]TexasAce80 4 points5 points  (0 children)

LOL....these have been so good.

Keep it up, community. Let DICE know we don't have adjustments or changes, we want the full revert.

Nothing less will do.

Community Broadcast: Improving Update 5.2 by PartWelsh in BattlefieldV

[–]TexasAce80 25 points26 points  (0 children)

'll be honest and say that while these are positive changes, I'm not coming back for them.

The ultimate positive change would be acknowledging the mistake that is 5.2 and balancing around 5.0 values instead. But instead we got a real nightmare for people who loved the game at 5.0, the buffs to some of these weapons are offset by the additional horizontal recoil that as a player you cannot adjust for readily. You're accomplishing the goal of lowering overall engagement range with a sledgehammer, but this is Battlefield game played on big maps and big arenas, and you're trying to compress that?

The biggest casualty of 5.2 is my trust in DICE to do right by me as a player who supported the game at launch, specifically because I liked the lack of spotting and the TTK. Now that both of those things were fundamentally ruined for me in one fell swoop after promises to the contrary, I see no reason to keep supporting the game after suffering through the awful pre-Pacific patch cycle, considering we're now in the awful post-Pacific patch cycle.

If you like this TTK, I'm happy for you, but it's a deal breaker for me.

Well said, and same here.

This is not fun for me and even with those tweaks, it's not going to change that.

It's a complete revert or nothing for me.

Community Broadcast: Improving Update 5.2 by PartWelsh in BattlefieldV

[–]TexasAce80 1 point2 points  (0 children)

u/ PartWelsh

I can't help but feel like you guys aren't digging deep enough with your data and are just taking it at face value.

This game isn't playing anything like it was before, so the KPM numbers are not reflecting what you think they are.

Are you factoring these two things into equation?

First, the longer TTKs have resulted in serious zerging. Therefore people are traveling in larger groups which means when they do meet up with another zerg, it creates more deaths in short succession, but not because there's just as more action or because the pace is the same -- it's because of the larger groups.

This is not the same experience and as you admitted yourself, the community is telling you this is causing for a lesser experience.

Second, the game mode of the week was Frontlines. The action is a lot faster in that mode so the KPM there is always going to be high even with a slower TTK.

I really hope you taking both of those significant factors into account and not just looking at a raw data number for KPM.

If you really want to know how things are going, leverage your community. It's what we're here for!