Jump to content


Photo

Player Acquired Setup


3 replies to this topic

#1 quickdraw3457

quickdraw3457

    Veteran

  • Members
  • PipPipPip
  • 33 posts

Posted 29 August 2019 - 05:54 AM

My league sets keeper value based on the draft round of a player, so the acquired column on the roster page is very important to our league. Every year though, I have to manually update this after the draft as commissioner. There is a setting that I have checked:

Reset Automatic Player Acquired Info:  When player is drafted 
 When player is kept in lieu of a draft pick

But it still stays as the round the player was at last year. Why? This is a really tedious process to update and I don't understand why this isn't resetting the player acquired info to our current draft results.



#2 bonscott

bonscott

    Veteran

  • Members
  • PipPipPip
  • 7,857 posts
  • Gender:Male

Posted 29 August 2019 - 07:01 AM

Not sure, I'd suggest a ticket.  Personally I have it wipe all the acquired info each season and start fresh.  I keep nothing going forward.

 

I have a similar keeper system where we assign a contract (which I rename to "Keeper Number" or KN) equal to the round they were drafted.  This number reduces by a certain amount per year kept (4 for us as a full IDP league).  This KN is thus the round you give up when kept.  So if I drafted Cam Newton in the 18th round this year I can keep him for a 14th next year, 10 the year after and so forth until I feel he's not worth it anymore.

 

So what I do to fill this in is I change the default contract for each round in the draft.  Start with 1 for the 1st round, then change to 2 for the 2nd round and so forth.  This will automatically fill in the contract/KN field with the number of the drafted round.  A bit of manual work but way less work then manually entering it for 28 round worth of 12 teams.  :)   Then next year I simply use the field to reduce by 4 and click a button and it automatically changes all the contracts for all the players.  The round drafted acquired field helps me make sure I didn't make a mistake but otherwise is just a "for fluff" field since you can't do anything automatic to it I don't use it for anything important.

 

The other thing I'll do with the field is when keepers are in I'll change the field to "Keep" for the keepers and wipe out the info for any player not kept.  Then going forward that year it will get either a draft pick or other designation (such as Trade or FCFS or BB Waiv) depending how the player was acquired. But in all cases that important contract/KN stays the same and follows the player around no matter what happens to him.

 

Just giving insight into how I handle it.  That may not work for you.



 


#3 quickdraw3457

quickdraw3457

    Veteran

  • Members
  • PipPipPip
  • 33 posts

Posted 29 August 2019 - 07:24 AM

Thanks for the response, sounds like we have somewhat similar rules but I can't wipe the info from the previous year because it's needed all offseason to determine someone's keeper round/value (which is important when trying to trade in offseason). I'll submit a ticket.



#4 bonscott

bonscott

    Veteran

  • Members
  • PipPipPip
  • 7,857 posts
  • Gender:Male

Posted 29 August 2019 - 11:38 AM

Thanks for the response, sounds like we have somewhat similar rules but I can't wipe the info from the previous year because it's needed all offseason to determine someone's keeper round/value (which is important when trying to trade in offseason). I'll submit a ticket.

 

FYI, that's what the contract/KN is for (how I use it).  If a player has a contract/KN of 8, that means if kept it costs an 8th round pick.

 

So when I upgrade to the new season (usually April), I transfer all rosters, decrease all contracts/KN by 4 and drop any unkeepable players.  So for the whole off season they can trade, etc. and will know exactly what the cost is in terms of round value.   That way I'm only counting on a field that is tracked year to year and has automated abilities (reducing in this case).  The Acquired field is a nice to have but I'm not counting on a field that can be wiped or modified so many different ways.



 




Reply to this topic



  


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users