Jim

Members
  • Content count

    35
  • Joined

  • Last visited

Community Reputation

14 Good

About Jim

  • Rank
    Experienced Member

Extra Life

Profile Fields

  • Location
    Chicago

Contact Methods

  • Twitter
    @jameswbutts

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Enable
  1. Jim

    Chicago Nerdery 2017

    Check out our full write up here!
  2. Jim

    What happens at the Events ?

    @BowieMoonen you can read what we did at ours: https://www.facebook.com/notes/jim-butts/extra-life-wrap-up-2017-chicago-nerdery/10100508101971858/
  3. Jim

    2017 Team Recap

    2017 was the second year that my wife and I coordinated Extra Life. We learned a lot from both events and are happy to share our details below: 2017: https://www.facebook.com/notes/jim-butts/extra-life-wrap-up-2017-chicago-nerdery/10100508101971858/ 2016: https://www.facebook.com/notes/jim-butts/extra-life-wrap-up-2016-chicago-nerdery/10100267867473718/ Feel free to post feedback and also share your stories!
  4. Jim

    Historic Data

    Agree, historic data would be great.
  5. Updated again for the most recent JSON changes, namely pagination.
  6. Thanks for the input @KnightHarbinger! I don't anticipate having that for this year's event, but I will add it to our list of considerations. I hope to revisit it after some changes to JSON from Extra Life are available. Keep in touch!
  7. Great, thank you @LeaveIt2Beaver!
  8. Update I've had a few people ask, so I'll mention here as well: The Team Dashboard is updated and working for 2017. Enjoy!
  9. @DJThunderstix @LeaveIt2Beaver @herobyclicking, I've created a dashboard for teams to display rosters and donations: http://nerdery.life It would be very helpful to have the hospital included in each participant's JSON response. My hope is that since it's not requesting more info from members that it could be added without any additional action for players. Thanks for your consideration!
  10. @KnightHarbinger Thank you so much!
  11. We have a quick-fix in place to make it work with 2017 data. No other changes from last year's version at this time.
  12. A quick-fix is in place so that it will now work with 2017 data. Thanks!
  13. That's correct. We need to update it to work with 2017 data. We were looking for feedback as we get back into the code. I'll update here when it's working with the new data. Thanks!
  14. If anyone found this particularly useful last year, please message me! We'd love to follow up with you. Thanks!
  15. @Lammy No plans to take it down soon. Good luck!