AHL to NHL Preseason: up and down and up and down

hagakure · 07-14-2020, 10:02 PM

I'm currently GM and HC of the Hershey Bears in challenge mode. Every day now since Sept 19, 2019 (day before preseason starts), the Washington Capitols call up and send down B. Leipsic. On the 19th, they sent him down, called him up and sent him down. From the 20th onward, they have called him up and sent him down each once per day. It was really disruptive because not only do I have to dismiss the ATTENTION banner twice before I can move on, it also wrecks my lines and I have to reset them before each preseason game, and it devastates Leipsic's fitness (he comes back the same day as low as 1% FIT!!!). It also spams my news box with the notifications of his one-way trips, which is a minor annoyance. Something similar happened a couple of times when I was GM'ing the Vancouver Giants in the WHL, someone would be called up and sent back down the same day, but that usually stopped after a single occurrence or maybe two. In the AHL, it happened every single day for all 10 days (19-29 Sep) of the preseason and then mercifully stopped. It rendered the preseason not only unproductive but practically unbearable.

hagakure · 07-14-2020, 10:13 PM

I'm also having a problem where some of my players keep needing to be assigned jersey numbers. Do they keep falling off?

Also, Washington just called up Leipsic again on Oct 3, but this time they didn't send him right back down... yet.

JeffR · 07-15-2020, 02:15 AM

Could you upload the save (instructions here)? I'd like to see what else was going on with Washington's roster that was causing him to get called up and sent down repeatedly like that.

Re: the jersey numbers, if they play a game for you before getting called up/sent down, it should "stick", but if they don't it may need to be re-selected when they come back (the game gets the number information from his stat history.)

hagakure · 07-15-2020, 11:31 PM

Hi Jeff. I've put it in your ftp folder as a file named: up_and_down2020-07-15-22-27-42

hagakure · 07-16-2020, 03:08 AM

Still happening, just thankfully not as often.

If we can agree that this would never happen in real life even once, then logically it should be completely removed from the game. Seems like that would just be a matter of adding a function to check how long it has been since a player has been either called up or sent down by an AI, and preventing it from happening in a shorter period than is reasonable, whether that's 24 hours, 48 hours, a week... whatever makes sense (perhaps looking at real world data), but certainly not allowing it to happen within the same day. The algorithm could be borrowed from the Injury List subroutine that clearly checks to see whether or not a player has been on the list long enough to be moved back to the active roster...

It seems like a funny-ha-ha error, but it's disruptive to the actual gameplay for all the reasons I've cited in the original post.

JeffR · 07-16-2020, 06:57 AM

Thanks. No obvious reason that I can see, but it looks like it's happening to a couple of other players in the league, too. I'll try to replicate it so we can find the source, my first suspicion is it has something to do with the extra tryout players on the roster in training camp, but exactly what I'm not sure.

hagakure · 07-16-2020, 04:28 PM

Hmm, so what I was trying to say above was, regardless of the cause, the cure might be a quick check just prior to the moment of execution that asks, "Has this player been moved up/down too recently?" It would need to allow trades to other teams, though, just prevent an overzealous AI from moving people up and down in the same day, even just once. So a bit trickier perhaps than I'm insinuating.

Anyway, thanks for looking into it. I play this game literally 6+ hours every day, so if there's an issue, I'm bound to run across it.

07-14-2020, 10:02 PM	#1
hagakure Minors (Rookie Ball) Join Date: Jun 2020 Location: Maryland, USA Posts: 39	AHL to NHL Preseason: up and down and up and down I'm currently GM and HC of the Hershey Bears in challenge mode. Every day now since Sept 19, 2019 (day before preseason starts), the Washington Capitols call up and send down B. Leipsic. On the 19th, they sent him down, called him up and sent him down. From the 20th onward, they have called him up and sent him down each once per day. It was really disruptive because not only do I have to dismiss the ATTENTION banner twice before I can move on, it also wrecks my lines and I have to reset them before each preseason game, and it devastates Leipsic's fitness (he comes back the same day as low as 1% FIT!!!). It also spams my news box with the notifications of his one-way trips, which is a minor annoyance. Something similar happened a couple of times when I was GM'ing the Vancouver Giants in the WHL, someone would be called up and sent back down the same day, but that usually stopped after a single occurrence or maybe two. In the AHL, it happened every single day for all 10 days (19-29 Sep) of the preseason and then mercifully stopped. It rendered the preseason not only unproductive but practically unbearable.

07-16-2020, 03:08 AM	#5
hagakure Minors (Rookie Ball) Join Date: Jun 2020 Location: Maryland, USA Posts: 39	Still happening, just thankfully not as often. If we can agree that this would never happen in real life even once, then logically it should be completely removed from the game. Seems like that would just be a matter of adding a function to check how long it has been since a player has been either called up or sent down by an AI, and preventing it from happening in a shorter period than is reasonable, whether that's 24 hours, 48 hours, a week... whatever makes sense (perhaps looking at real world data), but certainly not allowing it to happen within the same day. The algorithm could be borrowed from the Injury List subroutine that clearly checks to see whether or not a player has been on the list long enough to be moved back to the active roster... It seems like a funny-ha-ha error, but it's disruptive to the actual gameplay for all the reasons I've cited in the original post. Attached Images

07-14-2020, 10:13 PM	#2
hagakure Minors (Rookie Ball) Join Date: Jun 2020 Location: Maryland, USA Posts: 39	I'm also having a problem where some of my players keep needing to be assigned jersey numbers. Do they keep falling off? Also, Washington just called up Leipsic again on Oct 3, but this time they didn't send him right back down... yet.

07-15-2020, 02:15 AM	#3
JeffR FHM Producer Join Date: Apr 2002 Location: Kelowna, BC Posts: 17,419	Could you upload the save (instructions here)? I'd like to see what else was going on with Washington's roster that was causing him to get called up and sent down repeatedly like that. Re: the jersey numbers, if they play a game for you before getting called up/sent down, it should "stick", but if they don't it may need to be re-selected when they come back (the game gets the number information from his stat history.)

07-15-2020, 11:31 PM	#4
hagakure Minors (Rookie Ball) Join Date: Jun 2020 Location: Maryland, USA Posts: 39	Hi Jeff. I've put it in your ftp folder as a file named: up_and_down2020-07-15-22-27-42

07-16-2020, 06:57 AM	#6
JeffR FHM Producer Join Date: Apr 2002 Location: Kelowna, BC Posts: 17,419	Thanks. No obvious reason that I can see, but it looks like it's happening to a couple of other players in the league, too. I'll try to replicate it so we can find the source, my first suspicion is it has something to do with the extra tryout players on the roster in training camp, but exactly what I'm not sure.

07-16-2020, 04:28 PM	#7
hagakure Minors (Rookie Ball) Join Date: Jun 2020 Location: Maryland, USA Posts: 39	Hmm, so what I was trying to say above was, regardless of the cause, the cure might be a quick check just prior to the moment of execution that asks, "Has this player been moved up/down too recently?" It would need to allow trades to other teams, though, just prevent an overzealous AI from moving people up and down in the same day, even just once. So a bit trickier perhaps than I'm insinuating. Anyway, thanks for looking into it. I play this game literally 6+ hours every day, so if there's an issue, I'm bound to run across it.