Subpage under development, new version coming soon!
Asunto: »General Questions
why one would want Assistant Plus? it's superfluous
anyway, as I said, check old club page, in Your case it should be here: https://sokker.org/glowna/teamID/142367
look for button labelled Invite URL
anyway, as I said, check old club page, in Your case it should be here: https://sokker.org/glowna/teamID/142367
look for button labelled Invite URL
I don't see why you'd design a system where decimals are needed when it comes to wage calculation, when you're just going to round them down anyway. It seems unnecessarily complicated. This really just furthers my view that the game needs it's own currency.
I don't understand what your problem is with it. It probably works this way:
- they have some function that calculates wage impact for single skill with input in range [0.0000000, 18.0000000], let's call it single_skill_wage, it's perfectly reasonable that it outputs values with decimal parts, as the input can also be decimal. This formula most likely involves exponents, as the raise of wage with skill raise is close to exponential growth. Exponents don't care about numbers being "nice" :P
- then they have function that calculates total wage by adding 1500 (in pln) + 4* single_skill_wage(gk) + single_skill_wage(stamina) + single_skill_wage(pace) + ... + single_skill_wage(striker), and then rounds that number to hundreds before returning it (so the result is "nice" to human eye).
It's nothing complicated, it could be done in few lines of code.
They most likely store wages in database in pln, as that is the base currency, and when you open the coach page it gets converted to your currency using your country 6.66667 currency rate.
Few examples for you:
Przygocki: 1500 (base) + ~86872 + ~200 (wage impact from other skills) = ~88572, rounded down to 88500
Pyziak and Jakiel: 1500 + ~21718 + ~200 = ~23418, rounded down to 23400
Licheński: 1500 + ~200-299 from other skills = 1700 rounded down
I don't understand what your problem is with it. It probably works this way:
- they have some function that calculates wage impact for single skill with input in range [0.0000000, 18.0000000], let's call it single_skill_wage, it's perfectly reasonable that it outputs values with decimal parts, as the input can also be decimal. This formula most likely involves exponents, as the raise of wage with skill raise is close to exponential growth. Exponents don't care about numbers being "nice" :P
- then they have function that calculates total wage by adding 1500 (in pln) + 4* single_skill_wage(gk) + single_skill_wage(stamina) + single_skill_wage(pace) + ... + single_skill_wage(striker), and then rounds that number to hundreds before returning it (so the result is "nice" to human eye).
It's nothing complicated, it could be done in few lines of code.
They most likely store wages in database in pln, as that is the base currency, and when you open the coach page it gets converted to your currency using your country 6.66667 currency rate.
Few examples for you:
Przygocki: 1500 (base) + ~86872 + ~200 (wage impact from other skills) = ~88572, rounded down to 88500
Pyziak and Jakiel: 1500 + ~21718 + ~200 = ~23418, rounded down to 23400
Licheński: 1500 + ~200-299 from other skills = 1700 rounded down
I have a problem with bad design and I don't like that the solution is "We'll just round things up or down" to hide it.
So on that same token you want skill levels to not have decimals too because they also have decimals. As a result it’s hardly surprising wage calculation has decimals. Better to round off at the end than at the start. I don’t see an issue with decimals myself.
Inaccurate currency conversion that's technically shortchanging users, on a site that doesn't even need separate currencies is bad design.
Yeah, having currencies with different rates is a bad design, as it unnecessarily complicates code and hurts user experience. But we were talking about wages and there is nothing wrong with wage calculations algorithm.
One links to the other.
If you have a currency system that actually works and doesn't need rounding, separate currencies aren't a problem.
If you want a decimal system, you need a currency that's actually equal across all currencies. Or just 1 single currency.
This idea of "Oh well, it's close enough" bothers me when there is clearly a better system possible.
It really shouldn't be a terribly difficult fix either, as tools already exist on this site for currency conversion and the formula doesn't need changing. It would only be slightly more complicated than the process of creating a new currency for a new country.
If you have a currency system that actually works and doesn't need rounding, separate currencies aren't a problem.
If you want a decimal system, you need a currency that's actually equal across all currencies. Or just 1 single currency.
This idea of "Oh well, it's close enough" bothers me when there is clearly a better system possible.
It really shouldn't be a terribly difficult fix either, as tools already exist on this site for currency conversion and the formula doesn't need changing. It would only be slightly more complicated than the process of creating a new currency for a new country.
[img ]insert link here[/img]
Without the space, obviously
(editado)
Without the space, obviously
(editado)
Thanks Camus.
I have a trainer with 16 in pace.
This player is 22 YO.
Been training pace since the beggining.
He has so bad talent that he does not pop even in 5 training weeks in advance formation?
And this assuming he was bought when he just popped pace.
What do you think?
https://ibb.co/WtBSvWx
(editado)
I have a trainer with 16 in pace.
This player is 22 YO.
Been training pace since the beggining.
He has so bad talent that he does not pop even in 5 training weeks in advance formation?
And this assuming he was bought when he just popped pace.
What do you think?
https://ibb.co/WtBSvWx
(editado)