@JNH and @Mike Izzy  I appreciate it. Good points and suggestions - I do like the idea of an [updated] update template to incorporate in the "new player package", so to speak. It might help a little bit to blow the dust off the "My First PT!" template and re-visit just how useful a learning tool it is.

Updating template is a great idea.. although I feel like it shouldn't be complusory .Just provided for use. 
Especially if an updater just posts it in every new players update thread saying. Hey if you don't have a system you like better. Try use this. 

I think on thing I would say is, I got a really good update from someone at the start of this last season. I made a rookie mistake in understanding the update scale and they were really cool and updated me with some modifications to the numbers. I was able to learn from that and appreciated the help. So if someone is trying and has been fairly good, and makes a mistake, I feel like forgiveness and guidance is good not just, sorry can't update you .

Yup, I don't think a straight update is the answer. I forget who it was, but I made a mistake near playoffs this season and they rejected my update while @'ing me and letting me know what the issue was. I corrected it, PM'ed them and they were able to adjust the update. Easy process on both ends.

I don't think people should be expected to be perfect, nor do should the updaters have to be doing people's math and updates for them. A form as mentioned earlier would be a good step towards minimizing the errors and standardizing the process.

    -             -     

I've been working on a really simple bit of python code to format updates consistently. Ever since I had a 70 TPE update with equipment and realised that it must've been a pain to update.

I tried writing a utility in Python to help with updating, people hate downloading stuff :(

Cal Juice
Tomas Zadina
Brady McIntyre

I've been working on a really simple bit of python code to format updates consistently. Ever since I had a 70 TPE update with equipment and realised that it must've been a pain to update.

I tried writing a utility in Python to help with updating, people hate downloading stuff :(

Yeah that's the problem I anticipated. It might stay as something I use to help myself update forever...

Thanks to @Carpy48 , @sköldpaddor, @Weretarantula, @Bruins10  and @Wasty  for sigs
Extra special thanks to @Julio Tokolosh for the sick gif one



Tony Ford || D || Anchorage Armada || Los Angeles Panthers || 423 TPE
Name:Tony Ford
Age: 18
Height: 6' 3"
Weight: 200
Number: 47
Hometown: Cambridge, UK
------------------------------------
SMJHL Career Statistics
S46 ANC - GP: 50, G: 3, A: 7, +/-: -4, PIMs: 28, H: 43, S: 32, SB: 51
S47 ANC - GP:50, G: 11, A: 19, +/-: -21, PIMs: 50, H: 59, S: 76, SB: 65
S48 ANC - GP:50, G: 10, A: 30, +/-: 1, PIMs: 26, H: 54, S: 100, SB: 56
------------------------------------

SMJHL Playoff Statistics
S46 ANC - GP: 11, G: 2, A: 1, +/-: 2, PIMs: 10, H: 12, S: 6, SB: 12
S48 ANC* - GP: 4, G: 1, A: 3, +/-: -4, PIMs: 6, H: 4, S: 8, SB: 4
S49 ANC* - GP: 11, G: 4, A: 7, +/-: -5, PIMs: 12, H: 14, S: 17, SB: 13
An Asterisk denotes team's leading point scorer in that period
------------------------------------
SHL Career Statistics
S47 LAP - GP: 2, G: 0, A: 0, +/-: 0, PIMs: 0, H: 1, SB: 0
------------------------------------

Career Milestones
S46: Drafted 6th overall by Anchorage Armada in the SMJHL Entry Draft
S47: Drafted 6th overall (again) by West Kendall Platoon in the SHL Entry Draft
S47: Traded by WKP to LAP
------------------------------------------------------------

Thanks for the productive discussion, guys. This makes me feel much better about the state of updating heading into next season.

Having some updating consistency or assigned teams would go a long way in addressing these issues. Is there a reason we moved away from the assigned team model? Pardon my ignorance, I’ve never been behind the scenes on the updating side of things. It’s a new updater every week it seems like now.

RIP Dangel. See you on the other side, brother

Having some updating consistency or assigned teams would go a long way in addressing these issues. Is there a reason we moved away from the assigned team model? Pardon my ignorance, I’ve never been behind the scenes on the updating side of things. It’s a new updater every week it seems like now.

It was new to me when I re-entered the league. A little weird at first, but this allows the more dedicated members to get multiple teams finished, and I've enjoyed the change for the most part.

Having some updating consistency or assigned teams would go a long way in addressing these issues. Is there a reason we moved away from the assigned team model? Pardon my ignorance, I’ve never been behind the scenes on the updating side of things. It’s a new updater every week it seems like now.

Aside from what Gcool already stated, it makes it so if an updater has something happen and are unavailable for a weekend, teams aren't left in limbo of unclaimable status. Not every updater has the same amount of time to dedicate to the task each week and not every week is equal in terms of updating a team easily. This past weekend had Regressions, Equipment purchases, Call-ups, and many people who only update monthly or seasonly coming out of the woodwork. I would say on average teams that would take me 1 hour to get through normally, took 2-3+ hours this week. That's not to talk about the variance in a team with 13 beefy updates versus a team with 3 updates of just AC and Training.

Part of the current delay is that an updater can only claim 2-3 teams on Saturday for 24 hours at noon. Then on Sunday at noon there is no limit. That is when some of the more active updaters return to help finish off whatever teams are remaining. I believe the intent of this rule is to allow all updaters a chance to update regardless of if they are available at noon on Saturday or say 9 pm for example.

     

- Dilligent users sometimes make mistakes
- Humans in general make mistakes
- Some here are too lazy/don't feel like to check for their mistakes or ask for someone to double check
- Some still don't completely understand the updating format and process
- Math is hard

I think these are the main 5 problems and there isn't necessarily something updating can do about it unless we automate the process of adding TPE to players or have some kind of form (e.g. you put link/tpe earned from that task/stats adjusted/tpe cap into a form and it spits out a formatted update).  Then potentially we could just have the human side of things double checking that they entered the right amount.  Under these conditions, I see absolutely no reason why anyone could be upset their update was rejected because they'd have had every chance to make sure it was correct.  Sure an honest error or two may happen but it could be a step in the right direction.

I don't feel like the issue is with updating or anything you can do, I think you've done a great job directing the team and the updaters themselves have done great with updating, finding errors, notifying players and helping make changes.

Sums up my thoughts well. For me, it's usually number five, even as someone who is very particular about making the formatting as clear and pain-free as possible, I just sometimes suck at adding. And when I'm wrong, the updater tells me and I say, "Yep, I still suck at math."

I like the dialogue but at the end of the day you can't fix me being bad at math even as a well-intentioned end user.

Zach Evans[/b] | Player Page | Update Page
Nikolai Evans | Player Page | Update Page
Zach Evans || Forward || Winnipeg Jets
Name: Zach Evans
Height: 6'1"
Weight: 195 lbs
Number: 18
------------------------------------------------------------
SHL Career Statistics:
S32 (WPG): GP: 50, G: 9, A: 5, P: 14, +/-: -1, PIMS: 12, H: 59
S33 (WPG): GP: 50, G: 8, A: 15, P: 23, +/-: 3, PIMS: 49, H: 106
S34 (WPG): GP: 50, G: 14, A: 14, P: 28, +/-: 7, PIMS: 46, H: 96
S35 (WPG): GP: 50, G: 22, A: 26, P: 48, +/-: -4, PIMS: 23, H: 113
S36 (WPG): GP: 50, G: 28, A: 30, P: 58, +/-: 23, PIMS: 51, H: 140
S37 (WPG): GP: 50, G: 24, A: 27, P: 51, +/-: 2, PIMS: 36, H: 220
S38 (WPG): GP: 50, G: 27. A: 38, P: 65, +/-: 12, PIMS: 45, H: 158
S39 (WPG): GP: 50, G: 15, A: 32, P: 47, +/-: 11, PIMS: 43, H: 85
S40 (WPG): GP: 50, G: 22, A: 31, P: 53, +/-: 11, PIMS: 15, H: 49
S41 (WPG): GP: 50, G: 27, A: 35, P: 62, +/-: 26, PIMS: 34, H: 82
S42 (WPG): GP: 50, G: 16, A: 29, P: 45, +/-: -3, PIMS: 15, H: 6
S43 (WPG): GP: 50, G: 16, A: 29, P: 45, +/-: 11, PIMS: 27, H: 15
S44 (WPG): GP: 50, G: 14, A: 31, P: 45, +/-: 3, PIMS: 17, H: 17
S45 (WPG): GP: 50, G: 15, A: 34, P: 49, +/-: 4, PIMS: 2, H: 27
CAREER: GP: 700, G: 257, A: 376, P: 633, +/-: 105, PIMS: 415, H: 1,173
------------------------------------------------------------
SHL Playoff Statistics:
S34 (WPG): GP: 5, G: 2, A: 1, P: 3, +/-: 0, PIMS: 4, H: 7
S36 (WPG): GP: 6, G: 0, A: 3, P: 3, +/-: -1, PIMS: 0, H: 16
S37 (WPG): GP: 18, G: 11, A: 14, P: 25, +/-: 19, PIMS: 12, H: 81
S38 (WPG): GP: 13, G: 6, A: 9, P: 15, +/-: 5, PIMS: 4, H: 32
S39 (WPG): GP: 13, G: 5, A: 6, P: 11, +/-: -2, PIMS: 6, H: 31
S40 (WPG): GP: 14, G: 5, A: 4, P: 9, +/-: 1, PIMS: 13, H: 7
S41 (WPG): GP: 13, G: 8, A: 6, P: 14, +/-: 3, PIMS: 9, H: 26
S43 (WPG): GP: 17, G: 4, A: 9, P: 13, +/-: 11, PIMS: 2, H: 4
S44 (WPG): GP: 18, G: 4, A: 15, P: 19, +/-: 7, PIMS: 0, H: 3
S45 (WPG): GP: 4, G: 1, A: 2, P: 3, +/-: -1, PIMS: 0, H: 2
CAREER: GP: 121, G: 46, A: 69, P: 115, +/-: 41, PIMS: 50, H: 209
------------------------------------------------------------
SMJHL Career Statistics:
S30 (DET): GP: 50, G: 16, A: 12, P: 28, +/-: 8, PIMS: 10, H: 44
S31 (DET): GP: 50, G: 15, A: 23, P: 38, +/-: -2, PIMS: 35, H: 84
CAREER: GP: 100, G: 31, A: 35, P: 66, +/-: 6, PIMS: 45, H: 128
------------------------------------------------------------
SMJHL Playoff Statistics:
S30 (DET): GP: 5, G: 0, A: 1, P: 1, +/-: -1, PIMS: 2, H: 0
S31 (DET): GP: 13, G: 5, A: 7, P: 12, +/-: 3, PIMS: 0, H: 9
CAREER: GP: 18, G: 5, A: 8, P: 13, +/-: 2, PIMS: 2, H: 9
------------------------------------------------------------
IIHF Statistics (Russia):
S30: GP: 11, G: 1, A: 0, P: 1, +/-: -1, PIMS: 0, H: 7
S32: GP: 13, G: 1, A: 1, P: 2, +/-: -4, PIMS: 4, H: 17
S33: GP: 11, G: 3, A: 6, P: 9, +/-: 5, PIMS: 4, H: 12
S34: GP: 11, G: 6, A: 2, P: 8, +/-: 2, PIMS: 2, H: 10
S35: GP: 13, G: 5, A: 4, P: 9, +/-: 4, PIMS: 18, H: 22
S36: GP: 11, G: 4, A: 3, P: 7, +/-: -3, PIMS: 2, H: 5
S37: GP: 10, G: 1, A: 1, P: 2, +/-: 0, PIMS: 0, H: 8
S38: GP: 13, G: 3, A: 10, P: 13, +/-: 8, PIMS: 4, H: 5
S39: GP: 10, G: 6, A: 6, P: 12, +/-: 1, PIMS: 2, H: 11
S40: GP: 10, G: 1, A: 2, P: 3, +/-: -6, PIMS: 2, H: 8
S41: GP: 11, G: 4, A: 5, P: 9, +/-: 0, PIMS: 2, H: 7
S42: GP: 10, G: 5, A: 9, P: 14, +/-: 5, PIMS: 0, H: 1
S43: GP: 13, G: 4, A: 7, P: 11, +/-: 6, PIMS: 0, H: 0
S44: GP: 10, G: 4, A: 8, P: 12, +/-: 1, PIMS: 0, H: 0
S45: GP: 10, G: 6, A: 1, P: 7, +/-: -13, PIMS: 0, H: 2
CAREER: GP: 167 G: 54, A: 65, P: 119, +/-: 5, PIMS: 40, H: 105
------------------------------------------------------------
Transactions and Awards:
Drafted 25th overall by Detroit, S30 SMJHL Entry Draft
S30 Vyacheslav Onoprienko Trophy Winner
Drafted 5th overall by Winnipeg, S31 SHL Entry Draft
S32 Oriens Trophy Winner (Co-GM, Detroit)
S32 IIHF Bronze Medalist
S36 SHL Second-Team All-Star
S37 Challenge Cup Champion
S38 Sergei Karpotsov Trophy Winner
S38 SHL First-Team All-Star
S38 Sarmad Khan Trophy Winner
S38 Jeff Dar Trophy Winner
S38 Damian Littleton Trophy Winner
S38 IIHF Gold Medalist
S43 IIHF Silver Medalist
S44 Challenge Cup Champion
Inducted into SHL Hall of Fame, S47
------------------------------------------------------------
Two things are infinite.

Nikolai Evans || Defenseman || HAM/TBB/TEX
Name: Nikolai Evans
Height: 6'2"
Weight: 210 lbs
Number: 19
------------------------------------------------------------
SHL Career Statistics:
S47 (HAM): GP: 50, G: 1, A: 10, P: 11, +/-: -4, SB: 39, H: 32
S48 (HAM): GP: 50, G: 5, A: 9, P: 14, +/1: 6, SB: 57, H: 37
S49 (TBB): GP: 50, G: 9, A: 14, P: 23, +/-: -22, SB: 78, H: 51
S50 (TBB): GP: 50, G: 7, A: 20, P: 27, +/-: 4, SB: 64, H: 39
CAREER: GP: 200, G: 22, A: 53, P: 75, +/-: -16, SB: 238, H: 159
------------------------------------------------------------
SHL Playoff Statistics:
S48 (HAM): GP: 5, G: 1, A: 0, P: 1, +/-: -1, SB: 6, H: 3
S49 (TBB): GP: 12, G: 0, A: 5, P: 5, +/-: 0, SB: 20, H: 8
S50 (TBB): GP: 19, G: 5, A: 7, P: 12, +/-: 1, SB: 29, H: 6
CAREER: GP: 36, G: 6, A: 12, P: 18, +/-: 0, SB: 55, H: 17
------------------------------------------------------------
SMJHL Career Statistics:
S45 (MTL): GP: 50, G: 7, A: 13, P: 20, +/-: -1, SB: 60, H: 25
S46 (MTL/HFX): GP: 50, G: 7, A: 20, P: 27, +/-: -1, SB: 47, H: 68
CAREER: GP: 100, G: 14, A: 33, P: 47, +/-: -2, SB: 107, H: 93
------------------------------------------------------------
SMJHL Playoff Statistics:
S45 (MTL): GP: 6, G: 2, A: 3, P: 5, +/-: -1, SB: 7, H: 4
S46 (HFX): GP: 13, G: 3, A: 2, P: 5, +/-: -4, SB: 18, H: 14
CAREER: GP: 19, G: 5, A: 5, P: 10, +/-: -5, SB: 25, H: 18
------------------------------------------------------------
IIHF Statistics (Russia):
S45: GP: 10, G: 0, A: 1, P: 1, +/-: -5, SB: 12, H: 2
S46: GP: 12, G: 0, A: 1, P: 1, +/-: -2, SB: 11, H: 2
S47: GP: 12, G: 2, A: 7, P: 9, +/-: 2, SB: 17, H: 12
S48: GP: 12, G: 2, A: 4, P: 6, +/-: -6, SB: 22, H: 0
S49: GP: 15, G: 6, A: 6, P: 12, +/-: -6, SB: 25, H: 7
CAREER: GP: 61, G: 10, A: 19, P: 29, +/-: -17, SB: 87, H: 23
------------------------------------------------------------
WJC Statistics:
S44 (World): GP: 15, G: 6, A: 7, P: 13, +/-: 8, SB: 18, H: 13
S45 (Russia): GP: 22, G: 2, A: 10, P: 12, +/-: -13, SB: 33, H: 14
S46 (Russia): GP: 28, G: 9, A: 15, P: 23, +/-: 0, SB: 26, H: 14
CAREER: GP: 55, G: 17, A: 32, P: 48, +/-: -5, SB: 77, H: 41
------------------------------------------------------------
Transactions and Awards:
Drafted 1st overall by Montreal, S45 SMJHL Entry Draft
Drafted 1st overall by Hamilton, S46 SHL Entry Draft
Traded to Halifax Raiders during S46 SMJHL season
Traded to Tampa Bay Barracuda prior to S49 SHL season
S48 Fantasy Global Champion
S50 Mathias Chouinard Trophy Winner
I'll finish updating this at some point
------------------------------------------------------------
The Russian Prince

Zdenko Beranek || Winger || Quebec City Citadelles
Name: Zdenko Beranek
Height: 5'10"
Weight: 175 lbs
Number: 27
------------------------------------------------------------
SMJHL Career Statistics:
S55 (QCC): GP: 50, G: 6, A: 15, P: 21, +/-: -22, PIMS: 6
S56 (QCC): GP: 50, G: 10, A: 27, P: 37, +/-: 9, PIMS: 20
------------------------------------------------------------
Transactions and Awards:
Drafted 1st overall by Quebec City, S55 SMJHL Entry Draft
Drafted 18th overall by Seattle, S56 SHL Entry Draft
------------------------------------------------------------
Le Petite Chèvre

One thing I just learned was that you could use the player build tool to audit your own build

If anyone's unsure, go that route because it's a big help

               

| LD| Chad Nickelback | #24 | Nevada Battleborn
| 5'11 | |195 lbs|
Riverview, New Brunswick
---------------------------------------
Drafted 5th overall in the S64 SHL Entry Draft by the Manhattan Rage
Drafted 7th overall in the S63 SMJHL Entry Draft by the Nevada Battleborn
Selected to play in the S64 SMJHL All-Star Game
---------------------------------------
SMJHL Career Stats
S65: 66GP | 20G | 45A | 65PTS | 16PIM | 306SOG | +/-: +40
S64: 66GP | 20G | 28A | 48PTS | 30PIM | 275SOG | +/-: +1
S63: 66GP | 9G | 27A | 36PTS | 12PIM | 140SOG | +/-: +24

---------------------------------------
SMJHL Career Playoff Stats
S65: 10GP | 3G | 2A | 7 PTS | 0PIM | 31 SOG | +/-: +1 | 11 Hits
S64: 10GP | 2G | 5A | 7PTS | 2PIM | 41SOG | +/-: +2 | 8 Hits
S63: 6GP | 1G | 1A | 2PTS | 0 PIM | 10 SOG | +/-: 0 | 8 Hits

---------------------------------------
WJC Stats
S64 (Team Canada): 0GP | 0G | 0A | 0PTS | 0PIM | 0SOG | +/-: 0 | 0 Hits
S63 (Team NA): 12GP | 2G | 3A | 5PTS | 2 PIM | 29 SOG | +/-: -5 | 14 Hits

- Dilligent users sometimes make mistakes
- Humans in general make mistakes
- Some here are too lazy/don't feel like to check for their mistakes or ask for someone to double check
- Some still don't completely understand the updating format and process
- Math is hard

I think these are the main 5 problems and there isn't necessarily something updating can do about it unless we automate the process of adding TPE to players or have some kind of form (e.g. you put link/tpe earned from that task/stats adjusted/tpe cap into a form and it spits out a formatted update).  Then potentially we could just have the human side of things double checking that they entered the right amount.  Under these conditions, I see absolutely no reason why anyone could be upset their update was rejected because they'd have had every chance to make sure it was correct.  Sure an honest error or two may happen but it could be a step in the right direction.

I don't feel like the issue is with updating or anything you can do, I think you've done a great job directing the team and the updaters themselves have done great with updating, finding errors, notifying players and helping make changes.

Sums up my thoughts well. For me, it's usually number five, even as someone who is very particular about making the formatting as clear and pain-free as possible, I just sometimes suck at adding. And when I'm wrong, the updater tells me and I say, "Yep, I still suck at math."

I like the dialogue but at the end of the day you can't fix me being bad at math even as a well-intentioned end user.

Yeah ideally this is where an automated form would be nice. You could just put in the link for your season predictions and say you got 3 capped & 3 uncapped. It'll tally this up & add it to your S47 PT Cap. Then you say you want X TPE to go into checking and what your checking starting value is, and it spits out

Code:

[URL=link]Season Predictions - 3 Capped 3 Uncapped[/URL]

Points Added: 6
TPE: 412
Stats Adjusted:
Checking 40 --> 46

S47 PT Cap: 3/40

Or something along those lines. It wouldn't have to be mandatory, but for those that find updating hard it can streamline the process. Input link, input capped, input uncapped, check which season's cap the capped are for, say where you want them to go and starting value and it'll spit it out for you to copy & paste. It'd be hard to use for like regression/equipment/some other stuff but minimizes the math as much as possible, more just data entry and let the form add and subtract.

If I had even a little knowledge of how to do this I'd try, but I have none.

    -             -     

Sums up my thoughts well. For me, it's usually number five, even as someone who is very particular about making the formatting as clear and pain-free as possible, I just sometimes suck at adding. And when I'm wrong, the updater tells me and I say, "Yep, I still suck at math."

I like the dialogue but at the end of the day you can't fix me being bad at math even as a well-intentioned end user.

Yeah ideally this is where an automated form would be nice.  You could just put in the link for your season predictions and say you got 3 capped & 3 uncapped.  It'll tally this up & add it to your S47 PT Cap.  Then you say you want X TPE to go into checking and what your checking starting value is, and it spits out

Code:

[URL=link]Season Predictions - 3 Capped 3 Uncapped[/URL]

Points Added: 6
TPE: 412
Stats Adjusted:
Checking 40 --> 46

S47 PT Cap: 3/40

Or something along those lines.  It wouldn't have to be mandatory, but for those that find updating hard it can streamline the process.  Input link, input capped, input uncapped, check which season's cap the capped are for, say where you want them to go and starting value and it'll spit it out for you to copy & paste.  It'd be hard to use for like regression/equipment/some other stuff but minimizes the math as much as possible, more just data entry and let the form add and subtract.

If I had even a little knowledge of how to do this I'd try, but I have none.

I do it like:

+6 (3 capped) [URL=link]Season Predictions[/ url]

Stats Adjusted:
+6 Checking: 40 -> 43 (because everyone's weakness is CK and it's sad as hell to me)
S47 PT Cap: 3/40

Yeah ideally this is where an automated form would be nice.  You could just put in the link for your season predictions and say you got 3 capped & 3 uncapped.  It'll tally this up & add it to your S47 PT Cap.  Then you say you want X TPE to go into checking and what your checking starting value is, and it spits out

Code:

[URL=link]Season Predictions - 3 Capped 3 Uncapped[/URL]

Points Added: 6
TPE: 412
Stats Adjusted:
Checking 40 --> 46

S47 PT Cap: 3/40

Or something along those lines.  It wouldn't have to be mandatory, but for those that find updating hard it can streamline the process.  Input link, input capped, input uncapped, check which season's cap the capped are for, say where you want them to go and starting value and it'll spit it out for you to copy & paste.  It'd be hard to use for like regression/equipment/some other stuff but minimizes the math as much as possible, more just data entry and let the form add and subtract.

If I had even a little knowledge of how to do this I'd try, but I have none.

I do it like:

+6 (3 capped) [URL=link]Season Predictions[/  url]

Stats Adjusted:
+6 Checking: 40 -> 43 (because everyone's weakness is CK and it's sad as hell to me)
S47 PT Cap: 3/40

That's fine too, I just wanted an example of how it would spit out a template for copy and pasting purposes.

    -             -     

loosely related, can we simplify equipment? Every time i get an idea to do something, i roll my eyes at the idea having to handle that. Banked points that go specifically to an attribute, multiple purchases, multiple tiers.

loosely related, can we simplify equipment? Every time i get an idea to do something, i roll my eyes at the idea having to handle that. Banked points that go specifically to an attribute, multiple purchases, multiple tiers.

I like what the GOMHL did with equipment a few seasons ago.

loosely related, can we simplify equipment? Every time i get an idea to do something, i roll my eyes at the idea having to handle that. Banked points that go specifically to an attribute, multiple purchases, multiple tiers.

How would we simplify it?

Equipment's a bit of a cunt but I'm just not sure how we could make it easier to deal with. Need with more brain cells than myself to knock it down.

    -             -