Worlds CollideBob Shaftoes
Worlds Collide commentator and Camel Empire member Bob Shaftoes takes us through this exciting event and offers insight to the rules, setups, strategies and matches themselves. Enjoy! – NidenUnless you’ve been living under a rock for the past few months, you will likely have heard of Worlds Collide, an E-sports event hosted and heavily promoted by CCP to be the headline event for Fanfest 2015. CCP significantly raised the stakes for this tournament by offering a special edition ship as a prize for the event, the Victorieux Luxury Yacht. But instead of merely awarding the prize ship to the members of the winning team, as in CCPs flagship E-sports event The Alliance Tournament, CCP awarded the prize ship to the server of the winning team with a statement that the losing server would never receive the ship. The yacht itself is a fantastic addition to the ship roster in EVE. It’s a cloaky, bubble-proof cruiser hull with a fast align time and a 1/3/3 slot layout. There is nothing like it presently in game outside of a cloaky nullified Tech III cruiser. So which alliances were chosen to represent the two Eve Online server shards?
The Camel Empire—TranquillityCamel was chosen to represent Tranquility after winning the Twelfth Alliance Tournament. They are prolific small gang PvP:ers and tournament pilots having flown in ATXII, NEOII, and ATXI. What is most surprising about Camel, is that they started as tournament nobodies that few had heard of, and rapidly ascended to come second in NEOII (as Thingy) and winning ATXII last year. The Camel roster is as follows : Niart Gunn—Team Captain Eshnala Sturm Gewehr F4bske Water Ubersnol You can find out more about Camel in Apothne’s interview with them here.
City of Angels—SerenityCOA is a sov holding alliance on Serenity, holding both Catch and Providence presently. They have origins as a pirate roaming alliance, and eventually grew into a large player on the Serenity influence map. They were chosen to represent their server after winning the third Serenity equivalent of the Alliance Tournament. The COA roster is as follows: Stepnick—Team captain Bitter Tanis Jed Ask The Serenity roster names are actually nicknames, as it is really tough for people outside of China to read and pronounce the Mandarin characters. There is a pretty cool video from the live event with English translations of COA’s real character names here
The FormatOutside of the unique server vs. server fight, Worlds Collide was interesting for a number of reasons. Instead of using the regular Alliance tournament format, CCP came up with something special and produced an extremely intriguing set of rules that spiced up the fights somewhat, which increased hype about the event. In a normal alliance tournament, a team can have as many setups as they want. They are also free to modify them as they wish between matches, and consequently they have no idea what the enemy team is going to field. Additionally, AT allowed you to use whatever ships you wanted as long as the point value of a ship was within the prescribed limit, and you had three at the most of them in a setup. In WC, all of your cards are on the table. After the rules were announced, teams had about two to three weeks to come up with seven setups to use during the tournament. Added to this was the fact that within your seven setups, you could only use a ship hull twice. Once you had used that particular ship, you could not use it within any other setup in the tournament. Normal AT ship banning was not present in Worlds Collide at all—instead being replaced with a setup banning mechanic. Out of the seven setups, teams had to submit two, which could be banned in advance, and could not be fielded at all during the tournament. Also, if a team won a match with a setup, that setup would also be banned and could not be used for the rest of the best-of-five format. The final deviation that WC had from the AT rule set was to outright ban Tech II, faction drones and marauders from being fielded by either team. The drone restriction meant that all ships could only use Tech I damage, logistic or EWAR drones So all these rule changes had some really interesting ramifications on theorycrafting for both teams. The AT meta of the last few years has been heavily focused on drones or drone counter setups. With Tech II drones and Geckos banned, these setups were significantly weakened as Tech I drones are slower,have less hitpoints and do less damage overall. There are only really a few completely broken drone ships in a tournament context, and having a rule that you cannot use the same ship in multiple setups means that you are extremely limited in your choices for your overall setup pool if you want to pursue a drone heavy team. In fact, these rules had interesting ramifications for “overpowered” ships in general, as you had to spread them out within the seven setups or risk them being banned by the enemy team. In addition to this, you still needed to keep a strong pool of setups because as you win matches your pool shrinks one by one. For the final match of the tournament, out of the seven setups they theorycrafted, Camel could only choose from three setups. So what did the teams actually come up with after these fairly stringent rules?
The SetupsCamel Setups: Setup #1: Rook, Basilisk, Caracal, Caracal, Celestis (BANNED) Setup #2: Widow, Scimitar, Flycatcher, Flycatcher, Keres (BANNED) Setup #3: Eos, Ishtar, Ishtar, Navitas, Navitas Setup #4: Sleipnir, Broadsword, Curse, Burst, Burst Setup #5: Astarte, Phobos, Exequror, Heretic, Heretic Setup #6: Damnation, Oneiros, Confessor, Confessor, Maulus Setup #7: Absolution, Guardian, Sentinel, Blackbird, Ishkur COA Setups : Setup #1: Orthrus, Orthrus, Confessor, Crow, Vagabond Setup #2: Gila, Gila, Worm, Worm, Scimitar (BANNED) Setup #3: Widow, Widow, Daredevil, Daredevil, Taranis Setup #4: Ares, Typhoon Fleet Issue, Typhoon Fleet Issue, Merlin, Merlin Setup #5: Oneiros, Enyo, Enyo, Vigilant, Vigilant (BANNED) Setup #6: Stiletto, Rifter, Hyperion, Hyperion, Caracal Setup #7: Keres, Cynabal, Cerberus, Cerberus, Malediction Both of these setup pools show quite differing philosophies when it came to the challenge of theorycrafting for Worlds Collide. Camel are very well known for bringing lots of damps in a tournament context, and do not disappoint here. With two low damage setups consisting of bonused damps, ecm and logistics, Camel aimed for a control meta to shut down the enemy team, and slowly chew through their ships while tanking any incoming damage that isn’t countered by the damps or ECM. The Eos and Ishtar setup was a more traditional drone kiting comp that simply aimed to damage its way through the opposition, while trying to mitigate as much damage as possible via the Navitases and damps. The Sleipnir-Broadsword setup is a strong brawling comp with a Curse to shut down the enemy tank, and logistics frigates to increase survivability. The Astarte setup is a long range light missile and railgun platform with lots of unbonused damps to shut down the enemy team. It also played the metagame a bit as from first impressions it looked like a close range blaster setup, proving that even though both teams have a list of the others setups, that doesn’t mean you are going to get what you expect! The Confessor setup is a long range damage comp that utilises the flexibility brought in by the new Tech III destroyers. The final Camel comp is a bit of an oddball with a mix of neuts, ECM, and a beam Absolution for damage. COA brought a very interesting and unique pool of setups compared with Camel. In most alliance tournaments, people eventually come to the same general conclusion of what is strong and not strong within the context of the tournament. But COA were a wildcard coming from a completely different server, different culture, and a different way of thinking; the following setups reflect that. The first and seventh setups are very similar in that they are rapid light missile launcher ASB tanked kiting teams with a Minmatar cruiser for heavy tackle and frigate support. The Cerb setup is slightly stronger than the Orthrus setup due to having the Keres present, but it looks as if both ships had similar roles. The second COA setup was a Gila/Worm drone damage comp similar to what a wide range of teams fielded in ATXII. The Widow setup was a strong ECM team with a high damage frigate wing. Talking with COA after the tournament, it was discovered this setup was ban bait alongside the Gila setup, and was never intended to be flown at all. Setup #4 is arguably COAs strongest, two very mobile hull tanked Navy Typhoons with lots of neuting power and Rapid Heavy Missile Launchers for projection and frigates for tackle. Setups five and six were similar; they were both blaster rushes, but the Vigilant/Enyo comp relied on its logstics ship for reps, while the Hyperions in setup six had large active tanks and could take care of themselves. Overall, COA showed a bias towards having either large buffer or active tanks in their comps combined with lots of damage, and very little control outside of the Widow comp. Both teams had a fairly simple banning strategy that they revealed after the event. Camel banned both the COA comps that contained logistics ships meaning they simply would not have to deal with reps anymore. COA banned both of the Camel ECM comps, as one of them was only a 44 point setup. They felt that if Camel was willing to bring 2 similar setups, one of which was under points, then they needed to ban that concept entirely.
The EventThe Worlds Collide tournament took place during Fanfest on the Eldborg stage inside the Harpa in Reykjavik. If you missed the whole thing, you can watch it here. In terms of production, it was one of the coolest things I have ever been a part of. CCP Gargant and the rest of the dev team put in an incredible amount of effort and resources into making the production a success; barring a few technical difficulties and delays, the whole thing went pretty well. Rising up out of the smoke with the trinity music blaring in the background to a room with 1500 people was one of the scariest/most awesome things I have ever done as I was honoured to be included in the event. Anyway, enough about me, onto the matches.
The First Match
Camel : Eos, Ishtar, Ishtar, Navitas, Navitas COA : Ares, Typhoon Fleet Issue, Typhoon Fleet Issue, Merlin, Merlin For the first match, Camel brought out their kiting drones setup while COA brought the brawling hull tanked Typhoon Fleet Issue setup which was arguably their strongest one. Camel dropped drones and tried to kill the COA support frigates while staying away from the Typhoons. Initially, it was going fairly well and two Merlins were dropped without any losses on the Camel side. But out of nowhere one of the Typhoons initiated a manoeuvre referred to as an “MJD Noscope.” The Typhoon maintained a lock on the Ishtar, and got to within 100k range of it. He then aligned his ship towards the Ishtar, hit his Micro Jump Drive and landed within 5k, instantly neuting, scrambling and webbing him, leaving Eshnala’s Ishtar with no hope of escape. The tide started to turn in the match from that point onwards, with Camel trying to kill the Ares and eventually popping it while staying away from the Typhoons. The Eos was eventually caught and killed along with the Navitases, and with that gone the Ishtar lost his links. He too was run down and dispatched by the Typhoon Fleet Issues leading to a COA victory. 0-1
The Second Match
Camel : Eos, Ishtar, Ishtar, Navitas, Navitas COA : Keres, Cynabal, Cerberus, Cerberus, Malediction Camel did something fairly ballsy here and brought the same setup that they did in the first match whereas COA went over to their slightly stronger RLML setup with two Cerbs as the core. Camel primaried a Cerb right away with their drones receiving very little reciprocal damage from COA. The first Cerb died to drones while COA tried to apply damage to one of Camel’s Navitas with little success. Once the second Cerb died, it was essentially over for COA. With most of their damage gone, the rest of the ships were easily killed by Camel’s drones in short order. 1-1
The Third Match
Camel : Damnation, Oneiros, Confessor, Confessor, Maulus COA : Keres, Cynabal, Cerberus, Cerberus, Malediction COA brought back their Cerbs for this match, while Camel switched to their kiting Confessor comp. This was one of the most tense matches of the series with both sides having a good chance of winning it at various points. Camel started by damping the Cerbs and killed the Malediction with their Confessors’ long range ammo. COA responded in kind by brawling a Confessor with their Cerbs until the damps could no longer apply, and essentially volleyed it off the field before the Camel logistics ship could apply reps. The Camel Maulus was also quickly killed through reps, which meant the Cerbs were mostly free to apply their damage for the rest of the match. In brawling however, both the Cerbs had gotten tackled by the Damnation and the remaining Confessor, meaning they could no longer kite. Both Cerbs decided at this point to shoot the Oneiros, while the Damnation and Confessor shot at one of the Cerbs. Shooting at the logistics ship is the mistake that likely cost COA the match as it was dual rep fit and could trivially tank them, while the Cerbs were burning both light missiles and ASB charges attempting to kill something they could not possibly break. Eventually one Cerb went down, closely followed by the next Cerb. After that, it was just clean up of the Cynabal and the Keres for Camel. 2-1
The Fourth Match
Camel : Astarte, Phobos, Exequror, Heretic, Heretic COA : Stiletto, Rifter, Hyperion, Hyperion, Caracal The fourth match in the series was one that COA needed to win otherwise they would be out of the competition. Equally, Camel needed to win this one to take the whole series. Camel brought arguably their strongest setup with a lot of long range railgun damage and damps. COA brought their Hyperion setup having correctly hypothesized that Camel would take the Astarte setup. In theory, the Hyperions should be able to beat the Astarte/Phobos in a brawl if both were blaster fit, but since they were rail fit, COA ended up having a very bad time. Camel started the match by primarying one of the COA Hyperions to see if they could break him. Camel stuck as a group during this, with COA trying to charge in with the battleships to try and tackle something. The Hyperion bait tanked for a bit, and then held with the Camel team receiving no damage in reply. Both frigates on the COA side tried to approach the Camel formation with an eye to try and tackle something for the Hyperions, but were volleyed by the railguns and light missile launchers on the Camel team. With the frigates dead, Camel went to work on the first Hyperion forcing it out of the arena. With the Hyperion over the boundary and destroyed, Camel finished off the Caracal and the last Hyperion to take the last match of the series. 3-1 Camel Wins!