BZ 3371: Possible world template issue(s) with inaugural drafts

siobhan · 06-11-2009, 12:48 AM

Here's a curiosity that I've noticed in the current OOTP. It occurs when you save a world template that has the inaugural draft option unchecked. What happens is that if you load a template like that, and you opt to check the inaugural draft option, the inaugural draft is scheduled as usual BUT the active roster is still filled to capacity as if the option were unchecked. (The reserve rosters are empty when you do this.)

From what I've seen, the inaugural draft also works differently in this mode, at least when it's just the AI drafting. A Look in the full transactions of the teams after the draft will show that January is littered with "(Player) got drafted by the (Team)" transactions, including occurances where it will list players being drafted from the team that drafted them! (In other words, a "City Team Names" team's transactions would have occurances like "J. Ballplayer drafted by the City Team Names".)

I hope this makes sense. This may not be the most severe of problems but it does seem very peculiar.

For the record, I've noticed this problem with what seems like an OOTP9 template (part of the College Baseball BETA, if you wish to test) and an OOTP10 template I created.

That's all for now. Thanks for reading.

endgame · 06-19-2009, 12:49 AM

Sorry things are taking a little longer to get to lately. Can you try the template you created in X after installing the next patch and report if this issue is still a problem? Certainly and template created in 9 is problematic, but I'd want to hear more about templates created in X working improperly. Thanks in advance.

siobhan · 06-19-2009, 03:34 AM

No worries about the time it took to reply...the only worry I had was that I posted this bug correctly. I will certainly see if this is still occurring when the first patch for OOTP10 is released.

Some additional information that may factor into this: The template I'm using was saved after a new league was created without the inaugural draft, so there are players saved within the template. (There are custom stadiums saved within it too, which is the rationale for saving at that stage.) Anytime I use this template, it will initially give me the same rosters for each team on January 1 of the year I choose. On January 2, the inaugural draft occurs, and then all the things I mentioned with players being drafted from other teams (or their own) happens.

What I didn't realize right away is that, if you also have a reserve roster, and the limit is set at a low number like 15, you can end up with teams being unable to make many of their later picks because their team still contains a large number of players that were originally assigned to them but aren't supposed to be. In a test run without setting budgets, I had a team fail to draft in round 32 and 33 due to roster limits and draft normally in round 34. (They then failed to draft two rounds later only to draft again the very next round.)

So that's my wordy follow-up. Again, I will check to make sure if this still happens with the next OOTP10 release. We'll see if this is a problem they've already worked on and, hopefully, nipped in the bud.

siobhan · 06-21-2009, 07:51 PM

The patch is installed now. However, all the issues noted previously still exist. All the players still begin on their original teams and then those teams draft from each other as if everyone were in the free agent pool, occasionally running out of room when there's a reserve roster set.

I did two tests to see if similar things happened in other circumstances:

If I make a template with no inaugural draft and save it before I create a league, then re-load the template for a new league and turn on the inaugural draft option, it works as it should.

If I make a template with an inaugural draft and save it after I create a league, then re-load the template for a new league and turn off the inaugural draft option, it works as it should with players randomly assigned to teams, and it will always begin with the same players each time.

So basically, the issue only applies to league templates that are saved when teams have players on their rosters.

In summary, when a template is saved from a league where players are initially assigned to teams:
1. None of the players are being automatically released into the free agent pool when the inaugural draft option is turned on.
2. Players in the draft are being selected from the other teams instead of from the free agent pool.

Let me know if this still warrants being looked at or if it's just me saving a template at a strange time.

battists · 06-30-2009, 04:43 PM

Hi folks,

Thanks for your post, and sorry for the delay in getting back to you. The first few weeks after the release are always pretty busy around here!

I've logged this as bug 3371, and I'll ask Markus to take a look at the issue. However, as you intimated, I'm not sure it's likely to get a ton of attention compared to some other high priority issues...

Thanks!

Steve

06-11-2009, 12:48 AM	#1
siobhan Minors (Single A) Join Date: Sep 2007 Posts: 86	BZ 3371: Possible world template issue(s) with inaugural drafts Here's a curiosity that I've noticed in the current OOTP. It occurs when you save a world template that has the inaugural draft option unchecked. What happens is that if you load a template like that, and you opt to check the inaugural draft option, the inaugural draft is scheduled as usual BUT the active roster is still filled to capacity as if the option were unchecked. (The reserve rosters are empty when you do this.) From what I've seen, the inaugural draft also works differently in this mode, at least when it's just the AI drafting. A Look in the full transactions of the teams after the draft will show that January is littered with "(Player) got drafted by the (Team)" transactions, including occurances where it will list players being drafted from the team that drafted them! (In other words, a "City Team Names" team's transactions would have occurances like "J. Ballplayer drafted by the City Team Names".) I hope this makes sense. This may not be the most severe of problems but it does seem very peculiar. For the record, I've noticed this problem with what seems like an OOTP9 template (part of the College Baseball BETA, if you wish to test) and an OOTP10 template I created. That's all for now. Thanks for reading.

06-19-2009, 12:49 AM	#2
endgame Hall Of Famer Join Date: Aug 2002 Posts: 16,842	Sorry things are taking a little longer to get to lately. Can you try the template you created in X after installing the next patch and report if this issue is still a problem? Certainly and template created in 9 is problematic, but I'd want to hear more about templates created in X working improperly. Thanks in advance. __________________ "Try again. Fail again. Fail better." -- Samuel Beckett _____________________________________________

06-19-2009, 03:34 AM	#3
siobhan Minors (Single A) Join Date: Sep 2007 Posts: 86	No worries about the time it took to reply...the only worry I had was that I posted this bug correctly. I will certainly see if this is still occurring when the first patch for OOTP10 is released. Some additional information that may factor into this: The template I'm using was saved after a new league was created without the inaugural draft, so there are players saved within the template. (There are custom stadiums saved within it too, which is the rationale for saving at that stage.) Anytime I use this template, it will initially give me the same rosters for each team on January 1 of the year I choose. On January 2, the inaugural draft occurs, and then all the things I mentioned with players being drafted from other teams (or their own) happens. What I didn't realize right away is that, if you also have a reserve roster, and the limit is set at a low number like 15, you can end up with teams being unable to make many of their later picks because their team still contains a large number of players that were originally assigned to them but aren't supposed to be. In a test run without setting budgets, I had a team fail to draft in round 32 and 33 due to roster limits and draft normally in round 34. (They then failed to draft two rounds later only to draft again the very next round.) So that's my wordy follow-up. Again, I will check to make sure if this still happens with the next OOTP10 release. We'll see if this is a problem they've already worked on and, hopefully, nipped in the bud.

06-21-2009, 07:51 PM	#4
siobhan Minors (Single A) Join Date: Sep 2007 Posts: 86	The patch is installed now. However, all the issues noted previously still exist. All the players still begin on their original teams and then those teams draft from each other as if everyone were in the free agent pool, occasionally running out of room when there's a reserve roster set. I did two tests to see if similar things happened in other circumstances: If I make a template with no inaugural draft and save it before I create a league, then re-load the template for a new league and turn on the inaugural draft option, it works as it should. If I make a template with an inaugural draft and save it after I create a league, then re-load the template for a new league and turn off the inaugural draft option, it works as it should with players randomly assigned to teams, and it will always begin with the same players each time. So basically, the issue only applies to league templates that are saved when teams have players on their rosters. In summary, when a template is saved from a league where players are initially assigned to teams: 1. None of the players are being automatically released into the free agent pool when the inaugural draft option is turned on. 2. Players in the draft are being selected from the other teams instead of from the free agent pool. Let me know if this still warrants being looked at or if it's just me saving a template at a strange time.

06-30-2009, 04:43 PM	#5
battists Hall Of Famer Join Date: Jul 2004 Posts: 18,506	Hi folks, Thanks for your post, and sorry for the delay in getting back to you. The first few weeks after the release are always pretty busy around here! I've logged this as bug 3371, and I'll ask Markus to take a look at the issue. However, as you intimated, I'm not sure it's likely to get a ton of attention compared to some other high priority issues... Thanks! Steve