Dota 2 TI11 Fantasy predictions and tracker UPDATED REGULARLY! (October 30th, Grand Final)

1Play DOTA2 News
Oct 31

While not for everyone, Dota 2 TI11 Fantasy is a fun way to grind out a few more battle points each day with your Fantasy predictions. But often, picking the perfect Fantasy lineup can be a confusing process. That’s why we’ve made it easy with our handy Fantasy guide, complete with daily predictions and picks!

Core – Skiter (Tundra Esports)

Core – MATUMBAMAN (Team Liquid)

Mid – Nisha (Team Secret)

Support – Zayac (Team Secret)

Support – Boxi (Team Liquid)

Make sure you’re playing claiming your daily win pack and grabbing cards whenever you can. In most all cases a gold card that will underperform is better than a gray card that over performs. Make sure you’re slotting at minimum silver or gold cards. Gray cards are only really useful if you don’t have any other player for the slot.

Pick players that are playing the most games, especially in the group stage. The difference between the points that a player playing three games, will make over the points a player in two games is massive. To this end, as things go to best-of-threes, it’ll be better to pick players that will be in three-game series, rather than 2-0s. Double check the schedule ahead of time.

When picking players, it’s best to pick one positions for Cores and five positions for supports. This is because in general, one positions get more kills that pos-3, and pos-5 supports get the most assists.

In some cases, you should keep an eye out for the bonuses given by the Silver and Gold versions of a card. Watch out for support with the Camps Stacked, or Cores with the GPM stat. These are super good for generating points. 

Try not to pick more than two players from the same team. This is to guard against you getting blown out of the water if they tank on the day for some reason. Finally, remember that at the end of the day, this is just luck, not an exact science! Have fun, and enjoy TI11 Fantasy!

All comments (0)
No contentNothing here, please try again later.