Now I can probably say these will probably be bad ideas and potentially cause balance issues. Juice idea: What if you could VERY SLOWLY charge your juice by holding down the juice button combo (or left thumb stick). The charge would be insanely slow and cause light damage to your health while you do it to vaguely balance it out. This would be good for those moments you're close to juice but no bots, players, or turrets are nearby. Ice trap idea: all of us (except snipers, even they do at times) hate ice traps. What if they gave trapped pros damage resistance when caught in the trap, at least enough for say a gunner to take one headshot with Lv3 armor. This is probably a terrible idea overall, but I thought I'd toss it out there anyway
PLEASE. I find it extremely irritating when I get caught in an ice trap and the freeze lasts for such an ungodly amount of time that the Sniper can easily get 3 body shots on me, which kills a gold Armored Assassin.
this is why i don't use traps as a sniper, that and because i push up, i know how effective they can be but they are so god damn OP, almost as OP as a 3.3 firebase
What stops a player from standing in their base gaining juice, or someplace else similarly safe. If health didn't regenerate, this might be an option, but it would be way too easy to abuse unless we make it really, really slow. And in that situation it'll just be faster to wait for the next spawn of players / bots and shoot them from range. I'd like to see what peoples' impressions of the traps are after the DLC is released. If there are still issues with the trap further balance changes aren't out of the question, but I don't think damage resistance is the way to go. We use this mechanic in some very specific situations out of necessity, but it's rarely our first choice.
The only problem I have with ice traps is when I walk into one set off I get stuck, and that's fixed. Even then I only play against stupid snipers and shotgun them while frozen :lol: Juice Idea. It's called being Support. I still don't like being frozen but I'll see after the patch then. And Support is going to get a juice nerf you got the super slow part
Yeah, I agree, supports are really lame. I think traps were fine the way they were, with the exception of maybe being slightly too long of a freeze time. I think people object more to the inability to move in general, but that is complete opinion on my part. Because of this, I'm not sure if people are going to have much positive to say about the change to the ice traps, even if they are in fact positive changes. But then again, I could just be completely wrong. I'm curious about how Uber decides on balance changes for Title Updates and DLCs. Do you guys do regular playtesting as a whole, with a splash of community input from the forums, and decide as a group? I feel like it would be hard to maintain complete objectivity, because even as developers you probably each have favored classes, even if you cannot admit to it publicly.
I make the final decisions on all balance changes but I do so with a lot of input and calculation. We play test internally, we look at the balance changes on some test maps we use internally, we get feedback from members of the team (a lot from bgolus and forrestthewoods), we get feedback from outside testers we bring in, we get feedback from our friends at Microsoft and our test team over there, we look at what everyone has to say on the forums, and we have a few other undisclosed sources of feedback. So trust me when I say balance changes are not made lightly. A lot of thought and effort goes into each and every one.
:lol: Anyway something that might be a bit more feasible would be to have juice earned being able to be set to slower gain -> slower consumption or faster gain -> faster consumption. Juice bought should always burn out quickly. Maybe have the boosts for the slower ending juice to be slightly lesser and the faster ending have a slightly larger boost (excluding from juice vendors). Perhaps at the very least this could be a concept to consider for future releases if not for this installment.