User:Breeze one/Sandbox: Difference between revisions

Line 124:

Please leave any feedback in teh fourms, or send me a private message. Hope you all enjouyed the session and hope to see you again!

[/Welcome to the Team!

Tournament Summary:

This is a 7v7 tournament, held under what are essentially the same rules as the recent Alliance Tournament event – the key difference being that this is 7v7, rather than 10v10

It will be held on the Thunderdome server – this is CCP’s Tournament server, where all our pilots will be given All V skills, and we can get hold of any ship for free

We will get 75 points which we can use to choose ships at the start of each round, with each ship class assigned a certain points value. There will be a “ban” system where each team gets to ban 3 ships which neither side can then field during the fight. The fits on each ship can be whatever you like, but can only use maximum T2 modules (no faction/deadspace modules)

The teams for this event cannot be the same teams as in the recent Alliance Tournament, however the organisers will allow up to 50% of a team to be pilots who have previously competed in the AT, and the alliances themselves are still free to enter – its only pilots themselves who are restricted. Some known groups from the recent Alliance Tournament are planning on entering this event

Full rules are here:

The Plan

There are essentially two aspects to this as a project:

• Research & Development

• Practice & Execution

I’ll post up separate threads to discuss both these aspects. You don’t have to get involved in research & development, but it’s strongly encouraged and I think we’ll learn a lot doing this

Teams:

We can submit a total of 21 pilots for access to the Thunderdome server for training. If you’re reading this message, then your names are on that list, but I’m also just leaving it open a few days to see if we get any more joining

Of this 21, we can choose any 7 to be the team for each match. My understanding is we can swap pilots between matches if we wish

While the Tournament itself is nicely timed between EUTZ and USTZ, our squad is currently heavily biased towards EUTZ pilots. That means EUTZ pilots are going to get most of the training time here, and I’m going to be blunt – they are very likely to be the first choices for the team, simply because they will have done the majority of the training together. Sadly, USTZ pilots need to be aware of this going in. I would love to have two teams, one in each timezone, but that’s not how this is shaping up unfortunately

USTZ pilots who are interested though are very, very welcome, and encouraged to join in the R&D exercise, and to join whatever practices they can (probably on the weekends). As we move towards the event, it’s likely we will have drop-outs for various reasons, and you guys will be first call for that. Also, to be honest, just practicing for this is probably going to be a massive learning experience for all of us

Communication:

• This forum is for our personal use – please use it!

• I’ll be setting up a Team Slack

• I’ll also set up an in-game channel for discussion

Home truths folks. The chances of us, in the next 2 months, with our complete lack of experience and background, coming up with a devastating counterplay within the Alliance Tournament rule set which no-one from the big AT veteran teams has thought of is close to zero

We are starting so far back in knowledge and experience that we do not have time to waste building experimental doctrines from scratch

Instead, I want us to focus on understanding, adapting and practicing already proven strategies

If, after that we start experimenting then great, but let’s start out with mastering the basics

Below, I’ve noted down the commonly agreed “meta” from the recent Alliance Tournament. These are fleet compositions which were commonly used, with greater or lesser success, in the recent AT, under roughly the same rules as this tournament. The best theorycrafters in Eve designed these setups to be optimal under the current rules. Let’s take advantage of the work they’ve done for us

• Rush (Gallente & Minmatar variants)

• Headshot

• Drone Kite

• ECM-heavy (“Control”)

• Battleship Core

• Battlecruiser Core

• Octodad

(Yes, there’s probably some overlap between a lot of those – but let’s start with this and see where we get to)

I would like please volunteers to look at each one of these compositions with the following considerations:

• Design Principle – what is the composition trying to do?

• Strengths

• Weaknesses

• Variations

• Proposals to adapt the same design principle to a 7v7 format

Ideally, I’d want a separate discussion thread on the forum for each of the “meta” compositions above

Volunteers step forward please!

Tips on how to do this:

• Read/listen to the various reviews of the AT published

• Identify matches where people claim this meta composition was used

• Watch those matches (most are on Youtube). Watch them again

• Use Z-Kill to find the fits of the ships which died, and look at how they are fitted

• Watch the match again

• Start writing down

/]

@@ Line 124: / Line 124: @@
 Please leave any feedback in teh fourms, or send me a private message. Hope you all enjouyed the session and hope to see you again!
+[/Welcome to the Team!
+Tournament Summary:
+This is a 7v7 tournament, held under what are essentially the same rules as the recent Alliance Tournament event – the key difference being that this is 7v7, rather than 10v10
+It will be held on the Thunderdome server – this is CCP’s Tournament server, where all our pilots will be given All V skills, and we can get hold of any ship for free
+We will get 75 points which we can use to choose ships at the start of each round, with each ship class assigned a certain points value. There will be a “ban” system where each team gets to ban 3 ships which neither side can then field during the fight. The fits on each ship can be whatever you like, but can only use maximum T2 modules (no faction/deadspace modules)
+The teams for this event cannot be the same teams as in the recent Alliance Tournament, however the organisers will allow up to 50% of a team to be pilots who have previously competed in the AT, and the alliances themselves are still free to enter – its only pilots themselves who are restricted. Some known groups from the recent Alliance Tournament are planning on entering this event
+Full rules are here:
+The Plan
+There are essentially two aspects to this as a project:
+•	Research & Development
+•	Practice & Execution
+I’ll post up separate threads to discuss both these aspects. You don’t have to get involved in research & development, but it’s strongly encouraged and I think we’ll learn a lot doing this
+Teams:
+We can submit a total of 21 pilots for access to the Thunderdome server for training. If you’re reading this message, then your names are on that list, but I’m also just leaving it open a few days to see if we get any more joining
+Of this 21, we can choose any 7 to be the team for each match. My understanding is we can swap pilots between matches if we wish
+While the Tournament itself is nicely timed between EUTZ and USTZ, our squad is currently heavily biased towards EUTZ pilots. That means EUTZ pilots are going to get most of the training time here, and I’m going to be blunt – they are very likely to be the first choices for the team, simply because they will have done the majority of the training together. Sadly, USTZ pilots need to be aware of this going in. I would love to have two teams, one in each timezone, but that’s not how this is shaping up unfortunately
+USTZ pilots who are interested though are very, very welcome, and encouraged to join in the R&D exercise, and to join whatever practices they can (probably on the weekends). As we move towards the event, it’s likely we will have drop-outs for various reasons, and you guys will be first call for that. Also, to be honest, just practicing for this is probably going to be a massive learning experience for all of us
+Communication:
+•	This forum is for our personal use – please use it!
+•	I’ll be setting up a Team Slack
+•	I’ll also set up an in-game channel for discussion
+Home truths folks. The chances of us, in the next 2 months, with our complete lack of experience and background, coming up with a devastating counterplay within the Alliance Tournament rule set which no-one from the big AT veteran teams has thought of is close to zero
+We are starting so far back in knowledge and experience that we do not have time to waste building experimental doctrines from scratch
+Instead, I want us to focus on understanding, adapting and practicing already proven strategies
+If, after that we start experimenting then great, but let’s start out with mastering the basics
+Below, I’ve noted down the commonly agreed “meta” from the recent Alliance Tournament. These are fleet compositions which were commonly used, with greater or lesser success, in the recent AT, under roughly the same rules as this tournament. The best theorycrafters in Eve designed these setups to be optimal under the current rules. Let’s take advantage of the work they’ve done for us
+•	Rush (Gallente & Minmatar variants)
+•	Headshot
+•	Drone Kite
+•	ECM-heavy (“Control”)
+•	Battleship Core
+•	Battlecruiser Core
+•	Octodad
+(Yes, there’s probably some overlap between a lot of those – but let’s start with this and see where we get to)
+I would like please volunteers to look at each one of these compositions with the following considerations:
+•	Design Principle – what is the composition trying to do?
+•	Strengths
+•	Weaknesses
+•	Variations
+•	Proposals to adapt the same design principle to a 7v7 format
+Ideally, I’d want a separate discussion thread on the forum for each of the “meta” compositions above
+Volunteers step forward please!
+Tips on how to do this:
+•	Read/listen to the various reviews of the AT published
+•	Identify matches where people claim this meta composition was used
+•	Watch those matches (most are on Youtube). Watch them again
+•	Use Z-Kill to find the fits of the ships which died, and look at how they are fitted
+•	Watch the match again
+•	Start writing down
+/]