"No Potspam" "No Ghosting" "x Number of Class Only"

Yes, let's put engineer in official matches while we're at it!

 

Try it for yourself, these matches have been around since Mcpvp and their are quite a good amounts of reasons these limits are in effect. To put it to perspective, imagine everyone going medic or engineer, don't you see the chaos?

Also, reworks are not the cause to MOST of these issues. If you have an idea about a rework of any of the classes, put it on a thread and see the feedback you will get by the community. I'm not saying what you said is DUMB, but this has been around for a while and trust me, they know what they are doing.

 

His point is more that the classes are still broken then that the restrictions should be removed.

Which, to be honest, is not exactly an original opinion. We all know CTF is garbage, but you guys still play it, even though you have to specifically set restrictions on some classes.

Jeez.

 

Well ghosting allowed wouldnt do me anything ^^

 

There IS a reason why engineer and necro are banned, and why there's a limit to medics and pyros. Now don't get me wrong, I have no idea what the actual reason is, but I believe it's because nobody wants to tie 3 times in a row. It would be much harder to cap without these limits, and most people are on a time schedule and want to get the matches done fast so they aren't chewing up other teams time. (Although I have no clue why there are no necros, seeing how it's still useless atm)

 

Engineer only helps by getting free kills and cutting some time it takes players to get to one side of the map (which is chaotic when they'res tons of them). Therefore, in my opinion, it shouldn't have ever been introduced to this gamemode.

 

Dear lord I thought the sarcasm was implied.

 

Idc if all of these responses are relevant to your argument, but I want to address every point you bothered to bring up.

No match is official without rules.

Because some classes are broken and unfair as heck, and I'm aware that you've already argued this.

Yes.

Precisely.

Many wish that CTF can just change already, but until such time, we shall wait. Also while we wait, enforce certain rules in special matches so that organized games can actually be competitive and fun instead of too ridiculously unbalanced.

As a matter of fact all forms of spam are forbidden: potions, archer arrows, mage damage (at least a constant stream aimed at the flag), and medic webs. I'm not totally sure about elf (particularly earth element), but I don't see why not.

If official matches had ghosting, all teams would have disbanded by now due to pure rage.

No. But wall-spam is actually a sort of strategy when playing soldier. And anyway, the skilled archers who participate in official matches are the ones who deal with wall-climbing soldiers.

Plugin restrictions are usually in place in official matches. Otherwise, the referees are fantastic at their jobs for the most part.

You're not the only one crying out for this change. It'll be done ASAP (as in, when CTF gets a dedicated coder again).

Indeed.

I actually think Brawl is more willing to do so than MCPVP according to what I've seen from the discussion of MCPVP veterans (I myself have played MCPVP-CTF for a long time but remained ignorant to the community and administration).

Now, about broken classes. I'll address this in a very short manner because this thread has inspired me to make a new thread which will share my views on the following idea: CTF is designed for small games. That's why official matches don't involve the entire team playing--things are more manageable and organized when fewer archers are raining arrows, fewer chemists are buffing others and tossing damage potions, fewer pyros are defending the flag, etc.

 

> looks at update log

ha

ha

ha

 

I personally dislike having to limit classes for matches, although currently it is necessary.

 

Everybody who's arguing about whether or not classes should be banned / restricted are missing literally the entire point of this thread.

Did anyone actually read his post? Or the one he posted after it?

It's not at all about whether or not classes should or should not be limited, it's a request to fix the classes.

 

yeh, but any kind of English teacher would say he could have made that point more clear in his argument.

 

Ahem.

 

Excuse me, are you dissing engineer?

As a professional freeday engineer main, I am startled by your lack of knowledge. To play engineer effectively, you need to be extremely intellectual and strategic, and you must know all the ins and outs of every map. You must also know how to effectively counter classes that try to attack your engi nest.

With the nerf that hit engi a while ago, the most popular engi tactic was made obsolete: AFKing. Now, the amount of effective, objectively playing engineers are limited to a select, skilful few.

An engineer turreNt is useless if you don't know the map well. It needs to be placed in a key location so that teammates would want to teleport in, with enough enemies walking through that your turreNt affects the enemy offence significantly. Of course, I don't expect every new player to know how to find the ideal engi nest spot, as it requires finding the middle of a map, and counting other players.

Another thing you have to be mindful of is headshots. Archers will always try to shoot you, and if you are stationary or too close to your turreNt, you will get headshotted and lose your hard-earned 23 killstreak. You need to develop strategies to counter this cheap insta-kill method of killing you, such as pressing "W", "A", "S" or "D" in a random order to counter the spray-n-pray, or hiding behind an object.

You also have to be mindful of your turreNt's health and wellbeing. Engineer was nerfed really hard last update, and now you have to make sure you repair your turreNt. You can no longer hide and let your turreNt do all the work: you must now actively pop out of your hiding spot for all of two seconds and repair the turreNt. This leaves you horrifyingly vulnerable to enemy attackers, which brings me to my next point.

Enemies will always target your engi nest: most notably the noob instakill classes that require no skill. You must learn to effectively counter these enemies to ensure you survive. If an assassin is running at you, you must master the tactic of running backwards and blocking with your sword if they get too close. However, blocking also disables your turreNt: another massive disadvantage to the already easily-counterable class. Pyros can also break your turreNt with their axe or instakill you, so you must be able to spamclick your cake in order to survive the pyro fire, and have the patience to wait for someone else to teleport in to your engi nest as cannon fodder while you repair/rebuild your turreNt.

Occasionally, other classes will come in and try to attack you. If you have teammates around, it is important that you hide behind them and let them die before you do, or run around and spam click your cake while your turreNt deals big damage. You need to be very skilled, as engineer is a weak PVP class that can only hit an enemy 7-10 blocks back in a couple of hits with its pickaxe.

Finally, you must master the art of alternating between manual and automatic control. True master engineers use their manual control once in a while to demonstrate their dead-centre aim, but know to switch back to the automatic as soon as an enemy enters 1000 blocks of their turreNt.

All in all, you can see the sheer amount of skill and game theory that goes into playing engineer. Please consider these before making any further rash comments about the most skilled class in CTF.

Sincerely,
Engi mains of CTF Free Friday

 

His point was quite clear.

 

@BAWSS5 @Tysonyoshi

When making a more clear argument, it's usually nice to put it near the start so people know what the heck you're talking about before they bother reading the rest of whatever you wrote.

 

When criticizing somebody's argument, it's usually a good idea to read it first.

His point was very, very clear. He set up a problem which he discussed through the first half of the paragraph, and the second half is about what he suggests be done, where he says 'fix the classes' 3 times.

The only people who wouldn't understand this point are the people who got halfway through his paragraph and said 'k, replying now'

............

Which a lot of people did.

 

*ahem*... *straightens tie* I would say I'm one of the few who quite nearly always (in this case, I did) reads every word of a thread before responding. I presume you do the same, so I'll ask you to remember this:

Also, the only place where he directly asks for the classes to be fixed, although indeed made very clear, is the final three sentences of his paragraph. The rest was about class limitations in matches and their general brokenness. Anyway, I never really criticized his argument in any place in my first post on this thread, I merely responded with my own facts and opinions to every aspect of his post.