Formation Spreadsheet

When I started playing this game, I made this little spreadsheet to help me decide which formation I would use for matches:

Attachment 72402

Basically, I enter the formation of my opponent by placing a 1 where there is a player. Then I place my players. Below, it will show which team has better coverage on each block. The numbers inbetween are just indicators of how many defenders/midfielders/attackers that I have vs my opponent.

Previously, I could enter the individual player quality on the right side. I removed that for now since I didn't find it useful (It can easily be added back by changing the ACOUNT to SUM in the formulas.

I've been experimenting with the spreadsheet suggesting suitable tactics. They're probably all messed up but it's a work in progress. Use at your own risk.

No, it doesn't guarantee anything, and I make no claims for it. It only helps me visualize the strength of the formations and I figured someone here may find it useful.


I created a throwaway Google account to upload the spreadsheet to incase you just want to try it. Just remember that anyone can edit this one. I recommend you copy it to your own google sheet account and use from there.

Formation Spreadsheet

Interesting :)
It's good for me that I spend only 2-3 min to set my team for the next game.
Of course setting the formation is only the half job.

I got an error while opening the .xml =(.
"This XML file does not appear to have any style information associated with it".
Anyone have an idea on how to solve it?
Thanks!!

Not XML...xls. Excel spread sheet

I created a throwaway Google account to upload the spreadsheet to incase you just want to try it. Just remember that anyone can edit this one.

https://docs.google.com/spreadsheets...it?usp=sharing

I find it a fantastic idea. Will give it a try.

This is sooo clever, I can't believe i didn't think of this myself. ;)

Edit: The excel attachment didnt work, i used the Gdocs file

I'll work on this and make some adjustments (some of your calculations are misplaced IMHO).
When I'm done with the corrections I'll share it with you.

Already working on something:

Attachment 63775

Awesome... Modify away