1. Welcome to the Brawl website! Feel free to look around our forums. Join our growing community by typing /register in-game!

Idea Archer rework & engineer balancing

Discussion in 'Capture the Flag' started by Mc_Simp, Mar 17, 2016.

?

What do you think?

  1. Great rework! Archer will finaly be balanced!

  2. Needs some work (Tell me how)

  3. No, I'm an archer main and I enjoy ruining games of ctf with ranged instant kills with no counter

Results are only viewable after voting.
Thread Status:
Please be aware that this thread is more than 30 days old. Do not post unless the topic can still be discussed. Read more...
  1. Mc_Simp

    Mc_Simp Member

    Joined:
    Aug 1, 2015
    Messages:
    32
    Ratings:
    +6
    Hello! A lot of people dislike these two classes. and I can agree, maybe I'd be the most salty. So I have a rework for both these classes. Well, at least for archer.

    Goals of my rework: Keep archer the one who does massive ranged damage. Keep engineer the counter to low armoured classes. A way to counter engineer

    So, let's start with the problems. Headshots and bow spam. At least headshots should go.
    I was told that brawl/mcpvp want to move away from insta-kills completely and I can say I agree.
    Well, my suggestion for headshots would be following suite of pyro. Just have true damage headshots. I have suggested this 3 months ago, but I didn't do a sound job at my rework then. Here's how it would work: After 15 blocks from player to the target 2 hearts of true damage would be dealt + the untrue damage of the bow shot itself, And every 5 blocks the damage would increase by 0.5 hearts up to a maximum of 6 hearts
    of true damage, I believe this would make archer the class still great for killing at a distance whilest making it less frustrating to get randomly hit from across the map by that one randy who shoots an arrow and hopes for it to hit.

    What does this have to do with engineer? Well, when engineer received the turret nerf the patch notes stated that 100 arrows would destroy a full health turret, Currently this was never added and I believe it should. Because for such a massive change to archer, it would have to have some role, am I right? I propose that archer should be the class to take out engineer turrets, Maybe 6 fully charged arrows could destroy a full health turret. so the engineer would have to constantly be checking on his/her turret to avoid it being taken down

    Now we move on to the other problem, bow spamming. This one is really optional because if headshots removed archer would be close to perfect by then (I assume) But in case it's not, the punch on the bow should be replaced by unbreaking 3 (because enchants are nice :smile: ) and the stone sword would gain knockback (I or II) Finaly, something completely weird. Projectile protection I helmet, because why not.

    Conclusion
    From all this, I want to say I do not hate archer. I like the idea of headshots. just not insta kills without any (reasonable) way to counter them. Plus, engineer gets a counter, so yay?

    I'd like to hear what you all think of this. Thanks!
    Oh one more thing, if you are an archer main, don't instantly say "TERRIBLE! THIS REWORK IS SO BAD"
    think of everyone who does not play archer and how THEY feel to get headshot from across the map with no means of countering it reasonably or even knowing you were there.

    I might make an engineer rework to, because I have had a lot more experience with it, and I think it should be more skill based. Let me know if you want me to try make one! :grinning:
     
    • Like Like x 2
Loading...
Similar Threads Forum Date
Archer Rework Suggestions / Ideas Nov 23, 2021
Idea Archer 2 op(Rework idea) Capture the Flag Jun 7, 2020
Idea Archer Rework: Marked for Death Capture the Flag Apr 21, 2020
Petition to rework archer Capture the Flag Nov 5, 2019
Idea Archer rework (mobility buff but hs nerf) Capture the Flag Sep 26, 2019
Thread Status:
Please be aware that this thread is more than 30 days old. Do not post unless the topic can still be discussed. Read more...