CTF Tweak Update

Umm...Quick Fix-it Thread. What?

 

Yes, but don't you think it would be a lot more ideal if the planned changes were posted in a separate thread for more visibility before being implemented?

 

3.5 seconds on the bow is wayyyy too short. It's a bow for a reason, by the time a randee heavy gets to me the fire is out and I get rekt...
Edit: pyro is essentially broken now, no way to light the enemy on fire without dying; the flint and steel doesn't light 90% of the time.

 

I did forget about that, but I also would state what iMuffles stated: a more clear view of what is being updated. Also, there were a few things not on that list that were implemented yesterday (medics sword having no sharp instead of sharp 1 for example), so my claim is somewhat true. I do stand corrected however, and that is my fault for forgetting about that post.

 

I agree with this, seems much more sensible to me. The solution right now is a bit of a pain

 

There are a couple of bugs with this update. One of them is practically game breaking.

1. When being healed by a medic, if the medic continues to hit you with their sword, it acts like you're rapidly taking damage, resulting in a humorous, earthquake-like, effect.

2. OK, this one is insane. It's possible for dwarves to go past level 10. When they do, the levels start rapidly climbing, resulting in a truly OP dwarf that instakills everything. Plus, if they standup and/or sword-block and their level is in the 100s, they won't have to crouch for the rest of the match.

@NomNuggetNom

 

1. Imo the damage output was still insanely high. Too high. Probably still is. Dont get the 30 seconds fire res tho.
2. Don't get this either.
3. Agreed xdd The fire nerf now gives you 3.5 seconds to kill them. Which aint enough time, especially if they steak. Makes pyro a lot more reliable on frenzy.
4. other ppl have said about quarr's post cx

We wanted changes, we got changes, we probably could have specified some more stuff xdd

 

I dont remember you saying it first, I've been saying this when i got back from my break. If this is true then I am sorry for trying to make that idea my own, guess we agree on the same thing.

I think 15 health is great for engineer because lets just be happy engineer got nerfed again. Lets see if this made any difference before we want more nerfs okay?

 

I couldnt even damage a turret of the opposite team, +1 for nerf

 

Okay, +1 for a nerf.

Now onto the update

https://www.brawl.com/threads/57950/page-4#post-733450 Okay so lets check what was on the quick fix it thread and what the staff nerfed because they could.

Archer is on the list for the punch 2 nerf to punch 1.

Chemists pots are exactly how they are in the quick fix it thread, so its only you guys to blame there. The staff listened there

Dwarf level 10 cap and fire and chemist pot immunity is at lvl 10 is a thing. They listened there.

Elf is just as people wanted it. @GalaThundR is dancing with joy atm.

Engineer turret has less health. They listened here.

Medic webs can actually be broken by the enemy team now. Medics heal overrides chemists and engineers heal. Okay there

Pyro has everything from the quick fix it thread. If you wanted different then you should of said something or argue for your idea.

The only thing I see that isnt on the quick fix it thread was medics sharpness nerf.

Why did they nerf that of everything about medic? Why not make it unable to heal other medics for 30 seconds to a minute. Medic teaming was and still is the issue about medic as well as its healthpool.

The staff listened to our ideas now we are complaining about what we put. This is most likely why the staff dont listen to us most of the time guys. Be happy anything happened.

Yes I would of liked ninja nerfed and soldier nerfed, but seriously guys. Be happy anything happened at all.

Good job staff on 99% listening to us, sorry that most of us couldnt be as thankful that you did anything at all.

 

Okay, I said this before what im saying now. I also said this before the quick fix it update. I can admit it when im wrong sometimes. This is one of the times im wrong. Anywho, I do agree medic didnt need its sharpness removed.

 

You know, if ya'll need to let out some steam caused by the update, there's about 6 quadrillion (may be slightly overexaggerating) more servers in Minecraft. And if that's not enough for you, there's still a few billion other games out on the internet, and even then, there's still other stuff to do that doesn't involve video games, like youtube, paint.net or having a life. Just saying ^_^

 

Nom did around 20+ changes in about 20 minutes (all together) of coding time. The majority of time spent on this was our discussion and testing phase. I'm mentioning this to remind everyone for the hundredth time that these are simple fixes. Now that they've been played and tested, it isn't hard to revert, edit or change any of these. That was the biggest thing I tried to stress when communicating about this update (@ningeek212, slightly offended), but I figured that wouldn't have been listened too.

Yes the medic sharpness was a last second discuss because we wanted to see what it would be like. If we don't like it, then we'll probably go to plan b, which was nerfing their health pool - if you'd rather have that.

As for the chemist change, yes, it will change how matches work - you know why? Because how chemist is used in matches and in regular servers is ridiculous. 3/4 of the team buff their teammates than switch classes. It's like we should just add speed, strength and fire resistance to every single class - it was enough time to get there and back without another douse. It probably won't change too much, but maybe now support will be used during the game instead of just at the beginning of each run.

Also guys, like I mentioned, nom said it took him an hour to code/test/discuss all of this. Instead of always be sarcastic with everything, why don't you try living a little, opening up and being just regular constructive. These things are EASY to change.

 

why would you take an hour to make an update with several flaws and bugs when it would only take just another hour to have seen "I think the dwarf level cap isn't working!!!" when you make updates with constant flaws and expect everyone to say "Oh it's okay shucks we just need to wait for them to fix mistakes that should have never been in the game" do you really think you won't get any negative feedback?

 

health pool armor wise, steak wise, or actual health bar wise

 

This is what I'm talking about @Skarm. I don't care if someone gives me negative feedback but do really think this is a necessary comment? Even when Nom didn't suggest this change and it was mostly from people complaining about accidentally activating frenzy?

Also do you really think an update will be pushed with no bugs? We can't test literally everything on a private server. The first day should be expected to have something mess up, the code is being changed. My message wasn't even about bugs, it was about the feedback on the concept themselves. Obviously people can be upset about bugs, obviously there will be bugs and obviously they will get fixed - that wasn't the point of what I was trying to say. I did openly invite feedback at the end, unless you just felt like posting and not reading what I had to say.

@Daniellll, I don't know. We'd probably try one way and see how it works than if we need to, try another way.

 

yes i do think it's needed. when you push constant buggy updates is this just "Oh man first day darn unlucky!!! (" or is there something to say about the quality of work you are making. Making an update in an hour isn't something to be proud of if it has quality of creeper2007x's faction server update. there doesn't have to be bugs like this if you just took a beta test server for larger range of testing, or spent more time testing it among yourselves, but making update after update with this quality really shows how much attention you put into it.

 

Again, I never said anything against bugs - you're still missing my point. But it doesn't look like you're going to read that part so I'll just keep it myself.

 

my mistake! ignoring the problem is the best!