Post by llecha on Mar 1, 2014 19:25:44 GMT -5
Contributed by Pll
written by: Unforgiven
BLUE PRINT FOR BASIC PLANS
A fight plan is called a “plan” for a reason. You need to have specific goals in mind of what you want to accomplish, when, and what contingencies do you want in place in case things don’t go as expected. To make this easier for you break your plan down into workable sections and decide what you want to accomplish with each section. the rounds used in each section are arbitrary and and the number of sections can be anywhere from 1 section for the whole plan to 13 or more sections if you are a details nut. personally I have plans that are made of one section and I have plans made of 13 sections at the most.
Take a basic slugger plan perhaps his goals are
1. work the body regardless of score to tire his opponent
2. continue working the body but check score. and then
3. win fight on points if opp isn’t close to being knocked out.
Going by this fight plans goals we may divide the plan into 3 sections. the first section with:
goal one will be from rounds 1-4,
second goal will be covered in rounds 5-9,
final goal will be covered by rounds 10-12.
STATIC LINES AND CONDITIONAL ORDER
Each fight plan must begin with a “static line”. a static line is a 20 point action line with or without style with no conditional attached to it.
1) 4B/8/8 (ring)
7) 6/6/8
2) 5/7/8 (feint)
these are all examples of a static line, they have no conditional attached to them and they all contain a round number in which to start the line. these lines are used as “fall back lines”, if no conditional is met then these are the lines that are used. When writing beginning plans each section we make is going to start with a basic static line so it is easier to see the interaction between the static line and the conditioners below it.
Conditionals are placed below the static line in order of least to most important. The fight parser reads each section from bottom to top so conditionals lower than others take precedence as long as the conditonal is true. for this reason youhave to be careful how you rank your conditionals. make sure they do not concel each other out or make it impossible for the parser to read:
written by: Unforgiven
BLUE PRINT FOR BASIC PLANS
A fight plan is called a “plan” for a reason. You need to have specific goals in mind of what you want to accomplish, when, and what contingencies do you want in place in case things don’t go as expected. To make this easier for you break your plan down into workable sections and decide what you want to accomplish with each section. the rounds used in each section are arbitrary and and the number of sections can be anywhere from 1 section for the whole plan to 13 or more sections if you are a details nut. personally I have plans that are made of one section and I have plans made of 13 sections at the most.
Take a basic slugger plan perhaps his goals are
1. work the body regardless of score to tire his opponent
2. continue working the body but check score. and then
3. win fight on points if opp isn’t close to being knocked out.
Going by this fight plans goals we may divide the plan into 3 sections. the first section with:
goal one will be from rounds 1-4,
second goal will be covered in rounds 5-9,
final goal will be covered by rounds 10-12.
STATIC LINES AND CONDITIONAL ORDER
Each fight plan must begin with a “static line”. a static line is a 20 point action line with or without style with no conditional attached to it.
1) 4B/8/8 (ring)
7) 6/6/8
2) 5/7/8 (feint)
these are all examples of a static line, they have no conditional attached to them and they all contain a round number in which to start the line. these lines are used as “fall back lines”, if no conditional is met then these are the lines that are used. When writing beginning plans each section we make is going to start with a basic static line so it is easier to see the interaction between the static line and the conditioners below it.
Conditionals are placed below the static line in order of least to most important. The fight parser reads each section from bottom to top so conditionals lower than others take precedence as long as the conditonal is true. for this reason youhave to be careful how you rank your conditionals. make sure they do not concel each other out or make it impossible for the parser to read: