@_@
Floogal's right imo.
In a run like this you really have three different things you need to achieve. Beating the game, collecting all the "100% stuff" quickly and fluidly, then optimizing the battles. The proper approach to this is first working out the best way to collect everything you need to collect while going through the game. Basically you write down what you have to do from beginning to end, and if a forced battle comes up just jot down "fight ______" in your notes. This is the main route of the run, so it has to be done first.
Once you've worked all of that out and know exactly where you're going to be and when, then you can start worrying about the battles. If you absolutely need an FP item or something you can then look back in your route and say "Hmm... well, this Maple Syrup is on the way before the battle" and can work it into your path. If you try to work everything out at the same time you'll just end up getting more confused and that increases the potential for errors in your route that you'll have to find and fix later. At least that's the way I see it.
In a run like this you really have three different things you need to achieve. Beating the game, collecting all the "100% stuff" quickly and fluidly, then optimizing the battles. The proper approach to this is first working out the best way to collect everything you need to collect while going through the game. Basically you write down what you have to do from beginning to end, and if a forced battle comes up just jot down "fight ______" in your notes. This is the main route of the run, so it has to be done first.
Once you've worked all of that out and know exactly where you're going to be and when, then you can start worrying about the battles. If you absolutely need an FP item or something you can then look back in your route and say "Hmm... well, this Maple Syrup is on the way before the battle" and can work it into your path. If you try to work everything out at the same time you'll just end up getting more confused and that increases the potential for errors in your route that you'll have to find and fix later. At least that's the way I see it.