Date   
Re: ASSL '80 -- Valdosta at Czech #results

Art Widiger
 

Yeah, it does appear that way.  That's what I get for staying up so late.  I'll replay the series when the Playball file comes out.

Art


-----Original Message-----
From: Chris Strovel (Harpers Ferry Federal Armory) <strovel@...>
To: ASSL <ASSL@groups.io>
Sent: Tue, Jul 23, 2019 7:58 am
Subject: Re: [ASSL] ASSL '80 -- Valdosta at Czech #Results

Art, I don't think the PB file has come out....

==
On July 23, 2019 at 6:48 AM "Art Widiger via Groups.Io" <widiger@...> wrote:

The Czech Bouncers win 3 out of 5 from the Valdosta Crackers.

Art


-----Original Message-----
From: Steven Galbraith via Groups.Io <stevemgalbraith@...>
To: ASSL <ASSL@groups.io>
Sent: Sat, Jul 20, 2019 10:25 am
Subject: [ASSL] ASSL '80: Week/Series #6 Results

Week/series #6 results file. F-files/changes due Tuesday night.

ASSL '80: Week/Series #7 Play File

Steven Galbraith
 

Week/series #7 play c-file. Results due Tuesday night.

Note: Injury settings remain the same. We'll need to vote next on which reduced settings we'll have. More no that to follow.

ASSL '80: Poll on Injury Settings/Changes

Steven Galbraith
 



A majority (11 votes) of owners have voted to immediately change the current settings to a "reduced" setting. The vote was split among the three lower settings. We now need to vote on which setting to use.
A poll on that will follow.

locked ASSL '80: Poll on Injury Settings #poll

Steven Galbraith
 


We'll vote now on which specific injury settings to use. These changes will go into effect immediately and will be the setting for all future seasons pending any vote to change them again. Whichever setting receives the most votes will be the one we use. It does not require a majority of owners, i.e., 10.
In case of a tie we'll have another poll on just those settings. If it's a three way tie (not likely) we'll worry about that later.

Results

See Who Responded

locked Re: ASSL '80: Poll on Injury Settings #poll

Chris Strovel (Harpers Ferry Federal Armory)
 

Just a note as you head out to the polls today -- Option 2, 'Game Injuries and Fatigue,' represents almost no change from our current settings. It only eliminates AIM overuse injuries, which are rare. And, reading the help files, it appears the 'Reduced' injuries setting only applies to AIM injuries, and not to in-game injuries. Under that reading, Option 1 is not much of a change. Here is that Help language:

  • All Injuries and Fatigue - this option acts just like the above option plus fatigued players (Tired, Bushed or Worn-out) who appear in games are subject to AIM injuries. These injuries do not appear in the game script or the boxscore but show up on the team status report after the game. These injuries can be a significant length and the length of the injuries are directly related to the level of overuse a player has received.
  • Reduced Injuries and Fatigue - this option is identical to the above option except that the duration of AIM injuries has been somewhat reduced.

So it looks like neither of the first two options will do much to change the current setup.



==

On July 25, 2019 at 9:14 AM "Steven Galbraith via Groups.Io" <stevemgalbraith@...> wrote:

A new poll has been created:


We'll vote now on which specific injury settings to use. These changes will go into effect immediately and will be the setting for all future seasons pending any vote to change them again. Whichever setting receives the most votes will be the one we use. It does not require a majority of owners, i.e., 10.
In case of a tie we'll have another poll on just those settings. If it's a three way tie (not likely) we'll worry about that later.

1. Change to "Reduced Injuries and Fatigue"
2. Change to "Game Injuries and Fatigue"
3. Change to "Fatigue Only."

Vote Now

HF loses three to Polish

Chris Strovel (Harpers Ferry Federal Armory)
 

7s were kryptonite for HF hitters. Also, Wockenfuss' threw out five basestealers with 30+ success ratings....


==

locked Re: ASSL '80: Poll on Injury Settings #poll

Thomas Battiato
 

After reading Chris's note, I searched the help file and saw that he is correct - "Game injuies Enabled" is really no change at all! I had assumed it meant only for the duration of the current game and the injury didn't carry forward, but I was wrong. 

He is correct that anything other than"Fatigue Only" will not make ardly any change to the injury situation, so I changed my vote to "Fatigue Only." If you want to eliminate injuries, that is the only choice that will do so.

Thank you, Chris, for educating me that voting for the other two negates our earlier vote to eliminate injuries.  

Here is the complete description of all four categories from the Help file, with 'Game Injuries Enabled" highlighted to sow that it doesn't reduce injuries at all!


"There are four levels of A.I.M. interaction with League Manager and Baseball:

1. Fatigue only: A.I.M. will report the current status of a player, and will modify the player's abilities based upon his usage under fatigued status conditions.  However, no injuries that occur in games or that might result from over-use in A.I.M. terms will be enforced upon a player for subsequent games.

2. Game injuries enabled: In addition to maintaining fatigue status effects, injuries that occur due to rare plays during the course of a game will be enforced on players for the length of time in days that injury is scheduled to run.

3. All injuries enabled: In addition to the above, A.I.M. will often assess injuries against players who participate in a game while fatigued.  That is, players who are Tired, Bushed, or Worn out may become injured after a game if they appear in an active role in that game.

4. Reduced Injuries and Fatigue:  This option is identical to the above option except that the duration of A.I.M. injuries has been somewhat reduced."



-----Original Message-----
From: Chris Strovel (Harpers Ferry Federal Armory) <strovel@...>
To: ASSL <ASSL@groups.io>
Sent: Thu, Jul 25, 2019 10:01 am
Subject: Re: [ASSL] ASSL '80: Poll on Injury Settings #poll

Just a note as you head out to the polls today -- Option 2, 'Game Injuries and Fatigue,' represents almost no change from our current settings. It only eliminates AIM overuse injuries, which are rare. And, reading the help files, it appears the 'Reduced' injuries setting only applies to AIM injuries, and not to in-game injuries. Under that reading, Option 1 is not much of a change. Here is that Help language:
  • All Injuries and Fatigue - this option acts just like the above option plus fatigued players (Tired, Bushed or Worn-out) who appear in games are subject to AIM injuries. These injuries do not appear in the game script or the boxscore but show up on the team status report after the game. These injuries can be a significant length and the length of the injuries are directly related to the level of overuse a player has received.
  • Reduced Injuries and Fatigue - this option is identical to the above option except that the duration of AIM injuries has been somewhat reduced.
So it looks like neither of the first two options will do much to change the current setup.


==
On July 25, 2019 at 9:14 AM "Steven Galbraith via Groups.Io" <stevemgalbraith@...> wrote:

A new poll has been created:

We'll vote now on which specific injury settings to use. These changes will go into effect immediately and will be the setting for all future seasons pending any vote to change them again. Whichever setting receives the most votes will be the one we use. It does not require a majority of owners, i.e., 10.
In case of a tie we'll have another poll on just those settings. If it's a three way tie (not likely) we'll worry about that later.
1. Change to "Reduced Injuries and Fatigue"
2. Change to "Game Injuries and Fatigue"
3. Change to "Fatigue Only."

locked Re: ASSL '80: Poll on Injury Settings #poll

John Anderson
 

Do any of these settings change how SF and PR are calculated for players?

John Anderson 


On Jul 25, 2019, at 6:59 PM, Thomas Battiato via Groups.Io <Dodger300@...> wrote:

After reading Chris's note, I searched the help file and saw that he is correct - "Game injuies Enabled" is really no change at all! I had assumed it meant only for the duration of the current game and the injury didn't carry forward, but I was wrong. 

He is correct that anything other than"Fatigue Only" will not make ardly any change to the injury situation, so I changed my vote to "Fatigue Only." If you want to eliminate injuries, that is the only choice that will do so.

Thank you, Chris, for educating me that voting for the other two negates our earlier vote to eliminate injuries.  

Here is the complete description of all four categories from the Help file, with 'Game Injuries Enabled" highlighted to sow that it doesn't reduce injuries at all!


"There are four levels of A.I.M. interaction with League Manager and Baseball:

1. Fatigue only: A.I.M. will report the current status of a player, and will modify the player's abilities based upon his usage under fatigued status conditions.  However, no injuries that occur in games or that might result from over-use in A.I.M. terms will be enforced upon a player for subsequent games.

2. Game injuries enabled: In addition to maintaining fatigue status effects, injuries that occur due to rare plays during the course of a game will be enforced on players for the length of time in days that injury is scheduled to run.

3. All injuries enabled: In addition to the above, A.I.M. will often assess injuries against players who participate in a game while fatigued.  That is, players who are Tired, Bushed, or Worn out may become injured after a game if they appear in an active role in that game.

4. Reduced Injuries and Fatigue:  This option is identical to the above option except that the duration of A.I.M. injuries has been somewhat reduced."



-----Original Message-----
From: Chris Strovel (Harpers Ferry Federal Armory) <strovel@...>
To: ASSL <ASSL@groups.io>
Sent: Thu, Jul 25, 2019 10:01 am
Subject: Re: [ASSL] ASSL '80: Poll on Injury Settings #poll

Just a note as you head out to the polls today -- Option 2, 'Game Injuries and Fatigue,' represents almost no change from our current settings. It only eliminates AIM overuse injuries, which are rare. And, reading the help files, it appears the 'Reduced' injuries setting only applies to AIM injuries, and not to in-game injuries. Under that reading, Option 1 is not much of a change. Here is that Help language:
  • All Injuries and Fatigue - this option acts just like the above option plus fatigued players (Tired, Bushed or Worn-out) who appear in games are subject to AIM injuries. These injuries do not appear in the game script or the boxscore but show up on the team status report after the game. These injuries can be a significant length and the length of the injuries are directly related to the level of overuse a player has received.
  • Reduced Injuries and Fatigue - this option is identical to the above option except that the duration of AIM injuries has been somewhat reduced.
So it looks like neither of the first two options will do much to change the current setup.


==
On July 25, 2019 at 9:14 AM "Steven Galbraith via Groups.Io" <stevemgalbraith@...> wrote:

A new poll has been created:

We'll vote now on which specific injury settings to use. These changes will go into effect immediately and will be the setting for all future seasons pending any vote to change them again. Whichever setting receives the most votes will be the one we use. It does not require a majority of owners, i.e., 10.
In case of a tie we'll have another poll on just those settings. If it's a three way tie (not likely) we'll worry about that later.
1. Change to "Reduced Injuries and Fatigue"
2. Change to "Game Injuries and Fatigue"
3. Change to "Fatigue Only."

Re: Waterloo vs Seltzer

Umpy
 

Waterloo took the first two games as they silenced the Seltzer bats. (not very hard to do)  Seltzer took game 3 in 10 innings by a 1-0 score.  Seltzer won in 12 innings in game 4.  Seltzer won the finale to take 3 of 5.  

On July 25, 2019 at 9:05 AM "Steven Galbraith via Groups.Io" <stevemgalbraith@...> wrote:

Week/series #7 play c-file. Results due Tuesday night.

Note: Injury settings remain the same. We'll need to vote next on which reduced settings we'll have. More no that to follow.

locked Re: ASSL '80: Poll on Injury Settings #poll

Thomas Battiato
 

No, they have no effect on fatigue, only injuries.


-----Original Message-----
From: John Anderson via Groups.Io <andjohn1961@...>
To: ASSL <ASSL@groups.io>
Sent: Thu, Jul 25, 2019 9:54 pm
Subject: Re: [ASSL] ASSL '80: Poll on Injury Settings #poll

Do any of these settings change how SF and PR are calculated for players?

John Anderson 


On Jul 25, 2019, at 6:59 PM, Thomas Battiato via Groups.Io <Dodger300@...> wrote:

After reading Chris's note, I searched the help file and saw that he is correct - "Game injuies Enabled" is really no change at all! I had assumed it meant only for the duration of the current game and the injury didn't carry forward, but I was wrong. 

He is correct that anything other than"Fatigue Only" will not make ardly any change to the injury situation, so I changed my vote to "Fatigue Only." If you want to eliminate injuries, that is the only choice that will do so.

Thank you, Chris, for educating me that voting for the other two negates our earlier vote to eliminate injuries.  

Here is the complete description of all four categories from the Help file, with 'Game Injuries Enabled" highlighted to sow that it doesn't reduce injuries at all!


"There are four levels of A.I.M. interaction with League Manager and Baseball:

1. Fatigue only: A.I.M. will report the current status of a player, and will modify the player's abilities based upon his usage under fatigued status conditions.  However, no injuries that occur in games or that might result from over-use in A.I.M. terms will be enforced upon a player for subsequent games.

2. Game injuries enabled: In addition to maintaining fatigue status effects, injuries that occur due to rare plays during the course of a game will be enforced on players for the length of time in days that injury is scheduled to run.

3. All injuries enabled: In addition to the above, A.I.M. will often assess injuries against players who participate in a game while fatigued.  That is, players who are Tired, Bushed, or Worn out may become injured after a game if they appear in an active role in that game.

4. Reduced Injuries and Fatigue:  This option is identical to the above option except that the duration of A.I.M. injuries has been somewhat reduced."



-----Original Message-----
From: Chris Strovel (Harpers Ferry Federal Armory) <strovel@...>
To: ASSL <ASSL@groups.io>
Sent: Thu, Jul 25, 2019 10:01 am
Subject: Re: [ASSL] ASSL '80: Poll on Injury Settings #poll

Just a note as you head out to the polls today -- Option 2, 'Game Injuries and Fatigue,' represents almost no change from our current settings. It only eliminates AIM overuse injuries, which are rare. And, reading the help files, it appears the 'Reduced' injuries setting only applies to AIM injuries, and not to in-game injuries. Under that reading, Option 1 is not much of a change. Here is that Help language:
  • All Injuries and Fatigue - this option acts just like the above option plus fatigued players (Tired, Bushed or Worn-out) who appear in games are subject to AIM injuries. These injuries do not appear in the game script or the boxscore but show up on the team status report after the game. These injuries can be a significant length and the length of the injuries are directly related to the level of overuse a player has received.
  • Reduced Injuries and Fatigue - this option is identical to the above option except that the duration of AIM injuries has been somewhat reduced.
So it looks like neither of the first two options will do much to change the current setup.


==
On July 25, 2019 at 9:14 AM "Steven Galbraith via Groups.Io" <stevemgalbraith@...> wrote:

A new poll has been created:

We'll vote now on which specific injury settings to use. These changes will go into effect immediately and will be the setting for all future seasons pending any vote to change them again. Whichever setting receives the most votes will be the one we use. It does not require a majority of owners, i.e., 10.
In case of a tie we'll have another poll on just those settings. If it's a three way tie (not likely) we'll worry about that later.
1. Change to "Reduced Injuries and Fatigue"
2. Change to "Game Injuries and Fatigue"
3. Change to "Fatigue Only."

Hamilton at Mt. Lebanon

Steve Alvin
 

The Terriers are the big dogs as they took 3 from the Bulldogs.

Steve

ASSL '80: Series #7 - Cucamonga at Mudville

Kevin McNally
 

Mudville  4,  Cucamonga  3  -  11 Innings

Coconuts score 3 in the 9th to tie (Mayberry 3-run HR)

Meyer drives in Murray for the game winner

Oliver 2 hits, 2B, 2 BB, RS, 2 RBI

Carlton 10 IP, 5 H, 3 ER, 1 BB, 8 K

 

Mudville  4,  Cucamonga  3  -  10 Innings

Hernandez Sac Fly scores Bumbry for the Nine victory

Hernandez 2B, BB, 3 RBI

Bumbry 2 hits, SB, BB, 2 RS

Rivers 2 hits, 2B, 3B, RBI in the loss

 

Mudville  9,  Cucamonga  5

White 3-run 2B

Hernandez 2 hits, BB, RS, RBI

Carter H, 2 BB, 2 RS

Niekro CG, 7 H, 5 ER, 3 BB, 5 K

Brookens 2-run HR in the loss

 

Cucamonga  7,  Mudville  2

Mayberry 4 hits, 2B, 2 HR, 3 RS, 4 RBI

Gantner 2-run 2B

Perry 8 IP, 7 H, 2 ER, 3 BB, 7 K

 

Cucamonga  9,  Mudville  3

Coconuts plate 8 in the 2nd off JR

Rivers H, RS, 3 RBI

Thomas HR, 2 BB, 2 RS, 2 RBI

Dilone 3 hits, SB, RS, RBI

Brookens 2 hits, 2 RS, RBI

Abbott 8 IP, 8 H, 3 ER, 2 BB, 3 K

 

The Nine are ready for the next series.

 

Thanks,

Kevin

 

 

Re: ASSL '80: Week/Series #7 Play File Cascade and Bayou city results

Duane Webster
 



  Thanks Duane


From: ASSL@groups.io <ASSL@groups.io> on behalf of Steven Galbraith via Groups.Io <stevemgalbraith@...>
Sent: Thursday, July 25, 2019 6:05 AM
To: ASSL@groups.io <ASSL@groups.io>
Subject: [ASSL] ASSL '80: Week/Series #7 Play File
 
Week/series #7 play c-file. Results due Tuesday night.

Note: Injury settings remain the same. We'll need to vote next on which reduced settings we'll have. More no that to follow.

ASSL - Melonville at Spokane

mlassman2001
 

Melonville takes 3 of 5 from Spokane.

Mike

ASSL '80: Week/Series #7: Cut & Shoot at Silver City

JOHN CAMPBELL
 

Gunslingers win series 3-2

Thanks John

On Thursday, July 25, 2019, 8:05:42 AM CDT, Steven Galbraith via Groups.Io <stevemgalbraith@...> wrote:


Week/series #7 play c-file. Results due Tuesday night.

Note: Injury settings remain the same. We'll need to vote next on which reduced settings we'll have. More no that to follow.

ASSL '80 -- Valdosta at Czech

Art Widiger
 

The Czech Bouncers lose 3 out of 5 to the Valdosta Crackers.

Art


-----Original Message-----
From: Steven Galbraith via Groups.Io <stevemgalbraith@...>
To: ASSL <ASSL@groups.io>
Sent: Thu, Jul 25, 2019 8:05 am
Subject: [ASSL] ASSL '80: Week/Series #7 Play File

Week/series #7 play c-file. Results due Tuesday night.

Note: Injury settings remain the same. We'll need to vote next on which reduced settings we'll have. More no that to follow.

ASSL '80: Week/Series #7 Results

Steven Galbraith
 


Week/series #7 results. F-files/changes due Friday night.

ASSL '80: Poll on Injury Settings: Please Vote

Steven Galbraith
 



If you haven't voted on the poll on which injury settings to apply, please do so. I'm going to keep it open for another few days. It's a very close votes so I want everyone to add his voice/vote.

Re: ASSL '80: Week/Series #7 Results

Scott Clark
 

Melonville is good to go.



From: ASSL@groups.io <ASSL@groups.io> on behalf of Steven Galbraith via Groups.Io <stevemgalbraith@...>
Sent: July 31, 2019 12:38 PM
To: ASSL@groups.io <ASSL@groups.io>
Subject: [ASSL] ASSL '80: Week/Series #7 Results
 

Week/series #7 results. F-files/changes due Friday night.

Re: ASSL '80: Week/Series #7 Results

Mike Eliyas
 

Here is a new file for the POlish


-----Original Message-----
From: Steven Galbraith via Groups.Io <stevemgalbraith@...>
To: ASSL <ASSL@groups.io>
Sent: Wed, Jul 31, 2019 9:38 am
Subject: [ASSL] ASSL '80: Week/Series #7 Results


Week/series #7 results. F-files/changes due Friday night.