Subpage under development, new version coming soon!
Subject: »Sokker Questions/Answers
Based on your example and trust, i am wondering if there is not a hidden special skills in place ?
I'm almost convinced that pace isn't the skill that defines how fast a player runs and how fast a player reaches topspeed. I think that pace only defines how fast a player CAN run. But not how fast he WILL run.
I'm almost convinced that pace isn't the skill that defines how fast a player runs and how fast a player reaches topspeed. I think that pace only defines how fast a player CAN run. But not how fast he WILL run.
Cobe Palinck, age: 35, BMI: 25.76
Ibrahim Vrancken, age: 26, BMI: 26.61
They both have high BMI, but as far as I know, BMI was never implemented into the ME.
Who knows...
Ibrahim Vrancken, age: 26, BMI: 26.61
They both have high BMI, but as far as I know, BMI was never implemented into the ME.
Who knows...
When selling a player, 5% of the fee is deducted, the question remains, who gets these 5% ? Raul, Poland, dtox ?
And is the deducted money spent transparent? I want data, charts and graphs here !
Something is fishy here
(edited)
And is the deducted money spent transparent? I want data, charts and graphs here !
Something is fishy here
(edited)
I'm almost convinced that pace isn't the skill that defines how fast a player runs and how fast a player reaches topspeed. I think that pace only defines how fast a player CAN run. But not how fast he WILL run.
I doubt it, if we're talking about just running without ball [because speed of running with ball depends on pace AND technique]
there are many factors here
pace level
form
engine visualisation = what we see is not always 100% accurate to what happens [that's why sometimes players start running unnaturally fast or slow], it was explained in Polish forum by people more knowledgable about IT than I am so I won't even try it... but it's the same thing that affects the onside/offside... when the visualisation shows a player on offside position, while he was actually onside [since what counts is what happens "in engine" not in visualisation which is just an imperfect representation of what happened]
I doubt it, if we're talking about just running without ball [because speed of running with ball depends on pace AND technique]
there are many factors here
pace level
form
engine visualisation = what we see is not always 100% accurate to what happens [that's why sometimes players start running unnaturally fast or slow], it was explained in Polish forum by people more knowledgable about IT than I am so I won't even try it... but it's the same thing that affects the onside/offside... when the visualisation shows a player on offside position, while he was actually onside [since what counts is what happens "in engine" not in visualisation which is just an imperfect representation of what happened]
there are many factors here
pace level
form
Uhu...
Then explain... 35y old... incredible pace, weak form, runs faster than 26y old, divine ++++++++ pace, weak form.
I'm talking...almost always!
So match visual is not accurate from time to time...ok, but almost always??
pace level
form
Uhu...
Then explain... 35y old... incredible pace, weak form, runs faster than 26y old, divine ++++++++ pace, weak form.
I'm talking...almost always!
So match visual is not accurate from time to time...ok, but almost always??
How are we supposed to build tactics off a bad visualisation off the Match engine
Then explain... 35y old... incredible pace, weak form, runs faster than 26y old, divine ++++++++ pace, weak form.
I'm talking...almost always!
So match visual is not accurate from time to time...ok, but almost always??
I watched their last game, V. is faster as he should be...often starting from behind and overtaking the slower one
as for "the difference is not big enough", it is possible that form operates on %... thus the higher the skills, the more low form "takes away"... 30% of 18 is 5.4, 30% of 13 is 3.9 etc. to put it in simple math
it is also possible that engine takes into account the tactical position and actual position...in other words the bigger the distance players needs to move, the faster he goes/more of possible pace he uses, if that makes sense
also possible (I'd even say very probable) that there is a bit of random factor as with every other skill, so the pace might not be at same level in every action (same as in technique, where superdivine technique player might sometimes be stopped by formidable defender)
I'm talking...almost always!
So match visual is not accurate from time to time...ok, but almost always??
I watched their last game, V. is faster as he should be...often starting from behind and overtaking the slower one
as for "the difference is not big enough", it is possible that form operates on %... thus the higher the skills, the more low form "takes away"... 30% of 18 is 5.4, 30% of 13 is 3.9 etc. to put it in simple math
it is also possible that engine takes into account the tactical position and actual position...in other words the bigger the distance players needs to move, the faster he goes/more of possible pace he uses, if that makes sense
also possible (I'd even say very probable) that there is a bit of random factor as with every other skill, so the pace might not be at same level in every action (same as in technique, where superdivine technique player might sometimes be stopped by formidable defender)
Also a factor as how much remaining stamina due to other actions/running in match