Emm

I'm playing in Conference South and after a pretty appalling start I am slowly clawing my way up the table.

The first 27 league games of the season passed without too much incident. We conceded 5 penalties during that time, but 4 of these were in the first 8 games where our young and inexperineced, (not to mention unfit), team were battered into submission by each and every opposition they faced.

In the last 8 games however, things have been a little different.

After creating this thread about a problem with the positioning of my full-backs, I decided to break with tradition and experiment with pre-match opposition instructions. It has been the only thing that I have done differently over the last 8 games but it has resulted in a marked change in match incident.

First 27 games. 5 penalties against me.
Last 8 games. 7 penalties against me.

Now I'm not moaning in particular about penalties in general, because there are a number of reasons why they may happen.

1. My team is instructed to defend quite deep.

2. We have 5 players in the squad with the PPM, "dives into tackles" and 4 of these are regular starters, (including both first choice full-backs).

3. I instruct my players to tackle "hard".

So although there are a number of reasons why I might give free-kicks and penalties away, there seems to be only 1 reason why they have increased so much in regularity over the last 8 minths. The only thing that I am doing differently is the "show onto foot" option in the set-piece instructions. I do this for only the GK and the MR and ML positions.

Have I just been unlucky over this run of matches or is there a link?

Has anyone experienced something similar?

retired_vmacalik

Sounds like you have some tough guys in your team who think show onto weaker foot will be more easily acieved if they break both of them .

Seriously I cant see why that would cause an increase in penalties, its more likely that the ai has decided to instruct its players to run with ball often in order to draw fouls from your hard tackling.