Quote:
Originally Posted by Fat diinbong
And zarator, I think that guide would be best a bit more broad to be similar to this long term thinking guide of RSE. The information is basically the same, the examples and explanations just need to be adjusted to suit DPP. |
I know about that guide, but I think it is too limited and generic. I wanted something more in-depth and detailed like:
1) What late-game is
2) How to prepare to late-game during Team Building
a) Late-game sweepers
b) "Win conditions" (Trick, Encore, Perish Song, Explosion etc)
3) How to prepare to late-game in battle
a) Bulky Offense's late-game
b) Heavy Offense's late-game
c) Stall late-game
d) Weather Offense's late-game (with Weather I include also Trick Room and Gravity)
(You could add more categories here)
4) Conclusion
Basically, what I disliked about the guide you linked is that it did little to distinguish between the stallish and the offensive styles, which play very differently their late-games (and the aforementioned guide is a bit biased towards offense IMO). Also, to people who say "there is little you can do to prepare for late-game", this is false. A bad built offensive team, for example, can lose to Empoleon no matter how you play it. And even a well built team cannot face late-game situations properly if they have not behaved well in the early and mid-game (assuming they do not have as well team building issues).
Most people think that preparing for late-game is impossible because there are so many scenarios you should describe in a guide for it. Well, let me say that, for comparison's sake, there exist guides to late-game for chess: they are 800-page books with a miriad of situations which could derive from the standard 20 or so openings.
In short, I think such a guide is not impossible, and definitely not useless. It would be long, VERY detailed and full of specific examples and explainations, but still functional and much needed IMO.
Also, this thread needs more input! There are a lot of possibilities for articles, guides and so on.