|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Yorda
Battlestars GoonSwarm
|
Posted - 2008.05.22 15:38:00 -
[1]
Edited by: Yorda on 22/05/2008 15:42:49
Originally by: Papa Ina Well the motion to discuss has one reps backing. Let's pretend to have meaningful discussion about it for 7 days. Seriously, is there anybody that can make an argument against it?
There is no argument against it, but with a relatively small time frame to offline / online a jammer alliances could simply take the jammer offline, jump capitals in, and online the jammer and the effect would be the same. The real question is, if cynojammers where intended to support non-capital combat why does the jammer have no effect on the capitals in the system, just their ability to enter said system?
Originally by: nlewis jammers are the meatshield [Bob] wish their pets were
|
Yorda
Battlestars GoonSwarm
|
Posted - 2008.05.22 15:56:00 -
[2]
Originally by: Siona Windweaver Edited by: Siona Windweaver on 22/05/2008 15:52:01 While It's certainly intresting to think cyno jammers as double edged swords, i don't support this issue.
If you think about it in character, you should have some info (such as cyno jammer frequencies or something) about your systems, its your alliance space afterall. Deploying capitals in YOUR space is logical both in gameplay and RP view.
Edit: Goons started to make threads to fit their needs i see, with multiple account posting/supporting and all that...
Clearly a module that creates a cyno between two points should work next to a module that prevents cynos from being made. This makes perfect RP sense.
Originally by: nlewis jammers are the meatshield [Bob] wish their pets were
|
Yorda
Battlestars GoonSwarm
|
Posted - 2008.05.23 12:59:00 -
[3]
Originally by: Lord WarATron The key point is that in the past, people would reinforce whole regions of POS hoping to catch a incorrectly timed one then run away. The defenders would repair in their prime. This made capital fights a joke since there was nothing forcing people to use capitals against each other and forced weeks of alarm clock ops to take over systems that people would defend. And if the Smaller alliace defended one system in a alarm clock op, the attackers would attack another system since there was nothing forcing them to commit capitals.
This is why people called for a cynojammer. A Module that would force the attacker to commit capitals insted of playing risk free hopscotch with POS wars.
Now with Cynojammers, the attackers cannot cyno 50jumps away and dock up safely, they have to stay in system and lock it down for a couple of days otherwise the defenders will repair the jammer and get back in again. If the Defenders want to use caps/supercaps to defend their pos, then the agressors will have no choice but to use capitals for epic capital fights or risk doomsday.
This is good for the smaller alliances since they can take over systems in a couple of days insted of months of POS alarm clock wars which only larger alliances are good at doing. Problem has never been Cynojammers, its been people who used the old tactic of risk free dreadnaughts who are unhappy that they have to risk their capitals now. After all, its a seige and ships will be lost on both sides. It is not some lvl4 where you can rambo without loss.
As I said in the other thread where you posted this analogy, there is absolutely nothing that cynojammers do to stop people from alarmclocking ops and continue doing this. Just because they have to stay in system doesn't mean they cant log out and it doesn't mean they could just cyno out and take down the jammer at a later time. Cynojammers dont force people to commit to capital ships at all, if you want to defend or kill a pos you have to fight when it comes out of reinforced. Cynojamemr or not if there's caps to defend it and caps to attack it they'll be a cap fight cynojammer or not.
tl;dr you're ******** stop posting.
Originally by: nlewis jammers are the meatshield [Bob] wish their pets were
|
Yorda
Battlestars
|
Posted - 2008.05.28 13:24:00 -
[4]
Originally by: Lord WarATron Edited by: Lord WarATron on 28/05/2008 11:38:58
Originally by: Draygo Korvan
But now how does a smaller alliance take a cynojammed system in the first place when it requires a few hundred battleships if the pos is manned?
The Brige is the only thing giving Smaller alliances a chance. E.G
Large alliance vs Large Alliance Large Alliance kills cynojammer in 3-5 minutes and keeps capitals in system untill Sov Drops. Using a bridge or not makes no difference since jammer will be down far too quickly to matter.
Small alliance vs Large Alliance Small Alliance kills cynojammer in 10-15 minutes and keeps capitals in system untill Sov Drops. Using a bridge or not makes no difference since jammer will be down until sov drops
Large Alliance vs Small Alliance Large Alliance kills cynojammer in 3-5 minutes and keeps capitals in system untill Sov Drops. Using a bridge or not makes no difference since jammer will be down far too quickly to matter.
Cowardly Alliance vs Small Alliance
Cowardly alliance does not want to risk dreads so attacks Jammer. Jammer will be down in 3-5 minutes then the cowardly alliance removes all capitals out of harms way after reinforcing all pos. The Small alliance can put the jammer back up and bring capitals in via bridge to defend against the large alliance attack to remove pos's when they leave reinforced.
Point
The point is simple. The bridge ability does not effect Large alliances at all since Jammer is down in 3-5 mins making any benifit of bridges useless. It only effects the "Risk Free Capital" alliances using cowardly tactics and only harms the Small Alliances who try to defend against the cowardly alliances.
I knew BoB had lowered there application requirements, but goddamn that has to be one of the most ******** things I've ever read (and I read GF.com often).
The smaller alliances will never stand a chance against a bigger (even cowardly) alliance. They'll just be outnumbered / outspent and lose horribly. Not to mention they actually have to hold the system for the 30 whatever days it takes to get sov 3.
|
|
|
|