Unnatural aging of jocks

[Bernd Hesberg]

I've spent some time investigating this matter. It's common knowledge that each battle counts for one month in terms of money. And I've thought a long time that this applies to the jocks aging as well. Now, after being triggered by an earlier post to take a closer look, and after some short-sighted first conclusions, this is what I've found out.
The size of the team and the jocks position (being first/second/third member and so on) are used in a formula that reads like this

aging = team size - position + 1 [month / battle]

This doesn't seem quite right, if you ask me. And although we can't expect any update to the ToS freeware, it might be prudent checking this part for ToS:WS.

Larkin, when you read this and can confirm it as minor nuisance (I wouldn't say 'bug'), you might consider giving me a go for a small stand-alone team file patch.

[LarkinVB]

Will check the code. Of course the formula you did find is not what I wanted to be. And of course you are allowed to code any kind of fix for ToS. Its freeware and you are free to modify.

[Bernd Hesberg]

Ok, that's all I need at the moment. I'll code a small tool prog, which can be used on any team file. It will only check the age of all the jocks and modify these values if necessary. That means, applying it several times on the same file will be useless as long as no new battle has been fought.

Before I forget, I don't see this as a cheat, and I don't even think about coding a cheat program!

[Korgmeister]

Considering that you can make tournament teams with as much money and skill as you like, I think a cheat program for the HQ module would be rather unnescessary.

[Bernd Hesberg]

I'd say it's a bad habit to try to simplify problems before they are solved. I sometimes accuse my customers of doing so (of course, only when I'm alone ). And every now and then I realize that I've fallen prey to this same habit.

So, after further playtesting, and actually after programming that tool I talked about, here's my correction. The main difference is that, it doesn't depend on the team size or the jock's position in one of the files, but exclusively on the team size and sequence of jocks during the battle.
You may have fought battles, where not all jocks have been involved. And during game setup you may alter the sequence of jocks at will. All this can't be verified afterwards.
Now, when considering the planned use of that prog, and thinking of all the restrictions that must be made, I'd say we should rather forget about it. My sincerest apologies to all who wanted to use it.

But then, there's another brew fresh from my cauldron, the second edition of my excel sheet for jock management.
To all those who don't know it: You need MS Excel (~97 or newer) and shouldn't disable macros. No, there's no virus!

[Bernd Hesberg]

Just three downloads? Perhaps I should have found a better hideout for this.
Ok, so there are only few people who could have stumbled across the bug I've discovered recently. As a workaround for the sheet 'Titans' it would be sufficient to clear the contents of cell K481 and insert a new line of cells before row 482. Of course, all row numbers are only valid for the original download.

Maybe there's a chance that the older version (which is available via the ToS home page) could be replaced by this update.
Larkin, which of your email addresses would you like me to send it to?

[LarkinVB]

Send it to larkin@viciousbyte.de