Page 1 of 1

3.0.11 - Farm to Pro player movement problem

Posted: Wed May 17, 2017 1:24 am
by Président ANHS
Here are the operations I run on a daily basis:
1- Download and process database (using the manual command)
2- Load lines files
3- Sim games
4- Process trades, sign unassigned players, etc...

For a while, one of my teams has had problems with roster movements. Every time I sim, that team ends up with 40+ players in the pros and barely anything left in the farm.

Tonight just to make sure that it wasn't the GM's fault, here is what I did:
1- Downloaded and processed database (as usual)
2- Got a message that the team's roster was not ok (no big deal up to now)
3- Load lines files

Then, before simming the games, I went to check the team's roster. There were 21 players dressed in the pros and 20 in the farm. No big deal, I figured the sim would actually fix the problem when I sim the games.

After the games were simmed, the team ended up with 43 players in the pros...again. All I did was sign a player from the unassigned list after the sim, saved the league file and updated the website.

Team is called Denver Reign, and the League transaction log can be found here:
http://anhs.qc.ca/transactions.php?Info=LeagueLog

I don't think the problem comes from the unassigned player I added to his team because the same problem happened with another team earlier this season. The GM is using the web client to submit his lines, but never happened before 3.0.11 and that GM used the web client all season long under 3.0.10 without this problem happening.

Re: 3.0.11 - Farm to Pro player movement problem

Posted: Wed May 17, 2017 9:03 pm
by SimonT
Did the GM made the rosters/lines for the next days? When you look at this setting, I assume for Day #2, the 43 players are all pro scratches?

Re: 3.0.11 - Farm to Pro player movement problem

Posted: Thu May 18, 2017 8:11 am
by Président ANHS
Nope, there's 20 players dressed and 23 in the pro scratches. I have a problem understanding what is happening with this GM's lines...

Yesterday when I simmed, the GM had submitted rosters/lines with the web client. His roster was fine, although there was 1 skater too many. I was still able to sim the games, but after the games were simmed, the sim sent 21 of his farm players to pro scratches for no reason.

I have no way to know for how many games he had setup his rosters/lines through the web client.

Then, this morning, I simmed games. Obviously his roster had too many players (21 scratched in the pros) so I moved all the scratches to his farm, did auto roster for farm only. Right after I simmed the games, on the sim screen, I had a popup saying that the same team had too many players in the pros. I went to check the transactions log and sure enough, 20+ players had been sent to the pros again...

I have 4-5 other GM's using the web client on a daily basis and this is the only team I am having trouble with.

Re: 3.0.11 - Farm to Pro player movement problem

Posted: Thu May 18, 2017 7:58 pm
by SimonT
Can you send yesterday game? I'm looking for step by step method to reproduced the issue.

Re: 3.0.11 - Farm to Pro player movement problem

Posted: Thu May 18, 2017 8:16 pm
by Président ANHS
You want the last backup file?

Re: 3.0.11 - Farm to Pro player movement problem

Posted: Fri May 19, 2017 7:26 pm
by SimonT
Yes and No. I want all the files (League File, Client File from GM and/Or SqLite) to reproduced the error. I need to look at all the function one by one with the data of your league to reproduced the error.

Re: 3.0.11 - Farm to Pro player movement problem

Posted: Sun May 21, 2017 10:17 am
by JimToupet
I was running this issue all year long but I've switch from the v2 to v3 on the offseason last year and I was thinking that this switch was the purpose.

I'm happy to see this can be a change from the v3.0.10 to v3.0.11 and hope this will be resolved. It was a real nightmare and I receive a plenty of complaint from my GM all year long.

Re: 3.0.11 - Farm to Pro player movement problem

Posted: Sun Jun 04, 2017 2:42 pm
by SimonT
By the way, nobody was ever to reproduced the issue to me. :(