What happens when a player attempts to overrun the target of a charge? Lets assume the following:
1: The attacking character has a move of 30'
2: The target is 40' away
3: The attacker has improved overrun as a feat (to keep things simple)
4: There is nothing between the two, and it is not difficult terrain
5: The attacker and the target are both the same size
The attacking character charges the target with the intention of performing an overrun. If the character fails to overrun, the charge ends and the character stops directly in front of the target. Their turn ends, and we move on to the next player/creature. That seems pretty obvious based on page 201 of the core rule book.
But what happens if the overrun is successful? I assume it's going to be one of the following:
A: The attacking character stops on the square immediately behind the target, in the path of the charge. Their turn is over.
B: The attacking character continues past the target, stopping at exactly 2x their move distance in the direction of the charge (assuming there isn't anything in the way) and their turn is over.
C: The attacking character can choose to end it's movement anywhere between A and B above. And if so, does the character have to declare their intended stopping point before making the attack?
Now to complicate things a little. What happens if the square behind the target is occupied by another creature or is a wall? Does this prevent the overrun from even being attempted? Or do we copy the Bull Rush rules and assume that the attacker must continue the overrun at a -4 CMB penalty for each additional creature? Or does the attacking creature displace the first target, and if so where does the target creature move to?
|
C, and no.
For the complex part, the creature would make an extra overrun check against each additional creature and if they fail part way through, the stop at the square before the one they failed to move through. If this square is occupied they fall prone. A creature that has been overrun is NOT moved, even if that target chose to step out of the way.
This is how it was treated in a post by one o' them official types, though I don't remember which/where.